[SignedDistanceField] not expanded box precision #1046
Merged
Conversation
This file contains 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
|
Looks good, thanks! |
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.
When disabling the
expandBoxparameter of the signed distance field module it is possible for a triangle to lie on the boundary of the box.However in practice it can results in the triangle not being detected by a ray due to precision problems.
In the end, this can result in the algorithm being unable to detect the interior and exterior of the surface.
To fix this, this PR shift a little bit the rays that are cast on the boundary by 0.1% of the size of the spacing in the corresponding dimensions (i.e the extent of a dimension divided by its resolution).