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
Update BeamSpot for 2022 EOY MC #41123
Update BeamSpot for 2022 EOY MC #41123
Conversation
test parameters:
|
A new Pull Request was created by @francescobrivio for master. It involves the following packages:
@bbilin, @cmsbuild, @AdrianoDee, @srimanob, @saumyaphor4252, @kskovpen, @sunilUIET, @tvami, @francescobrivio can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test
|
-1 Failed Tests: RelVals-INPUT
RelVals-INPUT
Expand to see more relval errors ...
Comparison SummarySummary:
|
Well the tests failed due to DAS errors. |
@cms-sw/pdmv-l2 @cms-sw/upgrade-l2 a kind ping |
The error is not actually the DAS error, but because datasets do not exist. If you would like to merge this PR, full sets of relvals need to be produced. |
Hi Phat! But the GS dataset actually exists on DAS (see link here) and locally I was able to succesfully run:
so what am I missing? 😄 |
From https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-16f741/31504/dasqueries/runall-report-step123-.log, if you search on |
Thanks a lot Phat! So I guess we should generate the relvals with:
Should I open a JIRA @cms-sw/pdmv-l2 ? |
Hi @francescobrivio @cms-sw/pdmv-l2 Basically, the same setting that pdmv used to produce minbias. |
Just as update: @bbilin was super kind to submit the needed relvals very fast, see AFAIU the proc string should be unchanged, so once the relvals are done I will re-trigger the tests. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41123/34995
|
Pull request #41123 was updated. @bbilin, @AdrianoDee, @srimanob, @saumyaphor4252, @kskovpen, @sunilUIET, @tvami, @francescobrivio can you please check and sign again. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-16f741/31740/summary.html Comparison SummarySummary:
|
+alca
|
Finally!! |
+Upgrade |
+pdmv |
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:
This PR updates the MC BeamSpot to be used in the "2022 EOY" MC production planned for later this year.
The updates are only related to 2022 (since in 2023 the BeamSpot will be most probably be moved) and include:
BeamSpotObjects_Realistic25ns_13p6TeVCollisions_EOY2022_v2_mc
BeamSpotOnlineObjects_Realistic25ns_13p6TeVCollisions_EOY2022_v2_mc
upgradeWorkflowComponents.py
the vtx smearing for 2021 (used in 2022 relvals) toRealistic25ns13p6TeVEOY2022Collision
in order to be consistent with the GTrelval_steps.py
GT diffs:
The
[RFC]
is due to the fact that i'm not 100% sure if the updates I made are enough or more changes are needed, e.g. looking at #38760 I can see that several files that I didn't touch are using the (now) deprecatedRealistic25ns13p6TeVEarly2022Collision
vertex smearing...should I update those as well to be consistent?FYI @mmusich
PR validation:
Succesfully ran
11834.0
workflowBackport:
Not a backport - no backport needed