-
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
fix packing of muon-shower objects for L1-uGT FED #45519
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45519/40988 |
A new Pull Request was created by @missirol for master. It involves the following packages:
@aloeliger, @cmsbuild, @epalencia can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Will this PR be reviewed ? |
@cmsbuild, please test |
type bug-fix |
Sorry, I looked at this last week and then just didn't send my message.. This looks good to me, thanks a lot for spotting the problem! Cheers, |
+1 Size: This PR adds an extra 12KB to repository Comparison SummarySummary:
|
+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. @mandrenguyen, @rappoccio, @sextonkennedy, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
FYI, I opened the backport to |
thanks @missirol ! I think it's better to backport this for any REPACK use with 140X |
PR description:
This PR applies the fix in #40822 to
MuonPacker.cc
. Right now, whenL1REPACK
is used to re-emulate L1T,gtStage2Raw
is used to pack the L1-uGT data,gtStage2Raw.FwId
equals0x1150
, andMuonPacker::getMuonShowers
is not executed because the check touched by this PR fails (b/c0x1150 < 0x10f01
). This PR fixes the check inMuonPacker.cc
, and moves it to a static function inMuonRawDigiTranslator
for easier maintenance.Tagging @dinyar to review (cc: @eyigitba).
PR validation:
None.
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:
I don't know if any backports are needed. To be decided by experts.