Check that start _time_ in IOVs files is strictly monothonic
Consecutive start times in IOVs
file must be different and increasing.
The case
- 0 a
- 1 b
- 1 c
is strictly equivalent to just
- 0 a
- 1 c
so we should check and print a warning for the unused entry.
Something like
- 0 a
- 2 b
- 1 c
- 3 d
would cause inconsistent and wrong IOVs, so it should reported as an error (exception).
We need
-
runtime checks -
tools to validate the IOVs
files (e.g. Python scripts)