+$Id$
+
How to test the Shuttle preprocessor(s) for MUON.
We will get two "logical" MUON preprocessors : one for the tracker and one for the trigger.
root[] const char* dateFileName = "raw.date"; // base filename for the output
root[] Int_t runNumber = 80; // run number used to fetch the pedestals from the OCDB
root[] Int_t nevents = 100; // # of events to generate. 100 should be enough
+root[] gSystem->Load("libMUONshuttle");
root[] AliMUONPedestalEventGenerator ped(runNumber,nevents,dateFileName);
root[] ped.Exec("");
The raw.date.LDC* files are then processed using the makeped online program
(currently found, pending an agreement on where to put online programs under cvs,
- under /afs/cern.ch/user/a/abaldiss/public/v15; Please contact Alberto to check
+ under /afs/cern.ch/user/a/abaldiss/public/v16; Please contact Alberto to check
it's the latest version) which outputs manus-*.ped ASCII files (one per LDC) :
- makeped -f raw.date.LCDi (i=0,1,2,3)
- mv manus-1.ped LDCi.ped
+ makeped -f raw.date.LCDi -a LDCi.ped (i=0,1,2,3)
(repeat for each LDC)
HV DCS values are created in CreateDCSAliasMap() of TestMUONPreprocessor.C
You might want to modify this function to create a given set of error conditions
in order to test whether the HVSubprocessor is reacting properly to those errors.
-
+
+-------
+GMS
+-------
+
+The GMS alignment data for testing can be generated with
+the macro MUONGenerateTestGMS.C:
+The matrices of TGeoHMatrix type, with TObject::fUniqueID equal to the geometry
+module Id, are put in a TClonesArray and saved in the Root file with a
+key "GMSarray".