-
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
HLT release validation and offline DQM for EXO Run 3 HLT paths (12_5_X) #39856
Conversation
…tersNoVtx_v and HLT_TrkMu17_DoubleTrkMu8NoFiltersNoVtx_v; make it not required to have all paths valid in the numerator and denominator
A new Pull Request was created by @jalimena (Juliette Alimena) for CMSSW_12_5_X. It involves the following packages:
@emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @syuvivida, @pmandrik, @micsucmed, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
backport of #39799 |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-e8db76/28520/summary.html Comparison SummarySummary:
|
+1
|
merge |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_5_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_6_X is complete. This pull request will be automatically merged. |
PR description:
This PR is a backport of #39799
This PR:
The reason for the second part is because in the HLT 2022 v1.3 menu, one of the paths in the denominator was removed. As a result, the DQM plots did not get made, although they would have been fine, physics-wise. Changing this flag to false is the easiest way to have similar DQM plots with the earlier and later HLT menus, and it fixes this bug.
As a result of this PR, some DQM plots will be removed, and some will reappear.
PR validation:
Using the 11634.0 ttbar workflow, I have tested that the correct histograms are produced and filled in the harvested DQM file.
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:
Backport of #39799 . A backport to 12_4_X is necessary, and this backport is to make the intermediate release cycle 12_5_X consistent.