Update the 2026 HI MC GT in autoCond with a new L1T menu#50905
Conversation
|
ping bot |
|
cms-bot internal usage |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-50905/49264
|
|
A new Pull Request was created by @perrotta for master. It involves the following packages:
@Alejandro1400, @JanChyczynski, @arunhep, @atpathak, @cmsbuild, @perrotta can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
please test |
|
+1 Size: This PR adds an extra 20KB to repository Comparison SummarySummary:
|
|
The differences observed are consistent with L1T menu changes. |
|
+1 |
|
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. @mandrenguyen, @sextonkennedy, @ftenchini (and backports should be raised in the release meeting by the corresponding L2) |
|
test parameters:
|
|
@cmsbuild, please test |
|
+1 Size: This PR adds an extra 16KB to repository Comparison SummarySummary:
|
|
+1 |
PR description:
A new GT was prepared in 161X for the 2026 HI MC campaign, as requested in https://cms-talk.web.cern.ch/t/gt-mc-hin-request-for-a-pbpb-run-mc-queue-in-161x/143262/15
The new 2026 HI MC GT is 161X_mcRun3_2026_realistic_HI_v2 and the difference with the previous HI MC GT in autoCond is here (only the L1T menu was updated with respect to the 2025 HI MC GT so far).
PR validation:
Rely on the PR tests
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:
It will be backported in CMSSW_16_1_X for the 2026 HI MC productions