-
Notifications
You must be signed in to change notification settings - Fork 4.6k
[NGT] Fix parameters for "offline" Phase 2 Alpaka PixelTracks #49314
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
[NGT] Fix parameters for "offline" Phase 2 Alpaka PixelTracks #49314
Conversation
|
cms-bot internal usage |
|
type ngt, bug-fix |
|
enable gpu |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-49314/46672
|
|
A new Pull Request was created by @Parsifal-2045 for master. It involves the following packages:
@cmsbuild, @jfernan2, @mandrenguyen, @srimanob can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
@cmsbuild, please test |
|
+1 Size: This PR adds an extra 20KB to repository Comparison SummarySummary:
AMD_MI300X Comparison SummarySummary:
AMD_W7900 Comparison SummarySummary:
NVIDIA_H100 Comparison SummarySummary:
NVIDIA_L40S Comparison SummarySummary:
NVIDIA_T4 Comparison SummarySummary:
|
|
+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. @ftenchini, @sextonkennedy, @mandrenguyen (and backports should be raised in the release meeting by the corresponding L2) |
|
+1 |
PR description
As a follow up to #49288 (comment) this PR drops the outdated custom parameters used for "offline" Phase 2 Alpaka PixelTracks in workflows
*.402,*.403, and*.404.The customisation itself is not needed anymore since all relevant parameters are defined in separate
TrackerTraits(Phase1,Phase1HI,Phase2, andPhase2OT), meaning that the defaultfillDescriptionparameters can be used in all cases (except for theRecHitslabel that changes between HLT and offline-like workflows).PR validation:
Ran over 100 events for workflows
29834,29834.402,29834.403,29834.404with theCA_WARNINGSflag enabled and observed no issues both on plain CMSSW_16_0_X_2025-11-03-2300 and including #49282