3D support in distance_to to fix broken Douglas-Peucker algorithm #33
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
…nonplanar gcode export
|
Thank you for fixing this issue |
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.
3D support in distance_to to fix broken Douglas-Peucker algorithm in nonplanar gcode export.
The length of exported gcode segments is usually normalized to avoid a high number of very short movements in regions where the facet density in the original stl file is high. This is achieved by the recursive Douglas-Peucker algorithm. The introduction of a z-component to the Point.cpp class for the nonplanar feature has broken the
distance_tomethod, even in the 2D case, preventing the DP algo from termination, resulting in a stack overflow (segfault).