-
Notifications
You must be signed in to change notification settings - Fork 4.6k
ECAL DQM GpuTask add 2D comparison histograms and enable GPU validation on online DQM #38427
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
Merged
Merged
Changes from 5 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
dff13d2
Add 2D maps for comparing CPU and GPU quantities
alejands 8530b01
Create subdirectories for each ECAL object's plots
alejands 0046019
Add flags to customize what plots are enabled
alejands 9574e67
Enable ecalGpuTask in Online DQM using HLT collections
alejands 1e53aa1
Formatting in GpuTask.cc
alejands 165d426
Revert "Enable ecalGpuTask in Online DQM using HLT collections"
alejands f7002b2
Create separate dedicated client for GPU validation on ECAL online DQM
alejands d7f5f74
Correct output file name for ECAL GPU client
alejands File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given that all other input tags use the offline value by default (e.g.
ecalRecHit,particleFlowClusterECAL, etc.) I think it would be better to keep the offline values here as the default, and customise the configuration of the online DQM where it is used.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to follow a suggestion from DQMDC to have the online GPU module in its own dedicated client like HCAL did here: https://github.com/cms-sw/cmssw/blob/master/DQM/Integration/python/clients/hcalgpu_dqm_sourceclient-live_cfg.py. This way we can keep the offline values here and modify them for online in the new client, and we can also avoid crashing the standard ECAL client in case of issues with the GPU stream.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that makes sense.
In fact, the online client for the GPU vs CPU validation has to be separate from the regular one, because the HLT collections come in a different stream than the raw data.