Skip to content

Commit

Permalink
Merge pull request #12254 from mark-grimes/addPhase1AndPhase2Eras
Browse files Browse the repository at this point in the history
Add Phase1 pixel and Phase2 (2023) eras
  • Loading branch information
davidlange6 committed Nov 5, 2015
2 parents fb81efe + 1ac941b commit af4aac5
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions Configuration/StandardSequences/python/Eras.py
Original file line number Diff line number Diff line change
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

0 comments on commit af4aac5

Please sign in to comment.