Phase2 hcx3

[bsunanda]

New scenario

[cmsbuild]

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

Phase2 hcx3

It involves the following packages:

Configuration/Geometry
Geometry/CMSCommonData
SimG4CMS/Calo

@civanch, @Dr15Jones, @ianna, @mdhildreth, @cmsbuild, @nclopezo, @Degano, @ktf can you please review it and eventually sign? Thanks.
@ghellwig 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.
@fratnikov, @mark-grimes you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

[ianna]

+1

[mark-grimes]

All normal tests with muons and pions pass except for known errors. I also tried

runTheMatrix.py -w upgrade -l 13800,13861 --command "--geometry Extended2023SHCalNoTaperRebuild"

and both failed in step 1 with

----- Begin Fatal Exception 18-Jun-2014 12:52:32 CEST-----------------------
An exception of category 'EventSetupConflict' occurred while
   [0] Calling EventProcessor::runToCompletion (which does almost everything after beginJob and before endJob)
Exception Message:
two EventSetup Producers want to deliver type="GeometricDet" label=""
 from record IdealGeometryRecord. The two providers are 
1) type="TrackerGeometricDetESModule" label="trackerNumberingGeometryDB"
2) type="TrackerGeometricDetESModule" label="trackerNumberingSLHCGeometry"
Please either
   remove one of these Producers
   or find a way of configuring one of them so it does not deliver this data
   or use an es_prefer statement in the configuration to choose one.
----- End Fatal Exception -------------------------------------------------

Nothing existing is broken however so happy to merge, but does this also require customisations and a workflow in runTheMatrix from our side?

[mark-grimes]

merge