Updating JEC in data/mc and fixes for HI

[mmusich]

Summary of changes in GT

RunII simulation

• RunII Ideal scenario : 76X_mcRun2_design_v11 as 76X_mcRun2_design_v12 with the following changes:
  • updated MC JEC to v6 with updated L2L3Residuals and uncertainties for 25ns.
• RunII Asymptotic scenario : 76X_mcRun2_asymptotic_v11 as 76X_mcRun2_asymptotic_v12 with the following changes:
  • updated MC JEC to v6 with updated L2L3Residuals and uncertainties for 25ns;
  • adding label JEC with AK4Calo label for pp reference run at 5TeV.
• RunII Heavy Ions scenario : 76X_mcRun2_HeavyIon_v11 as 76X_mcRun2_HeavyIon_v12 with the following changes:
  • adding event plane calibrations for HI trough HeavyIonRPRcd;
  • adding label JEC with AK4Calo label for pp reference run at 5TeV.

RunI data

• RunI Offline processing : 76X_dataRun1_v10 as 76X_dataRun1_v11 with the following changes:
  • adding event plane calibrations for HI trough HeavyIonRPRcd;
  • adding label JEC with AK4Calo label for pp reference run at 5TeV;
  • updating AlCaReco Trigger bits to cover 2010 HI runs for new Tracker Alignment AlCaReco producers.

RunII data

• RunII Offline processing : 76X_dataRun2_v10 as 76X_dataRun2_v11 with the following changes:
  • adding event plane calibrations for HI trough HeavyIonRPRcd;
  • adding label JEC with AK4Calo label for pp reference run at 5TeV;
  • updating AlCaReco Trigger bits to cover 2010 HI runs for new Tracker Alignment AlCaReco producers.
  • updated DATA JEC to v3 with updated L2L3Residuals and uncertainties for 25ns;

[mmusich]

please test

[cmsbuild]

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

[cmsbuild]

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

Updating JEC in data/mc and fixes for HI

It involves the following packages:

Configuration/AlCa

@cmsbuild, @mmusich, @diguida, @franzoni, @cerminar can you please review it and eventually sign? Thanks.
@ghellwig, @Martin-Grunewald 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' or '@cmsbuild, please test' 'please test with cms-sw/cmsdist#PR' 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.

[cmsbuild]

Pull request #12349 was updated. @cmsbuild, @mmusich, @diguida, @franzoni, @cerminar can you please check and sign again.

[mmusich]

@cmsbuild please test

[cmsbuild]

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

[cmsbuild]

+1
Tested at: 703cffe
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-12349/9607/summary.html

[cmsbuild]

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

[mmusich]

+1

[cmsbuild]

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

[davidlange6]

a bit surprised that nothing seems to have changed in the comparisons of this PR.. Approving but might be worth a double check as I would have expected the DQM to consume the new JEC (naively)

[mmusich]

@davidlange6 as far as I could understand the JETMET POG provided new payloads with updates concerning only the uncertainties (used in the miniAOD and possibly nowhere else). Please @blinkseb @schoef confirm.

[schoef]

No changes expected in MC since MC JEC are identical. Uncertainties are presumably not tested.