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

SiPM pulse shape fixes #16825

Merged
merged 2 commits into from Dec 5, 2016
Merged

SiPM pulse shape fixes #16825

merged 2 commits into from Dec 5, 2016

Conversation

kpedro88
Copy link
Contributor

Some arbitrary cutoffs on the ranges of the Y11 and SiPM pulse shapes used in the digi simulation had been present in the code for several years. These cutoffs caused unphysical dropoffs in the output pulses, so they are now removed. Correspondingly, the RECO shape used for M2 is updated to be a full 250ns convolution.

Extensive investigation of these issues can be found in these slides: sipm_pulse_study_4.pdf. Plots of M2 performance are included. Additionally, here is a 50 GeV pion response/resolution plot ("ref" corresponds to 810pre16 + #16569, "new" is ref + this PR):
pion plot

NB: Changing Y11RANGE globally will also change HO simulation output for Run1 and Run2. Theoretically this is more accurate, so I think the change should be allowed. If it is not acceptable, as a hack I can reset Y11RANGE on a per-channel basis, but I would prefer not to do this.

Planned items for followup PRs:

  • Further cleanup of SiPM code (remove some unnecessary vars, hardcoded values, reduce duplication, etc.)
  • Move Y11 functions into HcalSiPMShape
  • Move HcalSiPMShape into CalibCalorimetry/HcalAlgos
  • Use HcalSiPMShape to calculate numerical convolution for RECO shape on demand (replacing array of values)
  • Option to store vector<CaloSamples> as event product for easier debugging

This PR will be backported to 81X.

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @kpedro88 (Kevin Pedro) for CMSSW_9_0_X.

It involves the following packages:

CalibCalorimetry/HcalAlgos
SimCalorimetry/HcalSimAlgos

@ghellwig, @civanch, @arunhep, @cerminar, @cmsbuild, @franzoni, @mdhildreth, @mmusich, @davidlange6 can you please review it and eventually sign? Thanks.
@ghellwig, @mariadalfonso, @tocheng this is something you requested to watch as well.
@slava77, @smuzaffar you are the release manager for this.

cms-bot commands are listed here #13028

@kpedro88
Copy link
Contributor Author

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 30, 2016

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/16696/console

@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-16825/16696/summary.html

The workflows 1003.0, 1001.0, 1000.0, 140.53, 136.731, 4.22 have different files in step1_dasquery.log than the ones found in the baseline. You may want to check and retrigger the tests if necessary. You can check it in the "files" directory in the results of the comparisons

@kpedro88
Copy link
Contributor Author

The changes in the comparisons for 2017 (and 2023) look reasonable to me. Other MC workflows show apparently-unrelated minor changes due to random number shifting. (The SiPM simulation is rather complex, with random number calls dependent on other random number calls that depend on parameters, so any parameter change can shift the whole chain.)

@slava77
Copy link
Contributor

slava77 commented Nov 30, 2016

in 10024 I see
wf10024_m2_log10chi2_he

Maria's plot moved in the opposite direction
maria_m2_log10chi2_he

Am I just comparing different phase space or other kind of apples to oranges?

@kpedro88
Copy link
Contributor Author

kpedro88 commented Dec 1, 2016

@slava77 the major differences are sample type (500 GeV pion vs ttbar) and size (1000 events vs 10 events).

I made the set of M2 plots using baseline and this PR from 10024 step3.root. The performance overall agrees with what I expect: reduced chi2 at high energy (low energy has a larger spread in the baseline, which is not surprising - this PR mostly serves to improve self-consistency) and less spread in the time distribution.

@civanch
Copy link
Contributor

civanch commented Dec 2, 2016

+1
I would think that the fix is OK for 9_0 but am not sure about needs of backport

@kpedro88
Copy link
Contributor Author

kpedro88 commented Dec 2, 2016

I'm not sure about the current plans for 81X vs 90X for 2017 tuning. If we no longer need to have the best local reco in 81X, the backport is unnecessary. But the POGs/DPGs still seem to be focusing on 81X as the standard for 2017...

@kpedro88
Copy link
Contributor Author

kpedro88 commented Dec 3, 2016

@mmusich @davidlange6 I would like to get this into pre2 if possible

@mmusich
Copy link
Contributor

mmusich commented Dec 5, 2016

+1

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 5, 2016

This pull request is fully signed and it will be integrated in one of the next CMSSW_9_0_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @smuzaffar

@davidlange6 davidlange6 merged commit e84a4be into cms-sw:CMSSW_9_0_X Dec 5, 2016
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

6 participants