bsunanda:Phase2-hgx73 Add a new scenario with TDR version for HGCal

[bsunanda]

No description provided.

[cmsbuild]

A new Pull Request was created by @bsunanda for master.

It involves the following packages:

Configuration/Geometry
Configuration/StandardSequences
Geometry/CMSCommonData

@civanch, @Dr15Jones, @ianna, @mdhildreth, @cmsbuild, @franzoni, @kpedro88, @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

[bsunanda]

@cmsbuild Please test

[cmsbuild]

The tests are being triggered in jenkins.

[boudoul]

Dear @bsunanda , @kpedro88 presumably this file
https://github.com/cms-sw/cmssw/blob/master/Configuration/Geometry/python/dict2023Geometry.py , should be updated (and used) ?

[cmsbuild]

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

[bsunanda]

@cmsbuild Please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/18563/console Started: 2017/03/20 18:25

[ianna]

+1

[kpedro88]

@bsunanda should there also be a matrix workflow defined for the D13 scenario?

NB, this PR will have to be rebased/updated if #17970 is merged first, due to a change in the M2 geometry.

[kpedro88]

@bsunanda I sent you bsunanda#11 with the workflow. I tested 10 events of ttbar (24834.0) and it runs fine, no unexpected errors or warnings.

[cmsbuild]

+1
Tested at: 504fd5a
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-17995/18563/summary.html

[cmsbuild]

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

[bsunanda]

@cmsbuild Please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/18574/console Started: 2017/03/20 21:24

[cmsbuild]

+1
Tested at: b1cbf5d
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-17995/18574/summary.html

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
b1cbf5d
You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-17995/18574/git-log-recent-commits
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-17995/18574/git-merge-result

[cmsbuild]

Comparison job queued.

[ianna]

+1

[cmsbuild]

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

[fabozzi]

+1

[kpedro88]

+1
(since this one seems ready to go and #17970 is not, we can merge this one first and that one will have to update accordingly)

[Dr15Jones]

The newly added workflows are failing with the exception

----- Begin Fatal Exception 23-Mar-2017 21:19:18 CET-----------------------
An exception of category 'ProductNotFound' occurred while
   [0] Processing  Event run: 1 lumi: 1 event: 4 stream: 2
   [1] Running path 'digi2raw_step'
   [2] Calling method for module HcalDigiToRaw/'hcalRawDataVME'
Exception Message:
Principal::getByToken: Found zero products matching all criteria
Looking for type: edm::SortedCollection<HcalTriggerPrimitiveDigi,edm::StrictWeakOrdering<HcalTriggerPrimitiveDigi> >
Looking for module label: simHcalTriggerPrimitiveDigis
Looking for productInstanceName: 

   Additional Info:
      [a] If you wish to continue processing events after a ProductNotFound exception,
add "SkipEvent = cms.untracked.vstring('ProductNotFound')" to the "options" PSet in the configuration.

----- End Fatal Exception -------------------------------------------------

[kpedro88]

@Dr15Jones where are you seeing that? The relval log for 24834.0 in CMSSW_9_1_X_2017-03-23-1100 looks fine to me. (I had also tested it privately before adding it in this PR...)