Skip to content
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 Phase1 pixel and Phase2 (2023) eras #12254

Merged
merged 1 commit into from Nov 5, 2015
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
5 changes: 5 additions & 0 deletions Configuration/StandardSequences/python/Eras.py
Expand Up @@ -13,6 +13,7 @@ def __init__(self):
self.run2_HI_specific = cms.Modifier()
self.stage1L1Trigger = cms.Modifier()
self.stage2L1Trigger = cms.Modifier()
self.phase1Pixel = cms.Modifier()
# Implementation note: When this was first started, stage1L1Trigger wasn't in all
# of the eras. Now that it is, it could in theory be dropped if all changes are
# converted to run2_common (i.e. a search and replace of "stage1L1Trigger" to
Expand All @@ -35,6 +36,10 @@ def __init__(self):
self.Run2_HI = cms.ModifierChain( self.run2_common, self.run2_HI_specific, self.stage1L1Trigger )
# Future Run 2 scenarios.
self.Run2_2016 = cms.ModifierChain( self.run2_common, self.run2_25ns_specific, self.stage2L1Trigger )
self.Run2_2017 = cms.ModifierChain( self.Run2_2016, self.phase1Pixel )
# Scenarios further afield.
# Phase2Dev is everything for the 2023 (2026?) detector that works so far in this release.
self.Phase2Dev = cms.Modifier()

# The only thing this collection is used for is for cmsDriver to
# warn the user if they specify an era that is discouraged from being
Expand Down