The rx stack contains GUI-related tools for using ROS, including:

 . rxbag: ROS bag recording, playback and visualization

 . rxgraph: ROS graph visualization

 . rxplot: ROS topic data visualization

 . rxconsole: ROS/rosout logging output

The actionlib package provides a standardized interface for interfacing with
preemptible tasks. Examples of this include moving the base to a target
location, performing a laser scan and returning the resulting point cloud,
detecting the handle of a door, etc.

In any large ROS based system, there are cases when someone would like to send
a request to a node to perform some task, and also receive a reply to the
request. This can currently be achieved via ROS services.

In some cases, however, if the service takes a long time to execute, the user
might want the ability to cancel the request during execution or get periodic
feedback about how the request is progressing. The actionlib package provides
tools to create servers that execute long-running goals that can be
preempted. It also provides a client interface in order to send requests to the
server.

common_msgs contains messages that are widely used by other ROS packages. These
includes messages for actions (actionlib_msgs), diagnostics (diagnostic_msgs),
geometric primitives (geometry_msgs), robot navigation (nav_msgs), and common
sensors (sensor_msgs), such as laser range finders, cameras, point clouds.

The ros_comm stack contains the ROS middleware/communications packages. This
packages are collectively known as the ROS "Graph" layer. They provide
implementations and tools for topics, nodes, services, and parameters. This
includes the supported ROS client libraries: roscpp, rospy, and roslisp.

std_msgs contains common message types representing primitive data types and
other basic message constructs, such as multiarrays. For common, generic
robot-specific message types, please see common_msgs.

std_msgs contains wrappers for ROS primitive types, which are documented in the
msg specification. It also contains the Empty type, which is useful for sending
an empty signal.

This package also contains the "MultiArray" types, which can be useful for
storing sensor data.

Meta package modeling the build-time dependencies for language bindings of
messages in ROS.

Meta package modeling the build-time dependencies for language bindings of
messages in ROS.

Lisp code generator for ros .msg and .srv files

python code generator for ROS .srv and .msg files

C++ code generator for ROS .msg and .srv files

Project genmsg exists in order to decouple code generation from ROS .msg & .srv
format files from the parsing of these files and from impementation details of
the build system (project directory layout, existence or nonexistence of
utilities like rospack, values of environment variables such as
ROS_PACKAGE_PATH): i.e. none of these are required to be set in any particular
way.

This module provides a simple interface to record some trajectory and
then replay it.

It makes the link between hyper, the supervision framework, and genom
modules that it must control.

Hyper is an implementation of the ROAR supervision framework.

Nothing really working here, just committing WIP.

Add configure/Makefile scripts, and try to make this robust.
This needs testing.

This package implements new geometry types in Kineo that can be used
in collision checking and proximity queries.

New geometries:
  * Capsule (Cylinder with two half-sphere caps)
  * Segment

  Low pass filters and Bayesian filters for sensor fusion: vision
  and forces

- Delete stackoftasks from toplevel SUBDIR
- Comment out an include of delete stackoftasks file in wip/sot-gui. Should
  wip/sot-gui be removed too?

Given the continuous control trajectory provided by the navigation module (MPC
avoidObs), the MPC controller is aimed at cheking if the control trajectory is
still valid and admissible for the robotic system (respects its motion
constraints) and computing a command to provide as input of the robotic system.

MPC_avoidObs genom is a module encapsulating several reactive navigation
algorithm including:
    - A trajectory selection approach : a reactive navigation method
      allowing to navigate in a unknown environment by computing at each
      time step a set of candidate trajectories and selecting the best
      one
    - A trajectory following with obstacle avoidance approach : a
      reactive method trying to follow a reference trajectory while
      avoiding unforseen obstacles

The MPC planner module provides several tools to plan, record and apply
geometric transformations over a discrete trajectory. The current
version to not include any global motion planning approach of the MPC
library as the current experiments have been focused on exloring an
unknown environment or repeating a learnt trajectory. However, it
provides any I/O tools to load, save, and modify a recorded trajectory.

The MPC dem treatment is aimed at preprocessing the data elevation map
given by the DTM genom module to provide a representation of the
environment understandable by the navigation algorithms. It can compute
slope maps, classify the environment into free or obstacle, and compute
distance to obstacles maps.

MPC is a set of libraries designed for outdoor robot navigation. It
contains several reactive and deliberative navigation algorithms.

This module is compatible with the Logitech Cordless RumblePad 2 joystick.