-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Scouting Offline DQM framework for muons #47207
Scouting Offline DQM framework for muons #47207
Conversation
cms-bot internal usage |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-47207/43479 Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-47207/43499 |
Pull request #47207 was updated. |
Merge MUO and EGM scouting DQM (solve conflicts)
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-47207/43513
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
if this PR is fully contained in #47235, this might be closed. |
PR description:
This PR adds two new plugins performing Offline DQM for scouting muons, a contribution to the new scouting DQM framework. One of the plugins performs a tag and probe (T&P) method to monitor scouting muon and vertex distributions and efficiencies. The second plugin is designed to monitor distributions and efficiencies of muon L1 seeds. We add the following to the HLTriggerOffline/Scouting directory:
This plugin is to be merged with Egamma and JetMet to have a full DQM Offline framework for scouting. The development of this code was presented in several meetings:
- https://indico.cern.ch/event/1476209/
- https://indico.cern.ch/event/1492373/
This PR doesn’t include the common sequences for the scouting DQM workflow. They will be integrated in a future PR.
The implementation was built on top of CMSSW_7.
PR validation:
We have checked out all dependencies and have a clean build. Code-checks were applied. Most runTheMatrix tests were successfully run as well:
runall-report-step123-.log