MUONtrgda.cxx:
[u/mrichter/AliRoot.git] / MUON / READMEmtrda.txt
CommitLineData
3e42bf30 1// $Id$
2
3/*!
4
5\page README_mtrda Trigger DA
6
7The detector algorithm is implemented for the Muon Trigger in the AliRoot framework.
8The main code is located in MUONTRGda.cxx and it runs in the MUON Trigger LDC.
9
10\section da_s1 The Muon Trigger Calibration
11
12The main goal of the DA is the transfert of the modified configuration files to the FES.
13The configuration files stored in the online DB are the following:
14
15MtgGlobalCrate-<version>.dat: contains the global crate information
16MtgRegionalCrate-<version>.dat: contains the regional crate information
17MtgLocalMask-<version>.dat: contains the local mask
18MtgLocalLut-<version>.dat: contains the local LUT
19MtgCurrent.dat: contains the name list of the above files with their version
20 and the flag for master/slave status on the DA
21
22The copy onto the FES for the modified local masks is only done when the flag is set to master for the DA.
23The DA creates a file (ExportedFiles.dat) containing the name of the files to be transfert by the shuttle.
24To be able to check the change of version of one the files, another file is created containing the last current
25list of configuration files: MtgLastCurrent.dat.
26The Muon trigger electronics could run with two types of calibration:
27
28\subsection da_ss1 ELECTRONICS_CALIBRATION_RUN (calib)
29
30This procedure allows to check dead channels. The FET pulses are injected to the 21 kchannels.
31
32The typical ECS sequence for calib is :
33
34- Switch ON the electronics LV
35- Load Configuration via the MTS package
36- Enable FET pulse
37- Data taking (typically 100 events)
38- The DA computes the occupancy, if a channel is not responding in 80% of the case, it will be marked as dead
39- The DA update the local mask file accordingly and put it on the File Exchange Server
40
41Then the SHUTTLE process the ASCII files and store the configuration on the OCDB
42
43This option is disable for the moment.
44
45\subsection da_ss2 DETECTOR_CALIBRATION_RUN (ped)
46
47This procedure checks the noisy channels. A normal physics run is performed.
48
49The typical ECS sequence for calibration is :
50
51- Switch ON the electronics LV
52- Load Configuration via the MTS package
53- Data taking (typically 100 events)
54- The DA computes the occupancy, if a channel is responding in 80% of the case, it will be marked as noisy
55- The DA update the local mask file accordingly and put it on the File Exchange Server
56
57Then the SHUTTLE process the ASCII files and store the configuration on the OCDB
58
59\section da_s2 Using the DA Online
60
61You have a line command help. To have it just type :
62
63\verbatim
64> MUONTRGda.exe -h
65
66******************* MUONTRGda.exe usage **********************
67MUONTRGda.exe -options, the available options are :
68-h help (this screen)
69
70 Input
71-f <raw data file> (default = )
72
73 output
74-r <root file> (default = none)
75
76 Options
77-t <threshold values> (default = 0.2)
78-d <print level> (default = 0)
79-s <skip events> (default = 0)
80-n <max events> (default = 1000000)
81-e <execute ped/calib> (default = nil)
82
83\endverbatim
84
85
86\section da_s3 In case of trouble
87
88Please contact:
89
90Franck Manso: manson@clermont.in2p3.fr
91
92or
93
94Christian Finck: finck@subatech.in2p3.fr (until 01 Septembre 08)
95
96
97This chapter is defined in the READMEmtrda.txt file.
98*/
99