-
Notifications
You must be signed in to change notification settings - Fork 20
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
setting unknown_cost_value to 100 #41
setting unknown_cost_value to 100 #41
Conversation
We also have the |
I have done some testing with this and haven't been able to make it plan over unknown areas yet, so I guess that works, I'll keep testing. As for the allow_unknown parameter apparently is the one that actually considers unknown cells in the cost_map as unknown if not it just gives them obstacle cost, but it does seem a bit hacky as seen in https://github.com/ros-planning/navigation/blob/indigo-devel/navfn/src/navfn.cpp#L251 I'll test changing both today and change the pull request if needed, so don't merge just yet |
@Jailander said:
So? |
… obstacles and not allowing them
This works and has been tested |
how is this related to strands-project/strands_navigation#188? |
It isn't, this has been tested and is ready to be merged, why? |
sorry... got lost ;-) |
setting unknown_cost_value to 100
Hahaha Ok, me too :-D |
solves issue #39