Repository navigation
Add resident GPU reductions for point-to-plane ICP - #172
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Depends on #171 (resident GPU GICP equations); this PR contains only the point-to-plane slice.
Point-to-plane ICP currently transforms source points and accumulates its 6x6 normal equations on CPU each iteration. Add an explicit
register-icp-point-to-plane-gpupath that retains positions/tree/raw target normals for GPU transforms, nearest matching, plane Hessian/gradient and fitness reductions. Each evaluation explicitly downloads 256 bytes; CPU solves normalized equations and converts the existing world step. Raw normals retain relative length weights and zero rows, and ordinary CPU ICP is unchanged.Finite geometry/normals, supported scales, valid configuration and runtime/device limits are checked. Nonfinite device arithmetic invalidates all payload. f32 transforms/reductions can change matches, pose and stopping; no automatic CPU fallback or placement change is introduced.
Validation:
Contracts, full timing tables, transfer receipts and precision limits.