-
Notifications
You must be signed in to change notification settings - Fork 4.6k
2026 RelVal Workflows #49419
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
2026 RelVal Workflows #49419
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| import FWCore.ParameterSet.Config as cms | ||
|
|
||
| from Configuration.Eras.Era_Run3_2025_FastSim_cff import Run3_2025_FastSim | ||
|
|
||
| Run3_2026_FastSim = cms.ModifierChain(Run3_2025_FastSim) | ||
| Original file line number | Diff line number | Diff line change | ||
|---|---|---|---|---|
| @@ -0,0 +1,5 @@ | ||||
| import FWCore.ParameterSet.Config as cms | ||||
|
|
||||
| from Configuration.Eras.Era_Run3_2025_cff import Run3_2025 | ||||
|
|
||||
| Run3_2026 = cms.ModifierChain(Run3_2025) | ||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I guess this needs to be added to
Otherwise it looks like we're getting the following configuration failures: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-fd870d/49576/runTheMatrix-results/18434.0_TTbar_14TeV+2026/step1_TTbar_14TeV+2026.log |
||||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -14,6 +14,7 @@ | |
| 'relval2023' : 'Fake2', | ||
| 'relval2024' : 'Fake2', | ||
| 'relval2025' : '2025v13', | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. eventually, now that we have coverage I guess we can demote this to fake (in another PR).
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, I'd wait to do that after pre3 is out just to use 2025 for one last round of validations. |
||
| 'relval2026' : 'GRun', | ||
| 'relvalRun4' : '75e33', | ||
| 'relvalRun4_timing' : '75e33_timing', | ||
| 'relvalRun4_trk' : '75e33_trackingOnly', | ||
|
|
||
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.
Just to point out that all other
Run*_FastSimeras are defined starting fromRun*. Is the deviation from that pattern now intentional? (e.g. betting thatRun3_2026will always be the same asRun3_2025)Uh oh!
There was an error while loading. Please reload this page.
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.
For me, this is just a placeholder here. I would ask @cms-sw/simulation-l2 for suggestions.
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.
This is fine for now. I actually hope we will be able to eliminate the Run3_202X_FastSim Eras entirely in the next couple of months, if the GEM developments converge. We will propagate the appropriate updates at that time.