Fix SteerForPathSimplified2D still getting stuck on loops #48
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
If resolving a loop means advancing further than 2*Vehicle.ArrivalRadius, the previous code would always stall. This change means that we will always resolve a loop no matter how loopy it is (usually max 2/3 iterations).
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.
If resolving a loop means advancing further than 2*Vehicle.ArrivalRadius, the previous code would always stall. This change means that we will always resolve a loop no matter how loopy it is (usually max 2/3 iterations).
I came across this case quite often for some reason and I realised because it only tried to advance once, if that didn't work, it would never resolve it. Making it a while loop works and is guaranteed to exit in edge cases since it's bounded by the path length.