Package Summary
ROS communications-related packages, including core client libraries (roscpp, rospy, roslisp) and graph introspection tools (rostopic, rosnode, rosservice, rosparam).
- Author: Maintained by Ken Conley
- License: BSD,LGPL
- Source: git https://github.com/ros/ros_comm.git
Package Summary
ROS communications-related packages, including core client libraries (roscpp, rospy, roslisp) and graph introspection tools (rostopic, rosnode, rosservice, rosparam).
- Author: Morgan Quigley, Troy Straszheim, Josh Faust, Brian Gerkey, Tim Field, Jeremy Leibs, Ken Conley
- License: BSD
- Source: git https://github.com/ros/ros_comm.git
Package Summary
ROS communications-related packages, including core client libraries (roscpp, rospy) and graph introspection tools (rostopic, rosnode, rosservice, rosparam).
- Maintainer: Dirk Thomas <dthomas@osrfoundation.org>
- Author: Morgan Quigley <mquigley@cs.stanford.edu>, Eric Berger <berger@willowgarage.com>, Ken Conley <kwc@willowgarage.com>, Rosen Diankov <rdiankov@cs.cmu.edu>, Josh Faust <jfaust@willowgarage.com>, Tim Field <tfield@willowgarage.com>, Tully Foote <tfoote@osrfoundation.org>, Brian Gerkey <gerkey@willowgarage.com>, Jeremy Leibs <leibs@willowgarage.com>, Bhaskara Marthi <bhaskara@willowgarage.com>, Troy Straszheim <straszheim@willowgarage.com>, Rob Wheeler <wheeler@willowgarage.com>
- License: BSD
- Source: git https://github.com/ros/ros_comm.git
Documentation
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.
- Graph Concepts:
Backwards compatibility for C Turtle
C Turtle has an empty version of the ros_comm stack. This is provided so that stacks may update their dependencies for Diamondback but not break dependency compatibility with a C Turtle release.
Report a Bug
Use GitHub to report bugs or submit feature requests. Please use 'ros_comm:' at the beginning of the title. [View active issues]
ros_comm developers only: release instructions