-
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 2023 MC GTs with the fixed L1T tag and re-snapshot the data GTs #42358
Update 2023 MC GTs with the fixed L1T tag and re-snapshot the data GTs #42358
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42358/36390
|
A new Pull Request was created by @saumyaphor4252 (Saumya Phor) for master. It involves the following packages:
@perrotta, @consuegs, @cmsbuild, @saumyaphor4252, @francescobrivio, @tvami can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
@cmsbuild, please abort |
test parameters:
|
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-173142/33878/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. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR updates the:
L1TMuonGlobalParams_Stage2v0_2023_mc_v2
to resolve the discrepancy observed in [1]. Also, see CMS Talk post [2] for the relevant tag details.[1] https://cms-pdmv.cern.ch/relmon/1688568203___CMSSW_13_2_0_pre2_2023vsCMSSW_13_1_0_pre4_2023/FullSimReport_HLT/RelValWToLNu_14TeV_131X_mcRun3_2023_realistic_v4_2023/7fdc3f5aa9.html
[2] https://cms-talk.web.cern.ch/t/mc-call-for-conditions-for-2023-mc/24376/23
GT Differences with respect to the last ones:
run3_hlt
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/130X_dataRun3_HLT_frozen_v3/130X_dataRun3_HLT_frozen_v4
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/130X_dataRun3_HLT_v2/130X_dataRun3_HLT_frozen_v4
run3_data_express:
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/130X_dataRun3_Express_frozen_v3/130X_dataRun3_Express_frozen_v4
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/130X_dataRun3_Express_v3/130X_dataRun3_Express_frozen_v4
run3_data_prompt::
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/130X_dataRun3_Prompt_frozen_v3/130X_dataRun3_Prompt_frozen_v4
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/130X_dataRun3_Prompt_v4/130X_dataRun3_Prompt_frozen_v4
Phase1 2023 realistic:
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/131X_mcRun3_2023_realistic_v8/131X_mcRun3_2023_realistic_v9
Phase1 2023 cosmics realistic:
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/131X_mcRun3_2023cosmics_realistic_deco_v8/131X_mcRun3_2023cosmics_realistic_deco_v9
PR validation:
GTs tested locally with
runTheMatrix.py -l 139.001,141.002,141.003,138.2,138.4,141.001,141.006,141.008,141.004,12434.0,12634.99 -j 8 --ibeos
runTheMatrix.py -l 12430.0,12440.0 --what upgrade -j 8 --ibeos
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:
Not a backport but
132X
,131X
and130X
backports will be followed up right after