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
HI 2023 relval wfs + realistic 2022 vtx smearing #41095
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41095/34714
|
A new Pull Request was created by @mandrenguyen (Matthew Nguyen) for master. It involves the following packages:
@SiewYan, @mkirsano, @bbilin, @alberto-sanchez, @Saptaparna, @tvami, @cmsbuild, @AdrianoDee, @srimanob, @saumyaphor4252, @kskovpen, @menglu21, @sunilUIET, @francescobrivio, @GurpreetSinghChahal can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test workflow 159, 159.01, 159.02, 159.03, 159.1, 159.2, 159.3, 310, 160, 160.02, 160.03, 160.1, 160.2, 160.3 |
312.0_Pyquen_ZeemumuJets_pt10_2760GeV_2022 is giving this error
|
-1 Failed Tests: RelVals RelVals
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41095/34719
|
sorry, seems the status will not go back to "approved", so i need to start the test again, right? |
Yes, I think the test has to be restarted for posterity, but you can already inspect the comparisons produced by the previous test. |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-3ac722/31430/summary.html Comparison SummarySummary:
|
+1 |
+pdmv |
@cms-sw/upgrade-l2 it is not clear to me why your signature is requested here... In any case, I think it could be useful to have these modified HI workflow available for testing in the 13_1_0_pre2 RelVals. Since we plan to cut that pre-release today, we would like to include this PR in it, if you don't have anything against it. |
+Upgrade |
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 now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Existing 2022 heavy-ion workflows (159.) are duplicated for 2023 detector conditions (160.).
The center-of-mass energy is updated to 5.362 TeV, the energy expected for the 2023 Pb-Pb data.
The Hydjet generator parameters are slightly modified to correspond to what will be used for 2023 MC production.
The vertex smearing for both 2022 and 2023 workflows are updated to realistic beam conditions derived from the 2022 data.
The autoconditions are updated to global tags containing the corresponding reco BS. See here
The GT change includes the tag
BeamSpotObjects_Realistic2022PbPbCollision_v5_mc
as can be seen in the diffs:https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/131X_mcRun3_2022_realistic_HI_v1/131X_mcRun3_2022_realistic_HI_v2
and
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/131X_mcRun3_2023_realistic_HI_v1/131X_mcRun3_2023_realistic_HI_v2
Relval wfs (322-324, 161.01) that use an input dataset are also added but commented out until input samples can be produced
For 2022 workflows, cleaned up outdated nomenclature by fully changing
2021
to2022
PR validation:
wfs 160.0, 160.02, 160.03, 160.1, 160.2, 160.3 were tested with the option -j0. The cmsDriver commands run successfully, but the cmsRun commands are left for the jenkins tests.
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:
No backport will be needed.