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
Fix precise setting for CaloSamplesAnalyzer with HPDs #19184
Conversation
…info for CaloSamples debugging
please test |
The tests are being triggered in jenkins. |
A new Pull Request was created by @kpedro88 (Kevin Pedro) for master. It involves the following packages: SimCalorimetry/CaloSimAlgos @cmsbuild, @civanch, @mdhildreth, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
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 requires discussion in the ORP meeting before it's merged. @davidlange6, @smuzaffar |
+1 |
In #16907, I added a tool called CaloSamplesAnalyzer to help debug intermediate stages of the HCAL digitization simulation. This included a special "precise" option for the HPD simulation, to get per-nanosecond
CaloSamples
(instead of just per-timeslice=per-25ns).However, it was recently pointed out to me that activating this debugging option caused the output digis to change. This is because the HPD pulse shape is integrated over 25ns by the
CaloCachedShapeIntegrator
before it is used by the simulation - so the "precise" setting was effectively integrating the pulse twice. To resolve this, I made a separate map of un-integrated pulses to be used in "precise" mode. I also cleaned up theHcalShapes
code, to make it more maintainable and modern.This PR should not change any standard results. The observed problem was only seen in a special debugging mode.