Reduced space usage for Moving Least Squares #785
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.
The
mls_results_
vector did not need to be allocated for most of the Moving Least Squares methods. However, a reference to an entry in this vector was needed for calls tocomputeMLSPointNormal
, which is why it was being allocated in full. This commit causes the vector to be resized to 1 for those methods that don't need the full version, and then a reference to entry 0 is passed. The decision was made not to modifycomputeMLSPointNormal
because it needs to be thread-safe and I do not have the means to test the OpenMP version of the code. Identical modifications were made toMovingLeastSquaresOMP::performProcessing
as toMovingLeastSquares::performProcessing
.Tests which do not depend on OpenMP still pass. I cannot speak to those tests which require OpenMP.
While this requires to additional comparisons per loop iteration, I believe these will be optimized out.