-
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
[Backport 10_6_X] Fix EmissionVetoHook for BB4L #42422
[Backport 10_6_X] Fix EmissionVetoHook for BB4L #42422
Conversation
A new Pull Request was created by @lauridsj (Laurids Jeppe) for CMSSW_10_6_X. It involves the following packages:
@SiewYan, @mkirsano, @Saptaparna, @cmsbuild, @alberto-sanchez, @menglu21, @GurpreetSinghChahal can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_10_6_X IBs after it passes the integration tests and once validation in the development release cycle CMSSW_13_3_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 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-0c80ec/33987/summary.html Comparison SummarySummary:
|
You backported to 10_6 and 12_4 |
Thank you @lauridsj ! |
+1 |
PR description:
Backport of #42264 (fixing the Pythia FSR hook for bb4l) to CMSSW 10_6_X for UL MC generation, as discussed with @Saptaparna.
PR validation:
See #42264.
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:
See above.