Draft: Update to Gaudi v36r5.002 and FieldMapCondAlg fixes
Update to Gaudi v36r5.002 which fixes a bug in the EventIDRange construction: gaudi/Gaudi!1347 (merged).
Fixing this bug uncovered several further bugs that are fixed as part of this MR:
- The
AtlasFieldMapCDO depends on run-lumi-indexed field-maps and time-stamp-indexed DCS data (magnet currents). So it has to be a mixed container. This MR fixes this problem. - The
AtlasFieldMapCondAlgdid not intersect with the output IOV-range with the range of the currents reads from DCS. This has a (hopefully small) impact on the run-2 reprocessing. Fixed by this MR. - The HLT athena-based workflow executed
AtlasFieldMapCondAlgwith an invalid event context (because runs it in the start transition, before the event context is known). This feature should only ever had been used when running athenaHLT or in a partition. Move the setting ofLoadMapOnStartto an HLT-specific job option.
cc @fwinkl
Relates to ATR-25671, ATLASRECTS-7086.
Edited by Frank Winklmeier