Skip to content

Remove alpaka procModfier from workflows in which it is no longer useful#220

Open
VourMa wants to merge 3 commits intomasterfrom
CMSSW_16_0_0_pre3_removeAlpakaFromWFs
Open

Remove alpaka procModfier from workflows in which it is no longer useful#220
VourMa wants to merge 3 commits intomasterfrom
CMSSW_16_0_0_pre3_removeAlpakaFromWFs

Conversation

@VourMa
Copy link
Collaborator

@VourMa VourMa commented Jan 7, 2026

Recently, Patatrack quadraplet pixel tracks were made the default in CMSSW, so the alpaka modifier was rendered useless in a quite a few workflows which was using it to enable Patatrack pixel tracking. This PR removes the alpaka procModifier from these workflows. One workflow is completely removed, as it was duplicate of another, and that leads to a small change in the workflow numbering.

The PR was validated by making sure that all the modified workflows succeed.

upgradeWFs['HLTTiming75e33SingleIter'].step2 = {
'-s':'DIGI:pdigi_valid,L1TrackTrigger,L1,L1P2GT,DIGI2RAW,HLT:75e33_timing,VALIDATION:@hltValidation',
'--procModifiers': 'alpaka,singleIterPatatrack',
'--procModifiers': 'singleIterPatatrack',
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did a git grep alpaka.to and found alpaka.toReplaceWith(_HgcalLocalRecoUnseededSequence, in HLTrigger/Configuration/python/HLT_75e33
that's in 16_0_0_pre2.
If these were strictly TrackingOnly workflows, then the change seems OK.
I'm less sure for the general table.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indeed, the alpaka procModifier is still used to enabled the HGCal heterogenous reconstruction, and hence it is kept in the general workflow (0.751) as well as the dedicated TICL one (0.771). I intend to bring this up to the HGCal developers and see if it's still useful there but this is beyond the scope of this PR.

I also noticed these two ESProducers that are enabled by the alpaka procModifier:

I don't know how these are useful but they do not affect the workflows that I changed. I intend to ask about them in the PR as well.

Copy link

@slava77 slava77 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approving based on the discussion during the meeting. The point is to highlight to HGCAL that in these (or all related to GPU) workflows we probably want alpaka-HGCAL

@VourMa VourMa force-pushed the CMSSW_16_0_0_pre3_removeAlpakaFromWFs branch from 59c9798 to b10522a Compare January 14, 2026 13:23
@VourMa VourMa mentioned this pull request Feb 1, 2026
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants