-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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 eras for 2016 and Run 1 (76X) #12117
Add eras for 2016 and Run 1 (76X) #12117
Conversation
A new Pull Request was created by @mark-grimes (Mark Grimes) for CMSSW_7_6_X. Add eras for 2016 and Run 1 (76X) It involves the following packages: Configuration/StandardSequences @cmsbuild, @franzoni, @davidlange6 can you please review it and eventually sign? Thanks. |
please test |
The tests are being triggered in jenkins. |
+1 |
Add eras for 2016 and Run 1 (76X)
As requested this is a back port of #12023 for 7_6_X. There was some discussion on there about changing era names, but then it was merged so I assume everything is okay. If not please comment here.
The description for #12023 copied here for completeness:
This adds a
Run2_2016
era that uses the stage 2 trigger. Thestage2L1Trigger
sub-era component of it is currently empty, but I'm expecting trigger experts to apply the correct commands.A
Run1
era is also added. This is foreseen as a no-operation era to help with scripting cmsDriver commands (e.g.--era=$MY_ERA
). However, it also adds the flexibility to add customisation changes at a later date.Both of these additions were discussed in the 20/Oct/2015 release planning meeting.