Remove force-loop checks for routes with u-turns #6858
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
Each leg of a via-route supporting u-turns does not need to consider force-loops. Negative weight checks are sufficient to prevent incorrect results when waypoints are on the same edge.
SiarheiFedartsou
approved these changes
May 5, 2024
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.
Issue
This is a fix for observation 1 discussed in #6852
Each leg of a via-route supporting waypoint u-turns does not need to consider force-loops.
Negative weight checks are sufficient to prevent incorrect results when waypoints are on the same edge.
I've not added additional tests, as the change is sufficiently simple, and there are enough existing
continue_straight=falsecucumber tests to verify it works.I will add additional tests for the more complicated fixes.
Tasklist
Requirements / Relations
#6852