5 \page README_evaluation Evaluation
8 \section evaluation_s1 How to process invariant mass spectra for J/psi or Upsilon
10 The macro MUONmassPlot_ESD.C reads back the MUON ESD informations and compute
11 the invariant mass spectra and corresponding uncorelated background.
12 Moreover gives the number of event in the resonance peak and the number of triggers.
15 root [0] .L $ALICE_ROOT/MUON/MUONmassPlot_ESD.C+
16 root [1] MUONmassPlot_ESD(ExtrapToVertex,
18 FirstEvent, LastEvent,
25 ExtrapToVertex (default -1)
27 =0: extrapolation to (0,0,0);
28 >0: extrapolation to ESDVertex if available, else to (0,0,0)
29 geoFilename (default "geometry.root") geometry file name needed to extrap to vertex
30 filename (default "galice.root") galice root file name
31 FirstEvent (default 0)
32 LastEvent (default 10000)
33 esdFileName (default "AliESDs.root") esd root file name
34 ResType (default 553): 553 for Upsilon, anything else for J/Psi
35 Chi2Cut (default 100): keep only tracks with chi2 per d.o.f. < Chi2Cut
36 PtCutMin (default 1): keep only tracks with transverse momentum > PtCutMin
37 PtCutMax (default 10000): keep only tracks with transverse momentum < PtCutMax
38 massMin (default 9.17 for Upsilon) keep only invariant masses with
39 massMax (default 9.77 for Upsilon) massMin < mass < massMax
42 \section evaluation_s2 How to run MUONRecoCheck macro
44 To check the muon reconstruction by comparing the reconstructed tracks
45 with the reference tracks made of "AliTrackReference" for the hits in chamber (0..9)
46 and kinematic informations (TreeK) for the vertex.
47 This macro can be used to check the track reconstruction e.g. efficiency,
48 momentum resolution ... but also to make physics analysis whenever
49 track identification is needed.
51 To compile MUONRecoCheck.C
53 .includepath $ALICE_ROOT/STEER
54 .includepath $ALICE_ROOT/MUON
55 .L $ALICE_ROOT/MUON/MUONRecoCheck.C+
60 MUONRecoCheck(nEvent,"geometry.root", "galice.root"); // nEvent = nb of events
64 \section evaluation_s3 Macros for MC studies
66 For MC studies the classes AliMUONTrackLight and AliMUONPairLight can be
67 used in order to fill not only the single muon / dimuon's kinematics (charge,
68 pT, rapidity, etc) at the generation AND reconstruction level, but also for
69 "decoding" the Pythia output and for the storing of the single muon's history.
70 This allows to tag if two muons of a given event come from a certain, well-defined
71 process, such as J/psi, Upsilons, correlated open charm or open beauty or the
72 low masses or if they are of uncorrelated origin. For open beauty/charm it also
73 tags the creation process (pair creation, flavour excitation or gluon splitting).
74 The classes also allow to tag feed-down or neutral B meson oscillation and
75 has a method that checks whether the reconstructed track is a muon or not.
77 The macros ReadRecoCocktail.C, DecodeRecoCocktail.C and MergeMuonLight.C
78 are examples how to use these two classes. DecodeRecoCocktail.C opens the
79 generated files, loops over the events and fills an AliMUONTrackLight object
80 for every reconstructed track for which the reference to its generated particle
81 could be established, using the AliMUONRecoCheck class.
82 It then takes the AliMUONTrackLight objects and forms - event by event -
83 AliMUONPairLight objects, on a combinatorial basis. For a given event these
84 objects are stored in respective TClonesArrays which are then stored in a tree.
85 By default, the produced output file is called "MuonLight.root".
86 This root file can then be taken by the macro "ReadRecoCocktail.C" that shows,
87 on the example of the reconstructed mass and pT of the AliMUONPairLight object,
88 how to access the available information. For large statistics, in which many
89 individual MuonLight.root files are produced, MergeMuonLight.C can be used
90 to merge the files and produce one common output root file.
92 To read a generation/reconstrution from PDC06 preproduction, and write a file
93 with a tree of AliMUONTrackLight / AliMUONPairLight :
94 go to the directory containing the generation/reconstruction. From there run
98 .L DecodeRecoCocktail.C+
103 To read the file previously generated:
106 .L ReadRecoCocktail.C+
111 This chapter is defined in the READMEevaluation.txt file.