You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Optionally apply BC shift to triggered detectors in CTF decoding
The TriggerOffsetsParam configurableParam got array of custom corrections per detector (0 by default)
which can be applied to triggered detectors IR as an ADDITIVE correction during CTF decoding.
Note that this convention is opposite to that for the LM_L0 convention which is subtracted from the
encoded IR (at the moment only for the TRD if an option --correct-trd-trigger-offset was provided to the
ctf-reader). Therefore, for the TRD, if this option is ON, the effect of the correction is
ir_corrected = ir_decoded - TriggerOffsetsParam::LM_L0 + TriggerOffsetsParam::customOffset[TRD];
while for other EMC,PHS,CPV and HMP (and TRD in absence of --correct-trd-trigger-offset) it is simply
ir_corrected = ir_decoded + TriggerOffsetsParam::customOffset[<det>];
In case the correction moves the IR before the TF 1st orbit, the trigger is discarded.
Extra: ZDC in pbpb2022 was reseting the orbit internally to 1 at the SOR: implemented the shift also for it.
0 commit comments