-
Notifications
You must be signed in to change notification settings - Fork 155
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
Added parameters for PbPb #1771
Conversation
REQUEST FOR PRODUCTION RELEASES:
This will add The following labels are available |
+async-label async-2024-PbPb-cpass0, async-2024-PbPb-apass1 |
is it intended that you set |
|
it looks reasonable, but I have not tested it.
You can use the feature to run with a local o2dpg checkout to test new o2dpg features.
|
[[ -z "${QC_JSON_ZDC:-}" ]] && has_processing_step ZDC_RECO && QC_JSON_ZDC=$O2DPG_ROOT/DATA/production/qc-async/zdc.json | ||
if [[ -z "${QC_JSON_ZDC:-}" ]] && has_processing_step ZDC_RECO; then | ||
if [[ "$BEAMTYPE" == "PbPb" ]]; then | ||
QQC_JSON_ZDC=$O2DPG_ROOT/DATA/production/qc-async/zdcPbPb.json |
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.
@cpuggion84 There is a typo QQC
. Please fix it.
@cpuggion84 I tested it locally. After fixing the typo, the async workflows worked without crashes and the ZDC QC plots were filled. cc @davidrohr @chiarazampolli |
Merged and fixed typo (#1775) |
Dear @cpuggion84, I tried to port this commit to the tag for PbPb (async-v1-01-21) starting from the branch async-v1-01-branch and it gave me conflicts. Please, let me know what is missing and I will include it in the next production tag |
@alcaliva I am helping Carlo to figure out what is wrong... we tried to cherry-pick the two commits in this PR into |
ERROR: There was a problem cherry-picking 6d96fa8 |
Ciao, There might other PRs that are needed. We can check tomorrow. Chiara |
@alcaliva I still cannot reproduce your error... I have tried to cherry-pick the two commits from master to the
Am I doing something wrong? |
The PR should be picked on version 12c. I cannot try today, sorry... |
Hi Chiara, I tried yesterday and re-tried now with: start_from: &start_from async-v1-01-12c I still get conflicts: |
Hi @aferrero2707 , I see that you are trying to cherry-pick this commit: ca3d4ce |
Hi Andrea, sorry, from https://aliceo2group.github.io/dpg-documentation/docs/software/requests_automatic/dpg_pr_report_MERGED.html I saw only one. It worked now! |
Hello @alcaliva , @aferrero2707 , I don't know how @aferrero2707 got the second hash, but I see it doing the usual "git log":
@davidrohr , @cpuggion84 , we should squash such commits the next time. Chiara |
Not needed for PbPb 2023 apass4, since the pass is over, and the PR does not affect MC, so the label was removed. |
Hello @alcaliva , Why did you add again the cpass0 PbPb 2024 label? I think the tag was done with this. Maybe it was a mistake. See also: https://aliceo2group.github.io/dpg-documentation/docs/software/accepted/O2DPG_accepted.html or: https://github.com/AliceO2Group/O2DPG/commits/async-v1-01-12e/ I am removing the label. Chiara |
No description provided.