Adapt pixel cpe algo to better handle broken clusters#47966
Adapt pixel cpe algo to better handle broken clusters#47966mroguljic wants to merge 5 commits intocms-sw:masterfrom
Conversation
|
cms-bot internal usage |
|
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-47966/44634
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
bab6a5b to
369a8ac
Compare
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-47966/44635
|
|
Pull request #47966 was updated. |
|
allow @mroguljic test rights |
|
@cmsbuild, please test |
|
+1 Size: This PR adds an extra 88KB to repository Comparison SummarySummary:
|
369a8ac to
1e286ad
Compare
|
@cmsbuild, please test Once more |
|
+1 Size: This PR adds an extra 16KB to repository Comparison SummarySummary:
CUDA Comparison SummarySummary:
ROCM Comparison SummarySummary:
|
There are some known non-reproducibilities in cmssw in wf 29634.911 (see issue #45505), so I would not pay too much attention to that. I would concentrate on the non-reproducibiities caused by this PR in the Run-3 workflows which are normally 100% reproducible (when run on the same arch). |
pixel cpe goodEdgeAlgo: simplified generic implementation and resolved wf collision Co-authored-by: Dinko F. <Dinko.Ferencek@cern.ch>
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-47966/44891
|
|
Pull request #47966 was updated. @AdrianoDee, @Martin-Grunewald, @Moanwar, @antoniovilela, @atpathak, @cmsbuild, @davidlange6, @DickyChant, @fabiocos, @francescobrivio, @fwyzard, @jfernan2, @makortel, @mandrenguyen, @miquork, @mmusich, @perrotta, @rappoccio, @srimanob, @subirsarkar can you please check and sign again. |
|
@mmusich, thanks for the pointer. I was not aware of that. Let me also mention that I discovered a plotting bug in the validation plots for the generic CPE applied to tracking RecHits posted earlier. The good edge curve actually corresponds to the template case and the effect of the new algorithm is in line with what we see for the template CPE, i.e., not much improvement. This is something we are now trying to understand. |
|
I just applied small changes based on code review, before further efforts on the wf differences. No need to test it yet. |
I'd suggest to start with valgrind, e.g. and post the (possibly large) log somewhere.
Small(?) differences between Intel and AMD are known, and (presumably) caused by some packages being compiled with |
|
Could someone please run tests in this draft? It would help me towards understanding the workflow differences we see here. |
|
based on the results shown here can the Pixel DPG team clarify what's the prognosis for this PR? |
During simulation testing of the algorithm proposed in this PR, based on the end of 2024, we observed unexpected results. Unexpected results were also seen with the current implementation of the generic CPE algorithm. We need to fully understand these anomalies before we can reliably validate the proposed changes. Intensive work is ongoing and we will follow up in the PR once things are understood. |
|
-hlt
|
|
Closing the PR because it is superseeded by #48356 |


PR description:
At the end of 2024, cluster breakage at high eta became significant. This caused issues when trying to improve calibrations for pixel cluster (position) parameter estimation, CPE.
This fix changes the CPE algorithms by relying on the "good" cluster edge, instead of both edges. This alternative algorithm is only used if the clusters are shorter than expected (e.g. broken). The change affects template reconstruction, and generic reconstruction both at CPU and GPU (alpaka). The fix is gated behind process modifiers for testing. The new versions of CPE algorithms require corresponding condition updates.
A report on this has been given at the Tracker DPG meeting.
PR validation:
Undergoing
runTheMatrix.py -l limited -i all --ibeos. We don't expect any workflow to be affect since the changes are protected by process modifiers. The PR was opened before the validation to allower others to comment early.Backport
To be backported to 15.0.X: #48008