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

[HBHE] Mahi configuration change: 8 pulses without baseline #25469

Merged
merged 12 commits into from Dec 20, 2018

Conversation

jaehyeok
Copy link
Contributor

HCAL DPG wants to make changes to the configuration of Mahi; we like to use 8 pulses instead of 3 and remove the baseline.

It was noticed that Mahi fit sometimes does not fit data correctly, particularly when there is a significant charge in OOT time slices. Also, the baseline is occasionally incapable of extracting a flat component properly.

We tested various configurations (different number of pulses and with/without baseline), and found that the 8-pulse without baseline fit performs best.

Details can be found in [1]. There are links to more studies (p35).

[1] https://indico.cern.ch/event/774376/contributions/3230469/attachments/1764961/2865685/20181204_Jae_HCALDPG_RecoConfigUL.pdf

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

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

It involves the following packages:

RecoLocalCalo/HcalRecAlgos
RecoLocalCalo/HcalRecProducers

@perrotta, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks.
@mariadalfonso, @argiro 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

@perrotta
Copy link
Contributor

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 11, 2018

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/32118/console Started: 2018/12/11 12:08

@slava77
Copy link
Contributor

slava77 commented Dec 11, 2018

@jaehyeok
please provide some timing measurements.
Data and ttbar MC PU50 is probably enough.

@slava77
Copy link
Contributor

slava77 commented Dec 11, 2018

@jaehyeok
please provide some timing measurements.
Data and ttbar MC PU50 is probably enough.

(I meant CPU timing)
igprof would be the best
https://twiki.cern.ch/twiki/bin/viewauth/CMS/RecoIntegration#Run_profiler_igprof

@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-25469/32118/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 18161 differences found in the comparisons
  • DQMHistoTests: Total files compared: 33
  • DQMHistoTests: Total histograms compared: 3136422
  • DQMHistoTests: Total failures: 3902
  • DQMHistoTests: Total nulls: 25
  • DQMHistoTests: Total successes: 3132291
  • DQMHistoTests: Total skipped: 204
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: -0.04 KiB( 32 files compared)
  • DQMHistoSizes: changed ( 136.731,... ): -0.012 KiB JetMET/SUSYDQM
  • DQMHistoSizes: changed ( 4.53 ): 0.023 KiB JetMET/SUSYDQM
  • DQMHistoSizes: changed ( 136.85 ): -0.008 KiB JetMET/SUSYDQM
  • DQMHistoSizes: changed ( 136.788 ): -0.031 KiB JetMET/SUSYDQM
  • Checked 137 log files, 14 edm output root files, 33 DQM output files

@jaehyeok
Copy link
Contributor Author

@slava77

@jaehyeok
please provide some timing measurements.
Data and ttbar MC PU50 is probably enough.

(I meant CPU timing)
igprof would be the best
https://twiki.cern.ch/twiki/bin/viewauth/CMS/RecoIntegration#Run_profiler_igprof

I ran over 500 JetHT events in Run2018A [1]. These events correspond to nPU~50 because they are at the beginning of a fill (Fill 6729).

The following are the igprof results using (1) 3 pulses + baseline and (2) 8 pulses. The full igprof results are in [2].

(1) 3 pulses + baseline

Rank    % total       Self       Self / Children   Function
[17]       35.6      38.79       0.55 / 38.24      MahiFit::phase1Apply(HBHEChannelInfo const&, float&, float&, bool&, float&) const
           34.6  .........      37.77 / 37.77        MahiFit::doFit(std::array<float, 3ul>&, int) const [18]
            0.4  .........       0.47 / 0.47         MahiFit::resetWorkspace() const [504]
            0.0  .........       0.01 / 0.86         _init [339]

(2) 8 pulses

Rank    % total       Self       Self / Children   Function
[12]       54.1      73.31       0.70 / 72.61      MahiFit::phase1Apply(HBHEChannelInfo const&, float&, float&, bool&, float&) const
           53.2  .........      72.18 / 72.18        MahiFit::doFit(std::array<float, 3ul>&, int) const [13]
            0.3  .........       0.41 / 0.41         MahiFit::resetWorkspace() const [528]
            0.0  .........       0.01 / 1.14         _init [281]

The processing time increased by about a factor of 2.

[1] /store/data/Run2018A/JetHT/RAW/v1/000/316/944/00000/2EF71399-6B64-E811-9B71- FA163ED59971.root
[2] http://jaehyeok.web.cern.ch/jaehyeok/HCAL/igprof/

@abdoulline
Copy link

abdoulline commented Dec 12, 2018

@cmsbuild
Copy link
Contributor

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

@slava77
Copy link
Contributor

slava77 commented Dec 19, 2018

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 19, 2018

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/32282/console Started: 2018/12/20 00:46

@slava77
Copy link
Contributor

slava77 commented Dec 20, 2018

Some more plots:

these are from flat-pt dijet with PU50 MC (wf 11071)

wf11071_he_m2_v_m0

the new is on the right. I guess this is better (I can't think of a clear reason we should have a two-branch relationship between M0 (raw) and MAHI (I guess M2 here is a misnomer in the plots).

The times are just reiterated to be "random"
wf11071_he_time_vs_energy

@jaehyeok
Copy link
Contributor Author

In the top plots, I guess x-axis is M0 and y-axis is Mahi?

@slava77
Copy link
Contributor

slava77 commented Dec 20, 2018 via email

@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-25469/32282/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 21138 differences found in the comparisons
  • DQMHistoTests: Total files compared: 33
  • DQMHistoTests: Total histograms compared: 3153717
  • DQMHistoTests: Total failures: 5385
  • DQMHistoTests: Total nulls: 27
  • DQMHistoTests: Total successes: 3148101
  • DQMHistoTests: Total skipped: 204
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: -0.007 KiB( 32 files compared)
  • DQMHistoSizes: changed ( 136.731 ): -0.035 KiB JetMET/SUSYDQM
  • DQMHistoSizes: changed ( 4.53 ): -0.004 KiB JetMET/SUSYDQM
  • DQMHistoSizes: changed ( 1000.0 ): 0.012 KiB JetMET/SUSYDQM
  • DQMHistoSizes: changed ( 136.788 ): 0.020 KiB JetMET/SUSYDQM
  • Checked 137 log files, 14 edm output root files, 33 DQM output files

@slava77
Copy link
Contributor

slava77 commented Dec 20, 2018

+1

for #25469 10874a1

  • code changes are in line with the PR description and the follow up review
  • jenkins tests pass and comparisons with the baseline show expected differences starting from hbhe(pre)reco
    • changes in the energy measurements do not have an immediate follow up (except maybe revisiting the chi2 switch point)
    • changes in the hit time distribution imply more work to be followed up in revisit HBHE MAHI algorithm hit time #25526
  • results of local tests with more stats were posted earlier in the thread

@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)

@abdoulline
Copy link

In the top plots, I guess x-axis is M0 and y-axis is Mahi?

"Better late than never" (to answer): yes, X: M0, Y: default energy (MAHI).
The histo name just wasn't properly renamed when the default moved from M2 to MAHI...

@fabiocos
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit 9529af0 into cms-sw:master Dec 20, 2018
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

10 participants