]>
Commit | Line | Data |
---|---|---|
267d502e | 1 | =================================================== |
643fea24 | 2 | Code to include the muon information in the |
3 | creation of the standard AOD from the ESD | |
4 | Roberta ARNALDI, Enrico SCOMPARIN Torino | |
28d9f4b3 | 5 | --------------------------------------------------------------- |
6 | ||
643fea24 | 7 | The following filter is used in the official analysis train, in order to copy the muon information from the ESD to the standard AOD. |
8 | ||
9 | 1) AliAnalysisTaskESDMuonFilter.h --> analysis task to copy the muon information from the ESD to the standard AOD | |
10 | 2) AliAnalysisTaskESDMuonFilter.cxx --> analysis task to copy the muon information from the ESD to the standard AOD | |
11 | ||
12 | In order to test locally the analysis train from the ESD to the Standard AOD production, the following macro is provided | |
13 | ||
14 | 1) AnalysisTrainMuonLocal.C | |
15 | - The input file is the ESD | |
16 | - The outputs are the standard AOD and the AOD tag file | |
17 | ||
18 | =================================================== | |
19 | Creation of the MUON-AOD from the standard AOD | |
20 | Roberta ARNALDI, Enrico SCOMPARIN Torino | |
21 | --------------------------------------------------------------- | |
22 | ||
23 | Code to produce a muon-AOD, i.e. a replica of the standard AOD containing only events where | |
24 | at least one muon in the dimuon spectrometer is present | |
25 | ||
26 | 1) AnalysisTrainFromStandardToMuonAODLocal.C --> macro to produce the MUON-AOD (it runs locally) | |
27 | 2) AliAnalysisTaskFromStandardToMuonAOD.h --> analysis task to replicate the AOD content for interesting events | |
28 | 3) AliAnalysisTaskFromStandardToMuonAOD.cxx --> analysis task to replicate the AOD content for interesting events | |
29 | ||
30 | - The input files are the standard AOD and the AOD tag file. | |
31 | The AOD tag file can be created in the previous step from ESD to Standard AOD, using AnalysisTrainMuonLocal.C, or it can be | |
32 | produced on the fly with this macro. | |
33 | - Events containing at least one muon in the muon spectrometer can be selected using the AOD tag files. | |
34 | - The contents of the MUON-AOD can be defined by the user in the AnalysisTrainFromStandardToMuonAODLocal.C | |
35 | macro with some settings as | |
36 | SetNeedsTracksBranchReplication(), SetNeedsVerticesBranchReplication() | |
37 | (defined in STEER/AliAODHandler.h)... | |
28d9f4b3 | 38 | |
267d502e | 39 | =================================================== |
40 | Calculation of the LUT | |
41 | Bogdan VULPESCU, Clermont | |
28d9f4b3 | 42 | --------------------------------------------------------------- |
39280342 | 43 | Analysis task for the calculation of the Look-up-Tables used by the MUON |
44 | trigger algorithm | |
45 | ||
46 | Purpose: extract from ESD files track information (ESD track parameters and | |
47 | matched local trigger decisions) and store in TNtuple; the ntuple is used | |
48 | for building 2D histograms (transverse momentum / local deviation) which | |
49 | afterwards enter calculation/optimization procedures for the selection of | |
50 | LUT cuts for individual local boards and several transverse momenta. | |
51 | ||
52 | This version is prepared for the use on the grid, see the JDL file. | |
53 | ||
54 | Files: | |
55 | ||
56 | AliAnalysisTaskLUT.cxx - source files of the analysis task | |
57 | AliAnalysisTaskLUT.h | |
58 | ||
59 | rootlutnt.sh - executable (script) | |
60 | ||
61 | runCreateLUTNT.C - macro for setting the libraries environment and | |
62 | execution of the main macro | |
63 | ||
64 | analysisTaskLUTNT.C - main macro for the analysis | |
65 | ||
66 | createLUTNT.jdl - JDL file | |
39280342 | 67 | |
267d502e | 68 | =================================================== |
69 | Analysis task for the calculation of the trigger chamber efficiency. | |
70 | Diego STOCCO, Torino | |
71 | ---------------------------------------------------------------- | |
72 | ||
73 | Purpose: produce histograms for the trigger chamber efficiency determination | |
74 | from MUON track info. The task works either with input ESD or AOD (default is ESD). | |
75 | ||
76 | This version works either locally or on grid. | |
77 | ||
78 | Files: | |
79 | AliAnalysisTaskTrigChEff.cxx -source files of the analysis task | |
80 | AliAnalysisTaskTrigChEff.h | |
81 | ||
82 | AnalysisTrigChEff.C - main macro for analysis | |
83 | ||
84 | Test analysis: | |
85 | - Preliminary: copy the following packages in the current working directory | |
86 | - STEERBase.par | |
87 | - ESD.par | |
88 | - AOD.par | |
89 | - ANALYSIS.par | |
90 | - ANALYSISalice.par | |
76b2028b | 91 | - PWG3muon.par |
267d502e | 92 | If the packages are not present, create them: |
93 | cd $ALICE_ROOT | |
94 | make STEERBase.par | |
95 | make ESD.par | |
96 | ... | |
97 | ||
98 | - Local test: | |
99 | root | |
100 | .x AnalysisTrigChEff.C(kMlocal) | |
101 | ||
102 | by default the macro searches for ESD in $ALICE_ROOT/MUON/test_out.100 | |
103 | The directory is generated by MUON/AlirootRun_MUONtest.sh (see README in MUON). | |
104 | ||
105 | - Grid test (interactive): | |
106 | root | |
107 | .x AnalysisTrigChEff.C(kMlocalGrid) | |
108 | ||
109 | by default the macro searches for a wn.xml in the current directory, with the list | |
110 | of grid files to analyse. | |
111 | ||
112 | - Display results: | |
113 | The macro creates the file MUON.TriggerEfficiencyMap.root | |
114 | aliroot | |
115 | AliMUONTriggerEfficiencyCells effCells("MUON.TriggerEfficiencyMap.root") | |
116 | effCells.DisplayEfficiency() | |
fe9005e3 | 117 | |
118 | =================================================== | |
119 | Analysis task for checking the consistency of ESD and AOD filling and contents. | |
120 | Mercedes LOPEZ NORIEGA, Orsay | |
121 | ---------------------------------------------------------------- | |
122 | ||
123 | Purpose:check the consistency between the ESDs and the AOD. | |
124 | ||
125 | The task works locally and on the grid, there are two macros depending where | |
126 | you want to run | |
127 | ||
128 | Files: | |
129 | AliAnalysisTaskAODvsESD.cxx -source files of the analysis task | |
130 | AliAnalysisTaskAODvsESD.h | |
131 | ||
132 | AnalysisTrainMuonComp.C - macro for analysis on the grid | |
133 | AnalysisTrainMuonCompLocal.C - macro for local analysis | |
134 | ||
135 | To run the check: | |
136 | 1. Copy the following packages in the current working directory | |
137 | - STEERBase.par | |
138 | - ESD.par | |
139 | - AOD.par | |
140 | - ANALYSIS.par | |
141 | - ANALYSISalice.par | |
142 | - PWG3muon.par | |
143 | ||
144 | 2. To run locally: | |
145 | root | |
146 | .x AnalysisTrainMuonCompLocal.C | |
147 | ||
148 | by default the macro searches for a tag file of ESDs in the | |
149 | working directory | |
150 | ||
151 | 3. To run on the grid: | |
152 | root | |
153 | .x AnalysisTrainMuonComp.C | |
154 | ||
155 | by default the macro searches for a wn.xml in the current directory, with the list | |
156 | of grid files to analyse. | |
157 | ||
158 | 4. Display results: | |
159 | The macro creates the file AODvsESDoutput.root | |
160 | It contains an Ntuple from the ESDs and Ntuple from the AODs and an inv. mass histo | |
161 | for each case | |
509204ee | 162 | |
163 | =================================================== | |
164 | Analysis task for extracting variables from the ESD for single muons | |
165 | Nicole BASTID and Bogdan VULPESCU, Clermont-Ferrand | |
166 | ---------------------------------------------------------------- | |
167 | ||
168 | Purpose: the output is an ntuple with single muon tracks selected variables; a | |
169 | histogram collects the number of events in different trigger classes. | |
170 | ||
171 | Files: | |
172 | ||
173 | AliAnalysisTaskSingleMuESD.cxx - source files of the analysis task | |
174 | AliAnalysisTaskSingleMuESD.h | |
175 | ||
176 | RunSingleMuonAnalysisFromESD.C - macro to run the analysis (with xml input | |
177 | collection and grid connection) | |
178 | ||
179 | ||
180 | How to run: | |
181 | ||
182 | 1. Copy the following packages in the current working directory | |
183 | - STEERBase.par | |
184 | - ESD.par | |
185 | - AOD.par | |
186 | - ANALYSIS.par | |
187 | - ANALYSISalice.par | |
188 | - PWG3muon.par | |
189 | ||
190 | 2. Run root | |
191 | ||
192 | gROOT->LoadMacro("$ALICE_ROOT/PWG3/muon/RunAnalysis.C"); | |
193 | setupPar("STEERBase"); | |
194 | setupPar("ESD"); | |
195 | setupPar("AOD"); | |
196 | setupPar("ANALYSIS"); | |
197 | setupPar("ANALYSISalice"); | |
198 | setupPar("PWG3muon"); | |
199 | ||
200 | 3. To analyse grid files, provide an XML collection file wn.xml and run | |
201 | ||
202 | gROOT->LoadMacro("$ALICE_ROOT/PWG3/muon/RunSingleMuonAnalysisFromESD.C"); | |
203 | RunSingleMuonAnalysisFromESD() | |
204 | ||
205 | 4. To analyse local files, modify RunSingleMuonAnalysisFromESD.C | |
206 | ||
207 | } else { | |
208 | chain->Add("/path_1_to/AliESDs.root"); | |
209 | chain->Add("/path_2_to/AliESDs.root"); | |
210 | chain->Add("/path_3_to/AliESDs.root"); | |
211 | } | |
212 | ||
213 | and run (notice the "1" argument) | |
214 | ||
215 | gROOT->LoadMacro("$ALICE_ROOT/PWG3/muon/RunSingleMuonAnalysisFromESD.C"); | |
216 | RunSingleMuonAnalysisFromESD(1) | |
217 | ||
218 | 5. Check the results in SingleMuESD.root | |
219 | ||
220 | Note: for some older runs (PDC08/LHC08t for instance) it is necessary to force | |
221 | the values of the trigger mask, because the function | |
222 | ||
223 | GetFiredTriggerClasses() | |
224 | ||
225 | from AliESDEvent does not return the proper names of the muon trigger classes. | |
226 | So one has to un-comment the line | |
227 | ||
228 | task->SetTriggerType("MUON"); | |
229 | ||
230 | in the macro RunSingleMuonAnalysisFromESD.C, if the simulation was produced | |
231 | with SetMakeTrigger("MUON") | |
232 | ||
233 | This bug is fixed starting with the TRUNK from 14.11.2008 | |
234 | ||
587dd11c | 235 | =================================================== |
236 | Analysis task for RecoCheck analysis of ESD and Kinematics | |
237 | Bogdan VULPESCU, Clermont-Ferrand | |
238 | ---------------------------------------------------------------- | |
239 | ||
240 | Purpose: the class MUON/AliMUONRecoCheck is used to extract single muon and | |
241 | muon pair information in objects of type AliMUONTrackLight and | |
242 | AliMUONPairLight. The output file is RecoCheck.root and contains a tree with | |
243 | arrays of both objects. | |
244 | ||
245 | Files: | |
246 | ||
247 | AliAnalysisTaskRecoCheck.cxx - source files of the analysis task | |
248 | AliAnalysisTaskRecoCheck.h | |
249 | ||
250 | RunRecoCheck.C - macro to run the analysis (with xml input | |
251 | collection and grid connection) | |
252 | ||
253 | ||
254 | How to run: | |
255 | ||
256 | 1. Run aliroot (not root!, the class is in the muondep library) | |
257 | ||
258 | 2. gROOT->LoadMacro("$ALICE_ROOT/PWG3/muondep/RunRecoCheck.C"); | |
259 | ||
260 | 3. RunRecoCheck() | |
261 | ||
262 | 4. To analyse local files, modify RunRecoCheck.C | |
263 | ||
264 | } else { | |
265 | chain->Add("/path_1_to/AliESDs.root"); | |
266 | chain->Add("/path_2_to/AliESDs.root"); | |
267 | chain->Add("/path_3_to/AliESDs.root"); | |
268 | } | |
269 | ||
270 | and run (notice the "1" argument) | |
271 | ||
272 | RunRecoCheck(1) | |
273 | ||
274 | 5. Check results in RecoCheck.root | |
509204ee | 275 | |
587dd11c | 276 | Note: the magnetic field is needed in order to initialize the tracker. The |
277 | corresponding field map is selected by looking at the value of the L3 current | |
278 | stored in the GRP database which was used for the reconstruction. | |
509204ee | 279 | |
4c904d93 | 280 | =================================================== |
281 | Analysis task to correlate ESD tracks to their corresponding Monte Carlo data. | |
282 | Artur Szostak, INFN | |
283 | --------------------------------------------------------------- | |
284 | ||
285 | The AliAnalysisTaskLinkToMC analysis task is used to correlate reconstructed tracks | |
286 | found in ESDs to their corresponding MC track information found in the kinematics | |
287 | tree. The the same algorithm is used as in MUON/AliMUONRecoCheck but without any | |
288 | dependancy on MUON library code. This analysis task will copy out ESD MUON track | |
289 | information into the AOD like AliAnalysisTaskESDMuonFilter does, however the MC | |
290 | track label in the AOD track class is filled with the label of the corresponding | |
291 | MC track. Thus, subsequent analysis tasks can easily find the correct MC track from | |
292 | the label. | |
293 | ||
294 | Files: | |
295 | ||
296 | AliAnalysisTaskLinkToMC.h - The header file for the analysis task code. | |
297 | AliAnalysisTaskLinkToMC.cxx - The source file for the analysis task code. | |
298 | ||
299 | RunLinkToMCAnalysisExample.C - An example macro for running the analysis task in | |
300 | local mode over simulated data. The macro takes one argument which is the name | |
301 | of the ESD file to process. By default it uses AliESDs.root in the current working | |
302 | directory. | |
303 | ||
304 | PlotEfficiency.C - This macro can be used to quickly check the control histograms | |
305 | which are generated by RunLinkToMCAnalysisExample.C by default. The macro simply | |
306 | calculates the reconstruction efficiency from the found and findable track histograms | |
307 | that are filled by the analysis task. | |
308 | ||
309 | How to run: | |
310 | ||
311 | To run the analysis task in local mode with the example macro simply run the command | |
312 | $ root RunLinkToMCAnalysisExample.C\(\"AliESDs.root\"\) | |
313 | where AliESDs.root can be replaced with the full path and name of the appropriate ESD | |
314 | file you wish to process. This command can also be run via AliRoot. | |
315 |