How to not use laser data for navigation?
I'd like to prevent the local planner from using laser data, but I still want to publish it so that I can process it elsewhere. How can I do that?
ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
I'd like to prevent the local planner from using laser data, but I still want to publish it so that I can process it elsewhere. How can I do that?
The easiest way to do that would be to set the occ_dist
parameter of the local planner to zero (I assume you're using base_local_planner
). This won't add any extra cost for potential trajectories to enter nonzero cost cells. I suppose you could even configure the local costmap to not have any layers, which would keep it empty.
I don't know your application, but you might find the robot will clip objects by doing something like this. The only way I see this working is if you update the global plan from navfn
at a pretty high frequency.
I hope this helps!
Asked: 2016-05-12 10:35:24 -0500
Seen: 181 times
Last updated: May 12 '16
change base_local_planner params min and max
No debugging symbols found in base_local_planner library
When planning a trajectory, why is there never an initial in-place rotation?
move_base/base_local_planner maximum velocity
Local planner behaves unordinary
How to use move_base with the DWA planner as the local planner in kinetic
Unify parameters names for local planner
what is the meaning of transformGlobalPlan in goalfunction.cpp line 80
Can you show us your YAML files to see the parameters you use ?