-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Update 2017 UL realistic GT and 2022/2023 HI MC GTs #40482
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
|
@cmsbuild, please test |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40482/33660
|
|
A new Pull Request was created by @saumyaphor4252 (Saumya Phor) for master. It involves the following packages:
@malbouis, @yuanchao, @saumyaphor4252, @francescobrivio, @ChrisMisan, @tvami can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
@saumyaphor4252 please update the PR title to reflect that it's the 2017 UL realistic GT and the 2022/2023 HI MC GT |
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-6b6a15/29915/summary.html The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
You can see more details here: Comparison SummaryThere are some workflows for which there are errors in the baseline: Summary:
|
|
+alca
|
|
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). 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:
This PR is a forward port of #40473 with the addition of updated 2017 realistic GT.
It updates the following MC GTs:
auto:phase1_2022_realistic_hi,auto:phase1_2023_realistic_hi) with latest SiPixel bad component tags requested in this CMSTalk post [1]. More details for the request can be found in [2].auto:phase1_2017_realistic) with correct UL 2017 JER tags requested in this CMSTalk post [3].[1] https://cms-talk.web.cern.ch/t/125x-run-3-hi-gt-update-for-pixel-bad-components/19077
[2] https://cms-talk.web.cern.ch/t/request-alca-input-to-update-vertex-in-mc-of-2022-pbpb-test-run/18799/10
[3] https://cms-talk.web.cern.ch/t/gt-update-wrong-ul-2017-jr-tags/19081
GT Differeces
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mc2017_realistic_v2/130X_mc2017_realistic_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/130X_mcRun3_2022_realistic_HI_v1/130X_mcRun3_2022_realistic_HI_v2
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/130X_mcRun3_2023_realistic_HI_v1/130X_mcRun3_2023_realistic_HI_v2
PR validation:
Successfully ran:
runTheMatrix.py -l 159.0,10024.0 -j10 --ibeoswhich consumes the
auto:phase1_2017_realisticandauto:phase1_2022_realistic_hiconditions.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:
Forward port of #40473. No other backport expected.