-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Run3 era for 2024 pp reference and UPC reco #44316
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44316/39336
|
@stahlleiton Normally we add a relVal workflow for testing. Do you want to give it a shot? |
For the UPC, the only change was to modify the base era from Run3_2023 to Run3, and I tested it on 13_2_X. To test it in 14_1_X, a new GT will be needed (I can try to request one and add a MC relval for 14_1_X) |
82d58a4
to
14aee38
Compare
Implemented 4 relval MC workflows:
The Pythia8 gamma-nucleus workflows needs the fix implemented in #44264 |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44316/39351
|
Pull request #44316 was updated. @vlimant, @jfernan2, @menglu21, @antoniovilela, @subirsarkar, @GurpreetSinghChahal, @mandrenguyen, @rappoccio, @bbilin, @SiewYan, @fabiocos, @cmsbuild, @srimanob, @davidlange6, @mkirsano, @hqucms, @AdrianoDee, @sunilUIET, @miquork, @alberto-sanchez can you please check and sign again. |
test parameters:
|
please test |
+Upgrade |
+1 |
+1 |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will be automatically merged. |
Workflow 180.1 fails in IBs, see #44536 |
Ok. I will try to update the gridpack of starlight. In the meantime, I will make a PR removing this workflow. |
PR description:
This PR implements a first version of the Run 3 eras for the 2024 pp reference (at 5.36 TeV) and PbPb UPC reconstruction.
@mandrenguyen
PR validation:
Validated using a minbias sample.
If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for: