updating JECs and Tracker Alignment tag for HLT

[mmusich]

Summary of changes in Global Tags

RunII simulation

• RunII Ideal scenario : 80X_mcRun2_design_v16 as 80X_mcRun2_design_v15 with the following changes:
  • updated JEC to Spring16_25ns_v3 HN
• RunII Asymptotic scenario : 80X_mcRun2_asymptotic_v16 as 80X_mcRun2_asymptotic_v15 with the following changes:
  • updated JEC to Spring16_25ns_v3 HN

RunII data

• RunII Offline processing : 80X_dataRun2_v17 as 80X_dataRun2_v16 with the following changes:
  • updated JEC to Spring16_25ns_v3 HN as in ICHEP2016B re-reco
• RunII HLTHI processing : 80X_dataRun2_HLTHI_frozen_v10 as 80X_dataRun2_HLTHI_frozen_v9 with the following changes:
  • technical change of Tracker Alignment tag to allow enabling of SiPixelAli PCL worfklow
• RunII HLT processing : 80X_dataRun2_HLT_frozen_v13 as 80X_dataRun2_HLT_frozen_v12 with the following changes:
  • technical change of Tracker Alignment tag to allow enabling of SiPixelAli PCL worfklow
• RunII HLT relval processing : 80X_dataRun2_HLT_relval_v12 as 80X_dataRun2_HLT_relval_v11 with the following changes:
  • technical change of Tracker Alignment tag to allow enabling of SiPixelAli PCL worfklow
• RunII Offline relval processing : 80X_dataRun2_relval_v15 as 80X_dataRun2_relval_v14 with the following changes:
  • updated JEC to Spring16_25ns_v3 HN ) as in ICHEP2016B re-reco

Side note: the change of snapshot will allow to "see" in the data (HLT and RECO) Global Tags the new IOV for 2016B as in the ICHEP Re-Reco @fabozzi

[cmsbuild]

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

It involves the following packages:

Configuration/AlCa

@ghellwig, @cerminar, @cmsbuild, @franzoni, @mmusich, @davidlange6 can you please review it and eventually sign? Thanks.
@makortel, @Martin-Grunewald, @ghellwig, @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/13992/console

[cmsbuild]

-1

Tested at: e15fbec

You can see the results of the tests here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-15174/13992/summary.html

I found follow errors while testing this PR

Failed tests: UnitTests RelVals AddOn

• Unit Tests:

I found errors in the following unit tests:

---> test runtestPhysicsToolsPatAlgos had ERRORS

• RelVals:

When I ran the RelVals I found an error in the following worklfows:
25202.0 step2

runTheMatrix-results/25202.0_TTbar_13+TTbar_13+DIGIUP15_PU25+RECOUP15_PU25+HARVESTUP15_PU25/step2_TTbar_13+TTbar_13+DIGIUP15_PU25+RECOUP15_PU25+HARVESTUP15_PU25.log

50202.0 step2

runTheMatrix-results/50202.0_TTbar_13+TTbar_13+DIGIUP15_PU50+RECOUP15_PU50+HARVESTUP15_PU50/step2_TTbar_13+TTbar_13+DIGIUP15_PU50+RECOUP15_PU50+HARVESTUP15_PU50.log

4.22 step1

DAS Error

1000.0 step1

DAS Error

1001.0 step1

DAS Error

• AddOn:

I found errors in the following addon tests:

cmsRun /build/cmsbuild/jenkins-workarea/workspace/ib-any-integration/CMSSW_8_0_X_2016-07-10-0000/src/PhysicsTools/PatAlgos/test/IntegrationTest_cfg.py : FAILED - time: date Tue Jul 12 17:37:49 2016-date Tue Jul 12 17:37:04 2016 s - exit: 23552

[mmusich]

nice...

[mmusich]

please test

[cmsbuild]

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

[cmsbuild]

-1

Tested at: e15fbec

You can see the results of the tests here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-15174/14005/summary.html

I found follow errors while testing this PR

Failed tests: UnitTests RelVals

• Unit Tests:

I found errors in the following unit tests:

---> test runtestPhysicsToolsPatAlgos had ERRORS

• RelVals:

When I ran the RelVals I found an error in the following worklfows:
1000.0 step1

DAS Error

1001.0 step1

DAS Error

[mmusich]

please test

[cmsbuild]

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

[mmusich]

@cmsbuild please test

[cmsbuild]

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

[cmsbuild]

+1
Tested at: e15fbec
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-15174/14122/summary.html

[cmsbuild]

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

[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, @smuzaffar

[mmusich]

@davidlange6 just to clarify the apparent change in the run2 MC GTs, it should not change the physics performance, since in the new payloads (V3 vs V1) a new level of correction (not consumed) is added, while keeping the rest the same. Please refer to this thread HN link @blinkseb FYI.

[davidlange6]

@mmusich - when discussed yesterday this PR affected only data - however it looks like MC GTs are also updated. Are these already in use for production?

[mmusich]

Hi @davidlange6,
see please my comment #15174 (comment).
The change is somewhat only technical being the content of the level of the Jet corrections consumed at miniAOD the same. I think the JETMET group changed the nomenclature mostly to keep the same version number of the data ones (see here: https://hypernews.cern.ch/HyperNews/CMS/get/calibrations/2417/1/1/1.html).
On a side note, this has already been validated in 81x.

[davidlange6]

+1