-
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
More resilient logic in determining MC events from AO2D file #1776
Conversation
Fixing a problem in detecting the right number of events from AO2D due to a recent name change O2mccollision --> O2mccolision_001 in the AOD format.
REQUEST FOR PRODUCTION RELEASES:
This will add The following labels are available |
+async-label async-2023-pbpb-apass4,async-2023-pp-apass4,async-2024-pp-apass1,async-2022-pp-apass7,async-2024-pp-cpass0 |
Hi @sawenzel, I tried to port this commit to the tag for async-2023-pp-apass4 but it didn't work, I get conflicts. The starting tag is async-20240229.pp.2g and I created the async-20240229.pp.2h. |
Fixing a problem in detecting the right number of events from AO2D due to a recent name change O2mccollision --> O2mccolision_001 in the AOD format. (cherry picked from commit e11820a)
Ported to async-v1-01-02f. |
removing for cpass0 of pp 2024, it makes no sense there. |
Fixing a problem in detecting the right number of events from AO2D due to a recent name change O2mccollision --> O2mccolision_001 in the AOD format. (cherry picked from commit e11820a)
Fixing a problem in detecting the right number of events from AO2D due to a recent name change O2mccollision --> O2mccolision_001 in the AOD format. (cherry picked from commit e11820a)
Fixing a problem in detecting the right number of events from AO2D due to a recent name change O2mccollision --> O2mccolision_001 in the AOD format.