-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Update L1T menu tag in GTs to L1Menu_Collisions2024_v1_2_0_xml #44860
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44860/40114
|
A new Pull Request was created by @perrotta for master. It involves the following packages:
@consuegs, @cmsbuild, @saumyaphor4252, @perrotta can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-a0f139/39128/summary.html Comparison SummarySummary:
|
+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. @antoniovilela, @rappoccio, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Update L1T menu with L1Menu_Collisions2024_v1_2_0_xml, as from cmsTalk https://cms-talk.web.cern.ch/t/gt-mc-data-relval-update-of-the-2024-l1t-menu-tag-l1menu-collisions2024-v1-2-0/39826
The new L1T menu tag is L1Menu_Collisions2024_v1_2_0_xml which replaces the previous L1Menu_Collisions2024_v1_1_0_xml. The difference wrt the previous tag is the addition of a few L1 HQ bits for lumi-decay.
All the differences w.r.t. the previous L1T menu are summarized here , and can be visible also via the Payload Inspector:
GT differences with the previous ones only relate to the updated L1T menu tag:
PR validation:
RunTheMatrix -s succesfully run with the GT Candidates corresponding to the versioned GTs included in this PR
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:
A backport PR to 14_0_X will be also submitted