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: speed up + mahi move double to float #28366
HBHE: speed up + mahi move double to float #28366
Conversation
The code-checks are being triggered in jenkins. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28366/12669
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28366/12672
|
A new Pull Request was created by @mariadalfonso 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. |
-1 Tested at: 393aff0 You can see the results of the tests here: I found follow errors while testing this PR Failed tests: AddOn
I found errors in the following addon tests: cmsRun /cvmfs/cms-ib.cern.ch/week1/slc7_amd64_gcc820/cms/cmssw-patch/CMSSW_11_0_X_2019-11-07-2300/src/HLTrigger/Configuration/test/OnLine_HLT_2018.py realData=False globalTag=@ inputFiles=@ : FAILED - time: date Fri Nov 8 15:33:09 2019-date Fri Nov 8 15:17:16 2019 s - exit: 34304 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
the crash seems related, it's in
|
please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
@mariadalfonso I'm noticing that in the validation plot linked to the PR description there is not the migration of the mahi arrival time from 0 to non zero values that was visible in the first instance of it. Does that new plot refer to the state after the latest commit d6a2dd1 of this PR? |
The igprof performance results still refer to a quite old version of this PR (after commit 0ac75e6 , as written in the PR descritpion): will you be able to update them with the most recent version of this PR? |
updated :)
the migration on the arrivalTime is visible on floats see page2 (both original PR and final commit) , not visible double see page1 (intermediate test) |
Ah, ok, sorry: I did not notice the second page... Then, I must agree with you that "ArrivalTime is pretty much a ill undefined", if by only changing the precision of the input quantities you end up with such large differences in the fitted result. Such arrival time eventually becomes the RecHit time: forgive my ignorance about it, but how is this evidently "ill defined" quantity relevant in the propagation to some higher level computed quantity? (Perhaps outside the scope of this PR) are there plans to make it more robust, if so? |
Goal of this PR is solely to speed up for Run3-HLT and I hope we can have it in the pre13. For the Run2/Run3 there is no use of the recHit time() other than the beamhalo filter. HCAL long term plan redefinition of the arrivalTime The physics case will be to target the LLP analyses. The possibilities we considered so far:
I never saw the correlation with a real MC signal displaced in time and this should be done before we use. In addition use the TDC from HE detector to validate the time with data. |
+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) |
Issue #28423 was opened to follow up with the progresses in fixing the |
+1 |
This PR gain 45% in CPU speed up in the minimize function see igprof results below.
Validation plots provided in double and floats
http://dalfonso.web.cern.ch/dalfonso/HCAL/HCAL_PR28366.pdf
Impact on the INtime energy is negligible, small changes on the arrivalTime.
To keep in mind in the future, the maxSV size should be moved 10 -->8 once the 2018menu is removed.
-- release tag: CMSSW_11_0_X_2019-11-07-2300 --
-- this PR at commit d6a2dd1 --
Tests above done on fu-c2a02-37-03 2 CPUs:
0: Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz (16 cores, 32 threads)
1: Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz (16 cores, 32 threads)