-
Notifications
You must be signed in to change notification settings - Fork 433
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
ZDC data model change #10973
ZDC data model change #10973
Conversation
Fixes and move of ZDC channel ids
Please consider the following formatting changes to AliceO2Group#10973
@@ -2522,7 +2573,11 @@ DataProcessorSpec getAODProducerWorkflowSpec(GID::mask_t src, bool enableSV, boo | |||
outputs.emplace_back(OutputLabel{"O2ambiguousMFTtrack"}, "AOD", "AMBIGUOUSMFTTR", 0, Lifetime::Timeframe); | |||
outputs.emplace_back(OutputLabel{"O2ambiguousFwdtrack"}, "AOD", "AMBIGUOUSFWDTR", 0, Lifetime::Timeframe); | |||
outputs.emplace_back(OutputLabel{"O2v0_001"}, "AOD", "V0_001", 0, Lifetime::Timeframe); | |||
#ifdef O2_ZDC_NEWDATAMODEL | |||
outputs.emplace_back(OutputLabel{"O2zdc_001"}, "AOD", "ZDC_001", 0, Lifetime::Timeframe); |
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.
This is incorrect, it should be "ZDC", 1
, the version for AOD tables is encoded in subspec.
Update: the same goes for V0 table above, the only reason this works is that AOD producer's output is not used directly by tasks.
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.
OK, this is wrong for all of them. See v0, cascade, collision etc. So it seems to work but is not good of course...
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.
Shall we change this everywhere? Or we keep doing as is? What do you think?
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.
Probably better to do the rest in a separate PR, for bookkeeping reasons.
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.
You mean the rest or all of them? What do you think? :-D
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.
ZDC should be done correctly from the start here, I think. The rest can be fixed elsewhere so we do not mix them with ZDC-specific change.
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.
So we include in this PR all the fixes for the ZDC and then another request will be open for the remaining issues, correct?
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.
Okay, the latest PR does as you suggested, @aalkin ! Can you please check if I did no do anything major wrong? (technically, though, it's in the part of the producer that is as-of-yet disabled, but I want to be sure it's ok already). If this is fine I would suggest we go ahead and merge so I can do a PR for the O2Physics part. Thanks!!!
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.
I have posted a few comments for cosmetic changes but the rest is fine with me
Co-authored-by: Jan Fiete <jgrosseo@cern.ch>
move `legacy` to `_000` Co-authored-by: Jan Fiete <jgrosseo@cern.ch>
Please consider the following formatting changes to AliceO2Group#10973
Please consider the following formatting changes to AliceO2Group#10973
Marked as ready to review to trigger all checks already (while also waiting for @aalkin 's green light). Thanks! |
Error while checking build/O2/fullCI for a182c90 at 2023-04-04 03:35:
Full log here. |
Is the PR for the converter already there (as draft)? |
I don't think I PR-ed it but I have it in my fork here. I will do a PR as soon as this is merged; anyway now I see some CI errors that I have to look into for O2Physics. More soon... |
Please consider the following formatting changes to AliceO2Group#10973
@@ -728,12 +731,317 @@ DECLARE_SOA_COLUMN(TimeZNC, timeZNC, float); //! | |||
DECLARE_SOA_COLUMN(TimeZPA, timeZPA, float); //! | |||
DECLARE_SOA_COLUMN(TimeZPC, timeZPC, float); //! | |||
} // namespace zdc | |||
namespace zdc_001 // Revised table, required for dynamic in-place replacements |
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.
Please use the same namespace, the versioning should only be done at the table level, otherwise you will have to rename the namespace later.
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.
Hi Anton, as explained in the comment inside the code, I need to have different namespaces to have different types of columns with the same names: we are swapping out a regular column with a dynamic column in the new version of the table, and these have the same exact name. This cannot be done keeping the same namespace, unfortunately...
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.
Since the columns will have different type, they may as well have a different name. In fact, you can rename old columns (only the type names, not the getters). This will be transparent for the users, since they are only using the getters.
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.
The latest commit should take care: it uses only the zdc
namespace but changes the column names for the dynamic columns while keeping the same getters. Can you please take a look @aalkin ? Thanks a lot!
Error while checking build/O2/fullCI for b8f8703 at 2023-04-04 15:10:
Full log here. |
Please consider the following formatting changes to AliceO2Group#10973
Error while checking build/O2/fullCI for aa608f9 at 2023-04-04 22:05:
Full log here. |
Okay, so the latest CI errors seem unrelated and the code does compile in the regular tests... Now I would say we just need a confirmation with @aalkin to see if everything is in order and then we can merge and proceed to the converter part: I will check if there is maybe any small update that may be required on that side and prepare a PR. Thanks a lot, everyone!! |
I have no additional comments, @ddobrigk. Although you may want to produce some new format data files first and test them with O2Physics. |
Yes, this is a good idea. We did it already with the previous version, but we can redo it. For now, because the data model changes will only kick in after the |
I think the CI is unrelated. @ktf can you confirm and then merge? |
I'll run the fullCI locally, will merge if ok. |
passed fullCI locally, merging |
Thank you very much @shahor02 ! I will prepare the O2Physics PR shortly. Have a nice easter break! |
@cortesep @coppedis @jgrosseo up for discussion / approval! Thanks :-D