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
HLT customisation for Patatrack pixel tracks and GPU offload [12.0.x] #34957
HLT customisation for Patatrack pixel tracks and GPU offload [12.0.x] #34957
Conversation
Add a customisation script for the HLT: - enable the Patatrack pixel track reconstruction, with quadruplets or triplets, running on CPU or GPU - optionally, add the possibility to offload the ECAL unpacking and local reconstruction to run on GPU - optionally, add the possibility to offload the HCAL local reconstruction to run on GPU Co-authored-by: Andrea Massironi <massironi.andrea@gmail.com>
backport #34956 |
A new Pull Request was created by @fwyzard (Andrea Bocci) for CMSSW_12_0_X. It involves the following packages:
@Martin-Grunewald, @cmsbuild can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test To make the bot happy, even if the new customisation is not used anywhere. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-0ca9ba/17897/summary.html Comparison SummarySummary:
|
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1
|
PR description:
Add a customisation script for the HLT:
The new customisation is not used by any workflows.
PR validation:
Validated in CMSSW_12_0_0_pre6 with
resulting in
Tested successfully both with and without a GPU.
The physics validation and the GPU vs CPU comparison will follow after the customisation has been merged.
if this PR is a backport please specify the original PR and why you need to backport that PR:
Backport of #34956 .
Before submitting your pull requests, make sure you followed this checklist: