-
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] adjust the L1T seeds to be monitored from L1TStage2uGTTiming
in Run3 PbPb modes
#46600
base: CMSSW_14_1_X
Are you sure you want to change the base?
[14.1.X] adjust the L1T seeds to be monitored from L1TStage2uGTTiming
in Run3 PbPb modes
#46600
Conversation
A new Pull Request was created by @mmusich for CMSSW_14_1_X. It involves the following packages:
@antoniovagnerini, @cmsbuild, @rseidita 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. @rappoccio, @sextonkennedy, @antoniovilela, @mandrenguyen (and backports should be raised in the release meeting by the corresponding L2) |
backport of #46590
PR description:
Addresses #43488 (comment), by removing from
DQM/L1TMonitor/python/L1TStage2uGTTiming_cfi.py
the monitoring seeds not existing in the Run3 PbPb L1T menus.PR validation:
Run the setup at #46584 (comment) with this commit and verified that the noisy warnings are removed.
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 #46590 to the production cycle of the 2024 PbPb run.