-
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
Update/fix SimBeamSpot tag for Run3 HI MC GT in 14_1_X #45346
Conversation
cms-bot internal usage |
@cmsbuild please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45346/40760
|
A new Pull Request was created by @perrotta for master. It involves the following packages:
@consuegs, @perrotta, @saumyaphor4252 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-5f49a1/40152/summary.html
Comparison SummarySummary:
|
+alca |
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. @sextonkennedy, @antoniovilela, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
Update on the SimBeamSpot tag for the HI MC production in run3. Previously, the HI SimBeamSpot tag was not synced with the 2023 PbPb vertex smearing parameters. Therefore, the new tag is updated using the vertex smearing parameters obtained from 2023 PbPb data. The updated GT in autoCond includes that tag.
The following GTs have been updated by including the updated SimBeamSpot (only the 141X GT is updated in autoCond for this release):
Differences with the previous HI MC GTs in autoCond: