[102X][Change GTs] 2016,2017 JES and JER

[lpernie]

Offline Data:

• https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/102X_dataRun2_v2/102X_dataRun2_v1
• https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/102X_dataRun2_relval_v3/102X_dataRun2_relval_v2

2016 Simulation

• https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/102X_mcRun2_asymptotic_v1/101X_mcRun2_asymptotic_v5
• https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/101X_mcRun2_design_v5/102X_mcRun2_design_v1
• https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/101X_mcRun2_startup_v5/102X_mcRun2_startup_v1
• https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/101X_mcRun2cosmics_startup_deco_v5/102X_mcRun2cosmics_startup_deco_v1
• https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/101X_mcRun2_HeavyIon_v6/102X_mcRun2_HeavyIon_v1
• https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/101X_mcRun2_pA_v5/102X_mcRun2_pA_v1

2017 Simulation

• https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/102X_mc2017_realistic_v1/101X_mc2017_realistic_v7
• https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/101X_mc2017_design_IdealBS_v7/102X_mc2017_design_IdealBS_v1
• https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/101X_mc2017cosmics_realistic_peak_v7/102X_mc2017cosmics_realistic_peak_v1
• https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/101X_mc2017cosmics_realistic_deco_v7/102X_mc2017cosmics_realistic_deco_v1

[cmsbuild]

The code-checks are being triggered in jenkins.

[lpernie]

please test

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-23212/4671

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/27968/console Started: 2018/05/16 02:28

[cmsbuild]

A new Pull Request was created by @lpernie (Luca Pernie) for master.

It involves the following packages:

Configuration/AlCa

@cmsbuild, @franzoni, @arunhep, @cerminar, @lpernie can you please review it and eventually sign? Thanks.
@makortel, @Martin-Grunewald, @mmusich, @tocheng this is something you requested to watch as well.
@davidlange6, @slava77, @fabiocos you are the release manager for this.

cms-bot commands are listed here

[cmsbuild]

+1
Tested at: 93eb792
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-23212/27968/summary.html

[cmsbuild]

Comparison job queued.

[cmsbuild]

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

Comparison Summary:

• No significant changes to the logs found
• Reco comparison results: 160 differences found in the comparisons
• DQMHistoTests: Total files compared: 30
• DQMHistoTests: Total histograms compared: 2715235
• DQMHistoTests: Total failures: 19
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 2715033
• DQMHistoTests: Total skipped: 183
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 29 files compared)
• Checked 124 log files, 14 edm output root files, 30 DQM output files

[lpernie]

+1

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2)

[fabiocos]

please test

now the code that is expected to fix the reproducibility of tests has been merged, try again

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/28097/console Started: 2018/05/22 09:02

[cmsbuild]

+1
Tested at: ff80a53
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-23212/28097/summary.html

[cmsbuild]

Comparison job queued.

[cmsbuild]

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

Comparison Summary:

• No significant changes to the logs found
• Reco comparison results: 985 differences found in the comparisons
• DQMHistoTests: Total files compared: 31
• DQMHistoTests: Total histograms compared: 2901712
• DQMHistoTests: Total failures: 4279
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 2897243
• DQMHistoTests: Total skipped: 190
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 30 files compared)
• Checked 128 log files, 14 edm output root files, 31 DQM output files

[fabiocos]

@lpernie @arunhep are the changes to Run1 test workflows expected? The PR is referring to 2016 and 2017 samples...

[lpernie]

Hello @fabiocos ,
I discussed with Sangeun.
The previous TAGs were single IOV TAGs with a payload describing 2017 data, and they were starting from RUN=1.
The new TAGs include 3 IOV for 2016 and 1 IOV for 2017. Also in this case they to start from RUN=1, so changes in the RUN1 workflow are observed.

[fabiocos]

@lpernie thanks for the clarification, my question is: is this the behaviour that we want? I understand that the Run1 legacy release cycle is 53X, but...

[lpernie]

Hi @fabiocos ,
I cannot imagine an better solution. Maybe that these TAGs could start not from RUN=1 but from the first RUN in 2016, but is something we prefer to avoid as a general rule.

[fabiocos]

+1