Fixed bug in PRM #114
Open
Fixed bug in PRM #114
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
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.
In the step of the PRM when the road map is created, the new vertice is added to the graph, and then the graph is investigated to find all vertices within a certain distance from the new vertice. This function will then also return the newly added vertice. As a result the set of edges will include edges of length zero from each vertice to itself. Later this becomes an issue when querying the road map: The returned path is certainly not optimal, as it should be, since the algorithm used is A*.
The pull request fixes this bug, by simply getting the closest vertices BEFORE adding the new vertice to the graph.