-
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
[12.5.X] PrimaryVertexMonitor
: fix beamspot centering for Run3 and actually fill the beamspot type histograms
#39333
[12.5.X] PrimaryVertexMonitor
: fix beamspot centering for Run3 and actually fill the beamspot type histograms
#39333
Conversation
type bug-fix |
@cmsbuild, please test |
A new Pull Request was created by @mmusich (Marco Musich) for CMSSW_12_5_X. It involves the following packages:
@emanueleusai, @ahmad3213, @jfernan2, @rvenditti, @micsucmed, @pmandrik 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-49c005/27400/summary.html Comparison SummarySummary:
|
+1
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_5_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_6_X is complete. 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 |
backport of #39322
PR description:
When casually looking at the GUI, I noticed that:
PR validation:
None, but changes are trivial
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:
vertbatim backport of #39322 to 12.5.X