TRK CPU vs. GPU path and infrastructure for Phase 2 HLT#50336
TRK CPU vs. GPU path and infrastructure for Phase 2 HLT#50336cmsbuild merged 2 commits intocms-sw:masterfrom
Conversation
|
cms-bot internal usage |
|
A new Pull Request was created by @VourMa for master. It involves the following packages:
@AdrianoDee, @DickyChant, @Martin-Grunewald, @antoniovagnerini, @civanch, @cmsbuild, @ctarricone, @davidlange6, @fabiocos, @ftenchini, @gabrielmscampos, @kpedro88, @mandrenguyen, @mdhildreth, @miquork, @mmusich, @nothingface0, @rseidita can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
test parameters:
|
| ) | ||
|
|
||
| from DQM.TrackingMonitorSource.TrackToTrackComparisonHists_cfi import TrackToTrackComparisonHists as _TrackToTrackComparisonHists | ||
| hltPixelTrackToTrackSerialSync = _TrackToTrackComparisonHists.clone( |
There was a problem hiding this comment.
as this uses only "data" and not simultation truth, I would naively assume it should go into "DQM" rather than "Validation"
There was a problem hiding this comment.
Sure, I can put it in a more appropriate file. Do you have any proposal about where to move it?
There was a problem hiding this comment.
I would create a new file in DQM/TrackingMonitorSource/python and reference it in the phase-2 hlt DQM sequence
There was a problem hiding this comment.
While we wait for a resolution of #48976 that would allow to run the DQM step in the same job as HLT, I think an acceptable compromise is to run the DQM modules themselves within the HLT menu as we did for most of Run 3 for the pixel heterogeneous tracking.
Here is a commit to that effect mmusich@07693a7.
I profited to:
- add the monitoring of the pixel tracks SoA-s
- add the harvesting step for the track-to-track comparisons
Tested with runTheMatrix.py --what upgrade -l 34434.7503 -t 4 -j 8 on lxplus-gpu
There was a problem hiding this comment.
Thanks for this, @mmusich! I will take a look and included today/tomorrow so that we can move forward.
There was a problem hiding this comment.
I applied the commit verbatim
| outputCommands = FEVTDEBUGHLTEventContent.outputCommands+[ | ||
| 'keep *_hltInitialStepTrajectorySeedsLSTTracks_*_*', | ||
| 'keep *_hltInitialStepTrajectorySeedsLSTTracksSerialSync_*_*', | ||
| 'keep *_hltPhase2PixelTracks_*_*', |
There was a problem hiding this comment.
some of these are already saved by default please clean up the redundant keep statements.
cmssw/Configuration/EventContent/python/EventContent_cff.py
Lines 709 to 720 in 7e37aba
There was a problem hiding this comment.
I updated the file accordingly.
ae0972b to
846424d
Compare
|
Pull request #50336 was updated. @AdrianoDee, @DickyChant, @Martin-Grunewald, @antoniovagnerini, @civanch, @cmsbuild, @ctarricone, @davidlange6, @fabiocos, @ftenchini, @gabrielmscampos, @kpedro88, @mandrenguyen, @mdhildreth, @miquork, @mmusich, @nothingface0, @rseidita can you please check and sign again. |
|
@cmsbuild, please test |
|
+1 Size: This PR adds an extra 28KB to repository HLT P2 Timing: chart Comparison SummarySummary:
AMD_MI300X Comparison SummarySummary:
AMD_W7900 Comparison SummarySummary:
NVIDIA_H100 Comparison SummarySummary:
NVIDIA_L40S Comparison SummarySummary:
|
It looks like this workflow did run in the GPU matrix: logs, but I can't see it in the bin-by-bin comparisons. To maximize usefulness I would suggest to move the workflow from the upgrade to the gpu matrix and then put it in here in the cms-bot configuration. This can be done at a later time. |
|
+hlt
|
Yes, since this requires an external, let's do it in a separate (set of) PR(s). I will prepare it and submit when this is in.
Right, I will do so later today. |
|
+1 |
|
+dqm |
|
@cms-sw/pdmv-l2 kind ping |
|
+pdmv |
|
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, @mandrenguyen, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
|
+1 |
This PR introduces CPU vs. GPU validation for the Phase 2 HLT, implementing the comparison for the tracking sequence. The relevant workflow is
0.7503.The approach has been presented at a recent HLT Upgrade meeting, and has been updated according to the feedback received there, i.e.:
simEcalTriggerPrimitiveDigisin different files? #48976), the DQM sequence has been included within the HLT menu.Here is the new DQM output (click to show):