Pixel GPU Online DQM Client changes for CMSHLT-3147#49237
Pixel GPU Online DQM Client changes for CMSHLT-3147#49237cmsbuild merged 3 commits intocms-sw:masterfrom
Conversation
…he pixelgpu_dqm_sourceclient-live_cfg.py
…e change of event content - See [CMSHLT-3147](https://its.cern.ch/jira/browse/CMSHLT-3147) for more details.
|
cms-bot internal usage |
|
test parameters: |
|
@cmsbuild, please test |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-49237/46584 |
|
A new Pull Request was created by @mmusich for master. It involves the following packages:
@ctarricone, @gabrielmscampos, @nothingface0, @rseidita can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
+1 Size: This PR adds an extra 24KB to repository Comparison SummarySummary:
|
Edit:
|
|
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) |
do yo have news concerning this point? |
We are running some tests now, hopefully within the day we'll have a better picture. |
given CMSHLT-3147 has converged, can this and the corresponding |
|
+dqm |
|
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:
This PR is opened in preparation of the integration of the ticket CMSHLT-3147.
In a nutshell that ticket suggests that the DQM plugins which are currently in the Path
DQM_PixelReconstruction_v(Sequence:HLTDQMPixelReconstruction) and in the PathDQM_PixelReconstruction_v(SequeceHLTDQMPixelReconstruction) can be removed from the HLT combined table, as long as the Tracker-DPG and/or Tracking-POG experts move the corresponding monitoring sequence into the appropriate online-DQM client (which reads theDQMGPUvsCPUstreamer files).This latter point is proposed in this PR, in which we change the client
DQM/Integration/python/clients/pixelgpu_dqm_sourceclient-live_cfg.pyto include directly the modules responsible of monitoring of the GPU vs CPU comparisons, as the input data to feed them will be sent by the inputDQMGPUvsCPUstream.PR validation:
I created a suitable set of streamer files using the following script:
and then placed the resulting files under the path
$CMSSW_BASE/src/DQM/Integration/data/run397813.The resulting streamers files have been committed to the
cms-dataDQM-Integrationrepository via PR cms-data/DQM-Integration#14 (that needs to be tested together with this one).I then run the unit test of the package via:
and I did not observe any issues.
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:
Not a backport, but it will be backported to CMSSW_15_1_X for 2025 datat-taking operations.