-
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
[14.0.X] Improvements for Tracker Alignment DiMuonValidation
#45002
[14.0.X] Improvements for Tracker Alignment DiMuonValidation
#45002
Conversation
A new Pull Request was created by @mmusich for CMSSW_14_0_X. It involves the following packages:
@consuegs, @saumyaphor4252, @cmsbuild, @perrotta can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
cms-bot internal usage |
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-c6c973/39435/summary.html Comparison SummarySummary:
|
+alca
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_14_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_14_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @rappoccio, @sextonkennedy, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
backport of #44994
PR description:
The goal of this PR is to inject in release few improvements for Tracker Alignment
DiMuonValidation
setup.These are:
This is foreseen in the longer term to replace the existing
Zmumumerge.cc
class which is currently used by the so-called "all-in-one" tool. The new plotting script fixes several issues with the final plotting currently provided by the all-in-one; however, the replacement is not done in this PR and will have to be done at a second time.PR validation:
Private validation was carried out using this branch and operating the new plotting macros.
The plots at this link were obtained. For a comparison with the output of the current code, see please here.
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:
Verbatim backport of #44994 to the 2024 data-taking release cycle.