/galice.root
-- Control - navigate in the tree with events
-- Exit - exit the main application
+- "Run input" - open a file and start with a given event number:
+ - "your_path/galice.root" to use simulated (or re-created) aliroot digits
+ - confirm with "Apply (galice)"
+ - "your_path/rawfilename.root" to use raw data in root format
+ - confirm with "Apply (raw)"
+- "Control" - navigate in the tree with events
+- "Exit" - exit the main application
\subsection trigger_s2_sub2 Maps
-- Digits map - graphical map with digits in the four chambers, MT11 ... MT22
+- "Digits map" - graphical map showing digits in the four chambers, MT11 ... MT22
+- "Reset digits" - clean the digits map
-\subsection trigger_s2_sub3 Chambers digit maps window
+\subsection trigger_s2_sub3 Chambers digit maps
-- Update - update the map after:
+- "Update" - update the map after:
- loading of another event
- changing interactively the strip signals in boards GUI
\subsection trigger_s2_sub4 Circuit
-- Open - open a board GUI by circuit number
-
+- "Open" - open a board GUI by circuit (board) number
-\subsection trigger_s2_sub5 Trigger
-- Trigger DSET - (re)run the trigger algorithm
+\subsection trigger_s2_sub5 TriggerDSET, run the trigger algorithm with interactively set strips
+- this is an interface to AliMUONTriggerElectronics
+- "Digit store" - create a digit store (object) with the current board digits (input from the circuit GUI)
+- "Trigger store" - create a trigger store (object) from the digit store, using AliMUONTriggerElectronics;
+each type of store can be "cleared" and "printed"
+- "Front End Test" - simulate a FET (all strips fire) on all boards or on a regional board
+- "Write raw data" - save the trigger store in a raw data file (DATE and ROOT) format
-\subsection trigger_s2_sub6 Circuit GUI window
+\subsection trigger_s2_sub6 Circuit GUI ("Circuit/Open" or click on boards map)
-- visualize x/y strips
-- "Set/unset" x (or) y strips
+- the window title shows the name of the board, the number and the status
+- "Draw" visualize x/y strips
+- "Set/unset" x (or) y strips, on mouse click
- "Digits" create board digits from the actual configuration created in the GUI
- "Reset" reset modification on strips done interactively
+The sequence to test the trigger algorithm is:
+- open a board GUI
+- set some x/y strips
+- press "Digits" to create board digits
+- from the TrigerDSET menu create a digit store, then a trigger store and print it to see the trigger
+decision
+- write raw data for further investigation
\section trigger_s3 How to check integrated trigger efficiency
@@ -96,7 +111,17 @@ root [0] .L $ALICE_ROOT/MUON/MUONTriggerEfficiency.C+
root [1] MUONTriggerEfficiency()
-For the CVS default version of the trigger LUT (i.e. lutAptLpt1Hpt1p7.root),
+Two LUTs are stored in the CDB (/Calib/TriggerLut/):
+- Run0_999999999_v0_s0.root with Lpt 1.0 GeV and Hpt 1.7 GeV
+- Run0_999999999_v1_s0.root with Lpt 0.0 GeV and Hpt 1.0 GeV (default)
+
+and can be built with the AliMUONCDB class taking as source the root files
+(found in $ALICE_ROOT/MUON/data/):
+- lutAptLpt1Hpt1p7.root
+- lutAptAptLpt1.root
+
+respectively.
+
The reference for J/psi and Upsilon is as below
For 1000 Jpsi events with:
@@ -114,15 +139,16 @@ The reference for J/psi and Upsilon is as below
the output should be
- Efficiency Lpt cut = 0.7362 +/- 0.0391
- Efficiency Hpt cut = 0.2662 +/- 0.0201
+ Efficiency Lpt cut = 0.9061 +/- 0.0456
+ Efficiency Hpt cut = 0.6943 +/- 0.0376
- Similarly, for 1000 Upsilon events, the output should be
+ Similarly, for 1000 Upsilon events (replace kJpsi by kUpsilon), the output
+should be
- Efficiency Lpt cut = 0.9806 +/- 0.0457
- Efficiency Hpt cut = 0.9537 +/- 0.0448
+ Efficiency Lpt cut = 0.9872 +/- 0.0458
+ Efficiency Hpt cut = 0.9851 +/- 0.0457
@@ -154,7 +180,8 @@ root [1] MUONTriggerEfficiencyPt()
\section trigger_s5 How to get trigger chamber efficiency from data
-Trigger chamber efficiency map is calculated during reconstruction and saved in AliESDs.root
+Trigger chamber efficiency map is calculated from AliESDs.root with the analysis task: PWG3/muon/AliMUONTriggerChamberEff.
+The output of the task is a file filename="MUON.TriggerEfficiencyMap.root" containing the numerator and denominator histograms for the efficiency calculation.
In order to view and save the map, use macro MUONTriggerChamberEfficiency.C
To compile MUONTriggerChamberEfficiency.C
@@ -165,12 +192,24 @@ To compile MUONTriggerChamberEfficiency.C
To run MUONTriggerChamberEfficiency.C
-MUONTriggerChamberEfficiency();
+MUONTriggerChamberEfficiency("filename");
+
+
+If you want to make the calculated map available for next simulation use option kTRUE, and specify the run validity:
+
+MUONTriggerChamberEfficiency("filename",kTRUE,firstRun,lastRun);
-If you want to make the calculated map available for next simulation use option kTRUE, i.e.
+The last option allows to set the efficiency of each board of an RPC with the mean value of the chamber: this is useful when the efficiency was calculated with low statistics (like in cosmic runs).
-MUONTriggerChamberEfficiency(kTRUE);
+MUONTriggerChamberEfficiency("filename",kFALSE,firstRun,lastRun,kTRUE);
+
+
+Finally, to have a look to the map stored in the OCDB for the run runNumber, do:
+
+.includepath $ALICE_ROOT/MUON
+.L $ALICE_ROOT/MUON/MUONTriggerChamberEfficiency.C+
+ShowOCDBmap(runNumber)
When running next simulation, please remember to activate trigger efficiency
@@ -179,5 +218,7 @@ by adding in Config.C:
MUON->SetTriggerEffCells(1);
+This chapter is defined in the READMEtrigger.txt file.
+
*/