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
Fix era for DQM BeamSpot clients [12_0_X] #35899
Fix era for DQM BeamSpot clients [12_0_X] #35899
Conversation
A new Pull Request was created by @francescobrivio for CMSSW_12_0_X. It involves the following packages:
@emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @pmandrik, @pbo0, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
backport of #35898 |
@cmsbuild please test |
@jfernan2 @ahmad3213 @pmandrik this is another one to be tested in playback, run 346373 should be fine here too. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b2befb/20053/summary.html Comparison SummarySummary:
|
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_2_X is complete. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
@qliphy @perrotta also this one is tested in DQM playback system and should be merged asap so DQM team (@ahmad3213 and @pmandrik) can deploy it in production before the SB tonight. The validation of this PR comes from the playback DQM plot: which shows the transverse width of the BeamSpot is correctly computed by the Legacy BeamSpot client. |
urgent |
@francescobrivio Ok, we can merge it now. But notice usually we need the master PR to be merged first. |
+1 |
PR description:
Backport of #35898
Fix the era modifier for the DQM BeamSpot clients.
PR validation:
Should be tested in Playback at P5.
Backport
Backport of #35898
Before submitting your pull requests, make sure you followed this checklist: