-
Type:
Story
-
Status: Done (View Workflow)
-
Priority:
Normal
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Sprint:2DDRP-2022 C
Calibration validity ranges is currently determined through a validity period specified when running ingestPfsCalibs.py, and where there are overlaps the midpoint is used. However, we want to use a mode where calibs are valid from the point the data used to construct them was taken until they are superseded. There appears to be a configuration variable for this: validityUntilSuperseded.
- relates to
-
PIPE2D-1039 Butler does not find matching object if validity ranges match taiObs exactly
-
- Done
-