[u/mrichter/AliRoot.git] / MUON / READMEevaluation.txt
518eb852 1// $Id$
5\page README_evaluation README evaluation
8\section evaluation_s1 How to run MUONRecoCheck macro
2ce5e44e 9
10To check the muon reconstruction by comparing the reconstructed tracks
11with the reference tracks made of "AliTrackReference" for the hits in chamber (0..9)
12and kinematic informations (TreeK) for the vertex.
13This macro can be used to check the track reconstruction e.g. efficiency,
14momentum resolution ... but also to make physics analysis whenever
15track identification is needed.
17To compile MUONRecoCheck.C
518eb852 18<pre>
2ce5e44e 19.includepath $ALICE_ROOT/STEER
20.includepath $ALICE_ROOT/MUON
518eb852 22</pre>
2ce5e44e 23
518eb852 24To run MUONRecoCheck
2ce5e44e 26MUONRecoCheck(nEvent,"geometry.root", "galice.root"); // nEvent = nb of events
518eb852 27</pre>
2ce5e44e 28
518eb852 30\section evaluation_s2 Macros for MC studies
2ce5e44e 31
518eb852 32For MC studies the classes AliMUONTrackLight and AliMUONPairLight can be
2ce5e44e 33used in order to fill not only the single muon / dimuon's kinematics (charge,
34pT, 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.
36This allows to tag if two muons of a given event come from a certain, well-defined
37process, such as J/psi, Upsilons, correlated open charm or open beauty or the
38low masses or if they are of uncorrelated origin. For open beauty/charm it also
39tags the creation process (pair creation, flavour excitation or gluon splitting).
40The classes also allow to tag feed-down or neutral B meson oscillation and
41has a method that checks whether the reconstructed track is a muon or not.
43The macros ReadRecoCocktail.C, DecodeRecoCocktail.C and MergeMuonLight.C
44are examples how to use these two classes. DecodeRecoCocktail.C opens the
45generated files, loops over the events and fills an AliMUONTrackLight object
46for every reconstructed track for which the reference to its generated particle
47could be established, using the AliMUONRecoCheck class.
48It then takes the AliMUONTrackLight objects and forms - event by event -
49AliMUONPairLight objects, on a combinatorial basis. For a given event these
50objects are stored in respective TClonesArrays which are then stored in a tree.
51By default, the produced output file is called "MuonLight.root".
52This root file can then be taken by the macro "ReadRecoCocktail.C" that shows,
53on the example of the reconstructed mass and pT of the AliMUONPairLight object,
54how to access the available information. For large statistics, in which many
55individual MuonLight.root files are produced, MergeMuonLight.C can be used
56to merge the files and produce one common output root file.
58To read a generation/reconstrution from PDC06 preproduction, and write a file
59with a tree of AliMUONTrackLight / AliMUONPairLight :
60go to the directory containing the generation/reconstruction. From there run
518eb852 62
2ce5e44e 64.L DecodeRecoCocktail.C+
518eb852 67</pre>
2ce5e44e 68
69To read the file previously generated:
518eb852 70<pre>
2ce5e44e 71aliroot
72.L ReadRecoCocktail.C+
518eb852 75</pre>
baa48044 77\section evaluation_s3 Macro MUONCheckDI.C
79MUONCheckDI.C performs a consistency check on the methods of the
80AliMUONMCDataInterface and AliMUONDataInterface classes. There are several
81helper methods in these classes which make it easier to fetch data, which
82means there are at least two ways of fetching the data within the same class
83interface. The macro checks to see that the results given by these different
84methods are identical, as they should be.
86The macro also inherently exercises the AliMUONMCDataInterface and
87AliMUONDataInterface classes and should be run after any modifications to
88these classes to see if things still work. Putting it another way:
89MUONCheckDI.C is a testing facility for developers of these two classes.
518eb852 91*/