-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[14_0_X] Fix logic in PFClusterSoAProducer kernels #44278
Conversation
Add non-seed rechit condition in exotic clustering
A new Pull Request was created by @jsamudio for CMSSW_14_0_X. It involves the following packages:
@cmsbuild, @mandrenguyen, @jfernan2 can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
cms-bot internal usage |
Maybe somebody can trigger jenkins? (not sure if test parameters will be inherited from the other PR #44273, or need to be redefined here) |
type bugfix |
backport #44273 |
urgent for data taking |
test parameters:
|
please test |
allow @jsamudio test rights (in case it needs to be updated and re-tested) |
type pf |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b38afa/37836/summary.html Comparison SummarySummary:
GPU Comparison SummarySummary:
|
assign heterogeneous |
+heterogeneous |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_14_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_14_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @sextonkennedy, @antoniovilela, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1
|
PR description:
This PR fixes an issue with the clustering logic in
PFClusterSoAProducer
. The issue was highlighted by 2024 thresholds giving rise to topological clusters exceeding 100 seeds, which we had never naturally encountered in previous validations of the code in order to catch this flaw. The fall-back kernel was not being launched as intended in the previous logic, and is now changed to behave as intended.PR validation:
For CPU-serial and GPU alpaka backends:
Validated QCDPU sample on 2022, 2023, and 2024 globalTag thresholds, and validated change in Pixel+ECAL+PF Alpaka HLT test workflow.
Cluster-level validation plots can be found here: https://hep.baylor.edu/jsamudio/fixLogic/
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:
Verbatim backport of #44273 for
14_0_X
@hatakeyamak @waredjeb @fwyzard @swagata87 @stahlleiton