-
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
[13.0.X] Misceallaneous Tracker Alignment validation updates for 2023 data-taking #41408
[13.0.X] Misceallaneous Tracker Alignment validation updates for 2023 data-taking #41408
Conversation
backport of #41378 |
A new Pull Request was created by @mmusich (Marco Musich) for CMSSW_13_0_X. It involves the following packages:
@cmsbuild, @tvami, @saumyaphor4252, @francescobrivio can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
backport of #41393 |
type bug-fix |
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9797d5/32151/summary.html Comparison SummarySummary:
|
@mmusich can you please include [130X] in the PR title? |
+alca
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_13_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_13_1_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 |
PR description:
This is a combined backport of #41378 and #41393
I add a generic vertex analyzer to be used for the Tracker Alignment alcareco monitoring. I profit of this PR to add some more histograms concerning the Beam Spot monitoring to an existing analyzer and to improve the unit test suite.
In addition it fixes some miscellaneous problems in the Tracker alignment di-muon validation code:
PR validation:
Private tests, plus run successfully the augmented unit 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:
This is a combined backport of #41378 and #41393 meant for analysis of the 2023 data from the Tracker Alignment group.