]>
Commit | Line | Data |
---|---|---|
2ce5e44e | 1 | ============================================================ |
2 | How to run MUONRecoCheck macro | |
3 | ============================================================ | |
4 | ||
5 | To check the muon reconstruction by comparing the reconstructed tracks | |
6 | with the reference tracks made of "AliTrackReference" for the hits in chamber (0..9) | |
7 | and kinematic informations (TreeK) for the vertex. | |
8 | This macro can be used to check the track reconstruction e.g. efficiency, | |
9 | momentum resolution ... but also to make physics analysis whenever | |
10 | track identification is needed. | |
11 | ||
12 | To compile MUONRecoCheck.C | |
13 | .includepath $ALICE_ROOT/STEER | |
14 | .includepath $ALICE_ROOT/MUON | |
15 | .L $ALICE_ROOT/MUON/MUONRecoCheck.C+ | |
16 | ||
17 | // To run MUONRecoCheck | |
18 | MUONRecoCheck(nEvent,"geometry.root", "galice.root"); // nEvent = nb of events | |
19 | ||
20 | ||
21 | ========================================================== | |
22 | Macros for MC studies | |
23 | ========================================================== | |
24 | ||
25 | For MC studies the classes "AliMUONTrackLight" and "AliMUONPairLight" can be | |
26 | used in order to fill not only the single muon / dimuon's kinematics (charge, | |
27 | pT, rapidity, etc) at the generation AND reconstruction level, but also for | |
28 | "decoding" the Pythia output and for the storing of the single muon's history. | |
29 | This allows to tag if two muons of a given event come from a certain, well-defined | |
30 | process, such as J/psi, Upsilons, correlated open charm or open beauty or the | |
31 | low masses or if they are of uncorrelated origin. For open beauty/charm it also | |
32 | tags the creation process (pair creation, flavour excitation or gluon splitting). | |
33 | The classes also allow to tag feed-down or neutral B meson oscillation and | |
34 | has a method that checks whether the reconstructed track is a muon or not. | |
35 | ||
36 | The macros ReadRecoCocktail.C, DecodeRecoCocktail.C and MergeMuonLight.C | |
37 | are examples how to use these two classes. DecodeRecoCocktail.C opens the | |
38 | generated files, loops over the events and fills an AliMUONTrackLight object | |
39 | for every reconstructed track for which the reference to its generated particle | |
40 | could be established, using the AliMUONRecoCheck class. | |
41 | It then takes the AliMUONTrackLight objects and forms - event by event - | |
42 | AliMUONPairLight objects, on a combinatorial basis. For a given event these | |
43 | objects are stored in respective TClonesArrays which are then stored in a tree. | |
44 | By default, the produced output file is called "MuonLight.root". | |
45 | This root file can then be taken by the macro "ReadRecoCocktail.C" that shows, | |
46 | on the example of the reconstructed mass and pT of the AliMUONPairLight object, | |
47 | how to access the available information. For large statistics, in which many | |
48 | individual MuonLight.root files are produced, MergeMuonLight.C can be used | |
49 | to merge the files and produce one common output root file. | |
50 | ||
51 | To read a generation/reconstrution from PDC06 preproduction, and write a file | |
52 | with a tree of AliMUONTrackLight / AliMUONPairLight : | |
53 | go to the directory containing the generation/reconstruction. From there run | |
54 | aliroot | |
55 | .L DecodeRecoCocktail.C+ | |
56 | DecodeRecoCocktail(); | |
57 | .q | |
58 | ||
59 | To read the file previously generated: | |
60 | aliroot | |
61 | .L ReadRecoCocktail.C+ | |
62 | ReadRecoCocktail(); | |
63 | .q |