-
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 ME-s needed for per-LS certification of Tracking at HLT in nanoDQMIO
output
#41857
add ME-s needed for per-LS certification of Tracking at HLT in nanoDQMIO
output
#41857
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41857/35759
|
A new Pull Request was created by @mmusich (Marco Musich) for master. It involves the following packages:
@nothingface0, @emanueleusai, @cmsbuild, @pmandrik, @syuvivida, @tjavaid, @micsucmed, @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-0d5448/32956/summary.html Comparison SummarySummary:
|
+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 now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
The goal of this PR is to add to the
nanoDQMIO
(per-LS) output the ME-s necessary to perform detailed Tracking at HLT monitoring and certification on the ExpressHLTMonitor
PD. A total of 38 new ME-s is added, but since they are available only in theHLTMonitor
PD they should not enlarge by any means the regular express / prompt output.PR validation:
cmssw
compiles.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, to be backported to 13.0.X for 2023 data-taking purposes.
FYI:
@kjpena @elusian @lguzzi @vjmastra