-
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
Add track-to-track monitoring of HLT GSF electron tracks with respect to offline #44868
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44868/40120
|
A new Pull Request was created by @mmusich for master. It involves the following packages:
@fabiocos, @cmsbuild, @antoniovagnerini, @syuvivida, @nothingface0, @rappoccio, @antoniovilela, @davidlange6, @tjavaid, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-c56e70/39155/summary.html Comparison SummaryThere are some workflows for which there are errors in the baseline: Summary:
|
type egamma, tracking |
@cms-sw/dqm-l2 this PR has been sitting idle for a week. Can you clarify plans for review and integration? |
+1 |
@cms-sw/orp-l2 is there is anything outstanding with this PR, can it be merged? |
+1 |
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 be automatically merged. |
PR description:
Title says it all, supports track-to-track monitoring of HLT GSF electron tracks with respect to offline for both Run 3 (
hltEgammaGsfTracks
) and Phase 2 (hltEgammaGsfTracksL1Seeded
).In addition:
egmTrackingMonHLT
PR validation:
Run successfully both
runTheMatrix.py -l 13034.0 -t 4 -j 8
(Run 3) andrunTheMatrix.py -l 24834.0 -t 4 -j 8
(Phase 2) and observed the corresponding monitoring elements filled.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_14_0_X for data-taking purposes.