Mesh 3 - speedup protecting balls placement #9052
Draft
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
and use it in domain.curve_segment_is_covered()
add a special locate_corner() because we don't want to store all incident polylines to a corner, and that it's only a few, cheap, locate operations
mesh_polyhedral_domain_with_features works fine with this version
the iterator we need is the one of p, not the one of `other_point`! + constify what can be + make loops more readable
and deal with the case where distance < 0 in point_at(), because we don't want to start from start_point all over
and add tons of assertions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary of Changes
Keep track of the segment on which each protecting ball was placed to speedup the algorithm
Release Management