-
Notifications
You must be signed in to change notification settings - Fork 446
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EMCAL-565, EMCAL-566]: Differentiate between run type and max time d… #12848
Conversation
REQUEST FOR PRODUCTION RELEASES:
This will add The following labels are available |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good
Error while checking build/O2/fullCI for b28c633 at 2024-03-13 22:05:
Full log here. |
…ifference for loading of calib hists - Online calibration relies on saving and loading the calibration histograms at the EOR (SOR) - However, the old objects should not be loaded if the run type (calib, physics etc.) differes, or if the time difference between the old object and the current data taking is too long - Now, the root file storing the objects is named differently, depending on the run type - The old timestamp (in hours) is stored in the file itself and then loaded at SOR and compared to the current ts - The fill Nr is stored in the file and an option is implemented to only load calibration objects if the fill is the same as for the old object - All parameters are configurable in the Calib Params
…ifference for loading of calib hists (AliceO2Group#12848) - Online calibration relies on saving and loading the calibration histograms at the EOR (SOR) - However, the old objects should not be loaded if the run type (calib, physics etc.) differes, or if the time difference between the old object and the current data taking is too long - Now, the root file storing the objects is named differently, depending on the run type - The old timestamp (in hours) is stored in the file itself and then loaded at SOR and compared to the current ts - The fill Nr is stored in the file and an option is implemented to only load calibration objects if the fill is the same as for the old object - All parameters are configurable in the Calib Params Co-authored-by: jokonig <[email protected]>
…ifference for loading of calib hists (AliceO2Group#12848) - Online calibration relies on saving and loading the calibration histograms at the EOR (SOR) - However, the old objects should not be loaded if the run type (calib, physics etc.) differes, or if the time difference between the old object and the current data taking is too long - Now, the root file storing the objects is named differently, depending on the run type - The old timestamp (in hours) is stored in the file itself and then loaded at SOR and compared to the current ts - The fill Nr is stored in the file and an option is implemented to only load calibration objects if the fill is the same as for the old object - All parameters are configurable in the Calib Params Co-authored-by: jokonig <[email protected]>
…ifference for loading of calib hists (AliceO2Group#12848) - Online calibration relies on saving and loading the calibration histograms at the EOR (SOR) - However, the old objects should not be loaded if the run type (calib, physics etc.) differes, or if the time difference between the old object and the current data taking is too long - Now, the root file storing the objects is named differently, depending on the run type - The old timestamp (in hours) is stored in the file itself and then loaded at SOR and compared to the current ts - The fill Nr is stored in the file and an option is implemented to only load calibration objects if the fill is the same as for the old object - All parameters are configurable in the Calib Params Co-authored-by: jokonig <[email protected]>
…ifference for loading of calib hists