Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Account for layer offset when using waferZ in new geometry #27503

Merged
merged 1 commit into from
Jul 15, 2019

Conversation

clelange
Copy link
Contributor

@clelange clelange commented Jul 11, 2019

PR description:

There is a bug in RecHitTools::getPositionLayer(int layer, bool nose): when getting the z position of the wafer, one needs to account for the FH (HGCalSi) offset, starting the layer number at 1 instead of continuing to count up beyond EE.

PR validation:

Ran in D41 (geometryType_ == 1) and instead of getting z = 0 for layers > 28, I actually obtained increasing z values:

layer 1: z = 322.103
layer 2: z = 323.047
layer 3: z = 325.073
layer 4: z = 326.017
layer 5: z = 328.043
layer 6: z = 328.987
layer 7: z = 331.013
layer 8: z = 331.957
layer 9: z = 333.983
layer 10: z = 334.927
layer 11: z = 336.953
layer 12: z = 337.897
layer 13: z = 339.923
layer 14: z = 340.867
layer 15: z = 342.893
layer 16: z = 343.837
layer 17: z = 345.863
layer 18: z = 346.807
layer 19: z = 348.833
layer 20: z = 349.777
layer 21: z = 351.803
layer 22: z = 352.747
layer 23: z = 354.773
layer 24: z = 355.717
layer 25: z = 357.743
layer 26: z = 358.687
layer 27: z = 360.713
layer 28: z = 361.657
layer 29: z = 367.699
layer 30: z = 373.149
layer 31: z = 378.599
layer 32: z = 384.049
layer 33: z = 389.499
layer 34: z = 394.949
layer 35: z = 400.399
layer 36: z = 405.849
layer 37: z = 411.299
layer 38: z = 416.749
layer 39: z = 422.199
layer 40: z = 427.649
layer 41: z = 436.199
layer 42: z = 444.749
layer 43: z = 453.299
layer 44: z = 461.849
layer 45: z = 470.399
layer 46: z = 478.949
layer 47: z = 487.499
layer 48: z = 496.049
layer 49: z = 504.599
layer 50: z = 513.149

FYI @bsunanda

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27503/10846

  • This PR adds an extra 12KB to repository

  • There are other open Pull requests which might conflict with changes you have proposed:

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @clelange (Clemens Lange) for master.

It involves the following packages:

RecoLocalCalo/HGCalRecAlgos

@perrotta, @cmsbuild, @kpedro88, @slava77 can you please review it and eventually sign? Thanks.
@edjtscott, @vandreev11, @sethzenz, @felicepantaleo, @rovere, @argiro, @cseez, @pfs, @lgray, @kpedro88 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

@kpedro88
Copy link
Contributor

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Jul 11, 2019

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/1435/console Started: 2019/07/11 20:28

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

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

@slava77 comparisons for the following workflows were not done due to missing matrix map:

  • /build/cmsbld/jenkins/workspace/compare-root-files-short-matrix/results/JR-comparison/PR-5a8e84/20034.0_TTbar_14TeV+TTbar_14TeV_TuneCUETP8M1_2023D35_GenSimHLBeamSpotFull14+DigiFullTrigger_2023D35+RecoFullGlobal_2023D35+HARVESTFullGlobal_2023D35
  • /build/cmsbld/jenkins/workspace/compare-root-files-short-matrix/results/JR-comparison/PR-5a8e84/20434.0_TTbar_14TeV+TTbar_14TeV_TuneCUETP8M1_2023D41_GenSimHLBeamSpotFull14+DigiFullTrigger_2023D41+RecoFullGlobal_2023D41+HARVESTFullGlobal_2023D41
  • /build/cmsbld/jenkins/workspace/compare-root-files-short-matrix/results/JR-comparison/PR-5a8e84/21234.0_TTbar_14TeV+TTbar_14TeV_TuneCUETP8M1_2023D44_GenSimHLBeamSpotFull14+DigiFullTrigger_2023D44+RecoFullGlobal_2023D44+HARVESTFullGlobal_2023D44

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 1 differences found in the comparisons
  • DQMHistoTests: Total files compared: 32
  • DQMHistoTests: Total histograms compared: 3081858
  • DQMHistoTests: Total failures: 1
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3081535
  • DQMHistoTests: Total skipped: 322
  • 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

@kpedro88
Copy link
Contributor

+upgrade

@@ -150,6 +150,10 @@ GlobalPoint RecHitTools::getPositionLayer(int layer, bool nose) const {
}
} else {
const HGCalDDDConstants* ddd = get_ddd(geom_, geometryType_, fhOffset_, lay);
if (geometryType_ == 1) {
if (lay > fhOffset_)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this be ">="? (Just guessing...)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, the fhOffset_ is the last layer of EE (=28), and only for the first layer of the hadronic calorimeter (29) the offset correction (29-28=1) be used, since the layer numbering starts with 1.

@perrotta
Copy link
Contributor

Please test
(Phase2 reco comparisons should be back and available now)

@cmsbuild
Copy link
Contributor

cmsbuild commented Jul 15, 2019

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/1468/console Started: 2019/07/15 09:40

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

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

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 2 differences found in the comparisons
  • DQMHistoTests: Total files compared: 32
  • DQMHistoTests: Total histograms compared: 3081858
  • DQMHistoTests: Total failures: 2
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3081534
  • DQMHistoTests: Total skipped: 322
  • 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

@perrotta
Copy link
Contributor

@clelange , automatic tests show no difference in the D41 workflow 20434.0
Shouldn't we notice any effect of the bug fix? There are a few methods in the HGCal software that rely on RecHitTools::getPositionLayer...

@clelange
Copy link
Contributor Author

@perrotta , I wouldn't expect any differences: there is only one method that's using this within CMSSW at the moment (see https://cmssdt.cern.ch/lxr/ident?_i=getPositionLayer) and that only uses the first layer of EE (https://github.com/cms-sw/cmssw/blob/master/RecoEgamma/EgammaTools/src/EgammaPCAHelper.cc#L330). However, for code that's developed outside the CMSSW repository, this shows (the expected) differences.

@perrotta
Copy link
Contributor

+1

@cmsbuild
Copy link
Contributor

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
Copy link
Contributor

as far as I can see there should not be real conflict with #27485, so it looks ok to integrate

@fabiocos
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit 21acc72 into cms-sw:master Jul 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants