-
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.1.X] Miscellaneous backports to DQM/TrackingMonitorSource
#46280
[14.1.X] Miscellaneous backports to DQM/TrackingMonitorSource
#46280
Conversation
… put early returns in case of missing input data in various plugins
A new Pull Request was created by @mmusich for CMSSW_14_1_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 16KB to repository Comparison SummarySummary:
|
+1
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_14_1_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_14_2_X is complete. This pull request will now be reviewed by the release team before it's merged. @mandrenguyen, @sextonkennedy, @rappoccio, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
backport of #46005
backport of #46187
PR description:
V0EventSelector
produce skimmed V0 collections based on their mass. It was suggested to modifyV0EventSelector
in order to produce skimmed V0 collections based on their mass, to enhance the purity in terms of strange origin of the tracks analyzed viaStandaloneTrackMonitor
, based on the results shown here and here.fillDescription
parameters and place early returns in case of missing input data in various pluginscatch2
based tests for various plugins in the packageThis update concerns only the Tracking Data/MC validation suite and is of no consequence on any DQM production sequence run in online or offline DQM.
PR validation:
Relies on the unit tests of this package: (existing)
scram b runtests_testTrackingDATAMC
and (newly added)scram b runtests_testTrackingDQMAnalyzers
both run fine.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 backports of #46005 and #46187