AUTO-607 use path distance instead of euclidean distance for pruning path #9
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.
This PR fixes the one of the issue with looping paths in MPPI, for searching the last point of the part of the global path to consider in the controller, we search up to the pruning distance along the path, instead of search up the euclidean distance. This avoid transforming path oscillations like the following:
https://user-images.githubusercontent.com/15727892/221850250-658af60f-8c94-4e67-a2ee-ec145b5d8bdf.mp4
(global path in green, transformed path in purple arrows)