-
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
[13.0.X] add DQM and Validation modules for doublet recovery tracks #42279
[13.0.X] add DQM and Validation modules for doublet recovery tracks #42279
Conversation
cc: @mtosi |
A new Pull Request was created by @mmusich (Marco Musich) for CMSSW_13_0_X. It involves the following packages:
@Martin-Grunewald, @nothingface0, @emanueleusai, @cmsbuild, @missirol, @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-1310dd/33713/summary.html Comparison SummarySummary:
|
+hlt |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_13_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_13_2_X is complete. 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 |
backport of #42266
PR description:
With the inclusion of the
hltDoubletRecoveryPFlowTrackSelectionHighPurity
collection to the track reconstruction at HLT,there is now the need of monitoring and validating it as well
This PR simply extend the already in place DQM and Validation sequences to include this collection as well
Not having the HLT menu w/ this extra collection in CMSSW, the expected output is to have empty plots, but the code will run
PR validation:
Relies on the master version
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 #42266 for 2023 data-taking