============================================================
How to run MUONRecoCheck macro
============================================================
+
To check the muon reconstruction by comparing the reconstructed tracks
-with the reference tracks made of "AliTrackReference" for the hits and
-kinematic informations (TParticle) for the vertex.
+with the reference tracks made of "AliTrackReference" for the hits in chamber (0..9)
+and kinematic informations (TreeK) for the vertex.
This macro can be used to check the track reconstruction e.g. efficiency,
momentum resolution ... but also to make physics analysis whenever
track identification is needed.
.L $ALICE_ROOT/MUON/MUONRecoCheck.C+
// To run MUONRecoCheck
-MUONRecoCheck(nEvent,"galice.root"); // nEvent = nb of events
+MUONRecoCheck(nEvent,"geometry.root", "galice.root"); // nEvent = nb of events
============================================================
===========================================================
Macro for generating the geometry data files
-and mis-alignment data.
Geometry data files:
- MUON/data/volpath.dat file contains the volume paths
but have different names (with extension ".out").
Replacement with new files has to be done manually.
-If the appropiate flags are set (zeroAlign, resMisAlign and/or fullMisAlign)
-zero, residual and/or full misalignment data are generated in a
-local CDB folder (defaults are ResMisAlignCDB and FullMisAlignCDB
+===========================================================
+ Macros to generate Mis-alignment data
+===========================================================
+
+Macro for generating the geometry mis-alignment data:
+MakeMUONFullMisAlignment.C
+MakeMUONResMisAlignment.C
+MakeMUONZeroMisAlignment.C
+
+To be run from aliroot:
+.x MakeMUONFullMisAlignment.C etc.
+
+If the environment variable TOCDB is not set to "kTRUE",
+the misalignment data are generated in a local file:
+(MUONFullMisalignment.root, etc.)
+
+If the data are stored in CDB, the storage can be specified in
+the environment variable STORAGE. The misalignment data are then
+generated in the CDB folder (defaults are ResMisAlignCDB and FullMisAlignCDB
in the working directory). Inside the local CDB the path for the
alignment data is (and must be) "MUON/Align/Data/".
Residual misalignment: Default is our current estimate of
hit-track is used to check the particle ID.
==========================================================
-Macro to process PDC06 preproduction
+Macros for MC studies
==========================================================
+For MC studies the classes "AliMUONTrackLight" and "AliMUONPairLight" can be
+used in order to fill not only the single muon / dimuon's kinematics (charge,
+pT, rapidity, etc) at the generation AND reconstruction level, but also for
+"decoding" the Pythia output and for the storing of the single muon's history.
+This allows to tag if two muons of a given event come from a certain, well-defined
+process, such as J/psi, Upsilons, correlated open charm or open beauty or the
+low masses or if they are of uncorrelated origin. For open beauty/charm it also
+tags the creation process (pair creation, flavour excitation or gluon splitting).
+The classes also allow to tag feed-down or neutral B meson oscillation and
+has a method that checks whether the reconstructed track is a muon or not.
+
+The macros ReadRecoCocktail.C, DecodeRecoCocktail.C and MergeMuonLight.C
+are examples how to use these two classes. DecodeRecoCocktail.C opens the
+generated files, loops over the events and fills an AliMUONTrackLight object
+for every reconstructed track for which the reference to its generated particle
+could be established, using the AliMUONRecoCheck class.
+It then takes the AliMUONTrackLight objects and forms - event by event -
+AliMUONPairLight objects, on a combinatorial basis. For a given event these
+objects are stored in respective TClonesArrays which are then stored in a tree.
+By default, the produced output file is called "MuonLight.root".
+This root file can then be taken by the macro "ReadRecoCocktail.C" that shows,
+on the example of the reconstructed mass and pT of the AliMUONPairLight object,
+how to access the available information. For large statistics, in which many
+individual MuonLight.root files are produced, MergeMuonLight.C can be used
+to merge the files and produce one common output root file.
+
To read a generation/reconstrution from PDC06 preproduction, and write a file
with a tree of AliMUONTrackLight / AliMUONPairLight :
go to the directory containing the generation/reconstruction. From there run
aliroot
-.x DecodeRecoCocktail.C+
+.L DecodeRecoCocktail.C+
+DecodeRecoCocktail();
.q
To read the file previously generated:
aliroot
-.x ReadRecoCocktail.C+
+.L ReadRecoCocktail.C+
+ReadRecoCocktail();
.q
+===========================================================
+ How to reprocess trigger decision from already produced digits
+===========================================================
+The MUONTrigger.C macro can be used to check the trigger algorithm w/o
+having to (re-)perform simulation and digitalization.
+It loads the digits, erase TreeR and store the current trigger output in
+TreeR.
+The different trigger outputs can be compared by looking at the GLT branch
+of TreeD (filled during simulation) and the TC branch of TreeR (filled from
+a copy of TreeD during reconstruction or with this macro).
+Note: rec points from tracking chamber will be lost.
+Usage:
+root [0] .L $ALICE_ROOT/MUON/MUONTrigger.C+
+root [1] MUONTrigger()
+
+===========================================================
+ How to check integrated trigger efficiency
+===========================================================
+The MUONTriggerEfficiency.C macro (included in the check scripts) calculates
+the trigger efficiency for the 2 pt cuts.
+The output is stored in MUONTriggerEfficiency.out file.
+Usage:
+root [0] .L $ALICE_ROOT/MUON/MUONTriggerEfficiency.C+
+root [1] MUONTriggerEfficiency()
+For the CVS default version of the trigger LUT (i.e. lutAptLpt1Hpt1p7.root),
+The reference for J/psi and Upsilon is as below
+ For 1000 Jpsi events with:
+ AliGenParam *gener = new AliGenParam(1, AliGenMUONlib::kJpsi);
+ gener->SetMomentumRange(0,999);
+ gener->SetPtRange(0,100.);
+ gener->SetPhiRange(0., 360.);
+ gener->SetCutOnChild(1);
+ gener->SetChildPhiRange(0.,360.);
+ gener->SetChildThetaRange(171.0,178.0);
+ gener->SetOrigin(0,0,0);
+ gener->SetForceDecay(kDiMuon);
+ gener->SetTrackingFlag(1);
+ the output should be
+ Efficiency Lpt cut = 0.7362 +/- 0.0391
+ Efficiency Hpt cut = 0.2662 +/- 0.0201
+ Similarly, for 1000 Upsilon events, the output should be
+ Efficiency Lpt cut = 0.9806 +/- 0.0457
+ Efficiency Hpt cut = 0.9537 +/- 0.0448
+
+===========================================================
+ How to check single muon trigger efficiency versus pt
+===========================================================
+The MUONTriggerEfficiencyPt.C macro produces trigger single muon efficiency
+versus pt plots for the 2 pt cuts.
+Results are compared to the reference (red curves).
+To be used with (at least) 10000 events as follows
+ AliGenBox * gener = new AliGenBox(1);
+ gener->SetPtRange(0.,10.);
+ gener->SetPhiRange(0., 360.);
+ gener->SetThetaRange(171.000,178.001);
+ gener->SetPart(13); // or -13
+ gener->SetOrigin(0.,0., 0.);
+ gener->SetSigma(0.0, 0.0, 0.0);
+Outputs are stored in MUONTriggerEfficiencyPt.gif/eps/out files
+Important note: this macro works with one (real) muon track per event only
+Usage:
+root [0] .L $ALICE_ROOT/MUON/MUONTriggerEfficiencyPt.C+
+root [1] MUONTriggerEfficiencyPt()
+
+===========================================================
+ How to process invariant mass spectra for J/psi or Upsilon
+===========================================================
+The macro MUONmassPlot_ESD.C reads back the MUON ESD informations and compute
+the invariant mass spectra and corresponding uncorelated background.
+Moreover gives the number of event in the resonance peak and the number of triggers.
+Usage:
+root [0] .L $ALICE_ROOT/MUON/MUONmassPlot_ESD.C+
+root [1] MUONmassPlot_ESD(ExtrapToVertex,
+ geoFilenam, filename
+ FirstEvent, LastEvent,
+ esdFileName,
+ ResType, Chi2Cut,
+ PtCutMin, PtCutMax,
+ massMin, massMax)
+
+with:
+ExtrapToVertex (default -1)
+ <0: no extrapolation;
+ =0: extrapolation to (0,0,0);
+ >0: extrapolation to ESDVertex if available, else to (0,0,0)
+geoFilename (default "geometry.root") geometry file name needed to extrap to vertex
+filename (default "galice.root") galice root file name
+FirstEvent (default 0)
+LastEvent (default 10000)
+esdFileName (default "AliESDs.root") esd root file name
+ResType (default 553): 553 for Upsilon, anything else for J/Psi
+Chi2Cut (default 100): keep only tracks with chi2 per d.o.f. < Chi2Cut
+PtCutMin (default 1): keep only tracks with transverse momentum > PtCutMin
+PtCutMax (default 10000): keep only tracks with transverse momentum < PtCutMax
+massMin (default 9.17 for Upsilon) keep only invariant masses with
+massMax (default 9.77 for Upsilon) massMin < mass < massMax
+
===========================================================
Still working ..............
===========================================================
git://git.uio.no / u / mrichter / AliRoot.git / blobdiff