]>
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 | ||
af2b48fb | 12 | In order to test the analysis train from the ESD to the Standard AOD production, the following macro is provided: |
643fea24 | 13 | |
af2b48fb | 14 | AnalysisTrainFromESDToAOD.C |
15 | ||
16 | Input file: ESD | |
17 | Output files: standard AOD (+AOD tags) | |
18 | ||
19 | Two wagons are attached to the analysis train: | |
20 | 1) $ALICE_ROOT/ANALYSIS/macros/AddTaskESDFilter.C | |
21 | 2) $ALICE_ROOT/PWG3/muon/AddTaskTagCreation.C | |
22 | ||
23 | Several flags can be activated: | |
24 | 1) iESDfilter: to activate, using AddTaskESDFilter.C, the copy of the ESD information into the AOD. | |
25 | In AddTaskESDFilter.C there is the possibility to apply cuts on the tracks and muon tracks in order | |
26 | to reject them before filling the AOD. | |
27 | 2) iAODAddMCBranch: to activate the inclusion of the MC branch (containing Kinematics info) into a branch of the AOD | |
28 | 3) iAODTagCreation: to activate, using AddTaskTagCreation.C, the AOD tag creation | |
29 | ||
30 | Runninng options tested: | |
31 | 1) GRID (with/without AliEn plugin) | |
32 | 2) LOCAL | |
33 | ||
34 | If the AliEn plugin is required, the macro | |
35 | CreateAlienHandler_FromESDToAOD.C | |
36 | can be used, in order to configure the jdl. | |
37 | ||
38 | AnalysisTrainFromESDToAOD.C is an updated version of the macro AnalysisTrainMuonLocal.C | |
39 | (input file: ESD, output files standard AOD and the AOD tag file) | |
40 | The main differences are related to implementations to be compliant with the analysis framework, | |
41 | possibility to run on the grid with/without the Alien Plugin and possibility of adding the MC truth in a branch of the AOD. | |
42 | ||
43 | The macro ReadAOD_MCBranch.C is an example on how to access MC information stored in the AOD. | |
643fea24 | 44 | |
45 | =================================================== | |
46 | Creation of the MUON-AOD from the standard AOD | |
47 | Roberta ARNALDI, Enrico SCOMPARIN Torino | |
48 | --------------------------------------------------------------- | |
49 | ||
50 | Code to produce a muon-AOD, i.e. a replica of the standard AOD containing only events where | |
51 | at least one muon in the dimuon spectrometer is present | |
52 | ||
53 | 1) AnalysisTrainFromStandardToMuonAODLocal.C --> macro to produce the MUON-AOD (it runs locally) | |
54 | 2) AliAnalysisTaskFromStandardToMuonAOD.h --> analysis task to replicate the AOD content for interesting events | |
55 | 3) AliAnalysisTaskFromStandardToMuonAOD.cxx --> analysis task to replicate the AOD content for interesting events | |
56 | ||
57 | - The input files are the standard AOD and the AOD tag file. | |
58 | The AOD tag file can be created in the previous step from ESD to Standard AOD, using AnalysisTrainMuonLocal.C, or it can be | |
59 | produced on the fly with this macro. | |
60 | - Events containing at least one muon in the muon spectrometer can be selected using the AOD tag files. | |
61 | - The contents of the MUON-AOD can be defined by the user in the AnalysisTrainFromStandardToMuonAODLocal.C | |
62 | macro with some settings as | |
63 | SetNeedsTracksBranchReplication(), SetNeedsVerticesBranchReplication() | |
64 | (defined in STEER/AliAODHandler.h)... | |
28d9f4b3 | 65 | |
267d502e | 66 | =================================================== |
67 | Calculation of the LUT | |
68 | Bogdan VULPESCU, Clermont | |
28d9f4b3 | 69 | --------------------------------------------------------------- |
39280342 | 70 | Analysis task for the calculation of the Look-up-Tables used by the MUON |
71 | trigger algorithm | |
72 | ||
73 | Purpose: extract from ESD files track information (ESD track parameters and | |
74 | matched local trigger decisions) and store in TNtuple; the ntuple is used | |
75 | for building 2D histograms (transverse momentum / local deviation) which | |
76 | afterwards enter calculation/optimization procedures for the selection of | |
77 | LUT cuts for individual local boards and several transverse momenta. | |
78 | ||
79 | This version is prepared for the use on the grid, see the JDL file. | |
80 | ||
81 | Files: | |
82 | ||
83 | AliAnalysisTaskLUT.cxx - source files of the analysis task | |
84 | AliAnalysisTaskLUT.h | |
85 | ||
86 | rootlutnt.sh - executable (script) | |
87 | ||
88 | runCreateLUTNT.C - macro for setting the libraries environment and | |
89 | execution of the main macro | |
90 | ||
91 | analysisTaskLUTNT.C - main macro for the analysis | |
92 | ||
93 | createLUTNT.jdl - JDL file | |
39280342 | 94 | |
267d502e | 95 | =================================================== |
96 | Analysis task for the calculation of the trigger chamber efficiency. | |
97 | Diego STOCCO, Torino | |
98 | ---------------------------------------------------------------- | |
99 | ||
100 | Purpose: produce histograms for the trigger chamber efficiency determination | |
101 | from MUON track info. The task works either with input ESD or AOD (default is ESD). | |
102 | ||
103 | This version works either locally or on grid. | |
104 | ||
105 | Files: | |
106 | AliAnalysisTaskTrigChEff.cxx -source files of the analysis task | |
107 | AliAnalysisTaskTrigChEff.h | |
108 | ||
109 | AnalysisTrigChEff.C - main macro for analysis | |
110 | ||
111 | Test analysis: | |
112 | - Preliminary: copy the following packages in the current working directory | |
113 | - STEERBase.par | |
114 | - ESD.par | |
115 | - AOD.par | |
116 | - ANALYSIS.par | |
117 | - ANALYSISalice.par | |
76b2028b | 118 | - PWG3muon.par |
267d502e | 119 | If the packages are not present, create them: |
120 | cd $ALICE_ROOT | |
121 | make STEERBase.par | |
122 | make ESD.par | |
123 | ... | |
124 | ||
125 | - Local test: | |
126 | root | |
127 | .x AnalysisTrigChEff.C(kMlocal) | |
128 | ||
129 | by default the macro searches for ESD in $ALICE_ROOT/MUON/test_out.100 | |
130 | The directory is generated by MUON/AlirootRun_MUONtest.sh (see README in MUON). | |
131 | ||
132 | - Grid test (interactive): | |
133 | root | |
134 | .x AnalysisTrigChEff.C(kMlocalGrid) | |
135 | ||
136 | by default the macro searches for a wn.xml in the current directory, with the list | |
137 | of grid files to analyse. | |
138 | ||
139 | - Display results: | |
140 | The macro creates the file MUON.TriggerEfficiencyMap.root | |
141 | aliroot | |
142 | AliMUONTriggerEfficiencyCells effCells("MUON.TriggerEfficiencyMap.root") | |
143 | effCells.DisplayEfficiency() | |
fe9005e3 | 144 | |
145 | =================================================== | |
146 | Analysis task for checking the consistency of ESD and AOD filling and contents. | |
147 | Mercedes LOPEZ NORIEGA, Orsay | |
148 | ---------------------------------------------------------------- | |
149 | ||
150 | Purpose:check the consistency between the ESDs and the AOD. | |
151 | ||
152 | The task works locally and on the grid, there are two macros depending where | |
153 | you want to run | |
154 | ||
155 | Files: | |
156 | AliAnalysisTaskAODvsESD.cxx -source files of the analysis task | |
157 | AliAnalysisTaskAODvsESD.h | |
158 | ||
159 | AnalysisTrainMuonComp.C - macro for analysis on the grid | |
160 | AnalysisTrainMuonCompLocal.C - macro for local analysis | |
161 | ||
162 | To run the check: | |
163 | 1. Copy the following packages in the current working directory | |
164 | - STEERBase.par | |
165 | - ESD.par | |
166 | - AOD.par | |
167 | - ANALYSIS.par | |
168 | - ANALYSISalice.par | |
169 | - PWG3muon.par | |
170 | ||
171 | 2. To run locally: | |
172 | root | |
173 | .x AnalysisTrainMuonCompLocal.C | |
174 | ||
175 | by default the macro searches for a tag file of ESDs in the | |
176 | working directory | |
177 | ||
178 | 3. To run on the grid: | |
179 | root | |
180 | .x AnalysisTrainMuonComp.C | |
181 | ||
182 | by default the macro searches for a wn.xml in the current directory, with the list | |
183 | of grid files to analyse. | |
184 | ||
185 | 4. Display results: | |
186 | The macro creates the file AODvsESDoutput.root | |
187 | It contains an Ntuple from the ESDs and Ntuple from the AODs and an inv. mass histo | |
188 | for each case | |
509204ee | 189 | |
190 | =================================================== | |
191 | Analysis task for extracting variables from the ESD for single muons | |
192 | Nicole BASTID and Bogdan VULPESCU, Clermont-Ferrand | |
193 | ---------------------------------------------------------------- | |
194 | ||
195 | Purpose: the output is an ntuple with single muon tracks selected variables; a | |
196 | histogram collects the number of events in different trigger classes. | |
197 | ||
198 | Files: | |
199 | ||
200 | AliAnalysisTaskSingleMuESD.cxx - source files of the analysis task | |
201 | AliAnalysisTaskSingleMuESD.h | |
202 | ||
203 | RunSingleMuonAnalysisFromESD.C - macro to run the analysis (with xml input | |
204 | collection and grid connection) | |
205 | ||
206 | ||
207 | How to run: | |
208 | ||
209 | 1. Copy the following packages in the current working directory | |
210 | - STEERBase.par | |
211 | - ESD.par | |
212 | - AOD.par | |
213 | - ANALYSIS.par | |
214 | - ANALYSISalice.par | |
215 | - PWG3muon.par | |
216 | ||
217 | 2. Run root | |
218 | ||
219 | gROOT->LoadMacro("$ALICE_ROOT/PWG3/muon/RunAnalysis.C"); | |
220 | setupPar("STEERBase"); | |
221 | setupPar("ESD"); | |
222 | setupPar("AOD"); | |
223 | setupPar("ANALYSIS"); | |
224 | setupPar("ANALYSISalice"); | |
225 | setupPar("PWG3muon"); | |
226 | ||
227 | 3. To analyse grid files, provide an XML collection file wn.xml and run | |
228 | ||
229 | gROOT->LoadMacro("$ALICE_ROOT/PWG3/muon/RunSingleMuonAnalysisFromESD.C"); | |
230 | RunSingleMuonAnalysisFromESD() | |
231 | ||
232 | 4. To analyse local files, modify RunSingleMuonAnalysisFromESD.C | |
233 | ||
234 | } else { | |
235 | chain->Add("/path_1_to/AliESDs.root"); | |
236 | chain->Add("/path_2_to/AliESDs.root"); | |
237 | chain->Add("/path_3_to/AliESDs.root"); | |
238 | } | |
239 | ||
240 | and run (notice the "1" argument) | |
241 | ||
242 | gROOT->LoadMacro("$ALICE_ROOT/PWG3/muon/RunSingleMuonAnalysisFromESD.C"); | |
243 | RunSingleMuonAnalysisFromESD(1) | |
244 | ||
245 | 5. Check the results in SingleMuESD.root | |
246 | ||
247 | Note: for some older runs (PDC08/LHC08t for instance) it is necessary to force | |
248 | the values of the trigger mask, because the function | |
249 | ||
250 | GetFiredTriggerClasses() | |
251 | ||
252 | from AliESDEvent does not return the proper names of the muon trigger classes. | |
253 | So one has to un-comment the line | |
254 | ||
255 | task->SetTriggerType("MUON"); | |
256 | ||
257 | in the macro RunSingleMuonAnalysisFromESD.C, if the simulation was produced | |
258 | with SetMakeTrigger("MUON") | |
259 | ||
260 | This bug is fixed starting with the TRUNK from 14.11.2008 | |
261 | ||
587dd11c | 262 | =================================================== |
263 | Analysis task for RecoCheck analysis of ESD and Kinematics | |
264 | Bogdan VULPESCU, Clermont-Ferrand | |
265 | ---------------------------------------------------------------- | |
266 | ||
267 | Purpose: the class MUON/AliMUONRecoCheck is used to extract single muon and | |
268 | muon pair information in objects of type AliMUONTrackLight and | |
269 | AliMUONPairLight. The output file is RecoCheck.root and contains a tree with | |
270 | arrays of both objects. | |
271 | ||
272 | Files: | |
273 | ||
274 | AliAnalysisTaskRecoCheck.cxx - source files of the analysis task | |
275 | AliAnalysisTaskRecoCheck.h | |
276 | ||
277 | RunRecoCheck.C - macro to run the analysis (with xml input | |
278 | collection and grid connection) | |
279 | ||
280 | ||
281 | How to run: | |
282 | ||
283 | 1. Run aliroot (not root!, the class is in the muondep library) | |
284 | ||
285 | 2. gROOT->LoadMacro("$ALICE_ROOT/PWG3/muondep/RunRecoCheck.C"); | |
286 | ||
287 | 3. RunRecoCheck() | |
288 | ||
289 | 4. To analyse local files, modify RunRecoCheck.C | |
290 | ||
291 | } else { | |
292 | chain->Add("/path_1_to/AliESDs.root"); | |
293 | chain->Add("/path_2_to/AliESDs.root"); | |
294 | chain->Add("/path_3_to/AliESDs.root"); | |
295 | } | |
296 | ||
297 | and run (notice the "1" argument) | |
298 | ||
299 | RunRecoCheck(1) | |
300 | ||
301 | 5. Check results in RecoCheck.root | |
509204ee | 302 | |
587dd11c | 303 | Note: the magnetic field is needed in order to initialize the tracker. The |
304 | corresponding field map is selected by looking at the value of the L3 current | |
305 | stored in the GRP database which was used for the reconstruction. | |
509204ee | 306 | |
4c904d93 | 307 | =================================================== |
308 | Analysis task to correlate ESD tracks to their corresponding Monte Carlo data. | |
309 | Artur Szostak, INFN | |
310 | --------------------------------------------------------------- | |
311 | ||
312 | The AliAnalysisTaskLinkToMC analysis task is used to correlate reconstructed tracks | |
313 | found in ESDs to their corresponding MC track information found in the kinematics | |
314 | tree. The the same algorithm is used as in MUON/AliMUONRecoCheck but without any | |
315 | dependancy on MUON library code. This analysis task will copy out ESD MUON track | |
316 | information into the AOD like AliAnalysisTaskESDMuonFilter does, however the MC | |
317 | track label in the AOD track class is filled with the label of the corresponding | |
318 | MC track. Thus, subsequent analysis tasks can easily find the correct MC track from | |
319 | the label. | |
320 | ||
321 | Files: | |
322 | ||
323 | AliAnalysisTaskLinkToMC.h - The header file for the analysis task code. | |
324 | AliAnalysisTaskLinkToMC.cxx - The source file for the analysis task code. | |
325 | ||
326 | RunLinkToMCAnalysisExample.C - An example macro for running the analysis task in | |
327 | local mode over simulated data. The macro takes one argument which is the name | |
328 | of the ESD file to process. By default it uses AliESDs.root in the current working | |
329 | directory. | |
330 | ||
331 | PlotEfficiency.C - This macro can be used to quickly check the control histograms | |
332 | which are generated by RunLinkToMCAnalysisExample.C by default. The macro simply | |
333 | calculates the reconstruction efficiency from the found and findable track histograms | |
334 | that are filled by the analysis task. | |
335 | ||
336 | How to run: | |
337 | ||
338 | To run the analysis task in local mode with the example macro simply run the command | |
339 | $ root RunLinkToMCAnalysisExample.C\(\"AliESDs.root\"\) | |
340 | where AliESDs.root can be replaced with the full path and name of the appropriate ESD | |
341 | file you wish to process. This command can also be run via AliRoot. | |
342 | ||
94af0645 | 343 | |
344 | =================================================== | |
345 | Analysis task to create mixed AOD events, containing a | |
346 | pair of muon tracks coming from two different real AOD events. | |
347 | Alessandro De Falco and Antonio Uras, INFN Cagliari | |
348 | --------------------------------------------------------------- | |
349 | ||
350 | IMPORTANT: The AliAnalysisTaskCreateMixedDimuons analysis task needs | |
351 | the class AliEventPoolMuon. | |
352 | ||
353 | In class AliEventPoolMuon the definition of the pools to be used | |
354 | in the mixing is implemented. Up to now, it is possible to create | |
355 | pools diving events by: | |
356 | - total multiplicity | |
357 | - forward muons multiplicity | |
358 | - z-position of the primary vertex | |
359 | ||
360 | In class AliAnalysisTaskCreateMixedDimuons the mixing is performed between | |
361 | each pair of events which can be built up picking events from the internal | |
362 | buffer: if the buffer contains n events, n(n-1)/2 mixed events are created | |
363 | within the same call of the task. | |
364 | ||
365 | Some more details: | |
366 | - the mixing task asks a completely fresh buffer for each call | |
367 | - the mixing task creates output events from scratch | |
368 | - output events are filled with two muon tracks (picked randomly | |
369 | from the events being mixed and a vertex having its z-position in the middle | |
370 | of the z-vertex bin defining the pool. Due to technical reasons, | |
371 | the tracks are NOT connected with the vertex | |
372 | - standard AOD are created as output, nearly completely empty | |
373 | ||
374 | Files: | |
375 | ||
376 | AliAnalysisTaskCreateMixedDimuons.(h,cxx) - The analysis task class. | |
377 | AliEventPoolMuon.(h,cxx) - The class implementing the pool. | |
378 | ||
379 | AnalysisTrainCreateMixedDimuons.C - An example macro enabling connections between | |
380 | the pool manager, the input event handler, the input and output containers, | |
381 | via the Analysis Manager. Input arguments: - directory containing AOD tag file | |
382 | - name of the output file | |
383 | - number of events to be loaded | |
384 | in the internal buffer | |
385 | ||
386 | How to run: | |
387 | ||
388 | To run the analysis task in local mode with the example macro, simply run | |
389 | the AnalysisTrainCreateMixedDimuons.C macro (without compiling it) with | |
390 | appropriate arguments. | |
391 |