]>
Commit | Line | Data |
---|---|---|
518eb852 | 1 | // $Id$ |
2 | ||
3 | /*! | |
4 | ||
5 | \page README_trigger README trigger | |
6 | ||
7 | ||
8 | \section trigger_s1 How to reprocess trigger decision from already produced digits | |
2ce5e44e | 9 | |
2ce5e44e | 10 | The MUONTrigger.C macro can be used to check the trigger algorithm w/o |
11 | having to (re-)perform simulation and digitalization. | |
12 | It loads the digits, erase TreeR and store the current trigger output in | |
13 | TreeR. | |
518eb852 | 14 | |
2ce5e44e | 15 | The different trigger outputs can be compared by looking at the GLT branch |
16 | of TreeD (filled during simulation) and the TC branch of TreeR (filled from | |
17 | a copy of TreeD during reconstruction or with this macro). | |
18 | Note: rec points from tracking chamber will be lost. | |
518eb852 | 19 | |
2ce5e44e | 20 | Usage: |
518eb852 | 21 | <pre> |
2ce5e44e | 22 | root [0] .L $ALICE_ROOT/MUON/MUONTrigger.C+ |
53958b19 | 23 | root [1] MUONTrigger("galice.root") |
518eb852 | 24 | </pre> |
25 | ||
2ce5e44e | 26 | |
518eb852 | 27 | \section trigger_s2 OFFLINE trigger GUI data quality and debugging tool |
2ce5e44e | 28 | |
2ce5e44e | 29 | - read digits and local trigger decision from simulated/real data |
30 | - display | |
31 | - reprocess trigger decision inside AliRoot | |
32 | - set x/y strips interactively on boards and transfer them to the AliRoot | |
33 | TriggerElectronics, execute trigger algorithm and recover the local trigger | |
34 | decision | |
35 | ||
518eb852 | 36 | To run: |
2ce5e44e | 37 | |
518eb852 | 38 | <pre> |
2ce5e44e | 39 | aliroot |
40 | new AliMUONTriggerGUI() | |
518eb852 | 41 | </pre> |
2ce5e44e | 42 | |
518eb852 | 43 | Main window shows the map of the local boards as seen from the I.P. |
44 | The main window is position sensitive (after file initialization) and it is | |
2ce5e44e | 45 | possible to open a GUI for a circuit. |
46 | ||
47 | By menus: | |
48 | ||
2ce5e44e | 49 | |
518eb852 | 50 | \subsection trigger_s2_sub1 File |
2ce5e44e | 51 | |
518eb852 | 52 | - Run - open a file and start with a given event number |
53 | takes the full path <path>/galice.root | |
54 | - Control - navigate in the tree with events | |
55 | - Exit - exit the main application | |
2ce5e44e | 56 | |
2ce5e44e | 57 | |
518eb852 | 58 | \subsection trigger_s2_sub2 Maps |
2ce5e44e | 59 | |
518eb852 | 60 | - Digits map - graphical map with digits in the four chambers, MT11 ... MT22 |
2ce5e44e | 61 | |
518eb852 | 62 | \subsection trigger_s2_sub3 Chambers digit maps window |
2ce5e44e | 63 | |
518eb852 | 64 | - Update - update the map after: |
2ce5e44e | 65 | - loading of another event |
66 | - changing interactively the strip signals in boards GUI | |
67 | ||
2ce5e44e | 68 | |
518eb852 | 69 | \subsection trigger_s2_sub4 Circuit |
70 | ||
71 | - Open - open a board GUI by circuit number | |
2ce5e44e | 72 | |
2ce5e44e | 73 | |
518eb852 | 74 | \subsection trigger_s2_sub5 Trigger |
2ce5e44e | 75 | |
518eb852 | 76 | - Trigger DSET - (re)run the trigger algorithm |
77 | ||
78 | ||
79 | \subsection trigger_s2_sub6 Circuit GUI window | |
2ce5e44e | 80 | |
81 | - visualize x/y strips | |
82 | - "Set/unset" x (or) y strips | |
83 | - "Digits" create board digits from the actual configuration created in the GUI | |
84 | - "Reset" reset modification on strips done interactively | |
85 | ||
2ce5e44e | 86 | |
518eb852 | 87 | \section trigger_s3 How to check integrated trigger efficiency |
2ce5e44e | 88 | |
2ce5e44e | 89 | The MUONTriggerEfficiency.C macro (included in the check scripts) calculates |
90 | the trigger efficiency for the 2 pt cuts. | |
91 | The output is stored in MUONTriggerEfficiency.out file. | |
518eb852 | 92 | |
2ce5e44e | 93 | Usage: |
518eb852 | 94 | <pre> |
2ce5e44e | 95 | root [0] .L $ALICE_ROOT/MUON/MUONTriggerEfficiency.C+ |
96 | root [1] MUONTriggerEfficiency() | |
518eb852 | 97 | </pre> |
98 | ||
2ce5e44e | 99 | For the CVS default version of the trigger LUT (i.e. lutAptLpt1Hpt1p7.root), |
100 | The reference for J/psi and Upsilon is as below | |
101 | For 1000 Jpsi events with: | |
518eb852 | 102 | <pre> |
2ce5e44e | 103 | AliGenParam *gener = new AliGenParam(1, AliGenMUONlib::kJpsi); |
104 | gener->SetMomentumRange(0,999); | |
105 | gener->SetPtRange(0,100.); | |
106 | gener->SetPhiRange(0., 360.); | |
107 | gener->SetCutOnChild(1); | |
108 | gener->SetChildPhiRange(0.,360.); | |
109 | gener->SetChildThetaRange(171.0,178.0); | |
110 | gener->SetOrigin(0,0,0); | |
111 | gener->SetForceDecay(kDiMuon); | |
112 | gener->SetTrackingFlag(1); | |
518eb852 | 113 | </pre> |
114 | ||
2ce5e44e | 115 | the output should be |
518eb852 | 116 | <pre> |
2ce5e44e | 117 | Efficiency Lpt cut = 0.7362 +/- 0.0391 |
118 | Efficiency Hpt cut = 0.2662 +/- 0.0201 | |
518eb852 | 119 | </pre> |
120 | ||
2ce5e44e | 121 | Similarly, for 1000 Upsilon events, the output should be |
518eb852 | 122 | |
123 | <pre> | |
2ce5e44e | 124 | Efficiency Lpt cut = 0.9806 +/- 0.0457 |
125 | Efficiency Hpt cut = 0.9537 +/- 0.0448 | |
518eb852 | 126 | </pre> |
127 | ||
128 | ||
129 | \section trigger_s4 How to check single muon trigger efficiency versus pt | |
2ce5e44e | 130 | |
2ce5e44e | 131 | The MUONTriggerEfficiencyPt.C macro produces trigger single muon efficiency |
132 | versus pt plots for the 2 pt cuts. | |
133 | Results are compared to the reference (red curves). | |
134 | To be used with (at least) 10000 events as follows | |
518eb852 | 135 | <pre> |
2ce5e44e | 136 | AliGenBox * gener = new AliGenBox(1); |
137 | gener->SetPtRange(0.,10.); | |
138 | gener->SetPhiRange(0., 360.); | |
139 | gener->SetThetaRange(171.000,178.001); | |
140 | gener->SetPart(13); // or -13 | |
141 | gener->SetOrigin(0.,0., 0.); | |
142 | gener->SetSigma(0.0, 0.0, 0.0); | |
518eb852 | 143 | </pre> |
144 | ||
2ce5e44e | 145 | Outputs are stored in MUONTriggerEfficiencyPt.gif/eps/out files |
146 | Important note: this macro works with one (real) muon track per event only | |
518eb852 | 147 | |
2ce5e44e | 148 | Usage: |
518eb852 | 149 | <pre> |
2ce5e44e | 150 | root [0] .L $ALICE_ROOT/MUON/MUONTriggerEfficiencyPt.C+ |
151 | root [1] MUONTriggerEfficiencyPt() | |
518eb852 | 152 | </pre> |
153 | ||
154 | ||
155 | \section trigger_s5 How to get trigger chamber efficiency from data | |
2ce5e44e | 156 | |
2ce5e44e | 157 | Trigger chamber efficiency map is calculated during reconstruction and saved in AliESDs.root |
158 | In order to view and save the map, use macro MUONTriggerChamberEfficiency.C | |
159 | ||
160 | To compile MUONTriggerChamberEfficiency.C | |
518eb852 | 161 | <pre> |
2ce5e44e | 162 | .includepath $ALICE_ROOT/MUON |
163 | .L $ALICE_ROOT/MUON/MUONTriggerChamberEfficiency.C+ | |
518eb852 | 164 | </pre> |
2ce5e44e | 165 | |
518eb852 | 166 | To run MUONTriggerChamberEfficiency.C |
167 | <pre> | |
2ce5e44e | 168 | MUONTriggerChamberEfficiency(); |
518eb852 | 169 | </pre> |
2ce5e44e | 170 | |
518eb852 | 171 | If you want to make the calculated map available for next simulation use option kTRUE, i.e. |
172 | <pre> | |
2ce5e44e | 173 | MUONTriggerChamberEfficiency(kTRUE); |
518eb852 | 174 | </pre> |
2ce5e44e | 175 | |
176 | When running next simulation, please remember to activate trigger efficiency | |
177 | by adding in Config.C: | |
518eb852 | 178 | <pre> |
2ce5e44e | 179 | MUON->SetTriggerEffCells(1); |
518eb852 | 180 | </pre> |
181 | ||
182 | */ | |
2ce5e44e | 183 |