[RFC] Add eras to select tracking configuration for 2017 detector #13266
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on the discussion in the HN thread https://hypernews.cern.ch/HyperNews/CMS/get/edmFramework/3597/1/2/1/1/1/1/1/1/1/1/1/1/1/1/1/1.html
I did the simplest (of the proposed alternatives) modification to
Eras.py
fulfilling our (TRK) need to run three tracking configurations with the phase1 detector.If this PR gets accepted, my plan for phase1 tracking era-migration is to do following two steps
trackingPhase1
eratrackingPhase1
era to the configuration in Update phase1 (2017) tracking sequence #13149, and move Phase1PU70-tracking totrackingPhase1PU70
eraTested in CMSSW_8_0_X_2016-02-11-2300, no changes expected.
@rovere @VinInn