Repository navigation
Add GPU resident radius GICP covariance preparation - #174
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.
Radius covariance preparation currently downloads full covariance arrays and uploads them again for resident GICP equations. Add explicit
align_with_gpu_resident_radius_covariances/upload_with_gpu_radius_covariancesto keep complete inclusive radius neighborhoods, compensated covariance sums and plane eigenvectors on GPU. Reuse original query/sample positions and the target tree; retain the CPU tree construction and 6x6 solve/update boundary.Caller capacity includes self/duplicates. Overflow or invalid arithmetic zeros both covariance sets and invalidates all equations; no truncated neighborhoods or automatic fallback are used. Sparse support retains epsilon*I. Existing CPU, grid and resident k-NN paths keep their contracts. The precision differences and measured latency tradeoffs are documented.
Validation:
Full conditions, raw-sample locations, transfer tables and all timing results: resident radius evidence.