-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
add DQM / Validation monitoring for hltInitialStep
and hltHighPtTriplet
tracks in the Phase2 HLT menu
#46823
base: master
Are you sure you want to change the base?
add DQM / Validation monitoring for hltInitialStep
and hltHighPtTriplet
tracks in the Phase2 HLT menu
#46823
Conversation
…etTracks in the Phase2 HLT menu
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-46823/42826
|
A new Pull Request was created by @mmusich for master. It involves the following packages:
@antoniovagnerini, @antoniovilela, @cmsbuild, @davidlange6, @fabiocos, @mandrenguyen, @rappoccio, @rseidita can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
-1 Failed Tests: RelVals RelVals
|
nice... |
@cmsbuild, please test |
+1 Size: This PR adds an extra 12KB to repository Comparison SummarySummary:
|
PR description:
Recently the Phase-2 HLT group started to review and optimize the Pixel tracks as seeds (and more) for HLT. In this context it is not unreasonable to foresee changes in that iteration as well as in the other (high pT triplet iteration) currently in use to build the final HLT tracks collection in the phase-2 menu
So it would be ideal to monitor both of them at the same time
This PR provides support for DQM and Validation for
hltInitialStep
andhltHighPtTriplet
tracks in the Phase2 HLT menu.PR validation:
Run the following workflow:
I observe in the output of the step3 the following additional collections:
Inspecting the output DQM file I see the new plots appearing for the considered collections.
An example root DQM file that can be obtained with this branch is available here.
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, no interest in backporting (at least for the time being)