3 How to test the Shuttle preprocessor(s) for MUON.
5 We will get two "logical" MUON preprocessors : one for the tracker and one for the trigger.
6 Both will manage several subtasks (e.g. the tracker one will handle pedestals,
7 gains and deadchannels, while the trigger one will handle masks and trigger lut)
8 "Physically", only one class will manage both the tracker and the trigger : AliMUONPreprocessor.
9 Depending on the subsystem and on the task to be performed (based on the run type), this class
10 will instanciate the correct set of AliMUONVSubProcessor(s) which does the actual job.
11 Output of most processors will end up in OCDB (Offine Condition DataBase). A set of helper functions
12 to peek at this OCDB are gathered in AiMUONCDB class.
15 TestMUONPreprocessor.C
18 This is the master macro used to check the MUON part of the Shuttle.
19 Depending on what you want to test, you'll have to modify the input files
20 (using shuttle->AddInputFile) and/or the run type (using shuttle->AddInputRunParameter())
23 AliMUONPreprocessor(const TString& detName)
26 Depending on how this one is constructed, and depending on the runtype, it will
27 perform differents tasks. Note that for the moment the runtypes are "fake", i.e.
28 put by hand in the TestMUONPreprocessor.C macro, and might not correspond to
29 the final values to be used by the DAQ.
31 detName runType task to be done worker class (AliMUONVSubprocessor child)
32 --------------------------------------------------------------------------------------------------------
33 MCH PEDESTAL_RUN read ASCII ped files AliMUONPedestalSubprocessor
34 and put them into OCDB
36 MCH GMS read GMS alignment files AliMUONGMSSubprocessor
37 and put them into OCDB
39 MCH PHYSICS read DCS HV values and AliMUONHVSubprocessor
42 MCH ELECTRONICS_CALIBRATION_RUN read ASCII gain files prototype only = AliMUONGainSubprocessor
43 and put them into OCDB
45 MTR to be defined to be defined to be done
51 Two options here. You can either use a pre-done set of ASCII pedestals files (generated as
52 explained below for the 2nd option), located at /afs/cern.ch/user/l/laphecet/public/LDC*.ped,
55 We've written an AliMUONPedestalEventGenerator which creates fake pedestal events. The pedestal values
56 are taken from the Offline Condition DataBase (OCDB) (which is itself fakely filled
57 using the WritePedestals() method of AliMUONCDB class
59 So first generate a valid pedestal CDB entry but using the AliMUONCDB class
61 root[] const char* cdbpath="local://$ALICE_ROOT/SHUTTLE/TestShuttle/TestCDB"; // where to put the CDB
62 root[] AliMUONCDB cdb(cdbpath)
63 root[] Bool_t defaultValues = kFALSE; // to generate random values instead of plain zeros...
64 root[] Int_t startRun = 80;
65 root[] Int_t endRun = 80;
66 root[] cdb.WritePedestals(defaultValues, startRun, endRun);
68 Expected output is (don't worry about the warnings, they are harmless) :
70 I-AliMUONCDB::ManuList: Generating ManuList...
71 I-AliMUONCDB::ManuList: Manu List generated.
72 I-AliMUONCDB::MakePedestalStore: 16828 Manus and 1064008 channels.
73 I-AliMUONCDB::WritePedestals: Ngenerated = 1064008
74 I-AliCDBManager::Init: AliEn classes enabled in Root. AliCDBGrid factory registered.
75 I-AliCDBManager::SetDefaultStorage: Setting Default storage to: local://$ALICE_ROOT/SHUTTLE/TestShuttle/TestCDB
76 I-AliCDBLocal::PutEntry: CDB object stored into file ($ALICE_ROOT)/SHUTTLE/TestShuttle/TestCDB/MUON/Calib/Pedestals/Run80_80_v0_s0.root
78 Then use the AliMUONPedestalEventGenerator to produce simulated pedestal events.
81 root[] AliCDBManager::Instance()->SetDefaultStorage(cdbpath); // so you will read
82 // back pedestals values generated in the previous step
83 root[] const char* dateFileName = "raw.date"; // base filename for the output
84 root[] Int_t runNumber = 80; // run number used to fetch the pedestals from the OCDB
85 root[] Int_t nevents = 100; // # of events to generate. 100 should be enough
86 root[] gSystem->Load("libMUONshuttle"); // needed or not depending on whether it's already loaded or not
87 root[] AliMUONPedestalEventGenerator ped(runNumber,nevents,dateFileName);
90 It *will* take a lot of time (mainly due to the fact that we're writting a
91 bunch of ASCII files = DDL files), so please be patient.
93 The output should be the normal simulated sequence of MUON.Hits.root, MUON.SDigits.root,
94 MUON.Digits.root, raw/*.ddl files and raw.date.LDCi where i=0-3 (i.e. one DATE file
95 per LDC, as will be used in real life), the latter ones being roughly 100 MB each.
97 The raw.date.LDC* files are then processed using the makeped online program
98 (currently found, pending an agreement on where to put online programs under cvs,
99 under /afs/cern.ch/user/a/abaldiss/public/v16; Please contact Alberto to check
100 it's the latest version) which outputs manus-*.ped ASCII files (one per LDC) :
102 makeped -f raw.date.LCDi -a LDCi.ped (i=0,1,2,3)
104 (repeat for each LDC)
106 The LDCi.ped files are the input for the pedestal subprocessor,
107 which is tested using the TestMUONPreprocessor.C macro.
108 The output of the pedestal subprocessor (upon success only) is written into the OCDB.
109 Difference between the input and the output can be inferred using the diff() function
117 HV DCS values are created in CreateDCSAliasMap() of TestMUONPreprocessor.C
118 You might want to modify this function to create a given set of error conditions
119 in order to test whether the HVSubprocessor is reacting properly to those errors.
125 The GMS alignment data for testing can be generated with
126 the macro MUONGenerateTestGMS.C:
127 The matrices of TGeoHMatrix type, with TObject::fUniqueID equal to the geometry
128 module Id, are put in a TClonesArray and saved in the Root file with a