-
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
[12_4_X] Adding extra protection against invalid data to EMTF PrimitiveSelection #38794
[12_4_X] Adding extra protection against invalid data to EMTF PrimitiveSelection #38794
Conversation
…his is necessary for Run 3 CSC TPs when CCLUT is not running correctly.
A new Pull Request was created by @eyigitba for CMSSW_12_4_X. It involves the following packages:
@epalencia, @cmsbuild, @cecilecaillol, @rekovic can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild , please test |
backport of #38775 |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-cdf548/26335/summary.html Comparison SummarySummary:
|
+l1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_4_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_5_X is complete. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
During the tests of #38373 we realized that EMTF
PrimitiveSelection.cc
was missing protection against invalid CSC data that is enabled with Run 3 flagsuseRun3CCLUT_OTMB
anduseRun3CCLUT_TMB
.This protection is necessary for Run 3 CSC TPs when CCLUT is not running correctly at P5 which was the case before June 2022.
The slope variable is a
uint16_t
and it exists for Run 2 or Run 3 CSC TPs. We only use this variable ifuseRun3CCLUT_OTMB
oruseRun3CCLUT_TMB
is enabled. That's why I left the max value as 65536 if these flags are disabled.PR validation:
Validated by checking failed workflows from #38722. We see correct behaviour of rejecting these "corrupt" LCTs and it doesn't change the outcome of the correct LCTs.
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:
Backport of #38775