-
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 an incorrect (D)CFEB number assignment in the CSC CLCT producer for Run-3 L1T (CCLUT-12) #33254
Fix an incorrect (D)CFEB number assignment in the CSC CLCT producer for Run-3 L1T (CCLUT-12) #33254
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33254/21730
|
A new Pull Request was created by @dildick (Sven Dildick) for master. It involves the following packages: L1Trigger/CSCTriggerPrimitives @cmsbuild, @rekovic, @cecilecaillol can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
@dildick @cms-sw/l1-l2 have you planned to use this fix in the next MWGR? |
@silviodonato No, the CCLUT algorithm is still in testing at B904. It has not yet been deployed at P5. No backport required. |
@dildick I'm not sure the average CMS user is able to understand which detector are affected from "Fix incorrect CFEB assignment (CCLUT-12)". Please add some words about CSC and L1T. It happens often that people look at the release notes (eg. https://github.com/cms-sw/cmssw/releases/CMSSW_11_3_0_pre5) to find the origin of some changes observed in RelVals. |
@silviodonato Done! |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-0ceeef/13735/summary.html Comparison SummarySummary:
|
@silviodonato @rekovic Can this PR be merged? |
is there any comment from @cms-sw/l1-l2 ? |
+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. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
bool noDigis
(which is used as a double-negative) tobool hasDigis
.PR validation:
Tested on a 10 GeV prompt muon sample produced with 11_0_X.
if this PR is a backport please specify the original PR and why you need to backport that PR:
N/A
Before submitting your pull requests, make sure you followed this checklist:
@tahuang1991 @msd14