-
Notifications
You must be signed in to change notification settings - Fork 483
DPL Analysis: centralised CCDB support in analysis #14567
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
Conversation
|
REQUEST FOR PRODUCTION RELEASES: This will add The following labels are available |
|
Error while checking build/O2/fullCI_slc9 for a7b2795 at 2025-08-10 18:36: Full log here. |
|
Still to do:
|
|
With this the example (o2TestAnalysisCCDB.cxx) of the centralised CCDB for analysis tasks actually works. I need to do some cleanup before I can merge this, and I need to check I did not break the non analysis CCDB access, but we should not be far. |
|
Error while checking build/O2/fullCI_slc9 for 71abb21 at 2025-08-20 21:53: Full log here. |
Thanks to the newly added binary view columns we can finally support proper CCDB integration in analysis. In order to do so, the user needs to create a TIMESTAMPED table, i.e. a table which is an extension of another one where the timestamps for each rows are provided. The extra columns of such timestamped table will be CCDB columns where the iterator of each provides access for one specified CCDB object. Notice the PR duplicates the CCDB code run in reconstruction and the additional device will never be added to the topology if running online, so there are no expected side effects.
|
Despite the large size, this PR only introduces new features so it should be relatively safe to merge. In particular I took extra care in making sure the code is not enabled at all in online more and I duplicated anything which might have been used also by the reconstruction CCDB fetcher, to minimise risks. This has also been tested on HyperLoop with no regressions in Correlations and Histograms, as expected. Merging. |
Thanks to the newly added binary view columns we can finally support proper CCDB integration in analysis. In order to do so, the user needs to create a TIMESTAMPED table, i.e. a table which is an extension of another one where the timestamps for each rows are provided. The extra columns of such timestamped table will be CCDB columns where the iterator of each provides access for one specified CCDB object. Notice the PR duplicates the CCDB code run in reconstruction and the additional device will never be added to the topology if running online, so there are no expected side effects.
Thanks to the newly added binary view columns we can finally support
proper CCDB integration in analysis.
In order to do so, the user needs to create a TIMESTAMPED table, i.e. a table
which is an extension of another one where the timestamps for each rows
are provided. The extra columns of such timestamped table will be CCDB columns
where the iterator of each provides access for one specified CCDB object.
Notice the PR duplicates the CCDB code run in reconstruction and the additional
device will never be added to the topology if running online, so there are no expected
side effects.