OpenIntervals: Difference between revisions
(Created page with "==Introduction== ==Examples==") |
|||
| Line 1: | Line 1: | ||
==Introduction== | ==Introduction== | ||
As explained more in [[ConditionsData]], the standard conditions database has "closed intervals". When a calibration is assigned to run range, the range must have a beginning and an end. If an executable attempts to retrieve calibrations outside the known intervals, the job throws an error. This style require more maintenance, but allows precise control and reproducibility of conditions. The "open intervals" reduces the reproducibility but is simpler to maintain. In this style calibrations are typically assigned an open run range. The interval start from a given run where the calibration was created, but there is no end to the interval. Requests for calibrations for future runs will be matched to last open interval. At some point in the future a new calibration is created, a new open interval is added, and this calibration takes over as the valid content for future runs. If a patch is required, it is added with a start and end to the patch period. | |||
==Examples== | ==Examples== | ||
Revision as of 22:26, 18 April 2025
Introduction
As explained more in ConditionsData, the standard conditions database has "closed intervals". When a calibration is assigned to run range, the range must have a beginning and an end. If an executable attempts to retrieve calibrations outside the known intervals, the job throws an error. This style require more maintenance, but allows precise control and reproducibility of conditions. The "open intervals" reduces the reproducibility but is simpler to maintain. In this style calibrations are typically assigned an open run range. The interval start from a given run where the calibration was created, but there is no end to the interval. Requests for calibrations for future runs will be matched to last open interval. At some point in the future a new calibration is created, a new open interval is added, and this calibration takes over as the valid content for future runs. If a patch is required, it is added with a start and end to the patch period.