Add eras for 2016 and Run 1

[mark-grimes]

This adds a Run2_2016 era that uses the stage 2 trigger. The stage2L1Trigger 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.

[cmsbuild]

A new Pull Request was created by @mark-grimes (Mark Grimes) for CMSSW_8_0_X.

Add eras for 2016 and Run 1

It involves the following packages:

Configuration/StandardSequences

@cmsbuild, @franzoni, @davidlange6 can you please review it and eventually sign? Thanks.
@ghellwig, @makortel, @GiacomoSguazzoni, @rovere, @VinInn, @Martin-Grunewald, @cerati, @dgulhan this is something you requested to watch as well.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.
If you are a L2 or a release manager you can ask for tests by saying 'please test' in the first line of a comment.
@Degano you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

[Martin-Grunewald]

please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/9119/console

[cmsbuild]

The jenkins tests job failed, please try again.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/9119/console

[cmsbuild]

+1
Tested at: 2b3418a
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-12023/9124/summary.html

[cmsbuild]

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-12023/9124/summary.html

[davidlange6]

@mark-grimes - thinking outloud - is changing run2 to 2015 a big deal at this point?

[mark-grimes]

You mean changing the name? Not really, git grep should easily point out all occurrences. The only thing is that it would introduce a lot of merge conflicts for things in the queue if people have started using them.

[davidlange6]

@mark-grimes - right - maybe this can be done purely within cms driver, as for most people, 2015 and 2016 (and 2017 and 2018) will be the same "run2". Also, we should do this in 76x together with adding a run1 era.

[mark-grimes]

I'm confused what you mean about doing it in cmsDriver. If that decision is hidden from the user then there would have to be some analysis of the input file to decide which year/scenario it's from and hence which era to activate.

Whatever happens, PRs in 7_6_X are automatically forward ported to 8_0_X, so I should close this one right?

[mark-grimes]

7_6_X version is #12117.