-
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
[CMSSW_14_0_X] Update the Run4 GT with the updated OMTF config #44305
[CMSSW_14_0_X] Update the Run4 GT with the updated OMTF config #44305
Conversation
A new Pull Request was created by @perrotta for CMSSW_14_0_X. It involves the following packages:
@cmsbuild, @perrotta, @saumyaphor4252, @consuegs can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
cms-bot internal usage |
backport of #44298 |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-4258d3/37887/summary.html Comparison SummarySummary:
|
+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, @sextonkennedy, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
The mcRun4 global tags used for Phase 2 contain an obsolete OMTF configuration, taken from Run 2. The obsolete tag is L1TMuonOverlapParams_static_2016_mc. and it is changed here to L1TMuonOverlapParams_static_2023_mc. The newer configuration is already in use since a while for the most recent mcRun3 global tags.
Relevant cmsTalk with details is:
Modified tag:
L1TMuonOverlapParams_static_2016_mc
toL1TMuonOverlapParams_static_2023_mc
Difference with respect to the previous run4 MC GT:
PR validation:
Successfully tested with the Run4 workflows in the short matrix
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:
Backport of #44298 to CMSSW_14_0_X