Source: ros-one-move-base
Section: misc
Priority: optional
Maintainer: David V. Lu!! <davidvlu@gmail.com>
Build-Depends: debhelper (>= 9.0.0), ros-one-actionlib, ros-one-base-local-planner, ros-one-catkin, ros-one-clear-costmap-recovery, ros-one-cmake-modules, ros-one-costmap-2d, ros-one-dynamic-reconfigure, ros-one-geometry-msgs, ros-one-message-generation, ros-one-move-base-msgs, ros-one-nav-core, ros-one-nav-msgs, ros-one-navfn, ros-one-pluginlib, ros-one-roscpp, ros-one-rospy, ros-one-rotate-recovery, ros-one-std-srvs, ros-one-tf2-geometry-msgs, ros-one-tf2-ros, ros-one-visualization-msgs
Homepage: http://wiki.ros.org/move_base
Standards-Version: 3.9.2

Package: ros-one-move-base
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, ros-one-actionlib, ros-one-base-local-planner, ros-one-clear-costmap-recovery, ros-one-costmap-2d, ros-one-dynamic-reconfigure, ros-one-geometry-msgs, ros-one-message-runtime, ros-one-move-base-msgs, ros-one-nav-core, ros-one-nav-msgs, ros-one-navfn, ros-one-pluginlib, ros-one-roscpp, ros-one-rospy, ros-one-rotate-recovery, ros-one-std-srvs, ros-one-tf2-ros, ros-one-visualization-msgs
Description: The move_base package provides an implementation of an action (see the actionlib package) that, given a goal in the world, will attempt to reach it with a mobile base.
 The move_base node links together a global and local planner to accomplish its global navigation task. It supports any global planner adhering to the nav_core::BaseGlobalPlanner interface specified in the nav_core package and any local planner adhering to the nav_core::BaseLocalPlanner interface specified in the nav_core package. The move_base node also maintains two costmaps, one for the global planner, and one for a local planner (see the costmap_2d package) that are used to accomplish navigation tasks.
