-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node extracted twice #1
Comments
I cannot understand this part. I looked at the paper and this seems to be correct. Can you elaborate, or tell me how can I verify this duplication? |
what I mean is that you already have: |
Will take a loot at it. Also I think this algorithm is quite crappy for real life world discovery. I will try to contact the authors of the paper to see what they think. |
I wrote a function that draws the routing tree onto the map (with some
small changes).. the routing tree on map looks different from the ones
shown in the demo videos..
I could push it to github in the evening and make a pull request, I think
it gives insight into how the algorithm works..
also there could be space for some speedups here and there..
…On Fri, Feb 23, 2018 at 2:08 PM, Paulo Neves ***@***.***> wrote:
Will take a loot at it. Also I think this algorithm is quite crappy for
real life world discovery. I will try to contact the authors of the paper
to see what they think.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAF5cuEMzRSgK2ZS35ZHGkP_skD8rhZwks5tXqongaJpZM4Ru6lR>
.
|
Sure. I think that a review by the authors, plus better presentation can be beneficial for both of us. Regarding the ellipse sampling, basically once you find a route to the goal you take the path distance as a parameter for the ellipse for convergent sampling. In the mean time I modified my code to provide the shortest path given the known nodes, basically short-circuiting the graph-tree when there is no obstacle. I am curious if I am not doing some La-palice here :D |
I agree that the authors would be best guides. |
I think you have a bug here:
rt-rrt/rt.py
Line 299 in 8f40302
x_closest is already the node of the result
The text was updated successfully, but these errors were encountered: