-
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
[14.0.X] DisplacedJet_Monitor
: use hltIter2MergedForDisplaced
instead of hltIter2MergedForBTag
to (as per CMSHLT-3303)
#45633
[14.0.X] DisplacedJet_Monitor
: use hltIter2MergedForDisplaced
instead of hltIter2MergedForBTag
to (as per CMSHLT-3303)
#45633
Conversation
A new Pull Request was created by @mmusich for CMSSW_14_0_X. It involves the following packages:
@antoniovagnerini, @cmsbuild, @nothingface0, @rvenditti, @syuvivida, @tjavaid can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
cms-bot internal usage |
@cmsbuild, please test |
+1 Size: This PR adds an extra 20KB to repository Comparison SummarySummary:
|
@cms-sw/dqm-l2, sorry to pressure you. We could this PR in the upcoming release for data-taking, can you have a look? |
+1
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_14_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_14_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @rappoccio, @mandrenguyen, @sextonkennedy, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
backport of #45632
PR description:
Title says it all, as per discussion at CMSHLT-3303.
The collection
hltIter2MergedForDisplaced
produced at HLT by few displaced object triggers is not monitored by the EXO monitoring setup inHLTMonitor
. This PR jointly with a HLT menu change foreseen for Aug-5 2024 will restore the monitoring.PR validation:
None, trivial input collection change.
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:
Verbatim backport of #45632 for 2024 data-taking purposes.