levelset: fix evaluation of levelset for surfaces that contain pixel elements #376
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
…ordered vertices The function that projects a point onto a polygon expects in input an anti-clockwise ordered list of vertex coordinates.
andrea-iob
force-pushed
the
levelset.fix.pixel.segments
branch
from
b4230a3
to
7bdc10a
Compare
|
I've added an additional fix for the hash operator of ElementHalfItem. |
edoardolombardi
approved these changes
Apr 3, 2023
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.
Connectivity of pixel elements does not list the vertices in anti-clockwise order. This needs to be properly taken into account when flipping the normal and when evaluating segment information.