![]() |
AliRoot Core
edcc906 (edcc906)
|
Macro to add an AliMUONAlignmentTask to an analysis train. More...
Go to the source code of this file.
Functions | |
AliMUONAlignmentTask * | AddTaskMuonAlignment (TString oldAlignmentOCDB, TString newAlignmentOCDB, Bool_t doAlignment=kTRUE, Bool_t writeRecords=kTRUE, Bool_t readRecords=kFALSE) |
Macro to add an AliMUONAlignmentTask to an analysis train.
Definition in file AddTaskMuonAlignment.C.
AliMUONAlignmentTask* AddTaskMuonAlignment | ( | TString | oldAlignmentOCDB, |
TString | newAlignmentOCDB, | ||
Bool_t | doAlignment = kTRUE , |
||
Bool_t | writeRecords = kTRUE , |
||
Bool_t | readRecords = kFALSE |
||
) |
AliMUONAlignmentTask calculates alignment correction for the muon spectrometer based on reconstructed tracks, either with or without magnetic field. It uses AliMillePede2 internally for alignment, and AliMillePedeRecords for storing the derivatives.
The task has two ways of operation
1/ Full mode: This corresponds to flags: readRecords = kFALSE, doAlignment = kTRUE, writeRecords = kFALSE
Note that writeRecords can also be set to kTRUE. This will output all derivatives to a special branch in an AOD for re-running the alignment with no need to process the tracks (see below)
2/ Split mode: The task must run twice. First pass with flags: readRecords = kFALSE, writeRecords = kTRUE, doAlignment = kFALSE This
Second pass with flags: readRecords = kTRUE, doAlignment = kTRUE
The split mode is usefull for running on the grid:
When performing the alignment (doAlignment=kTRUE), one can "fix", "group", or "constrain" detector's alignment parameters in order to ease the inversion.
One can redo the second pass as many times as needed, changing these "fixed/group/constrained" parameters, without re-processing the ESD tracks.
Creates a Muon Alignment task and adds it to the analysis manager.
Definition at line 56 of file AddTaskMuonAlignment.C.