-
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
Add workflows for 2023 and 2024. Replace 13TeV 2021 by 14TeV. #27433
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27433/10736
|
A new Pull Request was created by @zhenhu (Zhen Hu) for master. It involves the following packages: Configuration/PyReleaseValidation @pgunnell, @zhenhu, @prebello, @cmsbuild, @kpedro88 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@zhenhu what is 2024? I was under the impression Run3 would end after 2023... |
|
||
upgradeProperties[2017]['2024PU'] = deepcopy(upgradeProperties[2017]['2024']) | ||
upgradeProperties[2017]['2024PU']['ScenToRun'] = ['GenSimFull','DigiFullPU','RecoFullPU','HARVESTFullPU','NanoFull'] | ||
|
||
upgradeProperties[2023] = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will the Run 4 workflows be renamed at some point? Now there would be workflows with "2023" in their names for Run 3 and Run 4.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this will be done as part of #26938. Maybe it's better to hold this until I can implement all the cleanup there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kpedro88 @makortel Nominally Run 3 will end after 2023 but there are studies underway to investigate detector performance if Run 3 is extended by one year. The "2023" and "2024" scenarios correspond to simulation of the CMS detector after integrated luminosities of 450 fb-1 and 550 fb-1 respectively. See slide 18 of the PPD update at CMS Week
From the AlCa perspective, we would like to introduce 11_0_X queues for the 450 fb-1 and 550 fb-1 scenarios so that we can integrate new developments for these queues while closing the 10_6_X mcRun3_2023 and mcRun3_2024 queues to anything other than bug fixes. At the same time, we would like to rename all of the Run 3 and later GTs to standardize the naming. The year would be left off the name of the "mcRun4" scenario until a need to distinguish between the various years arises. This is the content of the autoCond update that @zhenhu referenced at the introduction to this PR.
@kpedro88, would the autoCond update by itself conflict with your goals in #26938?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently the autoCond key used in the Phase 2 workflows is auto:phase2_realistic
. If this key is preserved (even if the value changes), it should not interfere with the upcoming Phase 2 cleanup.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kpedro88 I think we need to agree on a global strategy before integrating bits and pieces that contradict each other
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer to submit the phase 2 cleanup before this, as it has been delayed for several weeks now by other conflicting developments. Today is a holiday in the US, but I might be able to prepare it tomorrow.
'2023' : { | ||
'Geom' : 'DB:Extended', | ||
'GT' : 'auto:phase1_2023_realistic', | ||
'HLTmenu': '@relval2017', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@zhenhu @mmusich indeed the idea is to use the new menu for Run3 as proposed by @Martin-Grunewald in #27331 for already existing workflows
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
+1 |
unhold |
+upgrade |
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. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
@zhenhu |
PR description:
Add new workflows for run3 2023 and 2024 scenarios.
Replace the 13TeV 2021 workflows by 14TeV.
This PR should be merged with the AlCa PR at the same time: https://github.com/cms-sw/cmssw/compare/CMSSW_11_0_X...christopheralanwest:alca-gt-2023-2024?expand=1
PR validation:
Local validation done