-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Custom MUON POG NANO includes default NANO #44425
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44425/39497
|
A new Pull Request was created by @vlimant for master. It involves the following packages:
@vlimant, @AdrianoDee, @sunilUIET, @subirsarkar, @cmsbuild, @hqucms, @miquork, @srimanob can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
enable nano |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-fdcf47/38170/summary.html Comparison SummarySummary:
NANO Comparison SummarySummary:
Nano size comparison Summary:
|
+1 |
@cms-sw/pdmv-l2 @cms-sw/upgrade-l2 : can you please sign quickly this trivial PR so that we can get the backport going. |
+Upgrade |
+pdmv |
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. @rappoccio, @antoniovilela, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
@vlimant |
please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44425/39649
|
Pull request #44425 was updated. can you please check and sign again. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-fdcf47/38356/summary.html The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
You can see more details here: Comparison SummarySummary:
NANO Comparison SummarySummary:
Nano size comparison Summary:
|
+1 |
PR description:
since the MUPOG custom nano will always include the standard nano, the definition in the mapping should strictly include the PHYS part, so that they never get separated. (oversight on my account in #43642 )
PR validation:
runTheMatrix.py --what nano -l 2500.314 --ibeos
to successI also verified that combining
--step NANO:@EGM+@MUPOG
leads to the inclusion of "only one PHYS"