-
Notifications
You must be signed in to change notification settings - Fork 20
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
Architectural changes to support multi-return feature #285
Conversation
src/gpu/nodeKernels.cu
Outdated
if (first.isHit[beamIdx]) { | ||
first.xyz[beamIdx] = beamSamples.xyz[beamIdx * samplesPerBeam + firstIdx]; | ||
first.distance[beamIdx] = beamSamples.distance[beamIdx * samplesPerBeam + firstIdx]; | ||
} | ||
|
||
last.isHit[beamIdx] = lastIdx >= 0; | ||
if (last.isHit[beamIdx]) { | ||
last.xyz[beamIdx] = beamSamples.xyz[beamIdx * samplesPerBeam + lastIdx]; | ||
last.distance[beamIdx] = beamSamples.distance[beamIdx * samplesPerBeam + lastIdx]; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it not like if beamSamples.isHit[beamIdx * samplesPerBeam + sampleIdx] != 0
(line 235 above) then you will always have first and last? If this is true, then two if-statements here may technically be reduced to one.
src/graph/NodesCore.hpp
Outdated
|
||
void enqueueExecImpl() override {} | ||
|
||
// Point cloud description |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably unsed docs from copy/paste?
964fcf2
to
b5be808
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🥇
* Architectural changes to support multi-return feature
* Architectural changes to support multi-return feature
No description provided.