-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Code performance improvements in follow-up to #31722 #33864
Code performance improvements in follow-up to #31722 #33864
Conversation
Also removed addition of transposed matrix by directly copying the needed elements. cms-sw#31722 (comment) cms-sw#31722 (comment)
Also introduced a computation simplification suggested in: cms-sw#31722 (comment)
Co-authored-by: Andrea Bocci <[email protected]>
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33864/22894
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33864/22897
|
A new Pull Request was created by @ericcano (Eric Cano) for master. It involves the following packages: RecoPixelVertexing/PixelTrackFitting @perrotta, @jpata, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
most of the changes affect Rienman fit that is not default.
|
is it possible to add a test then? |
This branch has conflicts that must be resolved Conflicting files please update, if this is till considered to be an active PR |
@ericcano |
@slava77 as the PR is pending testing RiemannFit, I opened an issue in patatrack (cms-patatrack#620) for creating a test, and will close it. We will re-introduce the changes when tests are available. |
PR description:
CMSSW #31722 Patatrack integration - Pixel track reconstruction (10/N) was merged with extra comments to be addressed.
This PR addresses the performance related comments.
PR validation:
The code was run in workflows (step3 and step4):
The workflow results where then compared using the plots generated by
makeTrackValidationPlots.py
. The CPU workflows gave results identical to the baseline integration build. The GPU workflows displayed slight variations, but the variations are also present between multiple runs of the same version (baseline or this branch).Unit tests were fine except one problem not related the this branch and followed up in #33797