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
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-25469/7570 |
A new Pull Request was created by @jaehyeok for master. It involves the following packages: RecoLocalCalo/HcalRecAlgos @perrotta, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
@jaehyeok |
(I meant CPU timing) |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
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
(2) 8 pulses
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 |
Here is an additional sanity check, comparing 2018 single-pion scan w/wo this PR |
@cmsbuild please test |
The tests are being triggered in jenkins. |
Some more plots: these are from flat-pt dijet with PU50 MC (wf 11071) 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). |
In the top plots, I guess x-axis is M0 and y-axis is Mahi? |
On 12/19/18 4:41 PM, jaehyeok wrote:
In the top plots, I guess x-axis is M0 and y-axis is Mahi?
I think so; but I didn't make an explicit check in the code.
Since this is coming from DQM, I'm assuming the plots are widely known.
|
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 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) |
"Better late than never" (to answer): yes, X: M0, Y: default energy (MAHI). |
+1 |
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