Phase2 workflow updates (add D14, D12 in short matrix, new OOT PU settings, Timing)

[kpedro88]

This PR contains several Phase2 workflow updates toward the Muon/Barrel TDR:

1. Add D14 scenario as D12 w/ T5 tracker (extra disk), corresponding workflows
2. Remove D7 from short matrix (uses C1, nobody really cares anymore), add D12
3. Default OOT window for Phase2 is now -3,+3 for 140 and 200 PU. Alternate versions with the old -12,+3 and a new special option -6,+6 are added (only for 25ns).
4. Reduce code duplication in relval_2023 (used to port upgrade workflows to regular matrix); here I fixed a bug where the trackingOnly workflows in the upgrade matrix didn't have the right beamspot for 14 TeV
5. Remove separate _Timing workflow keys (associated WF numbers added to skip list so other numbers won't change); instead add timing workflow variations as 2XXXX.2, only for ttbar (just Era changes), and run in IBs

attn: @boudoul @makortel @calabria @slava77 @mdhildreth

[cmsbuild]

A new Pull Request was created by @kpedro88 (Kevin Pedro) for master.

It involves the following packages:

Configuration/Geometry
Configuration/PyReleaseValidation
Configuration/StandardSequences
Geometry/CMSCommonData

@civanch, @Dr15Jones, @ianna, @mdhildreth, @fabozzi, @cmsbuild, @franzoni, @kpedro88, @GurpreetSinghChahal, @davidlange6 can you please review it and eventually sign? Thanks.
@ghellwig, @makortel, @felicepantaleo, @GiacomoSguazzoni, @rovere, @VinInn, @Martin-Grunewald, @ebrondol, @dgulhan this is something you requested to watch as well.
@Muzaffar, @davidlange6, @smuzaffar you are the release manager for this.

cms-bot commands are listed here #13028

[kpedro88]

@cmsbuild please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/19203/console Started: 2017/04/17 20:08

[cmsbuild]

+1
Tested at: cee79af
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-18373/19203/summary.html

[cmsbuild]

Comparison job queued.

[cmsbuild]

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

Comparison Summary:

• You potentially added 73 lines to the logs
• Reco comparison results: 3243 differences found in the comparisons
• DQMHistoTests: Total files compared: 22
• DQMHistoTests: Total histograms compared: 1766732
• DQMHistoTests: Total failures: 30047
• DQMHistoTests: Total nulls: 1
• DQMHistoTests: Total successes: 1736518
• DQMHistoTests: Total skipped: 166
• DQMHistoTests: Total Missing objects: 0
• Checked 90 log files, 14 edm output root files, 22 DQM output files

[kpedro88]

+1

[kpedro88]

also attn @lgray

[civanch]

+1

[kpedro88]

@fabozzi @GurpreetSinghChahal please sign

[fabozzi]

+1

[cmsbuild]

Pull request #18373 was updated. @civanch, @Dr15Jones, @ianna, @mdhildreth, @fabozzi, @cmsbuild, @franzoni, @kpedro88, @GurpreetSinghChahal, @davidlange6 can you please check and sign again.

[kpedro88]

@cmsbuild please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/19421/console Started: 2017/04/26 18:02

[cmsbuild]

+1
Tested at: 2edef77
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-18373/19421/summary.html

[cmsbuild]

Comparison job queued.

[cmsbuild]

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

Comparison Summary:

• No significant changes to the logs found
• Reco comparison results: 1690 differences found in the comparisons
• DQMHistoTests: Total files compared: 22
• DQMHistoTests: Total histograms compared: 1730813
• DQMHistoTests: Total failures: 37810
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 1692837
• DQMHistoTests: Total skipped: 166
• DQMHistoTests: Total Missing objects: 0
• Checked 90 log files, 14 edm output root files, 22 DQM output files

[kpedro88]

+1

[Dr15Jones]

It appears this change is causing two workflows to fail in the IB 26234.0 and 26234.2 with the error

----- Begin Fatal Exception 27-Apr-2017 19:37:49 CEST-----------------------
An exception of category 'StdException' occurred while
   [0] Processing  Event run: 1 lumi: 1 event: 1 stream: 3
   [1] Running path 'L1TrackTrigger_step'
   [2] Calling method for module TTStubBuilder_Phase2TrackerDigi_/'TTStubsFromPhase2TrackerDigis'
Exception Message:
A std::exception was thrown.
vector::_M_range_check: __n (which is 12) >= this->size() (which is 12)
----- End Fatal Exception -------------------------------------------------

[kpedro88]

Hm, those are the new workflows that were added for D14 (which is D12 with T5, the extra pixel disk).

@sviret @boudoul can you check why the track trigger does not work for D14, but works for D11?

[boudoul]

Hi , it does not work (yet) for D11, it has been disabled in D11 WFs