2 ===========================================================
3 How to reprocess trigger decision from already produced digits
4 ===========================================================
5 The MUONTrigger.C macro can be used to check the trigger algorithm w/o
6 having to (re-)perform simulation and digitalization.
7 It loads the digits, erase TreeR and store the current trigger output in
9 The different trigger outputs can be compared by looking at the GLT branch
10 of TreeD (filled during simulation) and the TC branch of TreeR (filled from
11 a copy of TreeD during reconstruction or with this macro).
12 Note: rec points from tracking chamber will be lost.
14 root [0] .L $ALICE_ROOT/MUON/MUONTrigger.C+
15 root [1] MUONTrigger()
18 ===========================================================
19 OFFLINE trigger GUI data quality and debugging tool
20 ===========================================================
21 - read digits and local trigger decision from simulated/real data
23 - reprocess trigger decision inside AliRoot
24 - set x/y strips interactively on boards and transfer them to the AliRoot
25 TriggerElectronics, execute trigger algorithm and recover the local trigger
36 new AliMUONTriggerGUI()
41 "Map of the local boards as seen from the I.P."
43 the main window is position sensitive (after file initialization) and it is
44 possible to open a GUI for a circuit.
51 Run - open a file and start with a given event number
52 takes the full path <path>/galice.root
54 Control - navigate in the tree with events
56 Exit - exit the main application
61 Digits map - graphical map with digits in the four chambers, MT11 ... MT22
63 Chambers digit maps window
64 --------------------------
66 Update - update the map after:
67 - loading of another event
68 - changing interactively the strip signals in boards GUI
73 Open - open a board GUI by circuit number
78 Trigger DSET - (re)run the trigger algorithm
83 - visualize x/y strips
84 - "Set/unset" x (or) y strips
85 - "Digits" create board digits from the actual configuration created in the GUI
86 - "Reset" reset modification on strips done interactively
89 vulpescu@clermont.in2p3.fr
93 ===========================================================
94 How to check integrated trigger efficiency
95 ===========================================================
96 The MUONTriggerEfficiency.C macro (included in the check scripts) calculates
97 the trigger efficiency for the 2 pt cuts.
98 The output is stored in MUONTriggerEfficiency.out file.
100 root [0] .L $ALICE_ROOT/MUON/MUONTriggerEfficiency.C+
101 root [1] MUONTriggerEfficiency()
102 For the CVS default version of the trigger LUT (i.e. lutAptLpt1Hpt1p7.root),
103 The reference for J/psi and Upsilon is as below
104 For 1000 Jpsi events with:
105 AliGenParam *gener = new AliGenParam(1, AliGenMUONlib::kJpsi);
106 gener->SetMomentumRange(0,999);
107 gener->SetPtRange(0,100.);
108 gener->SetPhiRange(0., 360.);
109 gener->SetCutOnChild(1);
110 gener->SetChildPhiRange(0.,360.);
111 gener->SetChildThetaRange(171.0,178.0);
112 gener->SetOrigin(0,0,0);
113 gener->SetForceDecay(kDiMuon);
114 gener->SetTrackingFlag(1);
116 Efficiency Lpt cut = 0.7362 +/- 0.0391
117 Efficiency Hpt cut = 0.2662 +/- 0.0201
118 Similarly, for 1000 Upsilon events, the output should be
119 Efficiency Lpt cut = 0.9806 +/- 0.0457
120 Efficiency Hpt cut = 0.9537 +/- 0.0448
122 ===========================================================
123 How to check single muon trigger efficiency versus pt
124 ===========================================================
125 The MUONTriggerEfficiencyPt.C macro produces trigger single muon efficiency
126 versus pt plots for the 2 pt cuts.
127 Results are compared to the reference (red curves).
128 To be used with (at least) 10000 events as follows
129 AliGenBox * gener = new AliGenBox(1);
130 gener->SetPtRange(0.,10.);
131 gener->SetPhiRange(0., 360.);
132 gener->SetThetaRange(171.000,178.001);
133 gener->SetPart(13); // or -13
134 gener->SetOrigin(0.,0., 0.);
135 gener->SetSigma(0.0, 0.0, 0.0);
136 Outputs are stored in MUONTriggerEfficiencyPt.gif/eps/out files
137 Important note: this macro works with one (real) muon track per event only
139 root [0] .L $ALICE_ROOT/MUON/MUONTriggerEfficiencyPt.C+
140 root [1] MUONTriggerEfficiencyPt()
142 ===========================================================
143 How to get trigger chamber efficiency from data
144 ===========================================================
145 Trigger chamber efficiency map is calculated during reconstruction and saved in AliESDs.root
146 In order to view and save the map, use macro MUONTriggerChamberEfficiency.C
148 To compile MUONTriggerChamberEfficiency.C
149 .includepath $ALICE_ROOT/MUON
150 .L $ALICE_ROOT/MUON/MUONTriggerChamberEfficiency.C+
152 // To run MUONTriggerChamberEfficiency.C
153 MUONTriggerChamberEfficiency();
155 //If you want to make the calculated map available for next simulation use option kTRUE, i.e.
156 MUONTriggerChamberEfficiency(kTRUE);
158 When running next simulation, please remember to activate trigger efficiency
159 by adding in Config.C:
160 MUON->SetTriggerEffCells(1);