-
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
move pixelTopology.h
from Geometry/TrackerGeometryBuilder
to Geometry/CommonTopologies
#36773
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36773/27910
|
A new Pull Request was created by @mmusich (Marco Musich) for master. It involves the following packages:
@malbouis, @civanch, @yuanchao, @makortel, @cvuosalo, @fwyzard, @ianna, @mdhildreth, @cmsbuild, @ggovi, @Dr15Jones, @clacaputo, @slava77, @jpata, @tvami, @francescobrivio can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild , please test with cms-sw/cmsdist#7575 |
-1 Failed Tests: RelVals-INPUT The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
You can see more details here: RelVals-INPUT
Comparison SummarySummary:
|
enable gpu |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-e6b9f8/21980/summary.html GPU Comparison SummarySummary:
Comparison SummarySummary:
|
I don't have comments on the code, but I've just a curiosity about the GPU test. |
+1 |
+1 |
I think a certain degree of non-reproducibility has been known to affect the pixel-related GPU workflows since ever. In my understanding, part of it, (especially for the vertexing related quantities) stems for the algorithm itself. On the other hand there might be other sources, which are incidentally being explored e.g. in this PR (#36390). |
Hi @clacaputo, yes, I can confirm @mmusich's answer: some level of non-reproducibility is intrinsic in the use of parallel algorithms, due to the non-associative nature of floating point operations ( Of course, there can be non-reproducibility issues that are due to, or amplified by, underlying bugs - both in the new GPU-based algorithms and in the existing non-GPU ones - so if you spot anything suspicious in the code, please do let us know ! |
+reconstruction
|
ping @cms-sw/heterogeneous-l2 |
thanks for the ping, and apologies for the delay, I had simply missed that it required the heterogeneous signature :-( |
+heterogeneous |
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. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1
|
resolves #36302
PR description:
As suggested in #36302 (comment)
PR validation:
cmssw
compilesif this PR is a backport please specify the original PR and why you need to backport that PR:
N/A
Note to reviewers:
Geometry/CommonTopologies
among the ones indicated in Placement of phase1PixelTopology.h #36302 (comment), but could be any other. Please confirm it's OK.Geometry/CommonTopologies
there is also aPixelTopology.h
file.cmssw/Geometry/CommonTopologies/interface/PixelTopology.h
Line 1 in 131e8b4
To avoid confusions, this one could be named
siPixelTopology.h
orsimplePixelTopology.h
or something like that. Suggestions are welcome.