-
Notifications
You must be signed in to change notification settings - Fork 4.6k
[10_6_X] Fix JR conditions for UL 2017 MC #40480
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
Conversation
|
A new Pull Request was created by @tvami (Tamas Vami) for CMSSW_10_6_X. It involves the following packages:
@malbouis, @yuanchao, @cmsbuild, @saumyaphor4252, @francescobrivio, @ChrisMisan, @tvami can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
|
test parameters:
|
|
@cmsbuild , please test |
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-84d911/29913/summary.html Comparison SummarySummary:
|
|
enable nano |
|
@cmsbuild , please test |
|
partial |
|
backport of #40482 |
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-84d911/29917/summary.html Comparison SummarySummary:
NANO Comparison SummarySummary:
|
|
+alca |
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_10_6_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_13_0_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 |
PR description:
As requested in https://cms-talk.web.cern.ch/t/gt-update-wrong-ul-2017-jr-tags/19081
we updated the UL 2017 MC GT with 24 new JR tags.
The new GT is called
106X_mc2017_realistic_v10The difference between v9 and v10 can be seen here: https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_mc2017_realistic_v9/106X_mc2017_realistic_v10
PR validation:
Tested with
1325.81If 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:
This is a dedicated change to 10_6_X for UL, a forward port will be done soon by updating the relevant 13_0_X GT