-
Notifications
You must be signed in to change notification settings - Fork 34
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
Remove map origin restriction #1
Comments
Hi there, is this problem fixed? or do you have any ideas how to fix it? I'm trying to use this algorithm as a local planner, so the map origin cannot be set at[0,0,0]. |
Hi, unfortunately, this limitation still exists. I will contact the original developer to see if he'd be able to point you in the right direction. |
Hi @RickeyLee09, seems that the [0,0,0] assumption is quite deeply rooted in the code. The best workaround at the moment would be to transform all poses before sending them to the planner and then to apply the inverse transform to the planner output. |
Got it! Thank you for your advise, I will look into it recently, if it works i will let you know!
…Sent from my iPhone
On Nov 25, 2019, at 23:42, Damjan Miklic ***@***.***> wrote:
Hi @RickeyLee09, seems that the [0,0,0] assumption is quite deeply rooted in the code. The best workaround at the moment would be to transform all poses before sending them to the planner and then to apply the inverse transform to the planner output.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Currently, the planner works only if the map origin is at [0,0,0]. Remove this restriction.
The text was updated successfully, but these errors were encountered: