-
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
Update GTs and modifiers for L1T 2024 menu L1Menu_Collisions2024_v1_3_0_xml [14_0_X] #45391
Conversation
A new Pull Request was created by @perrotta for CMSSW_14_0_X. It involves the following packages:
@cmsbuild, @consuegs, @perrotta, @saumyaphor4252 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
cms-bot internal usage |
please test |
+1 Size: This PR adds an extra 16KB to repository Comparison SummarySummary:
|
backport of #45389 |
+1
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_14_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_14_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @rappoccio, @antoniovilela, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
Update L1T menu in the 2024 MC GTs with L1Menu_Collisions2024_v1_3_0_xml, as from cmsTalk, as well as the modifier for the L1T menu to be used in data RelVals.
The new L1T menu tag replaces the previous L1Menu_Collisions2024_v1_2_0_xml. The difference wrt the previous tag is summarized here , and the new or removed seeds can be visible also via the Payload Inspector:
The updated 2024 MC GTs in autoCond are the following:
And the difference wrt the GTs previously in autocond are the following:
Please notice that the new
phase1_2024_realistic
GT includes also three additional updates that were not yet propagated to autocond, and therefore pile-up here on top of the L1T menu change:backport of #45389