-
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
clear badPixelDetsBarrel_
and badPixelDetsEndcap_
in PixelInactiveAreaFinder
#42378
clear badPixelDetsBarrel_
and badPixelDetsEndcap_
in PixelInactiveAreaFinder
#42378
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42378/36406
|
A new Pull Request was created by @mmusich (Marco Musich) for master. It involves the following packages:
@cmsbuild, @mandrenguyen, @clacaputo can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
type bug-fix |
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-007317/33915/summary.html Comparison SummarySummary:
|
looking at a few cases, there are migrations from pixelPair step tracks (algo 6) to some other bins e.g. TTbar13TeVPUppmx2018 it looks like everything is in the phase-1 workflows, as expected (no diffs in phase-2 or phase-0) |
@cms-sw/reconstruction-l2 please have a look. Integration of (backport of) this PR will be need to allow the introduction of the pixel doublet recovery in the next HLT menu. |
+1 |
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. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Title says it all, potentially fix for the issue described at https://its.cern.ch/jira/browse/CMSHLT-2881 (
Reproducibility issues with pixel-doublet-recovery iteration (GRun/V151 of 13_0_X)
).PR validation:
Run the script from @missirol 10 times and always obtained same trigger decisions.
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 backported down to 13.0.X