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 -0600
Seen: 205 times
Last updated: May 12 '16
Questions about the Dynamic Window Approach in ROS
base_local_planner generates rotations away from global path
Setting the goal in TrajectoryPlannerROS
Trajectory planner for a multi robot omniwheeled soccer system
dwa_planner vs. base_local_planner
No debugging symbols found in base_local_planner library
move_base/base_local_planner maximum velocity
How to make base_local_planner tightly follow the global plan?
Can you show us your YAML files to see the parameters you use ?