-
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
[12.4_HLT_X
] HLT configurations for 2022 MC: remove menu 2022 V1.2
#46034
[12.4_HLT_X
] HLT configurations for 2022 MC: remove menu 2022 V1.2
#46034
Conversation
A new Pull Request was created by @mmusich for CMSSW_12_4_HLT_X. It involves the following packages:
@Martin-Grunewald, @cmsbuild, @consuegs, @mmusich, @perrotta, @saumyaphor4252 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
cms-bot internal usage |
Incidentally, I checked with this script which are the GTs in autoCond that still contain the L1T menu
I would still at least update the keys |
@cms-sw/alca-l2 do you have any news about this? |
Dear @mmusich, Please update of the GlobalTags in
Please let me know if you need anywhere else to update in order to test this PR. Thanks |
610d908
to
68132ca
Compare
…_xml, as needed by the HLT menus HLT:2022v14 (or v15) Co-authored-by: atpathak <pathakatanu01@gmail.com>
68132ca
to
adc04b6
Compare
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-92b987/41786/summary.html Comparison SummarySummary:
|
+hlt |
+alca
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_4_HLT_X IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @rappoccio, @antoniovilela, @sextonkennedy, @mandrenguyen (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Development of HLT menu for
CMSSW_12_4_HLT_X
.This update is meant exclusively for the Summer2024 production of Run 3 MC.
This PR is NOT a backport.
This PR is a follow-up to #45939.
The goal of this PR is to remove the frozen menu 2022 V1.2 only from
CMSSW_12_4_HLT_X
(which is the branch in which CMS targets to run the HLT step of theRun3Summer2024
MC production).As it was agreed to use the frozen menu V1.5 for that (that was proposed in #45939), the earlier version V1.2 (for 2022 pre-EE era) will not be needed in this particular branch, thus it is removed to avoid possible confusions.
In order to remove the menu from the release and avoid massive relval failures, jointly with the removal commit 72a3bd0 there is an update of the GlobalTags in
autoCond.py
(commit adc04b6) for the following keys:run3_hlt_relval
:124X_dataRun3_HLT_relval_v9
→124X_dataRun3_HLT_relval_v10
(diff)run3_data_relval
:124X_dataRun3_relval_v13
→124X_dataRun3_relval_v14
(diff)phase1_2022_realistic
:124X_mcRun3_2022_realistic_v12
→124X_mcRun3_2022_realistic_v13
(diff)phase1_2023_realistic
:124X_mcRun3_2023_realistic_v13
→124X_mcRun3_2023_realistic_v14
(diff)phase1_2024_realistic
:124X_mcRun3_2024_realistic_v13
→124X_mcRun3_2024_realistic_v14
(diff)phase1_2022_realistic_postEE
:124X_mcRun3_2022_realistic_postEE_v1
→124X_mcRun3_2022_realistic_postEE_v3
(diff)The first five of them contain the L1T menu tag
L1Menu_Collisions2022_v1_2_0_xml
(which is incompatible with the menu 2022 V1.5 that we are targeting to use for tests), while the last is an update requested by AlCa.The exact content of the MC GT is still being discussed in this cmsTalk thread, but these are intermediate GlobalTags for these keys that contain instead
L1Menu_Collisions2022_v1_3_0-d1_xml
(compatible with menu V1.5) such that we could (at least techincally) remove V1.2 from this branch.PR validation:
I performed the following tests:
addOnTests.py
runs fine.runTheMatrix.py -l limited --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, not to be backported.