Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Protect against and diagnose OrbitReset issues (AliceO2Group#7622)
* Protect against and diagnose OrbitReset issues This change adds the caching of the start-of-run and end-of-run timestamps in addition to the orbit-reset timestamp. It also validates that the calculated timestamp is within the run duration before adding it to the timestamp table. This ensures that only valid timestamps are used, improving the reliability of the data. * Add configurable option to make invalid timestamps fatal The changes introduce a new configurable option `fatalOnInvalidTimestamp` that allows the user to control the behavior when the timestamp information is not available in the CCDB. When set to `true`, the task will generate a fatal error, otherwise it will just log a warning. This gives the user more control over how to handle invalid timestamps. Additionally, the commit clarifies the meaning of the SOR/EOR timestamps, indicating that they can represent the start/end of the run, or the start/end of the sub-timeframe, depending on the run type.
- Loading branch information