Move NN search back to the VoxelHashMap #388
Merged
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.
I simply moved the functions related to the Nearest Neighbor search from
Registration
toVoxelHashMap
, as this is the data structure that is used to compute the neighbors. This allows other people to use our same strategy of NN search without copy-pasting code from an unnamed namespace. I know that this is something we did a long time ago, but I changed my mind, and this makes much more sense, as now you can use our NN search decoupled from the registration module. Of course, performances are completely unaffected, as I can show here.Ps: this change is propedeutic (io non parlo inglese) to a slightly more significant change that will remove a useless copy of points from the voxels during the NN search.
Related PRs
This PR basically shadows what we did in #290 when we refactored a bit the system to support different number of threads in #252