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