Adding RelVal Global Tags for Run2 data

[mmusich]

Addresses issues as outlined in:
https://hypernews.cern.ch/HyperNews/CMS/get/relval/4478/1/2/1/1/2/1/1.html
To avoid mergeing conflicts it takes commits to Configuration/PyReleaseValidation/python/relval_steps.py from #13267 and also to Configuration/AlCa/python/autoCond.py from #13115.

Differences of the newly introduced Global Tags:

RunII data

• RunII Offline processing : 80X_dataRun2_relval_v0 as 80X_dataRun2_v5 with the following changes:
  • single IOV L1 menu (v5);
• RunII HLT processing : 80X_dataRun2_HLT_relval_v0 as 80X_dataRun2_HLT_frozen_v2 with the following changes:
  • single IOV L1 menu (v5);

[cmsbuild]

A new Pull Request was created by @mmusich (Marco Musich) for CMSSW_8_0_X.

It involves the following packages:

Configuration/AlCa
Configuration/PyReleaseValidation

@diguida, @boudoul, @franzoni, @cerminar, @fabozzi, @cmsbuild, @srimanob, @mmusich, @hengne, @davidlange6 can you please review it and eventually sign? Thanks.
@ghellwig, @Martin-Grunewald, @tocheng this is something you requested to watch as well.
@slava77, @Degano, @smuzaffar you are the release manager for this.

cms-bot commands are list here #13028

[mmusich]

please test

[cmsbuild]

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

[cmsbuild]

+1
Tested at: 688ca9e
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-13280/11213/summary.html

[hengne]

+1

[mmusich]

+1

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_8_0_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @Degano, @smuzaffar

[cmsbuild]

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

[davidlange6]

@mmusich - what are the run 1 GT changes?

[mmusich]

@davidlange6 no specific run changes, run1 and run2 GT keys are the same since beginning of the 80X release cycle, so that when we add new records, like here for the benefit of #13115, both keys are involved.

[davidlange6]

ah - maybe we can also unify the keys in the alca matrix - I guess I will continue to be confused:)

On Feb 15, 2016, at 7:37 PM, Marco Musich notifications@github.com wrote:

@davidlange6 no specific run changes, run1 and run2 GT keys are the same since beginning of the 80X release cycle, so that when we add new records, like here for the benefit of #13115, both keys are involved.

—
Reply to this email directly or view it on GitHub.

[mmusich]

@davidlange6 we could do that, but we would need also to clean the relval steps configuration and probably several tens of occurrences in privately owned configuration files. Shall I do this with this PR?

[davidlange6]

is not an emergency! but seems like the right solution assuming you plan to keep one GT for data (I guess you do)

On Feb 15, 2016, at 9:28 PM, Marco Musich notifications@github.com wrote:

@davidlange6 we could do that, but we would need also to clean the relval steps configuration and probably several tens of occurrences in privately owned configuration files. Shall I do this with this PR?

—
Reply to this email directly or view it on GitHub.

[davidlange6]

+1