Add option to exclude crossings from acutely intersection lines #6346
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
PaulWessel
added
the
new feature
maxrjones
approved these changes
Feb 18, 2022
|
Fine to ignore vercel failure. |
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.
Description of proposed changes
See this forum post for background. The issue is how to prevent finding crossovers if the two track-lines are nearly parallel. One may not want such crossings for a variety of reasons, including the larger uncertainty in crossover point and hence time and therefore the crossover error value. This PR adds -Elimit which will exclude crossovers where the absolute difference in track orientations is less than limit [Default is 0].