Run2-sim30 Try to remove dependency of Reco geometry for CaloSteppingAction

[bsunanda]

Step toward to have a code which can do scoring for Geant4 as well as GeantV

[cmsbuild]

The code-checks are being triggered in jenkins.

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-26023/8544

• This PR adds an extra 32KB to repository

[cmsbuild]

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

It involves the following packages:

Geometry/HcalCommonData
SimG4CMS/Calo

@civanch, @Dr15Jones, @cvuosalo, @ianna, @mdhildreth, @cmsbuild can you please review it and eventually sign? Thanks.
@makortel this is something you requested to watch as well.
@davidlange6, @slava77, @fabiocos you are the release manager for this.

cms-bot commands are listed here

[bsunanda]

@cmsbuild Please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/33308/console Started: 2019/02/26 22:49

[cmsbuild]

+1
Tested at: 8590bc8
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-26023/33308/summary.html

[cmsbuild]

Comparison job queued.

[cmsbuild]

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

Comparison Summary:

• No significant changes to the logs found
• Reco comparison results: 4 differences found in the comparisons
• DQMHistoTests: Total files compared: 32
• DQMHistoTests: Total histograms compared: 3098286
• DQMHistoTests: Total failures: 1
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3098088
• DQMHistoTests: Total skipped: 197
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 31 files compared)
• Checked 133 log files, 14 edm output root files, 32 DQM output files

[cvuosalo]

+1

[civanch]

+1

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2)

[fabiocos]

@bsunanda @civanch for my understanding could you please clarify the purpose of this PR, apart for the cleaning of couts? Is the CaloSteppingAction not used in the default workflow, as I would say from configurations?

[bsunanda]

@fabiocos @civanch These codes are developed to allow a common platform of comparing Geant4 and GeantV. Certainly this is not in standard workflow and will be used by experts making the comparisons (both physics and performance). CaloSteppingAction without reference to Hcal geometry is the source of the scoring code

[fabiocos]

+1