-
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
Set 3 instead of 4 OMTF track sub-address as expected by uGMT #45030
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45030/40321
|
A new Pull Request was created by @mbluj for master. It involves the following packages:
@aloeliger, @epalencia, @cmsbuild can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ef2244/39495/summary.html Comparison SummarySummary:
|
type bug-fix |
+l1 |
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. @sextonkennedy, @rappoccio, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
As title says: this PR reduces number of OMTF track sub-addresses sent to uGMT from 4 to 3 to meet expected number. It calms "OMTF muon track address map contains 4 instead of the expected 3 subaddresses. Check the data format. Setting track address to 0." warning without impact on performance as the sub-addresses are currently not used.
PR validation:
tested with wf 141.044
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:
To be potentially backported to 14_0_X to calm warning in uGMT emulator.