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

Switching to full pulse nonlinearity for SiPMs #18866

Merged
merged 3 commits into from
Jun 3, 2017

Conversation

igv4321
Copy link
Contributor

@igv4321 igv4321 commented May 19, 2017

Changing TS-by-TS SiPM nonlinearity calculation to estimating the nonlinearity from the charge collected in the 3 time slices (almost full pulse). This treatment is consistent with what was done for calibrating the SiPM non-linearity so far in the lab. While eventually we will need to go back to correcting nonlinearity for individual time slices, we can not do so with the existing measurements and models.

For a detailed description of the problem, see the talks by Jim Hirschauer, Federico De Guio, and Pawel De Barbaro at https://indico.cern.ch/event/640431/

Please test and integrate asap, this fix is needed for the data taking.

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @igv4321 (Igor Volobouev) for master.

It involves the following packages:

RecoLocalCalo/HcalRecProducers

@perrotta, @cmsbuild, @slava77, @davidlange6 can you please review it and eventually sign? Thanks.
@mariadalfonso this is something you requested to watch as well.
@davidlange6 you are the release manager for this.

cms-bot commands are listed here

@slava77
Copy link
Contributor

slava77 commented May 19, 2017

@igv4321
please point to the expected before and after response plots for this proposed change.
Also, please clarify if the effect is expected to be different in data and MC.
For data, it would be good to see a reference to test and compare.

Thank you.

@slava77
Copy link
Contributor

slava77 commented May 19, 2017

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented May 19, 2017

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/20001/console Started: 2017/05/19 22:31

@cmsbuild
Copy link
Contributor

Pull request #18866 was updated. @perrotta, @cmsbuild, @slava77, @davidlange6 can you please check and sign again.

@kpedro88
Copy link
Contributor

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented May 19, 2017

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/20003/console Started: 2017/05/19 22:51

@kpedro88
Copy link
Contributor

@slava77 there will be a similar effect in both data and MC. The MC nonlinearity simulation does not exactly match the data, but they're close enough.

@igv4321
Copy link
Contributor Author

igv4321 commented May 19, 2017

It became obvious with splashes that the original treatment of SiPM nonlinearity is inconsistent with the nonlinearity calibrations in the lab. The algorithm (with a slightly different implementation) has been tested by Federico, see https://indico.cern.ch/event/640431/contributions/2597635/attachments/1462296/2259023/20170517_-_joint_DPGPhase1_meeting_on_HEP17.pdf

And yes, various relevant people are aware of the upcoming change.

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison job queued.

@slava77
Copy link
Contributor

slava77 commented May 19, 2017 via email

@cmsbuild
Copy link
Contributor

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

Comparison Summary:

  • You potentially added 191 lines to the logs
  • Reco comparison results: 4398 differences found in the comparisons
  • DQMHistoTests: Total files compared: 24
  • DQMHistoTests: Total histograms compared: 1833901
  • DQMHistoTests: Total failures: 34037
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 1799684
  • DQMHistoTests: Total skipped: 180
  • DQMHistoTests: Total Missing objects: 0
  • Checked 98 log files, 14 edm output root files, 24 DQM output files

@slava77
Copy link
Contributor

slava77 commented May 22, 2017

IIUC, this PR is pending discussion in (Wednesday?) HCAL meeting.

@deguio
Copy link
Contributor

deguio commented May 23, 2017

@slava77 correct.

@perrotta
Copy link
Contributor

Any outcome on the discussion at the HCal meeting? Are there slides that can be linked?

@hatakeyamak
Copy link
Contributor

hatakeyamak commented May 25, 2017

We had discussions on this, and we are pending results of a validation test. The plan is to test the change in this PR with also another PR that should come for sipm+qie11 pulse shape for HEP17 using the splash data with method 2.

The sipm+qie11 pulse shape is being measured at low energies and we don't include any energy dependence. If this performs acceptably at very high energies as in splash (where non-linearity effect is most significant), we would like to push this change forward. If everything goes well, we may hear the outcome of this test tomorrow.

@abdoulline
Copy link

abdoulline commented May 30, 2017

In the meantime - MC test with 1 TeV pions. Two samples of 100k each.
Plotted is HCAL RecHits sum in R=0.3 around pion direction (no mag.field, no vertex smearing)

(1) Pions shot specifically at HEP17 wedge (1 out of 18 in HE+)

ietapr18866_e1000

(2) pions shot at HE+ randomly

a) iphi distribution in HE+
iphipr18866_e1000

b) ieta distribution (over all iphi's in HE+ )
energy scale change is diluted by factor 18:1 (one wedge out of 18)

ietapr18866_e1000_he

@deguio
Copy link
Contributor

deguio commented May 30, 2017

hi,
as mentioned at the orp here some cross check on splash data with M0 and M2 which are both affected by this fix. For M0 the cosmics reco was used (sum all 10TS with no containment correction).

c1
c2
c3
c4

Regions outside HEP17 are not affected.

@deguio
Copy link
Contributor

deguio commented May 30, 2017

btw. linearity fix in the legend is this PR

@perrotta
Copy link
Contributor

+1
Visual inspection of the code shows no issues.
Performance plots provided for both MC and 2017 beam splash data confirm that the modifications (also visible in low stat jenkins tests) are according to the expectations

@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 requires discussion in the ORP meeting before it's merged. @davidlange6, @smuzaffar

@slava77
Copy link
Contributor

slava77 commented Jun 1, 2017

@davidlange6
what was the reason that this PR was not included in CMSSW_9_2_1?

@davidlange6
Copy link
Contributor

davidlange6 commented Jun 1, 2017 via email

@deguio
Copy link
Contributor

deguio commented Jun 1, 2017

Hi,
we (HCAL) think that that the effect will be completely negligible on the PFCluster calibration.
I wrote to JetMet to ask their opinion. I will make sure they are informed about the reco meeting tomorrow.
F.

@slava77
Copy link
Contributor

slava77 commented Jun 1, 2017 via email

@davidlange6
Copy link
Contributor

Let's see if the symmetric calibrations is considered a bug or feature later....

@davidlange6 davidlange6 merged commit c09fc84 into cms-sw:master Jun 3, 2017
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

9 participants