-
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
Changed delayed jet skim to add HT350 and L1Tau paths [13_0_X] #41622
Changed delayed jet skim to add HT350 and L1Tau paths [13_0_X] #41622
Conversation
A new Pull Request was created by @rtschmitz for CMSSW_13_0_X. It involves the following packages:
@cmsbuild, @bbilin, @sunilUIET, @kskovpen can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
backport of #41592 |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-45d01f/32610/summary.html Comparison SummarySummary:
|
+pdmv |
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 |
Just bringing up the idea if trigger inputs change a lot, we have the trigger bit tag in the GT that could be refurbished to control the same thing, and would not need CMSSW changes (for the future, and again with the caveat that these change frequent enough) |
PR description:
Backport of #41592
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:
#41592
Fix for delayed jet skim for 2023 data-taking