Recently in releases Category

ROS 2 Bouncy Bolson Released!

We're happy to announce the ROS 2 release Bouncy Bolson!

Check out our installation instructions and tutorials and give it a try! We're excited to hear your feedback and the applications that this release will enable!

To get an idea of what's in this release, be sure to read the Bouncy release page.

A few features and improvements we would like to highlight in this release:

Bouncy Bolson is the second non-beta ROS 2 release and will be supported with bug fixes and platform updates (particularly on rolling dependencies like Windows and MacOS) for one year with support ending in June 2019. While we do aim to keep the API as stable as possible, we can't guarantee 100% API compatibility between releases. Check the features page and ROS 2 roadmap to evaluate whether or not ROS 2 is ready to be used for your application or if you can switch from ROS 1 to ROS 2 as it will depend on the exact feature set and requirements of your use case.

As always, we invite you to try out the new software, give feedback, report bugs, and suggest features (and contribute code!): We also invite you to release your ROS 2 packages in Bouncy! Here's a tutorial to do so.

We would also like to announce the name of the next ROS 2 release: Crystal Clemmys

Your friendly ROS 2 Team

P.S. There's still a few days left on the t-shirt campaign.


ROS Melodic Morenia Released

From Discourse

Greetings ROS users,

Happy World Turtle Day! :turtle: [1]

I am pleased to announce that the 12th ROS distribution, Melodic Morenia [2], is now available on Ubuntu Bionic 18.04, Ubuntu Artful 17.10, and Debian Stretch. 32-bit ARM (armhf) packages are available on Bionic, and 64-bit ARM (aarch64) packages are available for Ubuntu Bionic and Debian Stretch.

To install ROS Melodic, refer to the Installation page on the Wiki:

There are a couple of Release notes to be aware of while installing Melodic:

  • If you installed Melodic from binaries during the beta, you'll have to remove all of your packages and reinstall them.
  • There are currently no debug packages (containing the debug symbols) available for Ubuntu Bionic or Artful packages. This will be remedied a short time after the release, see for details and the fix.

Check out the Migration guide for a changelog of new features and API changes:

465 packages in the ROS ecosystem are in the initial release of Melodic, compared to 2020 currently in Kinetic. You can see the released packages on the status page for Melodic:

And you can compare the versions of packages in Melodic and other active ROS distributions here:

If there's a package missing in Melodic that you'd like to see released, please: * check if the package can be released here: * contact the maintainers to let them know: * by opening an issue on the source repository * posting on the ROS discourse release category:

Even though we've made the initial Melodic release, it's never too late to add packages to Melodic (or Lunar, Kinetic, or Indigo) for upcoming syncs.

Melodic T-shirts (and hoodies) should come through in the mail this week.

We'd also like to announce the name of the next ROS distribution:

Noetic Ninjemys

Thank you to all of the maintainers and contributors who helped make this release possible. We couldn't do this without you.

Chris and the ROS Team

[1] [2]

Lunar Loggerhead Buildfarm Available

We're excited to announce the availability of the buildfarm for the next distribution of ROS, Lunar Loggerhead!

Current Status of the release: The targeted platforms and minimum requirements are specified in REP-003. As of today 114 packages have been released into Lunar with binaries available for Ubuntu Xenial, Yakkety and Zesty as well as Debian Stretch.

To make the release as convenient as possible for our beloved maintainers, we now have a status page keeping track of which repositories have been released compared to ROS Kinetic. This page allows you to see if your repositories are releasable, it also shows what dependencies are not satisfied (if any) and all the repositories depending on your repositories.

Call for action to all maintainers: Check the status page to see if you can already release your package, if yes, please consider getting a Lunar release out soon, if no, please use the lunar release category to coordinate with the maintainers of packages blocking your releases. Make sure that you have the latest version python-bloom and python-rosdistro before starting your release.

Please record any API changes or major behavioral changes in your package on the Migration wiki page for Lunar.

Once your package has been added to Lunar in rosdistro, you can generate a prerelease command on Before running the prerelease make sure that python-ros-buildfarm is up to date.

The Lunar release date is May 2017, but it's good to get started early (especially if many packages depend, directly or indirectly, on yours)!

Your friendly ROS Team

Announcement Thread

New Package: pylon_camera for Basler cameras

From Marcel Debout

We developed and released a ROS camera driver for Basler cameras ( under BSD license.

The package supports Baslers mono USB 3.0, GigE as well as the DART cameras. It offers many functions of the Basler-pylon API inside the ROS-Framework. Exposure Time, Gain, Gamma and Brightness values can be adapted via services. Image grabbing is provided continuously via topics or via action interfaces. Furthermore image rectification with the use of the camerainfomanager is supported.

The package can be found on GitHub:

Documentation can be found in the ROS-Wiki:

Hope you enjoy!

New Package: Bag Database

From P. J. Reed

As hinted yesterday, the real project I have to announce is the Bag Database. This is a server that will scan and monitor an arbitrary directory of bag files, index them, and provide a web-based interface that can be used to quickly search through, analyze, and download them. Have you ever wondered, "Do we have any bags that have a TexturedMarker message in them?", or "What did the path this vehicle followed look like on a satellite terrain map?" This will help you answer both of those questions.

It was designed primarily for internal use; our team has a NAS on which we store thousands of bag files, many of which are several GB in size, and searching through them by hand was difficult and time-consuming. With the Bag Database, everybody can still use tools such as Samba or SFTP to put their bags on the NAS, and the Bag DB will automatically analyze them and make them available in its UI. We have about 15 TB of bags, and it takes about half a second to search through all of them for arbitrary message types or topics.


  • Display any of the information about a bag normally obtained through "rosbag info"
  • Quickly search for bags based on their filename, location, contained message types, or published topics
  • Filter the visible list of bags based on start and end times, latitude/longitude, size, and more
  • Store user-entered metadata such as the vehicle name or description
  • Display the bag's path of GPS coordinates on a MapQuest or Bing map
  • Use Google's reverse-geocoding API to get a string describing a bag's location from its lat/lon coordinates
  • Identify duplicate bag files and tell you about them (although this UI could be better...)

The Bag Database is a Java servlet that only needs a PostgreSQL database to be useful, and it's easiest to deploy it as a Docker container. Source code, documentation, and installation instructions are all available on GitHub:

I know it still has a few rough spots I can work out, but I thought now was a good time to go ahead and release it and see how much interest there is.

Feel free to submit any issues or feature requests on GitHub, and let me know if you have any other questions about it.

From Michal Staniaszek via ros-users@

Version 1.8.9 of the diagnostics package (Indigo and later) has some new functionality for the diagnostic aggregator. You can now change the diagnostic aggregator at runtime by dynamically loading or unloading diagnostic analysers. This can be done by including a node in launch file, or directly from code if you require more control. The intention of the change is to give more flexibility to the aggregator, allow individual packages to specify the analysers that they need, and reduce clutter in the diagnostic aggregator GUI.

Please see the tutorial for examples and more information.

Jacob Perron via ros-users@

This is an announcement for create_autonomy, a ROS driver for the iRobot Create 1 and Create 2 (Roomba 400-800 series).
Based on iRobot's Open Interface Spec, it provides access to a variety of sensor information including wheel odometry, bumpers, light sensors, and button presses. There is also interfaces for controlling the various LEDs and invoking the built-in docking behaviour.

Documentation and source code can be found on GitHub:

Many additional features are planned for the near future, such as a sound interface and access to the brush/vacuum motors.

Hope you enjoy!
Today, the ROS Community Build Tool Team has released the second catkin_tools beta, Version 0.4.0!

Previously, a quick summary:
- `catkin_tools` is an improved toolchain for building catkin workspaces
- the CLI command is `catkin build`
- it builds packages in parallel with isolated build directories (no CMake crosstalk)
- it builds "pure" CMake packages that don't use Catkin macros
- it lets you build subsets of a workspace
- it needs to be tested more before being recommended over `catkin_make`
- the documentation for all the additional features can be found here:

The top five reasons you'll want to try Beta 2:
Either install it with pip:
pip install catkin_tools --upgrade

or install via apt-get with:
apt-get update
apt-get install python-catkin-tools

To check the version of catkin_tools you're using, run:
catkin --version

If you've installed the second beta (0.4.0), you should see:
catkin_tools 0.4.0 (C) 2014-2016 Open Source Robotics Foundation

For those new to catkin_tools, see the migration guide:

Any issues, questions, or feature requests should be posted on GitHub:

-The ROS Community Build Tool Team

Announcement of ROS In-hand scanner

| No Comments | No TrackBacks
From Patrick Wiesen via ros-users@

I'd like to announce my first ROS package - the ROS In-hand scanner. It is a 3D Scanning application based on the PCL In-hand scanner for small objects by Martin Sälzle and the PCL developers.

Until now it was only possible to use OpenNI based sensors. I implemented a standard ROS interface for PointCloud2 message type.

My first results using Intel RealSense can be seen in the following video:

For the future it could be possible to create a RVIZ plugin, implement a global registration or generate watertight meshes for 3D printing applications.

You find the source code on GitHub:

A ROS wiki page including some instructions on how to use will follow soon hopefully.

For the moment have fun with scanning!
From David Scaramuzza via ros-users@

We are happy to release an open source implementation of our approach for real-time, monocular, dense depth estimation, called "REMODE".

The code is available at:

It implements a "REgularized, probabilistic, MOnocular Depth Estimation", as described in the paper:

M. Pizzoli, C. Forster, D. Scaramuzza
REMODE: Probabilistic, monocular dense reconstruction in real time
IEEE International Conference on Robotics and Automation (ICRA), pp. 2609-2616, 2014

The idea is to achieve real-time performance by combining Bayesian, per-pixel estimation with a fast regularization scheme that takes into account the measurement uncertainty to provide spatial regularity and mitigate the effect of noise.
Namely, a probabilistic depth measurement is carried out in real time for each pixel and the computed uncertainty is used to reject erroneous estimations and provide live feedback on the reconstruction progress.
The novelty of the regularization is that the estimated depth uncertainty from the per-pixel depth estimation is used to weight the smoothing.

Since it provides real-time, dense depth maps along with the corresponding confidence maps, REMODE is very suitable for robotic applications, such as environment interaction, motion planning, active vision and control, where both dense information and map uncertainty may be required.
More info here:

The open source implementation requires a CUDA capable GPU and the NVIDIA CUDA Toolkit.
Instructions for building and running the code are available in the repository wiki.

Announcing roslaunch graph generator

| No Comments | No TrackBacks
From Brett Ponsler via ros-users@

I thought it would be useful to be able to generate a graph of the tree of files and nodes used by a particular launch file. After not being able to find anything capable of doing this, I wrote a quick python script to do just that and thought I would share it with everyone.

It's fairly simple to use, but feel free to message me if you have any questions, issues, or suggestions for improvements.

ROS Web Control Center

| No Comments | No TrackBacks
From Lars Berscheid

The ROS Control Center is a universal tool for controlling ROS robots. It runs in the browser using a websocket connection androslibjs from RobotWebToolsIn general, the ROS Control Center offers an easy way to
  • show nodes, topics and service names,
  • subscribe and publish messages,
  • call services,
  • show and change parameters.
Furthermore, it contains features like custom formatting for your own message and service types, a console output and a battery status view. A camera stream view based on the Web Video Server is implemented, many standard message and service types (from common_msgs or std_srvs) work out of the box. It can save multiple robot configurations and has a built-in mode to hide unimportant topics and services. And even better, you can check it out online!

Find more infos at Feedback and contributions are really welcome!
From Manos Tsardoulias

Dear all,

We are happy to announce the first open-source versions of RAPP Platform and RAPP API, oriented to provide an online platform for delivering ready-to-use generic cloud services to robots!

RAPP is a 3-year research project (2013-2016) funded by the European Commission through its FP7 programme, which provides an open source software platform to support the creation and delivery of robotic applications. Its technical objectives include the development of an infrastructure for developers of robotic applications, so they can easily build and include machine learning and personalization techniques to their applications, the creation of a repository from which robots can download Robotic Applications (RApps) and upload useful monitoring information, as well as developing a methodology for knowledge representation and reasoning in robotics and automation. More information on RAPP can be found at

One of the most important parts of RAPP is the RAPP Platform, along with the RAPP API. RAPP Platform is a collection of ROS nodes and back-end processes that aim to provide generic web services to robots. The main concept of RAPP Platform aligns with the cloud robotics approach. RAPP Platform is divided in two main parts: the RAPP ROS nodes and the RAPP Web services.

  • The RAPP ROS nodes are back-end processes providing generic functionality, such as Image processing, Audio processing, Speech synthesis & Automatic speech recognition (ASR), Ontology & Database operations, as well as Machine Learning algorithms.

  • The RAPP Web services are the front-end of the RAPP Platform. These expose specific RAPP Platform functionalities to the world, thus any robot can invoke specific algorithms, simplifying the work of developers. The developed web services utilize HOP, a language dedicated to programming reactive and dynamic applications on the web.

Finally, RAPP API is the software means to invoke a RAPP Platform service via C++, Python or JavaScript from any computational system (either in-robots or standalone such as PCs and laptops).

Links of interest:

From Dave Coleman via ros-users@

I'm happy to announce the release a bunch of packages I've worked on and found useful over the years. They have been used in mine and other's research at the University of Colorado Boulder, as well as in the Amazon Picking Challenge and other external projects for companies. They all have decent documentation in their file, example launch files, utilize Travis CI, and have been released in Indigo and Jade. As always, please help in making them even better!

Rviz Visual Tools
Ever wanted to make visualizing data in Rviz easier? rviz_visual_tools provides a ton of helper functions for visualizing different types of shapes and data in Rviz in an efficient way.

MoveIt! Visual Tools
Want to visualize multiple RobotStates while also showing different trajectories, trajectory lines, and grasp positions? moveit_visual_tools contains all the functionality of rviz_visual_tools while also providing visualization of many of the MoveIt! data types. It also makes it easy to add collision objects to your planning scene.

OMPL Visual Tools
Add to the functionality of Rviz and MoveIt! visual tools with even more specialized features for OMPL data types and for introspecting your sampling-based geometric OMPL planners. ompl_visual_tools is specially good for working in 2D or 3D spaces.

ROS Control Boilerplate
Want to get started with ros_control for your next robot/robot upgrade? ros_control_boilerplate contains lots of working example code for the RRBot (as seen in Gazebo) as well as many helper utilities such as loading joint limits from rosparam and URDF, recording trajectories to file, playing back from file, etc.

MoveIt! Sim Controller
moveit_sim_controller is a pass-through non-physics based simulator for quickly testing your ros_control robot offline. It also allows you to load your robot's initial state from a SRDF (semantic robot description format) state instead of the default 0's state.

TF Keyboard Cal
Don't want to worry about more specialized calibration techniques for moving your /tf transforms to different locations? tf_keyboard_cal lets you use your computer keyboard to tweak the 6 dof transform of a frame quickly and intuitively, and even load/save the settings from file.

ROS Param Shortcuts
The package rosparam_shortcuts provides lots of helper functions for all sorts of datatypes to be easily loaded from parameter server with good user feedback if the parameter is missing. This package enforces the philosphy that there should be no default parameters - everything must be defined by the user in yaml files (or launch files or where ever) otherwise your program should not run.

Two New Message Types
For those interested, I've created cartesian_msgs for commanding a robot's Cartesian end effector position (instead of by joint values), and I've also released graph_msgs for sending graphs of nodes and edges across ROS topics.

I hope these are helpful to your robotics projects!

New package: joystick_sdl

| No Comments | No TrackBacks
From Mike Purvis via ros-users@

A small Christmas present to share, especially for non-Ubuntu ROS users:

For myself as a Mac user, it's long been a thorn in my side that I'm unable to plug in a joystick to drive around real and simulated robots-- when rviz, Gazebo, rqt, and everything else in ROS runs under OS X, why do I have to start a VM just to do a little teleoperation?

Please give it a try and let me know your thoughts,

ROS Support for Blue WorkForce Ragnar Robot

| No Comments | No TrackBacks

ROS-Industrial software developers at Southwest Research Institute have collaborated with the product development team at Blue WorkForce to create a ROS package for their Ragnar robot. The Ragnar is a 4-legged delta style robot designed to be affordable and reconfigurable for a variety of work volumes and tasks. Special thanks to:

  • ROS-I Team: Jonathan Meyer, Alex Goins, and Jeremy Zoss
  • Blue WorkForce Team: Michael Frederiksen and Preben Hjørnet

The source code can be found at:

Laser Scan Matchers - release

| No Comments | No TrackBacks
From Isaac Saito via ros-users@

CCNY's laser-related utility, scan_tools[1], has been in source space
for 5 years since ROS Electric episode. Now it strikes back in the
binary galaxy!

Please see REAME for the installation.

**Those who build from source** are advised to adjust to the way
suggested in README above; recent work changed the way how one of the
depended libraries gets built (*1).

Credit goes to Kei Okada, Carlos Jaramillo for release work, Andrea
Censi for providing help for his CSM library, and Ivan Dryanovski for
the original creation of these ROS packages.


*1...To build one of the included package, laser_scan_matcher[2], its
dependency CSM[3] used to be downloaded and built during the build
time. Upon a trial to conform to ROS buildfarm usage, it's now
separated and released as a "3rd party package"[4].


ROS Web Services

| No Comments | No TrackBacks
From Anis Koubaa via ros-users@

I have developed ROS Web Services to provide new abstractions to ROS using SOAP and REST Web services. The objective was to provide an additional software abstraction layer on top of ROS to allow a seamless interaction with ROS even for non-roboticians. We can say that ROS Web services is another alternative to rosbridge and rosjs which use the Web to interact with ROS. 

Using ROS Web services layer allow any developer with no background on robotics to develop Web service client (SOAP or REST) to monitor and control ROS-enabled robot through simple interfaces.  

paper presenting ROS Web services  is published in The Journal of Software Engineering for Robotics. In the paper, I present an object-oriented design of software meta-models for the integration of both Web services into ROS and we validate it through a real implementation on a service robot. Implementation was performed using ROSJAVA under Hyrdo version.

A video illustration can be seen here:

A brief description is also available here

I still did not release the code due to lack of time, but should post it on GITHUB soon. Any comment on this will be welcome. 
We are working now on extending ROS Web services with new features and we plan to apply them in ROS-enabled drones.

ROS 2 alpha3 (Cement)

| No Comments | No TrackBacks
We're happy to announce the release of ROS 2 alpha3, code-named Cement!

Installation instructions and tutorials designed to exercise new
features in ROS 2 are in the wiki:

To get an idea of what's in (and what's not in) this release, be sure
to read the overview page:

From that page, an important caveat that will persist for the next few
alpha releases:
As the "alpha" qualifier suggests, this release of ROS 2 is far from
complete. You should not expect to switch from ROS 1 to ROS 2, nor
should you expect to build a new robot control system with ROS 2.
Rather, you should expect to try out some demos, explore the code, and
perhaps write your own demos.

We're now on a ~6-week cadence for alpha releases.  We're continually
updating the roadmap to forecast what will be included in each alpha

As always, we invite you to try out the new software, give feedback,
report bugs, and suggest features (and contribute code!):

ROS 2 alpha2 (Baling Wire)

| No Comments | No TrackBacks
We're happy to announce the release of ROS 2 alpha2, code-named Baling Wire!

Installation instructions and tutorials designed to exercise new
features in ROS 2 are in the wiki:

To get an idea of what's in (and what's not in) this release, be sure
to read the overview page:

From that page, an important caveat that will persist for the next few
alpha releases:
As the "alpha" qualifier suggests, this release of ROS 2 is far from
complete. You should not expect to switch from ROS 1 to ROS 2, nor
should you expect to build a new robot control system with ROS 2.
Rather, you should expect to try out some demos, explore the code, and
perhaps write your own demos.

We're now on a ~6-week cadence for alpha releases.  We're continually
updating the roadmap to forecast what will be included in each alpha

As always, we invite you to try out the new software, give feedback,
report bugs, and suggest features (and contribute code!):

Announcing Mapviz, a ROS Visualization Tool

| No Comments | No TrackBacks
From Edward Venator via ros-users@

Southwest Research Institute (SwRI) is pleased to announce the release of Mapviz, a graphical tool for viewing ROS data from outdoor robotic systems. Mapviz, like Rviz, uses an extensible plugin architecture to display ROS data. The Intelligent Vehicles sections at SwRI developed Mapviz as a tool for our work using ROS in automotive applications. Whereas Rviz is designed for 3D display of data from indoor robots, Mapviz is a 2D (top-down) viewer designed for use with outdoor robots. We look forward to feedback and contributions from others who find Mapviz useful.

Some Features of Mapviz:

* Tile Map background maps from OpenMapQuest ( and stamen design (, with Bing map support coming soon
* Multires Image backgrounds to display custom maps or backgrounds
* Robot marker(s) with custom robot image icons
* Plugins for several ROS message types:
    - sensor_msgs/Disparity
    - gps_common/GPSFix (sensor_msgs/NavSatFix support coming soon)
    - sensor_msgs/Image
    - sensor_msgs/LaserScan
    - visualization_msgs/Marker
    - nav_msgs/Odometry
    - nav_msgs/Path
    - marti_visualization_msgs/Textured Marker (a custom message type for painting image data onto the visualization)
    - TF transforms

Jerry Towler of Southwest Research Institute will give a presentation on Mapviz during Day 2 of ROSCon 2015.

If you want to use Mapviz, it is available on GitHub at Ubuntu Debian installers from the OSRF build farm are up in the shadow-fixed repository for Indigo (Trusty) and Jade (Trusty, Utopic, and Vivid). Additionally, Mapviz can be compiled from source for ROS Jade, Indigo, Hydro, Groovy, and Fuerte. Documentation is available on the ROS wiki at

rospeex updates

| No Comments | No TrackBacks
From Komei Sugiura via ros-users@

I would like to announce the release of latest version of rospeex, a
cloud-based multilingual communication package for ROS. Rospeex cloud
services have been operated for two years and used by nearly 20,000
unique users. The details will be presented at IROS 2015.

* Documentation and samples:
* Installation information:

 - Cloud-based speech recognition and synthesis
 - Multilingual (Chinese, English, Japanse, Korean)
 - HTML5-based user interface
 - Can connect to third-party speech APIs

ROS Gentoo Status

| No Comments | No TrackBacks
From Allen Hunter via ros-users@

thought I would take a moment to update you all on the current status
of ROS Gentoo (Woot).

Namely, the location of the overly has moved! It is now located at
ros/ros-overlay as opposed to allenh1/ros-overlay. The wiki has been
changed to reflect this move.

Also, as a neat side-note, Gazebo is working!

Finally, an ebuild was created for the most recent release of wstool.

wstool/rosws updates

| No Comments | No TrackBacks
From Thibault Kruse via ros-users@

the latest release of wstool (1.6 -> 1.9.1) provides some minor improvements I'd like to advertise.

- 'wstool info' provides more information about (git) branches and remote state
- There is a new 'wstool foreach' sub-command that allows to execute shell scripts inside all or selected repositories (similar to vcstool's 'custom' command)
- manpages and bash/zsh completion scripts are also packaged
- 'wstool set ... --update' updates new / changed repositories

Thanks to Kentaro Wada for the initiative and coding effort.

The complete changelog is available at

Report any issues to

TurtleBot updates for Indigo

| No Comments | No TrackBacks


We would like to announce that TurtleBot got major(and minor) updates in both software and hardware. These updates are final (apart from bugfixes) and won't change api for indigo.

  • Turtlebot2 has equipped with better navigation skills, so it can now navigates a lot better with tuned parameters and by Asus Xtion Pro as default sensor.

  • It supports integrated interaction tools, Remocon & Interactions as new ways to interact with robots.

  • Turtlebot2 now can be easily installed and repaired by Turtlebot2 ISO to create Turtlebot2 netbook easily. Check Turtlebot Installation Tutorial.

  • In addition, there are miscellaneous updates in configuration, simulation, and multi robot implementation. Please see Migration Guide for the details.


TurtleBot Team

ROS 2 alpha1 release: Anchor

| No Comments | No TrackBacks
We're happy to announce the release of ROS 2 alpha1, code-named Anchor!

Installation instructions and tutorials designed to exercise new
features in ROS 2 are in the wiki:

To get an idea of what's in (and what's not in) this release, be sure
to read the overview page:

From that page, an important caveat:
As the "alpha" qualifier suggests, this release of ROS 2 is far from
complete. You should not expect to switch from ROS 1 to ROS 2, nor
should you expect to build a new robot control system with ROS 2.
Rather, you should expect to try out some demos, explore the code, and
perhaps write your own demos.

We invite you to try out the new software, give feedback, report bugs,
and suggest features:

- your ROS 2 team

ROS Jade Turtle Release

| No Comments | No TrackBacks
We're happy to announce the official release of ROS Jade Turtle [1]! 


Jade Turtle is the ninth release of ROS and is primarily targeted at the Ubuntu distributions Trusty, Utopic, and Vivid. Our current count of packages is 520, you can compare the packages available in Indigo vs. Jade here:

You can install Jade by following the Jade installation instructions here:

I'm also happy to officially announce the name of the next release of ROS as Kinetic Kame, which we'll refer to as just "kinetic"!

We've also just finished deploying the new website and updated the documentation[3] on the new way to do prereleases for Jade and Indigo:

We're also aware of, and working on, an issue that affects rosbuild on newer Ubuntu's. The issue is a blocker, but not on Trusty. We hope to have a solution in the next few weeks. Please follow this issue if you are interested:

Finally, I want to thank all of the people who helped make this release and get it started strong and on time by the release date (which is also World Turtle day [2])! Thanks also to Tully who put together a video representation of the 40 some odd contributors across around 500 packages:

Thanks to everyone, and enjoy ROS Jade!

Announcing a ROS driver for CH Robotics UM7 IMU

| No Comments | No TrackBacks
From Alex Brown via ros-users@

I'd like to announce the availability of a ROS driver for the  UM7 Inertial Orientation sensor (IMU).  The UM7 is an up-to-date device with quite good performance.

You can see its specs at  The driver documentation is at
From Jon Bohren via ros-users@

Some ROS devs got frustrated with Catkin. You won't believe what happened next!
This is what they built:

Quick summary:
- `catkin_tools` is an improved toolchain for building catkin workspaces
- this toolchain is ready for beta testing, and we want your feedback
- the CLI command is simply called `catkin`
- the build sub-command is `catkin build`
- it builds packages with isolated build directories (no CMake crosstalk)
- it builds packages in parallel
- it builds "pure" CMake packages that don't use Catkin macros
- it lets you build selected packages in a workspace
- it lets you build packages without cd'ing to the workspace root
- it needs to be tested more before being recommended over `catkin_make`
- the documentation for all the additional features can be found here:

Install it now (from the ROS debian repos):
sudo apt-get install python-catkin-tools

Or install it now (from PIP):
sudo pip install -U catkin_tools

Take a look at the cheat sheet:

Give it a try and report issues or feature requests here:

For some background and the relationship to the current top-level `catkin_make` command:

Many thanks to Contributors:
William Woodall
Jonathan Bohren
Nikolaus Demmel
Dave Coleman
Felix Ruess
Dirk Thomas
Kartik Mohta
Thibault Kruse
Ian McMahon
Kei Okada

Those of us who've put time into this project over the last year hope that `catkin build` makes your lives less stressful and helps you build robotic systems faster. 

New 3rd party packages available

| No Comments | No TrackBacks
From Daniel Stonier via ros-users@

This is just a heads up with regards to a few new third party packages on the ros apt-get server that others might find useful:

Google's optimization solver library. It is not a catkin 3rd party, but packaged by Vincent Rabaud and available via the usual ros apt-get server. We were doing everything by source for months before finding out Vincent had packaged it for us - thanks Vincent!

A really awesome c++ implementation of lie groups by Hauke Strasdat built on top of Eigen. Thanks Hauke!

Backports some useful features for qt's imshow from 3.0 to the ubuntu system release of 2.4.x. It lets you zoom, save, and run from parallel threads (great for use on top of ecto).

A new comms release from the author of zeromq (official web page). We often use this for lightweight communications on low level arm boards that can't support ros. Cross compile with catkin from source for the arm boards, or use the deb for the pc side.

Enjoy your robot'icking!

Rosjava/Android Indigo Release

| No Comments | No TrackBacks
From Daniel Stonier via ros-users@

A quick heads up for the official rosjava/android release on indigo. This has been the result of some on and off work over the last couple of weeks - a big thank you to input from a few lads who were busy on the github rosjava issue trackers. Also to Damon for the android improvements since hydro.

Starting points:

Shiny new things (details in the Migration Guide):
  • Gradle version -> 2.2
  • More (and easier) methods of generating message artifacts.
  • Build rosjava debs on the build farm without special workarounds
  • Android Studio 1.x support
  • Android interactions/pairing now stable with tutorials.
  • Lots of other minor fixes and updates.
From Josh Langsfeld via ros-users@

Hello all,

I've been a heavy user of the new Julia programming language ( for my research since the summer and believe it would be a great fit for the ROS community. In a sentence, I've found it combines the expressiveness of Python with the natural mathematical syntax of Matlab with the speed and type safety of C++.

In support of this idea, I've written a Julia package that provides near-native interfacing with ROS in the same vein as rospy or roscpp. This includes automatic generation of Julia types for messages and Julia scripts can be invoked through rosrun or roslaunch in the same manner as Python.

The package itself and more details are here:
For those interested in learning some more technical details about Julia I highly recommend browsing the manual at:

Please feel free to send me any questions and I'm looking forward to working with anyone who might find this a good option to explore.

ROS Vagrant base boxes

| No Comments | No TrackBacks
From Mark Pitchless of Shadowrobot via ros-users@

Hello All,

I'm very pleased to announce a set of vagrant virtual box base boxes, we have been working on at shadow robot, are now available on the cloud for public consumption.

You need vagrant 1.5+ to use these. On trusty bring up a new ros machine like so:

apt-get install vagrant
mkdir indigovm
cd indigovm
vagrant init shadowrobot/ros-indigo-desktop-trusty64
vagrant up

After a bit a logged in desktop will appear, just open a terminal, roscore and away you go.

Currently we have Hydro and Indigo machines in 32bit and 64bit variants.

These are built using vagrant and ansible as part of our build tools project (more on this next week).
Feel free to log issues, ideas there or post here.

Collaboration welcome especially creating bases for other providers.

Have fun,

New ROS package available for the Barrett Hand

| No Comments | No TrackBacks
From Román Navarro García via ros-users@

Hi Everyone,

We're pleased to announce a new package for the Barrett Hand BH8-28X

This package allows the control of the hand either in velocity or position, and reading the current state of the joints and the sensors (fingertip torque and tactile sensors).

The software includes packages with the model description and a graphical interface (rqt) to interact with the hand.

Links: -> Technical description -> ROS package description 

Groovy and Hydro are currently supported, Indigo soon.

If you are interested in verifying all these features of the hand, you can visit us from 14th until 18th of September in booth nº303 at IROS 2014.

Best regards,

ROS Indigo Igloo Released!

| No Comments | No TrackBacks


Hi Everyone,

We're pleased to announce the official release of ROS Indigo Igloo! This is the first LTS release of ROS; it will be supported until April 2019 in parallel with Ubuntu Trusty Tahr. It will also be available for Saucy Salamander during its duration of support from Canonical as outlined in the ROS Distributions page.

Thanks to our many active maintainers it can be seen on the Indigo Igloo build status page that 643 packages have already been released for Indigo Igloo. And we expect this number to continuously grow over the lifetime of the distribution.

The main focus of Indigo development has been to clean up the core packages in preparation for the LTS support cycle. Efforts have included integrating the ROS packages with packages officially taken up into the upstream Debian and Ubuntu repositories such as console_bridge, urdfdom, and OpenCV.

With the release of Indigo, development will be transitioned forward to the next ROS release, Jade Turtle.  ROS Jade Turtle will be targeted for release in May 2015, following the new 12 month release cycle. Also with the beginning of development for Jade Turtle, Groovy Galapagos will reach its end-of-life. Releases into Groovy have been winding down and in the near future the build infrastructure for Groovy will be taken offline.

To get started with Indigo see the installation page. A summary of updates for packages can be found in the migration guide.

Although Indigo is now officially available, ROS distributions are living entities built on the contributions of the community.  Hydro Medusa has almost doubled the number of packages available since it was initially released 9 months ago, and Indigo is tracking a similar trajectory through it's development phases.

We'd also like to take a moment to thank the many contributors to the community who improve documentation on the wiki as well as answering questions and moderating on One of the things that distinguishes ROS is the large helpful community. We now have dozens of moderators and thousands of contributors, thank you all for your contributions!

Details of the latest updated packages in Indigo are listed below as well as updated packages for Hydro.

Your ROS Indigo Igloo Release Team

Updates to indigo

Added Packages [43]:

 * ros-indigo-ax2550: 0.1.1-0

 * ros-indigo-gazebo-ros-control: 2.4.4-0

 * ros-indigo-image-exposure-msgs: 0.9.2-0

 * ros-indigo-nav2d: 0.1.3-0

 * ros-indigo-nav2d-exploration: 0.1.3-0

 * ros-indigo-nav2d-karto: 0.1.3-0

 * ros-indigo-nav2d-localizer: 0.1.3-0

 * ros-indigo-nav2d-msgs: 0.1.3-0

 * ros-indigo-nav2d-navigator: 0.1.3-0

 * ros-indigo-nav2d-operator: 0.1.3-0

 * ros-indigo-nav2d-remote: 0.1.3-0

 * ros-indigo-nav2d-tutorials: 0.1.3-0

 * ros-indigo-ntpd-driver: 1.0.1-0

 * ros-indigo-orocos-kinematics-dynamics: 1.3.0-0

 * ros-indigo-pointgrey-camera-driver: 0.9.2-0

 * ros-indigo-rosh: 1.0.5-0

 * ros-indigo-rosh-common: 1.0.1-0

 * ros-indigo-rosh-core: 1.0.5-0

 * ros-indigo-rosh-desktop: 1.0.2-0

 * ros-indigo-rosh-desktop-plugins: 1.0.2-0

 * ros-indigo-rosh-geometry: 1.0.1-0

 * ros-indigo-rosh-robot: 1.0.1-0

 * ros-indigo-rosh-robot-plugins: 1.0.1-0

 * ros-indigo-rosh-visualization: 1.0.2-0

 * ros-indigo-roshlaunch: 1.0.5-0

 * ros-indigo-serial-utils: 0.1.0-0

 * ros-indigo-shadow-robot: 1.3.2-0

 * ros-indigo-sr-description: 1.3.2-0

 * ros-indigo-sr-example: 1.3.2-0

 * ros-indigo-sr-gazebo-plugins: 1.3.2-0

 * ros-indigo-sr-hand: 1.3.2-0

 * ros-indigo-sr-hardware-interface: 1.3.2-0

 * ros-indigo-sr-mechanism-controllers: 1.3.2-0

 * ros-indigo-sr-mechanism-model: 1.3.2-0

 * ros-indigo-sr-moveit-config: 1.3.2-0

 * ros-indigo-sr-movements: 1.3.2-0

 * ros-indigo-sr-robot-msgs: 1.3.2-0

 * ros-indigo-sr-self-test: 1.3.2-0

 * ros-indigo-sr-standalone: 1.3.2-0

 * ros-indigo-sr-tactile-sensors: 1.3.2-0

 * ros-indigo-sr-utilities: 1.3.2-0

 * ros-indigo-statistics-msgs: 0.9.2-0

 * ros-indigo-wfov-camera-msgs: 0.9.2-0

Updated Packages [94]:

 * ros-indigo-arbotix: 0.9.2-0 -> 0.10.0-0

 * ros-indigo-arbotix-controllers: 0.9.2-0 -> 0.10.0-0

 * ros-indigo-arbotix-firmware: 0.9.2-0 -> 0.10.0-0

 * ros-indigo-arbotix-msgs: 0.9.2-0 -> 0.10.0-0

 * ros-indigo-arbotix-python: 0.9.2-0 -> 0.10.0-0

 * ros-indigo-arbotix-sensors: 0.9.2-0 -> 0.10.0-0

 * ros-indigo-compressed-depth-image-transport: 1.9.0-0 -> 1.9.1-0

 * ros-indigo-compressed-image-transport: 1.9.0-0 -> 1.9.1-0

 * ros-indigo-flir-ptu-description: 0.1.3-0 -> 0.1.4-0

 * ros-indigo-flir-ptu-driver: 0.1.3-0 -> 0.1.4-0

 * ros-indigo-flir-ptu-viz: 0.1.3-0 -> 0.1.4-0

 * ros-indigo-gazebo-msgs: 2.4.3-1 -> 2.4.4-0

 * ros-indigo-gazebo-plugins: 2.4.3-1 -> 2.4.4-0

 * ros-indigo-gazebo-ros: 2.4.3-1 -> 2.4.4-0

 * ros-indigo-gazebo-ros-pkgs: 2.4.3-1 -> 2.4.4-0

 * ros-indigo-image-transport-plugins: 1.9.0-0 -> 1.9.1-0

 * ros-indigo-mavlink: 1.0.9-5 -> 1.0.9-7

 * ros-indigo-mavros: 0.5.0-0 -> 0.6.0-0

 * ros-indigo-message-filters: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-mk: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-opencv-candidate: 0.2.1-0 -> 0.2.3-0

 * ros-indigo-orocos-kdl: 1.2.2-2 -> 1.3.0-0

 * ros-indigo-python-orocos-kdl: 1.2.2-2 -> 1.3.0-0

 * ros-indigo-ros: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-ros-comm: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-ros-ethercat: 0.1.7-0 -> 0.1.8-0

 * ros-indigo-ros-ethercat-eml: 0.1.7-0 -> 0.1.8-0

 * ros-indigo-ros-ethercat-hardware: 0.1.7-0 -> 0.1.8-0

 * ros-indigo-ros-ethercat-loop: 0.1.7-0 -> 0.1.8-0

 * ros-indigo-ros-ethercat-model: 0.1.7-0 -> 0.1.8-0

 * ros-indigo-rosbag: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosbag-storage: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosbash: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-rosboost-cfg: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-rosbuild: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-rosclean: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-rosconsole: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosconsole-bridge: 0.4.1-0 -> 0.4.2-0

 * ros-indigo-roscpp: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-roscreate: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-rosgraph: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-roslang: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-roslaunch: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-roslib: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-roslz4: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosmake: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-rosmaster: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosmsg: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosnode: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosout: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosparam: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rospy: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosservice: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rostest: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rostopic: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosunit: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-roswtf: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rqt-action: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-bag: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-bag-plugins: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-common-plugins: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-console: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-dep: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-ez-publisher: 0.0.5-0 -> 0.2.0-0

 * ros-indigo-rqt-graph: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-image-view: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-launch: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-logger-level: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-msg: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-plot: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-publisher: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-py-common: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-py-console: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-reconfigure: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-service-caller: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-shell: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-srv: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-top: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-topic: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-web: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-sr-ronex: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-controllers: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-drivers: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-examples: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-external-protocol: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-hardware-interface: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-launch: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-msgs: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-test: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-transmissions: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-utilities: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-theora-image-transport: 1.9.0-0 -> 1.9.1-0

 * ros-indigo-topic-tools: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-xmlrpcpp: 1.11.6-0 -> 1.11.7-0

Removed Packages [0]:

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

 * Aaron Blasdel

 * Ben Charrow

 * Dan Lazewatsky

 * David Gossow

 * Dirk Thomas

 * Dorian Scholz

 * Isaac Isao Saito

 * Isaac Saito

 * John Hsu

 * Jonathan Bohren

 * Julius Kammerl

 * Maintained by Dan Lazewatsky

 * Manos Nikolaidis

 * Michael Ferguson

 * Mike Purvis

 * MoveIt Setup Assistant

 * Orocos Developers

 * Ruben Smits

 * Scott K Logan

 * Sebastian Kasperski

 * Shadow Robot's software team

 * Takashi Ogura

 * Vincent Rabaud

 * Vladimir Ermakov

 * William Woodall

Updates to hydro

Added Packages [24]:
 * ros-hydro-catkinize-this: 0.1.0-2
 * ros-hydro-easy-markers: 0.1.0-2
 * ros-hydro-laser-filtering: 0.0.1-0
 * ros-hydro-leg-detector: 1.0.4-0
 * ros-hydro-libpointmatcher: 1.2.0-0
 * ros-hydro-manifest-cleaner: 0.1.0-2
 * ros-hydro-map-laser: 0.0.1-0
 * ros-hydro-multisense-description: 1.0.0-1
 * ros-hydro-nlopt: 1.0.29-0
 * ros-hydro-object-recognition-clusters: 0.1.0-0
 * ros-hydro-orocos-kinematics-dynamics: 1.3.0-0
 * ros-hydro-people-tracking-filter: 1.0.4-0
 * ros-hydro-people-velocity-tracker: 1.0.4-0
 * ros-hydro-range-sensor-layer: 0.2.0-0
 * ros-hydro-rosbaglive: 0.1.0-2
 * ros-hydro-rosh-desktop: 1.0.2-0
 * ros-hydro-rosh-desktop-plugins: 1.0.2-0
 * ros-hydro-rosh-visualization: 1.0.2-0
 * ros-hydro-roswiki-node: 0.1.0-2
 * ros-hydro-rqt-ez-publisher: 0.2.0-0
 * ros-hydro-simple-robot-control: 0.0.2-0
 * ros-hydro-social-navigation-layers: 1.0.4-0
 * ros-hydro-speech-recognition-msgs: 1.0.29-0
 * ros-hydro-wu-ros-tools: 0.1.0-2

Updated Packages [159]:
 * ros-hydro-amcl: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-assimp-devel: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-base-local-planner: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-bayesian-belief-networks: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-bond: 1.7.13-0 -> 1.7.14-0
 * ros-hydro-bond-core: 1.7.13-0 -> 1.7.14-0
 * ros-hydro-bondcpp: 1.7.13-0 -> 1.7.14-0
 * ros-hydro-bondpy: 1.7.13-0 -> 1.7.14-0
 * ros-hydro-camera-umd: 0.2.1-0 -> 0.2.4-0
 * ros-hydro-capabilities: 0.1.1-0 -> 0.2.0-0
 * ros-hydro-carrot-planner: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-checkerboard-detector: 0.1.7-0 -> 0.1.11-0
 * ros-hydro-clear-costmap-recovery: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-collada-urdf-jsk-patch: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-costmap-2d: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-default-cfg-fkie: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-depth-image-proc-jsk-patch: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-downward: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-dwa-local-planner: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-dynamic-tf-publisher: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-eus-assimp: 0.1.4-0 -> 0.1.6-0
 * ros-hydro-euscollada: 0.1.4-0 -> 0.1.6-0
 * ros-hydro-euslisp: 1.1.19-0 -> 1.1.21-0
 * ros-hydro-face-detector: 1.0.3-0 -> 1.0.4-0
 * ros-hydro-fake-localization: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-ff: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-ffha: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-flir-ptu-description: 0.1.3-0 -> 0.1.4-0
 * ros-hydro-flir-ptu-driver: 0.1.3-0 -> 0.1.4-0
 * ros-hydro-flir-ptu-viz: 0.1.3-0 -> 0.1.4-0
 * ros-hydro-geneus: 1.1.19-0 -> 1.1.21-0
 * ros-hydro-global-planner: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-gmapping: 1.3.2-1 -> 1.3.3-0
 * ros-hydro-hector-localization: 0.1.2-0 -> 0.1.3-0
 * ros-hydro-hector-pose-estimation: 0.1.2-0 -> 0.1.3-0
 * ros-hydro-hector-pose-estimation-core: 0.1.2-0 -> 0.1.3-0
 * ros-hydro-hironx-moveit-config: 1.0.14-0 -> 1.0.18-1
 * ros-hydro-hironx-ros-bridge: 1.0.14-0 -> 1.0.18-1
 * ros-hydro-image-exposure-msgs: 0.9.1-0 -> 0.9.2-0
 * ros-hydro-image-view-jsk-patch: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-image-view2: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-imagesift: 0.1.7-0 -> 0.1.11-0
 * ros-hydro-imu-compass: 0.0.3-0 -> 0.0.5-0
 * ros-hydro-jpeg-streamer: 0.2.1-0 -> 0.2.4-0
 * ros-hydro-jsk-common: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-jsk-footstep-msgs: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-jsk-gui-msgs: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-jsk-hark-msgs: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-jsk-interactive: 1.0.4-0 -> 1.0.5-0
 * ros-hydro-jsk-interactive-marker: 1.0.4-0 -> 1.0.5-0
 * ros-hydro-jsk-interactive-test: 1.0.4-0 -> 1.0.5-0
 * ros-hydro-jsk-model-tools: 0.1.4-0 -> 0.1.6-0
 * ros-hydro-jsk-pcl-ros: 0.1.7-0 -> 0.1.11-0
 * ros-hydro-jsk-perception: 0.1.7-0 -> 0.1.11-0
 * ros-hydro-jsk-recognition: 0.1.7-0 -> 0.1.11-0
 * ros-hydro-jsk-roseus: 1.1.19-0 -> 1.1.21-0
 * ros-hydro-jsk-rqt-plugins: 1.0.4-0 -> 1.0.5-0
 * ros-hydro-jsk-rviz-plugins: 1.0.4-0 -> 1.0.5-0
 * ros-hydro-jsk-tools: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-jsk-topic-tools: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-laser-filters-jsk-patch: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-libsiftfast: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-libuvc: 0.0.3-0 -> 0.0.5-0
 * ros-hydro-map-server: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-master-discovery-fkie: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-master-sync-fkie: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-mavlink: 1.0.9-4 -> 1.0.9-5
 * ros-hydro-mavros: 0.5.0-0 -> 0.6.0-0
 * ros-hydro-message-to-tf: 0.1.2-0 -> 0.1.3-0
 * ros-hydro-move-base: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-move-base-msgs: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-move-slow-and-clear: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-moveit-commander: 0.5.5-0 -> 0.5.7-0
 * ros-hydro-moveit-core: 0.5.8-0 -> 0.5.9-0
 * ros-hydro-moveit-planners: 0.5.4-0 -> 0.5.6-0
 * ros-hydro-moveit-planners-ompl: 0.5.4-0 -> 0.5.6-0
 * ros-hydro-moveit-python: 0.2.4-0 -> 0.2.5-0
 * ros-hydro-moveit-ros: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-benchmarks: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-benchmarks-gui: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-manipulation: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-move-group: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-perception: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-planning: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-planning-interface: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-robot-interaction: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-visualization: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-warehouse: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-multi-map-server: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-multimaster-fkie: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-multimaster-msgs-fkie: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-nav-core: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-navfn: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-navigation: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-nextage-description: 0.2.14-0 -> 0.2.15-1
 * ros-hydro-nextage-moveit-config: 0.2.14-0 -> 0.2.15-1
 * ros-hydro-nextage-ros-bridge: 0.2.14-0 -> 0.2.15-1
 * ros-hydro-node-manager-fkie: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-opencv-candidate: 0.2.1-0 -> 0.2.3-0
 * ros-hydro-openni-tracker-jsk-patch: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-opt-camera: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-orocos-kdl: 1.2.2-0 -> 1.3.0-0
 * ros-hydro-pal-vision-segmentation: 0.0.1-0 -> 1.0.0-0
 * ros-hydro-people: 1.0.3-0 -> 1.0.4-0
 * ros-hydro-people-msgs: 1.0.3-0 -> 1.0.4-0
 * ros-hydro-pointgrey-camera-driver: 0.9.1-0 -> 0.9.2-0
 * ros-hydro-posedetection-msgs: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-pr2-groovy-patches: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-python-orocos-kdl: 1.2.2-0 -> 1.3.0-0
 * ros-hydro-qt-build: 0.2.5-0 -> 0.2.6-0
 * ros-hydro-qt-create: 0.2.5-0 -> 0.2.6-0
 * ros-hydro-qt-ros: 0.2.5-0 -> 0.2.6-0
 * ros-hydro-qt-tutorials: 0.2.5-0 -> 0.2.6-0
 * ros-hydro-resized-image-transport: 0.1.7-0 -> 0.1.11-0
 * ros-hydro-robot-pose-ekf: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-ros-ethercat: 0.1.7-0 -> 0.1.7-1
 * ros-hydro-ros-ethercat-eml: 0.1.7-0 -> 0.1.7-1
 * ros-hydro-ros-ethercat-hardware: 0.1.7-0 -> 0.1.7-1
 * ros-hydro-ros-ethercat-loop: 0.1.7-0 -> 0.1.7-1
 * ros-hydro-ros-ethercat-model: 0.1.7-0 -> 0.1.7-1
 * ros-hydro-roseus: 1.1.19-0 -> 1.1.21-0
 * ros-hydro-roseus-msgs: 1.1.19-0 -> 1.1.21-0
 * ros-hydro-roseus-smach: 1.1.19-0 -> 1.1.21-0
 * ros-hydro-rosh: 1.0.3-0 -> 1.0.5-0
 * ros-hydro-rosh-core: 1.0.3-0 -> 1.0.5-0
 * ros-hydro-roshlaunch: 1.0.3-0 -> 1.0.5-0
 * ros-hydro-rosjava-bootstrap: 0.1.21-0 -> 0.1.22-0
 * ros-hydro-rospatlite: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-rosping: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-rostwitter: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-rotate-recovery: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-rtmros-hironx: 1.0.14-0 -> 1.0.18-1
 * ros-hydro-rtmros-nextage: 0.2.14-0 -> 0.2.15-1
 * ros-hydro-sklearn: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-slam-gmapping: 1.3.2-1 -> 1.3.3-0
 * ros-hydro-smclib: 1.7.13-0 -> 1.7.14-0
 * ros-hydro-sr-ronex: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-controllers: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-drivers: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-examples: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-external-protocol: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-hardware-interface: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-launch: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-msgs: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-test: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-transmissions: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-utilities: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-statistics-msgs: 0.9.1-0 -> 0.9.2-0
 * ros-hydro-stereo-synchronizer: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-uvc-camera: 0.2.1-0 -> 0.2.4-0
 * ros-hydro-vision-visp: 0.7.3-1 -> 0.7.4-0
 * ros-hydro-visp-auto-tracker: 0.7.3-1 -> 0.7.4-0
 * ros-hydro-visp-bridge: 0.7.3-1 -> 0.7.4-0
 * ros-hydro-visp-camera-calibration: 0.7.3-1 -> 0.7.4-0
 * ros-hydro-visp-hand2eye-calibration: 0.7.3-1 -> 0.7.4-0
 * ros-hydro-visp-tracker: 0.7.3-1 -> 0.7.4-0
 * ros-hydro-voxel-grid: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-wfov-camera-msgs: 0.9.1-0 -> 0.9.2-0
 * ros-hydro-world-magnetic-model: 0.1.2-0 -> 0.1.3-0

Removed Packages [0]:

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:
 * Alexander Tiderko
 * Bence Magyar
 * Carnegie Robotics
 * Dan Lazewatsky
 * Daniel Stonier
 * David Lu!!
 * David V. Lu!!
 * Esteve Fernandez
 * Fabien Spindler
 * Francois Pomerleau
 * Hiroyuki Mikita
 * Ioan Sucan
 * Isaac Isao Saito
 * Johannes Meyer
 * KazutoMurase
 * Kei Okada
 * Ken Tossell
 * Manos Nikolaidis
 * Michael Ferguson
 * Mike Purvis
 * Noda Shintaro
 * Orocos Developers
 * Prasenjit Mukherjee
 * Ruben Smits
 * Ryohei Ueda
 * Sachin Chitta
 * Shadow Robot's software team
 * Shohei Fujii
 * Takashi Ogura
 * Takuya Nakaoka
 * Vincent Rabaud
 * Vladimir Ermakov
 * William Woodall
 * Yohei Kakiuchi
 * Youhei Kakiuchi
 * Yuki Furuta
 * Yusuke Furuta
 * furuta
 * k-okada
 * lil1pal

ROS Indigo Igloo Beta 2

| No Comments | No TrackBacks
We are pleased to announce ROS Indigo Igloo Beta 2 today. We have resolved all the issues discovered during the first beta and plan this to be the release candidate for a final release. If everything goes well through the next ~10 days of testing we will make the final release. 

This release includes many updates as well a few new packages. The full list is below. Thank you to everyone who has worked hard to get this out. 

In the next week I encourage all maintainers and developers to review their packages as well as any Indigo relevant documentation to verify that it is up to date. Of particular note please make sure to review the migration guide [1].


Updates to indigo

Added Packages [3]:
 * ros-indigo-effort-controllers: 0.8.1-0
 * ros-indigo-ros-controllers: 0.8.1-0
 * ros-indigo-rqt-ez-publisher: 0.0.5-0

Updated Packages [73]:
 * ros-indigo-catkin: 0.6.7-0 -> 0.6.9-1
 * ros-indigo-diff-drive-controller: 0.8.0-1 -> 0.8.1-0
 * ros-indigo-force-torque-sensor-controller: 0.8.0-1 -> 0.8.1-0
 * ros-indigo-forward-command-controller: 0.8.0-1 -> 0.8.1-0
 * ros-indigo-genmsg: 0.5.2-0 -> 0.5.3-0
 * ros-indigo-gripper-action-controller: 0.8.0-1 -> 0.8.1-0
 * ros-indigo-imu-sensor-controller: 0.8.0-1 -> 0.8.1-0
 * ros-indigo-joint-state-controller: 0.8.0-1 -> 0.8.1-0
 * ros-indigo-joint-trajectory-controller: 0.8.0-1 -> 0.8.1-0
 * ros-indigo-message-filters: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-position-controllers: 0.8.0-1 -> 0.8.1-0
 * ros-indigo-python-qt-binding: 0.2.13-0 -> 0.2.14-0
 * ros-indigo-qt-dotgraph: 0.2.24-0 -> 0.2.25-0
 * ros-indigo-qt-gui: 0.2.24-0 -> 0.2.25-0
 * ros-indigo-qt-gui-app: 0.2.24-0 -> 0.2.25-0
 * ros-indigo-qt-gui-core: 0.2.24-0 -> 0.2.25-0
 * ros-indigo-qt-gui-cpp: 0.2.24-0 -> 0.2.25-0
 * ros-indigo-qt-gui-py-common: 0.2.24-0 -> 0.2.25-0
 * ros-indigo-ros-comm: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rosbag: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rosbag-storage: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rosconsole: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-roscpp: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rosgraph: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-roslaunch: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-roslz4: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rosmaster: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rosmsg: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rosnode: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rosout: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rospack: 2.2.3-1 -> 2.2.4-0
 * ros-indigo-rosparam: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rospy: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rosservice: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rostest: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rostopic: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-roswtf: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rqt-action: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-bag: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-bag-plugins: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-common-plugins: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-console: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-dep: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-graph: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-image-view: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-launch: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-logger-level: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-moveit: 0.3.5-0 -> 0.3.6-0
 * ros-indigo-rqt-msg: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-nav-view: 0.3.5-0 -> 0.3.6-0
 * ros-indigo-rqt-plot: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-pose-view: 0.3.5-0 -> 0.3.6-0
 * ros-indigo-rqt-publisher: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-py-common: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-py-console: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-reconfigure: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-robot-dashboard: 0.3.5-0 -> 0.3.6-0
 * ros-indigo-rqt-robot-monitor: 0.3.5-0 -> 0.3.6-0
 * ros-indigo-rqt-robot-plugins: 0.3.5-0 -> 0.3.6-0
 * ros-indigo-rqt-robot-steering: 0.3.5-0 -> 0.3.6-0
 * ros-indigo-rqt-runtime-monitor: 0.3.5-0 -> 0.3.6-0
 * ros-indigo-rqt-rviz: 0.3.5-0 -> 0.3.6-0
 * ros-indigo-rqt-service-caller: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-shell: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-srv: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-tf-tree: 0.3.5-0 -> 0.3.6-0
 * ros-indigo-rqt-top: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-topic: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-web: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-topic-tools: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-velocity-controllers: 0.8.0-1 -> 0.8.1-0
 * ros-indigo-xacro: 1.9.1-0 -> 1.9.2-0
 * ros-indigo-xmlrpcpp: 1.11.5-0 -> 1.11.6-0

Removed Packages [0]:

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:
 * Aaron Blasdel
 * Adolfo Rodriguez Tsouroukdissian
 * Ben Charrow
 * Bence Magyar
 * Dan Lazewatsky
 * Dirk Thomas
 * Dorian Scholz
 * Isaac Isao Saito
 * Isaac Saito
 * Mirza A. Shah
 * Morgan Quigley
 * Sachin Chitta
 * Scott K Logan
 * Takashi Ogura
 * Vijay Pradeep
 * Wim Meeussen
 * Ze'ev Klapow

From Christian Forster via ros-users@

Dear Colleagues,

We would like to draw your attention to a new open-source monocular
visual odometry algorithm called SVO (``Semi-direct Visual Odometry'').
The semi-direct approach eliminates the need of costly feature
extraction and robust matching techniques for motion estimation. Our
algorithm operates directly on pixel intensities, which results in
subpixel precision at high frame-rates (up to 70 fps on latest
smartphone processors, up to 400 fps on laptops). A probabilistic
mapping method that explicitly models outlier measurements is used to
estimate 3D points, which results in fewer outliers and more reliable
points. Precise and high frame-rate motion estimation brings increased
robustness in scenes of repetitive, and high-frequency texture.

In our group, we use SVO for vision-based, on-board ego-motion
estimation of micro aerial vehicles, which also allows them to navigate
fully autonomously.

Please check the video with a demonstration of the system capabilities:

The code is hosted on GitHub:
A closed-source professional edition is available for commercial
purposes. Please contact us for further info.

The algorithm is described in our the paper (please cite it if you use
it for your publications):
C. Forster, M. Pizzoli, D. Scaramuzza, "SVO: Fast Semi-Direct Monocular
Visual Odometry," IEEE International Conference on Robotics and
Automation (ICRA), 2014.

Best regards,

Christian Forster, Matia Pizzoli, Davide Scaramuzza

Robotics and Perception Group,
University of Zurich,

ROS Indigo Igloo Beta Available

| No Comments | No TrackBacks
We're pleased to announce the availability of the first beta release of ROS Indigo Igloo in the repositories. ROS Indigo Igloo now has over 500 packages including everything in ros-indigo-desktop-full as defined in REP 142 [1]. 

ROS Indigo Igloo will be our first LTS release synchronized to pair with the Ubuntu Trusty Tahr release which came out last month. The support period and a summary of distributions can be found on the wiki [2]. 

As this is an LTS release most of the core components have been focused on minor incremental improvements for stability and maintainability. For a summary of updates important to all developers please see the migration guide [3]. This is an aggregation of package changes which maintainers would like the community to be aware of. If you are maintaining a package and have made major changes it is encouraged to fill this page in before the final release. 

This is the first beta release and we ask that people try out the system in the coming weeks. We have just recently detected a major issue with the Debian packaging system and thanks to the great community of ROS maintainers in one week we have rereleased over 300 packages.

To make sure that we have adequate testing we will delay the final release into June.  

Full details of updated packages in Indigo Hydro and Groovy are below. 

Updates to indigo (1 of 3)

Added Packages [28]:
 * ros-indigo-amcl: 1.11.8-0
 * ros-indigo-arbotix: 0.9.2-0
 * ros-indigo-arbotix-controllers: 0.9.2-0
 * ros-indigo-arbotix-firmware: 0.9.2-0
 * ros-indigo-arbotix-msgs: 0.9.2-0
 * ros-indigo-arbotix-python: 0.9.2-0
 * ros-indigo-arbotix-sensors: 0.9.2-0
 * ros-indigo-base-local-planner: 1.11.8-0
 * ros-indigo-carrot-planner: 1.11.8-0
 * ros-indigo-clear-costmap-recovery: 1.11.8-0
 * ros-indigo-costmap-2d: 1.11.8-0
 * ros-indigo-dwa-local-planner: 1.11.8-0
 * ros-indigo-fake-localization: 1.11.8-0
 * ros-indigo-global-planner: 1.11.8-0
 * ros-indigo-map-server: 1.11.8-0
 * ros-indigo-move-base: 1.11.8-0
 * ros-indigo-move-base-msgs: 1.11.8-0
 * ros-indigo-move-slow-and-clear: 1.11.8-0
 * ros-indigo-nav-core: 1.11.8-0
 * ros-indigo-navfn: 1.11.8-0
 * ros-indigo-navigation: 1.11.8-0
 * ros-indigo-openni2-launch: 0.2.1-0
 * ros-indigo-pocketsphinx: 0.3.0-0
 * ros-indigo-robot-pose-ekf: 1.11.8-0
 * ros-indigo-rotate-recovery: 1.11.8-0
 * ros-indigo-rviz-animated-view-controller: 0.1.1-0
 * ros-indigo-view-controller-msgs: 0.1.2-0
 * ros-indigo-voxel-grid: 1.11.8-0

Updated Packages [222]:
 * ros-indigo-actionlib: 1.11.1-0 -> 1.11.2-0
 * ros-indigo-actionlib-msgs: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-bond: 1.7.14-0 -> 1.7.14-1
 * ros-indigo-bond-core: 1.7.14-0 -> 1.7.14-1
 * ros-indigo-bondcpp: 1.7.14-0 -> 1.7.14-1
 * ros-indigo-bondpy: 1.7.14-0 -> 1.7.14-1
 * ros-indigo-camera-calibration-parsers: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-camera-info-manager: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-class-loader: 0.2.4-0 -> 0.2.5-1
 * ros-indigo-common-msgs: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-control-msgs: 1.3.0-1 -> 1.3.0-2
 * ros-indigo-control-toolbox: 1.11.0-0 -> 1.11.0-1
 * ros-indigo-controller-interface: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-controller-manager: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-controller-manager-msgs: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-controller-manager-tests: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-cpp-common: 0.5.0-0 -> 0.5.0-1
 * ros-indigo-cv-bridge: 1.11.2-0 -> 1.11.2-1
 * ros-indigo-diagnostic-msgs: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-diff-drive-controller: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-dynamic-reconfigure: 1.5.36-0 -> 1.5.36-1
 * ros-indigo-eigen-conversions: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-fcl: 0.3.0-1 -> 0.3.1-0
 * ros-indigo-force-torque-sensor-controller: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-forward-command-controller: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-freenect-camera: 0.3.2-0 -> 0.3.2-1
 * ros-indigo-freenect-launch: 0.3.2-0 -> 0.3.2-1
 * ros-indigo-freenect-stack: 0.3.2-0 -> 0.3.2-1
 * ros-indigo-gazebo-msgs: 2.4.3-0 -> 2.4.3-1
 * ros-indigo-gazebo-plugins: 2.4.3-0 -> 2.4.3-1
 * ros-indigo-gazebo-ros: 2.4.3-0 -> 2.4.3-1
 * ros-indigo-gazebo-ros-pkgs: 2.4.3-0 -> 2.4.3-1
 * ros-indigo-geometric-shapes: 0.3.8-1 -> 0.3.8-2
 * ros-indigo-geometry: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-geometry-msgs: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-gripper-action-controller: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-hardware-interface: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-humanoid-msgs: 0.3.0-0 -> 0.3.0-1
 * ros-indigo-humanoid-nav-msgs: 0.3.0-0 -> 0.3.0-1
 * ros-indigo-image-common: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-image-geometry: 1.11.2-0 -> 1.11.2-1
 * ros-indigo-image-transport: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-imu-sensor-controller: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-interaction-cursor-3d: 0.0.3-0 -> 0.0.3-1
 * ros-indigo-interaction-cursor-demo: 0.0.3-0 -> 0.0.3-1
 * ros-indigo-interaction-cursor-msgs: 0.0.3-0 -> 0.0.3-1
 * ros-indigo-interaction-cursor-rviz: 0.0.3-0 -> 0.0.3-1
 * ros-indigo-joint-limits-interface: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-joint-state-controller: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-joint-trajectory-controller: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-kdl-conversions: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-libccd: 1.5.0-0 -> 1.5.0-1
 * ros-indigo-libfreenect: 0.1.2-1 -> 0.1.2-2
 * ros-indigo-message-filters: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-mk: 1.11.1-0 -> 1.11.1-1
 * ros-indigo-moveit-core: 0.5.8-0 -> 0.5.8-1
 * ros-indigo-moveit-fake-controller-manager: 0.5.6-0 -> 0.5.6-1
 * ros-indigo-moveit-planners: 0.5.5-0 -> 0.5.5-1
 * ros-indigo-moveit-planners-ompl: 0.5.5-0 -> 0.5.5-1
 * ros-indigo-moveit-plugins: 0.5.6-0 -> 0.5.6-1
 * ros-indigo-moveit-python: 0.2.1-0 -> 0.2.2-0
 * ros-indigo-moveit-ros: 0.5.18-0 -> 0.5.18-1
 * ros-indigo-moveit-ros-benchmarks: 0.5.18-0 -> 0.5.18-1
 * ros-indigo-moveit-ros-benchmarks-gui: 0.5.18-0 -> 0.5.18-1
 * ros-indigo-moveit-ros-manipulation: 0.5.18-0 -> 0.5.18-1
 * ros-indigo-moveit-ros-move-group: 0.5.18-0 -> 0.5.18-1
 * ros-indigo-moveit-ros-perception: 0.5.18-0 -> 0.5.18-1
 * ros-indigo-moveit-ros-planning: 0.5.18-0 -> 0.5.18-1
 * ros-indigo-moveit-ros-planning-interface: 0.5.18-0 -> 0.5.18-1
 * ros-indigo-moveit-ros-robot-interaction: 0.5.18-0 -> 0.5.18-1
 * ros-indigo-moveit-ros-visualization: 0.5.18-0 -> 0.5.18-1
 * ros-indigo-moveit-ros-warehouse: 0.5.18-0 -> 0.5.18-1
 * ros-indigo-moveit-simple-controller-manager: 0.5.6-0 -> 0.5.6-1
 * ros-indigo-nao-bringup: 0.2.3-0 -> 0.2.3-1
 * ros-indigo-nao-description: 0.2.3-0 -> 0.2.3-1
 * ros-indigo-nao-driver: 0.2.3-0 -> 0.2.3-1
 * ros-indigo-nao-msgs: 0.2.3-0 -> 0.2.3-1
 * ros-indigo-nao-pose: 0.2.3-0 -> 0.2.3-1
 * ros-indigo-nao-robot: 0.2.3-0 -> 0.2.3-1
 * ros-indigo-nav-msgs: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-nmea-msgs: 0.1.0-0 -> 0.1.0-1
 * ros-indigo-nodelet: 1.8.3-0 -> 1.8.3-1
 * ros-indigo-nodelet-core: 1.8.3-0 -> 1.8.3-1
 * ros-indigo-nodelet-topic-tools: 1.8.3-0 -> 1.8.3-1
 * ros-indigo-octomap: 1.6.4-1 -> 1.6.5-0
 * ros-indigo-octomap-msgs: 0.3.1-4 -> 0.3.1-5
 * ros-indigo-octomap-ros: 0.4.0-0 -> 0.4.0-1
 * ros-indigo-octomap-rviz-plugins: 0.0.5-0 -> 0.0.5-1
 * ros-indigo-octovis: 1.6.4-1 -> 1.6.5-0
 * ros-indigo-openni2-camera: 0.1.2-0 -> 0.2.0-0
 * ros-indigo-orocos-kdl: 1.2.2-1 -> 1.2.2-2
 * ros-indigo-pluginlib: 1.10.0-0 -> 1.10.0-1
 * ros-indigo-polled-camera: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-position-controllers: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-python-orocos-kdl: 1.2.2-1 -> 1.2.2-2
 * ros-indigo-qt-dotgraph: 0.2.23-0 -> 0.2.24-0
 * ros-indigo-qt-gui: 0.2.23-0 -> 0.2.24-0
 * ros-indigo-qt-gui-app: 0.2.23-0 -> 0.2.24-0
 * ros-indigo-qt-gui-core: 0.2.23-0 -> 0.2.24-0
 * ros-indigo-qt-gui-cpp: 0.2.23-0 -> 0.2.24-0
 * ros-indigo-qt-gui-py-common: 0.2.23-0 -> 0.2.24-0
 * ros-indigo-razer-hydra: 0.0.13-1 -> 0.0.13-2
 * ros-indigo-realtime-tools: 1.9.0-0 -> 1.9.0-1
 * ros-indigo-robot-localization: 2.1.2-0 -> 2.1.2-1
 * ros-indigo-ros: 1.11.1-0 -> 1.11.1-1
 * ros-indigo-ros-comm: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-ros-control: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-ros-ethercat: 0.1.6-1 -> 0.1.7-0
 * ros-indigo-ros-ethercat-eml: 0.1.6-1 -> 0.1.7-0
 * ros-indigo-ros-ethercat-hardware: 0.1.6-1 -> 0.1.7-0
 * ros-indigo-ros-ethercat-loop: 0.1.6-1 -> 0.1.7-0
 * ros-indigo-ros-ethercat-model: 0.1.6-1 -> 0.1.7-0
 * ros-indigo-ros-tutorials: 0.5.1-0 -> 0.5.1-1
 * ros-indigo-rosapi: 0.5.5-1 -> 0.6.0-0
 * ros-indigo-rosbag: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rosbag-storage: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rosbash: 1.11.1-0 -> 1.11.1-1
 * ros-indigo-rosboost-cfg: 1.11.1-0 -> 1.11.1-1
 * ros-indigo-rosbridge-library: 0.5.5-1 -> 0.6.0-0
 * ros-indigo-rosbridge-server: 0.5.5-1 -> 0.6.0-0
 * ros-indigo-rosbridge-suite: 0.5.5-1 -> 0.6.0-0
 * ros-indigo-rosbuild: 1.11.1-0 -> 1.11.1-1
 * ros-indigo-rosclean: 1.11.1-0 -> 1.11.1-1
 * ros-indigo-rosconsole: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-roscpp: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-roscpp-core: 0.5.0-0 -> 0.5.0-1
 * ros-indigo-roscpp-serialization: 0.5.0-0 -> 0.5.0-1
 * ros-indigo-roscpp-traits: 0.5.0-0 -> 0.5.0-1
 * ros-indigo-roscpp-tutorials: 0.5.1-0 -> 0.5.1-1
 * ros-indigo-roscreate: 1.11.1-0 -> 1.11.1-1
 * ros-indigo-rosgraph: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-roslang: 1.11.1-0 -> 1.11.1-1
 * ros-indigo-roslaunch: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-roslib: 1.11.1-0 -> 1.11.1-1
 * ros-indigo-roslz4: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rosmake: 1.11.1-0 -> 1.11.1-1
 * ros-indigo-rosmaster: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rosmsg: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rosnode: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rosout: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rospack: 2.2.3-0 -> 2.2.3-1
 * ros-indigo-rosparam: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rospy: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rospy-tutorials: 0.5.1-0 -> 0.5.1-1
 * ros-indigo-rosservice: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rostest: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rostime: 0.5.0-0 -> 0.5.0-1
 * ros-indigo-rostopic: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rosunit: 1.11.1-0 -> 1.11.1-1
 * ros-indigo-roswtf: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rqt: 0.2.14-0 -> 0.2.14-1
 * ros-indigo-rqt-action: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-bag: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-bag-plugins: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-capabilities: 0.1.1-0 -> 0.1.2-0
 * ros-indigo-rqt-common-plugins: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-console: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-controller-manager: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-rqt-dep: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-graph: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-gui: 0.2.14-0 -> 0.2.14-1
 * ros-indigo-rqt-gui-cpp: 0.2.14-0 -> 0.2.14-1
 * ros-indigo-rqt-gui-py: 0.2.14-0 -> 0.2.14-1
 * ros-indigo-rqt-image-view: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-launch: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-logger-level: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-moveit: 0.3.4-0 -> 0.3.4-1
 * ros-indigo-rqt-msg: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-nav-view: 0.3.4-0 -> 0.3.4-1
 * ros-indigo-rqt-plot: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-pose-view: 0.3.4-0 -> 0.3.4-1
 * ros-indigo-rqt-publisher: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-py-common: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-py-console: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-reconfigure: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-robot-dashboard: 0.3.4-0 -> 0.3.4-1
 * ros-indigo-rqt-robot-monitor: 0.3.4-0 -> 0.3.4-1
 * ros-indigo-rqt-robot-plugins: 0.3.4-0 -> 0.3.4-1
 * ros-indigo-rqt-robot-steering: 0.3.4-0 -> 0.3.4-1
 * ros-indigo-rqt-runtime-monitor: 0.3.4-0 -> 0.3.4-1
 * ros-indigo-rqt-rviz: 0.3.4-0 -> 0.3.4-1
 * ros-indigo-rqt-service-caller: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-shell: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-srv: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-tf-tree: 0.3.4-0 -> 0.3.4-1
 * ros-indigo-rqt-top: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-topic: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-web: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rviz-fixed-view-controller: 0.0.2-0 -> 0.0.2-1
 * ros-indigo-sensor-msgs: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-shape-msgs: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-smclib: 1.7.14-0 -> 1.7.14-1
 * ros-indigo-sr-ronex: 0.9.11-0 -> 0.9.13-0
 * ros-indigo-sr-ronex-controllers: 0.9.11-0 -> 0.9.13-0
 * ros-indigo-sr-ronex-drivers: 0.9.11-0 -> 0.9.13-0
 * ros-indigo-sr-ronex-examples: 0.9.11-0 -> 0.9.13-0
 * ros-indigo-sr-ronex-external-protocol: 0.9.11-0 -> 0.9.13-0
 * ros-indigo-sr-ronex-hardware-interface: 0.9.11-0 -> 0.9.13-0
 * ros-indigo-sr-ronex-launch: 0.9.11-0 -> 0.9.13-0
 * ros-indigo-sr-ronex-msgs: 0.9.11-0 -> 0.9.13-0
 * ros-indigo-sr-ronex-test: 0.9.11-0 -> 0.9.13-0
 * ros-indigo-sr-ronex-transmissions: 0.9.11-0 -> 0.9.13-0
 * ros-indigo-sr-ronex-utilities: 0.9.11-0 -> 0.9.13-0
 * ros-indigo-std-msgs: 0.5.9-0 -> 0.5.9-1
 * ros-indigo-stereo-msgs: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-tf: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-tf-conversions: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-topic-tools: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-trajectory-msgs: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-transmission-interface: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-turtlesim: 0.5.1-0 -> 0.5.1-1
 * ros-indigo-velocity-controllers: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-vision-opencv: 1.11.2-0 -> 1.11.2-1
 * ros-indigo-vision-visp: 0.7.3-0 -> 0.7.3-1
 * ros-indigo-visp: 2.9.0-10 -> 2.9.0-11
 * ros-indigo-visp-auto-tracker: 0.7.3-0 -> 0.7.3-1
 * ros-indigo-visp-bridge: 0.7.3-0 -> 0.7.3-1
 * ros-indigo-visp-camera-calibration: 0.7.3-0 -> 0.7.3-1
 * ros-indigo-visp-hand2eye-calibration: 0.7.3-0 -> 0.7.3-1
 * ros-indigo-visp-tracker: 0.7.3-0 -> 0.7.3-1
 * ros-indigo-visualization-msgs: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-xmlrpcpp: 1.11.2-0 -> 1.11.3-0

Removed Packages [0]:

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:
 * Aaron Blasdel
 * Adam Leeper
 * Adolfo Rodriguez Tsouroukdissian
 * Armin Hornung
 * Ben Charrow
 * Bence Magyar
 * Brandon Alexander
 * Dan Lazewatsky
 * David Lu!!
 * David V. Lu!!
 * Dirk Thomas
 * Dorian Scholz
 * Eric Perko
 * Esteve Fernandez
 * Fabien Spindler
 * Ioan Sucan
 * Isaac Isao Saito
 * Isaac Saito
 * Jack O'Quin
 * John Hsu
 * Julius Kammerl
 * Kelsey Hawkins
 * Manos Nikolaidis
 * Michael Ferguson
 * Mirza A. Shah
 * Ruben Smits
 * Sachin Chitta
 * Scott K Logan
 * Severin Lemaignan
 * Shadow Robot's software team
 * Stuart Glaser
 * Tom Moore
 * Tully Foote
 * Vijay Pradeep
 * Vincent Rabaud
 * William Woodall
 * Willow Garage
 * Wim Meeussen
 * Ze'ev Klapow

Updates to indigo (2 of 3)

Added Packages [0]:

Updated Packages [52]:
 * ros-indigo-catkin: 0.6.4-1 -> 0.6.5-0
 * ros-indigo-concert-msgs: 0.7.5-2 -> 0.7.5-3
 * ros-indigo-concert-service-msgs: 0.7.5-2 -> 0.7.5-3
 * ros-indigo-ecl: 0.60.0-0 -> 0.60.0-1
 * ros-indigo-ecl-build: 0.60.1-0 -> 0.60.1-1
 * ros-indigo-ecl-command-line: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-concepts: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-config: 0.60.1-0 -> 0.60.1-2
 * ros-indigo-ecl-containers: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-converters: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-converters-lite: 0.60.1-0 -> 0.60.1-2
 * ros-indigo-ecl-core: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-core-apps: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-devices: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-eigen: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-errors: 0.60.1-0 -> 0.60.1-2
 * ros-indigo-ecl-exceptions: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-formatters: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-geometry: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-io: 0.60.1-0 -> 0.60.1-2
 * ros-indigo-ecl-ipc: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-license: 0.60.1-0 -> 0.60.1-1
 * ros-indigo-ecl-linear-algebra: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-lite: 0.60.1-0 -> 0.60.1-2
 * ros-indigo-ecl-manipulation: 0.60.0-0 -> 0.60.0-1
 * ros-indigo-ecl-manipulators: 0.60.0-0 -> 0.60.0-1
 * ros-indigo-ecl-math: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-mobile-robot: 0.60.0-0 -> 0.60.0-1
 * ros-indigo-ecl-mpl: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-navigation: 0.60.0-0 -> 0.60.0-1
 * ros-indigo-ecl-sigslots: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-sigslots-lite: 0.60.1-0 -> 0.60.1-2
 * ros-indigo-ecl-statistics: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-streams: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-threads: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-time: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-time-lite: 0.60.1-0 -> 0.60.1-2
 * ros-indigo-ecl-tools: 0.60.1-0 -> 0.60.1-1
 * ros-indigo-ecl-type-traits: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-utilities: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-gateway-msgs: 0.7.5-2 -> 0.7.5-3
 * ros-indigo-rocon-app-manager-msgs: 0.7.5-2 -> 0.7.5-3
 * ros-indigo-rocon-device-msgs: 0.7.5-2 -> 0.7.5-3
 * ros-indigo-rocon-interaction-msgs: 0.7.5-2 -> 0.7.5-3
 * ros-indigo-rocon-msgs: 0.7.5-2 -> 0.7.5-3
 * ros-indigo-rocon-service-pair-msgs: 0.7.5-2 -> 0.7.5-3
 * ros-indigo-rocon-std-msgs: 0.7.5-2 -> 0.7.5-3
 * ros-indigo-rocon-tutorial-msgs: 0.7.5-2 -> 0.7.5-3
 * ros-indigo-scheduler-msgs: 0.7.5-2 -> 0.7.5-3
 * ros-indigo-zeroconf-avahi: 0.2.3-0 -> 0.2.3-1
 * ros-indigo-zeroconf-avahi-demos: 0.2.3-0 -> 0.2.3-1
 * ros-indigo-zeroconf-avahi-suite: 0.2.3-0 -> 0.2.3-1

Removed Packages [0]:

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:
 * Daniel Stonier
 * Dirk Thomas
 * Dongwook Lee

Updates to indigo (3 of 3)

Added Packages [0]:

Updated Packages [28]:
 * ros-indigo-moveit-python: 0.2.2-0 -> 0.2.3-0
 * ros-indigo-ompl: 0.14.1002831-0 -> 0.14.2002850-0
 * ros-indigo-rocon-app-manager: 0.7.0-0 -> 0.7.1-0
 * ros-indigo-rocon-app-platform: 0.7.0-0 -> 0.7.1-0
 * ros-indigo-rocon-app-utilities: 0.7.0-0 -> 0.7.1-0
 * ros-indigo-rocon-apps: 0.7.0-0 -> 0.7.1-0
 * ros-indigo-rocon-bubble-icons: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-console: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-ebnf: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-gateway: 0.7.2-0 -> 0.7.3-0
 * ros-indigo-rocon-gateway-tests: 0.7.2-0 -> 0.7.3-0
 * ros-indigo-rocon-gateway-utils: 0.7.2-0 -> 0.7.3-0
 * ros-indigo-rocon-hub: 0.7.2-0 -> 0.7.3-0
 * ros-indigo-rocon-hub-client: 0.7.2-0 -> 0.7.3-0
 * ros-indigo-rocon-icons: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-interactions: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-launch: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-master-info: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-multimaster: 0.7.2-0 -> 0.7.3-0
 * ros-indigo-rocon-python-comms: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-python-redis: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-python-utils: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-python-wifi: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-semantic-version: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-test: 0.7.2-0 -> 0.7.3-0
 * ros-indigo-rocon-tools: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-unreliable-experiments: 0.7.2-0 -> 0.7.3-0
 * ros-indigo-rocon-uri: 0.1.6-0 -> 0.1.8-0

Removed Packages [0]:

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:
 * Daniel Stonier
 * Ioan Sucan
 * Jihoon Lee
 * Michael Ferguson

Updates to hydro

Added Packages [35]:
 * ros-hydro-bayesian-belief-networks: 1.0.24-0
 * ros-hydro-data-vis-msgs: 0.0.2-0
 * ros-hydro-designator-integration-msgs: 0.0.2-0
 * ros-hydro-dna-extraction-msgs: 0.0.2-0
 * ros-hydro-grasp-stability-msgs: 0.0.2-0
 * ros-hydro-iai-common-msgs: 0.0.2-0
 * ros-hydro-iai-content-msgs: 0.0.2-0
 * ros-hydro-iai-kinematics-msgs: 0.0.2-0
 * ros-hydro-iai-pancake-perception-action: 0.0.2-0
 * ros-hydro-interaction-cursor-3d: 0.0.3-1
 * ros-hydro-interaction-cursor-demo: 0.0.3-1
 * ros-hydro-interaction-cursor-msgs: 0.0.3-1
 * ros-hydro-interaction-cursor-rviz: 0.0.3-1
 * ros-hydro-jsk-interactive-marker: 1.0.3-0
 * ros-hydro-jsk-rqt-plugins: 1.0.3-0
 * ros-hydro-jsk-rviz-plugins: 1.0.3-0
 * ros-hydro-ml-classifiers: 0.3.0-1
 * ros-hydro-mln-robosherlock-msgs: 0.0.2-0
 * ros-hydro-moveit-python: 0.2.2-0
 * ros-hydro-nav2d-exploration: 0.1.1-0
 * ros-hydro-nav2d-localizer: 0.1.1-0
 * ros-hydro-nav2d-msgs: 0.1.1-0
 * ros-hydro-nav2d-navigator: 0.1.1-0
 * ros-hydro-nav2d-operator: 0.1.1-0
 * ros-hydro-nav2d-remote: 0.1.1-0
 * ros-hydro-ros-ethercat: 0.1.7-0
 * ros-hydro-ros-ethercat-eml: 0.1.7-0
 * ros-hydro-ros-ethercat-loop: 0.1.7-0
 * ros-hydro-rviz-animated-view-controller: 0.1.1-0
 * ros-hydro-rviz-fixed-view-controller: 0.0.2-1
 * ros-hydro-saphari-msgs: 0.0.2-0
 * ros-hydro-scanning-table-msgs: 0.0.2-0
 * ros-hydro-sherlock-sim-msgs: 0.0.2-0
 * ros-hydro-sklearn: 1.0.24-0
 * ros-hydro-view-controller-msgs: 0.1.2-0

Updated Packages [232]:
 * ros-hydro-amcl: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-assimp-devel: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-base-local-planner: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-bride: 0.3.1-1 -> 0.3.2-1
 * ros-hydro-bride-compilers: 0.3.1-1 -> 0.3.2-1
 * ros-hydro-bride-plugin-source: 0.3.1-1 -> 0.3.2-1
 * ros-hydro-bride-templates: 0.3.1-1 -> 0.3.2-1
 * ros-hydro-bride-tutorials: 0.3.1-1 -> 0.3.2-1
 * ros-hydro-bwi-desktop: 0.2.0-0 -> 0.2.1-0
 * ros-hydro-bwi-desktop-full: 0.2.0-0 -> 0.2.1-0
 * ros-hydro-bwi-launch: 0.2.0-0 -> 0.2.1-0
 * ros-hydro-camera-calibration-parsers: 1.11.1-0 -> 1.11.3-1
 * ros-hydro-camera-info-manager: 1.11.1-0 -> 1.11.3-1
 * ros-hydro-camera-info-manager-py: 0.2.2-0 -> 0.2.3-0
 * ros-hydro-camera1394: 1.9.5-0 -> 1.9.5-1
 * ros-hydro-carrot-planner: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-clear-costmap-recovery: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-collada-urdf-jsk-patch: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-control-msgs: 1.2.0-0 -> 1.2.0-1
 * ros-hydro-control-toolbox: 1.10.4-1 -> 1.10.4-2
 * ros-hydro-controller-interface: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-controller-manager: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-controller-manager-msgs: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-controller-manager-tests: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-costmap-2d: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-create-dashboard: 2.2.2-0 -> 2.2.2-1
 * ros-hydro-create-description: 2.2.0-0 -> 2.2.0-1
 * ros-hydro-create-driver: 2.2.0-0 -> 2.2.0-1
 * ros-hydro-create-gazebo-plugins: 2.2.2-0 -> 2.2.2-1
 * ros-hydro-create-node: 2.2.0-0 -> 2.2.0-1
 * ros-hydro-cv-bridge: 1.10.17-0 -> 1.10.17-1
 * ros-hydro-depth-image-proc-jsk-patch: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-diff-drive-controller: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-downward: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-dwa-local-planner: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-dynamic-tf-publisher: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-effort-controllers: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-euslisp: 1.1.17-3 -> 1.1.18-0
 * ros-hydro-fake-localization: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-fanuc: 0.2.0-0 -> 0.2.0-1
 * ros-hydro-fanuc-assets: 0.2.0-0 -> 0.2.0-1
 * ros-hydro-fanuc-driver: 0.2.0-0 -> 0.2.0-1
 * ros-hydro-fanuc-m10ia-support: 0.2.0-0 -> 0.2.0-1
 * ros-hydro-fanuc-m16ib-support: 0.2.0-0 -> 0.2.0-1
 * ros-hydro-fanuc-m430ia-support: 0.2.0-0 -> 0.2.0-1
 * ros-hydro-fanuc-resources: 0.2.0-0 -> 0.2.0-1
 * ros-hydro-ff: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-ffha: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-force-torque-sensor-controller: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-forward-command-controller: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-freenect-camera: 0.3.2-0 -> 0.3.2-1
 * ros-hydro-freenect-launch: 0.3.2-0 -> 0.3.2-1
 * ros-hydro-freenect-stack: 0.3.2-0 -> 0.3.2-1
 * ros-hydro-geneus: 1.1.17-3 -> 1.1.18-0
 * ros-hydro-global-planner: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-gripper-action-controller: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-hardware-interface: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-hrpsys-ros-bridge: 1.0.12-0 -> 1.2.0-0
 * ros-hydro-hrpsys-tools: 1.0.12-0 -> 1.2.0-0
 * ros-hydro-humanoid-msgs: 0.3.0-0 -> 0.3.0-1
 * ros-hydro-humanoid-nav-msgs: 0.3.0-0 -> 0.3.0-1
 * ros-hydro-image-common: 1.11.1-0 -> 1.11.3-1
 * ros-hydro-image-geometry: 1.10.17-0 -> 1.10.17-1
 * ros-hydro-image-transport: 1.11.1-0 -> 1.11.3-1
 * ros-hydro-image-view-jsk-patch: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-image-view2: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-imu-sensor-controller: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-ipa-canopen: 0.5.4-0 -> 0.5.5-0
 * ros-hydro-ipa-canopen-core: 0.5.4-0 -> 0.5.5-0
 * ros-hydro-ipa-canopen-ros: 0.5.4-0 -> 0.5.5-0
 * ros-hydro-joint-limits-interface: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-joint-state-controller: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-joint-trajectory-controller: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-jsk-common: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-jsk-footstep-msgs: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-jsk-gui-msgs: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-jsk-hark-msgs: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-jsk-roseus: 1.1.17-3 -> 1.1.18-0
 * ros-hydro-jsk-tools: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-jsk-topic-tools: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-kobuki: 0.5.5-1 -> 0.5.6-0
 * ros-hydro-kobuki-auto-docking: 0.5.5-1 -> 0.5.6-0
 * ros-hydro-kobuki-bumper2pc: 0.5.5-1 -> 0.5.6-0
 * ros-hydro-kobuki-controller-tutorial: 0.5.5-1 -> 0.5.6-0
 * ros-hydro-kobuki-core: 0.5.3-0 -> 0.5.4-0
 * ros-hydro-kobuki-dashboard: 0.3.2-0 -> 0.3.2-1
 * ros-hydro-kobuki-description: 0.5.5-1 -> 0.5.6-0
 * ros-hydro-kobuki-desktop: 0.3.2-0 -> 0.3.2-1
 * ros-hydro-kobuki-dock-drive: 0.5.3-0 -> 0.5.4-0
 * ros-hydro-kobuki-driver: 0.5.3-0 -> 0.5.4-0
 * ros-hydro-kobuki-ftdi: 0.5.3-0 -> 0.5.4-0
 * ros-hydro-kobuki-gazebo: 0.3.2-0 -> 0.3.2-1
 * ros-hydro-kobuki-gazebo-plugins: 0.3.2-0 -> 0.3.2-1
 * ros-hydro-kobuki-keyop: 0.5.5-1 -> 0.5.6-0
 * ros-hydro-kobuki-msgs: 0.5.0-0 -> 0.5.0-1
 * ros-hydro-kobuki-node: 0.5.5-1 -> 0.5.6-0
 * ros-hydro-kobuki-qtestsuite: 0.3.2-0 -> 0.3.2-1
 * ros-hydro-kobuki-random-walker: 0.5.5-1 -> 0.5.6-0
 * ros-hydro-kobuki-rviz-launchers: 0.3.2-0 -> 0.3.2-1
 * ros-hydro-kobuki-safety-controller: 0.5.5-1 -> 0.5.6-0
 * ros-hydro-kobuki-testsuite: 0.5.5-1 -> 0.5.6-0
 * ros-hydro-laser-filters-jsk-patch: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-libfreenect: 0.1.2-1 -> 0.1.2-2
 * ros-hydro-libsiftfast: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-linux-hardware: 2.2.4-0 -> 2.2.5-0
 * ros-hydro-map-server: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-move-base: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-move-base-msgs: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-move-slow-and-clear: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-multi-map-server: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-nao-bringup: 0.2.3-0 -> 0.2.3-1
 * ros-hydro-nao-description: 0.2.3-0 -> 0.2.3-1
 * ros-hydro-nao-driver: 0.2.3-0 -> 0.2.3-1
 * ros-hydro-nao-msgs: 0.2.3-0 -> 0.2.3-1
 * ros-hydro-nao-pose: 0.2.3-0 -> 0.2.3-1
 * ros-hydro-nao-robot: 0.2.3-0 -> 0.2.3-1
 * ros-hydro-nav-core: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-navfn: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-navigation: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-nmea-msgs: 0.1.0-0 -> 0.1.0-1
 * ros-hydro-object-recognition-core: 0.6.1-0 -> 0.6.2-0
 * ros-hydro-octomap: 1.6.4-0 -> 1.6.5-0
 * ros-hydro-octomap-msgs: 0.3.1-1 -> 0.3.1-2
 * ros-hydro-octomap-ros: 0.3.1-0 -> 0.3.1-1
 * ros-hydro-octomap-rviz-plugins: 0.0.5-1 -> 0.0.5-3
 * ros-hydro-octovis: 1.6.4-0 -> 1.6.5-0
 * ros-hydro-openni-tracker-jsk-patch: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-openni2-camera: 0.1.2-0 -> 0.1.3-0
 * ros-hydro-openni2-launch: 0.1.3-0 -> 0.1.4-0
 * ros-hydro-openrtm-ros-bridge: 1.0.12-0 -> 1.2.0-0
 * ros-hydro-openrtm-tools: 1.0.12-0 -> 1.2.0-0
 * ros-hydro-opt-camera: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-pano-core: 2.2.5-0 -> 2.2.5-1
 * ros-hydro-pano-py: 2.2.5-0 -> 2.2.5-1
 * ros-hydro-pano-ros: 2.2.5-0 -> 2.2.5-1
 * ros-hydro-polled-camera: 1.11.1-0 -> 1.11.3-1
 * ros-hydro-posedetection-msgs: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-position-controllers: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-pr2-groovy-patches: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-razer-hydra: 0.0.12-0 -> 0.0.12-2
 * ros-hydro-realtime-tools: 1.8.3-0 -> 1.8.3-1
 * ros-hydro-robot-localization: 1.1.2-0 -> 1.1.2-1
 * ros-hydro-robot-pose-ekf: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-ros-control: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-ros-controllers: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-ros-ethercat-hardware: 0.1.2-0 -> 0.1.7-0
 * ros-hydro-ros-ethercat-model: 0.1.3-0 -> 0.1.7-0
 * ros-hydro-rosapi: 0.5.5-1 -> 0.6.0-0
 * ros-hydro-rosbridge-library: 0.5.5-1 -> 0.6.0-0
 * ros-hydro-rosbridge-server: 0.5.5-1 -> 0.6.0-0
 * ros-hydro-rosbridge-suite: 0.5.5-1 -> 0.6.0-0
 * ros-hydro-roseus: 1.1.17-3 -> 1.1.18-0
 * ros-hydro-roseus-msgs: 1.1.17-3 -> 1.1.18-0
 * ros-hydro-roseus-smach: 1.1.17-3 -> 1.1.18-0
 * ros-hydro-rosnode-rtc: 1.0.12-0 -> 1.2.0-0
 * ros-hydro-rospatlite: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-rosping: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-rotate-recovery: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-rqt-capabilities: 0.1.1-0 -> 0.1.2-0
 * ros-hydro-rqt-controller-manager: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-rtmbuild: 1.0.12-0 -> 1.2.0-0
 * ros-hydro-rtmros-common: 1.0.12-0 -> 1.2.0-0
 * ros-hydro-sr-ronex: 0.9.6-0 -> 0.9.12-0
 * ros-hydro-sr-ronex-controllers: 0.9.6-0 -> 0.9.12-0
 * ros-hydro-sr-ronex-drivers: 0.9.6-0 -> 0.9.12-0
 * ros-hydro-sr-ronex-examples: 0.9.6-0 -> 0.9.12-0
 * ros-hydro-sr-ronex-external-protocol: 0.9.6-0 -> 0.9.12-0
 * ros-hydro-sr-ronex-hardware-interface: 0.9.6-0 -> 0.9.12-0
 * ros-hydro-sr-ronex-launch: 0.9.6-0 -> 0.9.12-0
 * ros-hydro-sr-ronex-msgs: 0.9.6-0 -> 0.9.12-0
 * ros-hydro-sr-ronex-test: 0.9.6-0 -> 0.9.12-0
 * ros-hydro-sr-ronex-transmissions: 0.9.6-0 -> 0.9.12-0
 * ros-hydro-sr-ronex-utilities: 0.9.6-0 -> 0.9.12-0
 * ros-hydro-stereo-synchronizer: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-transmission-interface: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-turtlebot: 2.2.4-0 -> 2.2.5-0
 * ros-hydro-turtlebot-actions: 2.2.5-0 -> 2.2.5-1
 * ros-hydro-turtlebot-apps: 2.2.5-0 -> 2.2.5-1
 * ros-hydro-turtlebot-bringup: 2.2.4-0 -> 2.2.5-0
 * ros-hydro-turtlebot-calibration: 2.2.5-0 -> 2.2.5-1
 * ros-hydro-turtlebot-core-apps: 2.2.5-0 -> 2.2.5-1
 * ros-hydro-turtlebot-create: 2.2.0-0 -> 2.2.0-1
 * ros-hydro-turtlebot-create-desktop: 2.2.2-0 -> 2.2.2-1
 * ros-hydro-turtlebot-dashboard: 2.2.3-0 -> 2.2.3-1
 * ros-hydro-turtlebot-description: 2.2.4-0 -> 2.2.5-0
 * ros-hydro-turtlebot-follower: 2.2.5-0 -> 2.2.5-1
 * ros-hydro-turtlebot-gazebo: 2.1.1-0 -> 2.1.1-1
 * ros-hydro-turtlebot-interactive-markers: 2.2.3-0 -> 2.2.3-1
 * ros-hydro-turtlebot-msgs: 2.2.0-0 -> 2.2.0-1
 * ros-hydro-turtlebot-navigation: 2.2.5-0 -> 2.2.5-1
 * ros-hydro-turtlebot-panorama: 2.2.5-0 -> 2.2.5-1
 * ros-hydro-turtlebot-rviz-launchers: 2.2.3-0 -> 2.2.3-1
 * ros-hydro-turtlebot-simulator: 2.1.1-0 -> 2.1.1-1
 * ros-hydro-turtlebot-teleop: 2.2.5-0 -> 2.2.5-1
 * ros-hydro-turtlebot-viz: 2.2.3-0 -> 2.2.3-1
 * ros-hydro-underwater-sensor-msgs: 1.3.1-0 -> 1.3.1-1
 * ros-hydro-underwater-vehicle-dynamics: 1.3.1-0 -> 1.3.1-1
 * ros-hydro-universal-robot: 1.0.2-0 -> 1.0.2-1
 * ros-hydro-ur-bringup: 1.0.2-0 -> 1.0.2-1
 * ros-hydro-ur-description: 1.0.2-0 -> 1.0.2-1
 * ros-hydro-ur-driver: 1.0.2-0 -> 1.0.2-1
 * ros-hydro-ur-gazebo: 1.0.2-0 -> 1.0.2-1
 * ros-hydro-ur-kinematics: 1.0.2-0 -> 1.0.2-1
 * ros-hydro-ur10-moveit-config: 1.0.2-0 -> 1.0.2-1
 * ros-hydro-ur5-moveit-config: 1.0.2-0 -> 1.0.2-1
 * ros-hydro-uwsim: 1.3.1-0 -> 1.3.1-1
 * ros-hydro-uwsim-osgbullet: 3.0.1-0 -> 3.0.1-1
 * ros-hydro-uwsim-osgworks: 3.0.3-1 -> 3.0.3-2
 * ros-hydro-velocity-controllers: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-velodyne: 1.1.2-0 -> 1.1.2-1
 * ros-hydro-velodyne-driver: 1.1.2-0 -> 1.1.2-1
 * ros-hydro-velodyne-msgs: 1.1.2-0 -> 1.1.2-1
 * ros-hydro-velodyne-pointcloud: 1.1.2-0 -> 1.1.2-1
 * ros-hydro-vision-opencv: 1.10.17-0 -> 1.10.17-1
 * ros-hydro-vision-visp: 0.7.3-0 -> 0.7.3-1
 * ros-hydro-visp: 2.9.0-3 -> 2.9.0-4
 * ros-hydro-visp-auto-tracker: 0.7.3-0 -> 0.7.3-1
 * ros-hydro-visp-bridge: 0.7.3-0 -> 0.7.3-1
 * ros-hydro-visp-camera-calibration: 0.7.3-0 -> 0.7.3-1
 * ros-hydro-visp-hand2eye-calibration: 0.7.3-0 -> 0.7.3-1
 * ros-hydro-visp-tracker: 0.7.3-0 -> 0.7.3-1
 * ros-hydro-voxel-grid: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-xsens-driver: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-yocs-cmd-vel-mux: 0.5.3-0 -> 0.5.3-1
 * ros-hydro-yocs-controllers: 0.5.3-0 -> 0.5.3-1
 * ros-hydro-yocs-diff-drive-pose-controller: 0.5.3-0 -> 0.5.3-1
 * ros-hydro-yocs-math-toolkit: 0.5.3-0 -> 0.5.3-1
 * ros-hydro-yocs-msgs: 0.5.2-0 -> 0.5.2-1
 * ros-hydro-yocs-velocity-smoother: 0.5.3-0 -> 0.5.3-1
 * ros-hydro-yocs-virtual-sensor: 0.5.3-0 -> 0.5.3-1
 * ros-hydro-yocs-waypoints-navi: 0.5.3-0 -> 0.5.3-1
 * ros-hydro-yujin-ocs: 0.5.3-0 -> 0.5.3-1

Removed Packages [2]:
- ros-hydro-ardrone-autonomy
- ros-hydro-bwi

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:
 * AI Robotics
 * Adam Leeper
 * Adolfo Rodriguez Tsouroukdissian
 * Alexander Bubeck
 * Andrei Haidu
 * Armin Hornung
 * Bence Magyar
 * Brandon Alexander
 * Daniel Stonier
 * David Lu!!
 * David V. Lu!!
 * Eric Perko
 * Fabien Spindler
 * Ferenc Balint-Benczedi
 * Francis Colas
 * G.A. vd. Hoorn (TU Delft Robotics Institute)
 * Georg Bartels
 * Hiroyuki Mikita
 * Jack O'Quin
 * Jan Winkler
 * Jihoon Lee
 * Jorge Santos
 * Jorge Santos Simon
 * Julius Kammerl
 * KazutoMurase
 * Kei Okada
 * Kelsey Hawkins
 * Manos Nikolaidis
 * Marcus Liebhardt
 * Mario Prats
 * Melonee Wise
 * Michael Ferguson
 * MoveIt Setup Assistant
 * Nate Koenig
 * Ryohei Ueda
 * Sachin Chitta
 * Scott Niekum
 * Sebastian Kasperski
 * Severin Lemaignan
 * Shadow Robot's software team
 * Shaun Edwards
 * Shohei Fujii
 * Stuart Glaser
 * Takuya Nakaoka
 * Thiago de Freitas
 * Tom Moore
 * Vijay Pradeep
 * Vincent Rabaud
 * William Woodall
 * Willow Garage
 * Wim Meeussen
 * Yohei Kakiuchi
 * Younghun Ju
 * ferenc
 * ferko
 * furuta
 * jworch

Updates to groovy

Added Packages [16]:
 * ros-groovy-bayesian-belief-networks: 1.0.24-0
 * ros-groovy-designator-integration: 0.0.0-1
 * ros-groovy-dna-extraction-msgs: 0.0.2-0
 * ros-groovy-ff: 1.0.24-0
 * ros-groovy-ffha: 1.0.24-0
 * ros-groovy-jsk-interactive-marker: 1.0.3-0
 * ros-groovy-jsk-planning: 0.1.2-1
 * ros-groovy-jsk-rqt-plugins: 1.0.3-0
 * ros-groovy-jsk-rviz-plugins: 1.0.3-0
 * ros-groovy-pddl-msgs: 0.1.2-1
 * ros-groovy-pddl-planner: 0.1.2-1
 * ros-groovy-pddl-planner-viewer: 0.1.2-1
 * ros-groovy-pr2eus: 0.1.6-3
 * ros-groovy-roseus-msgs: 1.1.18-0
 * ros-groovy-sklearn: 1.0.24-0
 * ros-groovy-task-compiler: 0.1.2-1

Updated Packages [83]:
 * ros-groovy-assimp-devel: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-baxter-common: 0.7.0-0 -> 1.0.0-0
 * ros-groovy-baxter-core-msgs: 0.7.0-0 -> 1.0.0-0
 * ros-groovy-baxter-description: 0.7.0-0 -> 1.0.0-0
 * ros-groovy-baxter-examples: 0.7.0-0 -> 1.0.0-0
 * ros-groovy-baxter-interface: 0.7.0-0 -> 1.0.0-0
 * ros-groovy-baxter-maintenance-msgs: 0.7.0-0 -> 1.0.0-0
 * ros-groovy-baxter-sdk: 0.7.0-0 -> 1.0.0-0
 * ros-groovy-baxter-tools: 0.7.0-0 -> 1.0.0-0
 * ros-groovy-camera-calibration: 1.10.15-0 -> 1.10.17-0
 * ros-groovy-camera-info-manager-py: 0.2.2-0 -> 0.2.3-0
 * ros-groovy-collada-urdf-jsk-patch: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-data-vis-msgs: 0.0.0-0 -> 0.0.2-0
 * ros-groovy-depth-image-proc: 1.10.15-0 -> 1.10.17-0
 * ros-groovy-depth-image-proc-jsk-patch: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-designator-integration-msgs: 0.0.0-0 -> 0.0.2-0
 * ros-groovy-downward: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-dynamic-tf-publisher: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-euslisp: 1.1.11-2 -> 1.1.18-0
 * ros-groovy-geneus: 1.1.11-2 -> 1.1.18-0
 * ros-groovy-grasp-stability-msgs: 0.0.0-0 -> 0.0.2-0
 * ros-groovy-hrpsys: 315.1.9-2 -> 315.2.1-2
 * ros-groovy-hrpsys-ros-bridge: 1.0.11-0 -> 1.2.0-2
 * ros-groovy-hrpsys-tools: 1.0.11-0 -> 1.2.0-2
 * ros-groovy-humanoid-msgs: 0.3.0-0 -> 0.3.0-1
 * ros-groovy-humanoid-nav-msgs: 0.3.0-0 -> 0.3.0-1
 * ros-groovy-iai-common-msgs: 0.0.0-0 -> 0.0.2-0
 * ros-groovy-iai-content-msgs: 0.0.0-0 -> 0.0.2-0
 * ros-groovy-iai-kinematics-msgs: 0.0.0-0 -> 0.0.2-0
 * ros-groovy-iai-pancake-perception-action: 0.0.0-0 -> 0.0.2-0
 * ros-groovy-image-pipeline: 1.10.15-0 -> 1.10.17-0
 * ros-groovy-image-proc: 1.10.15-0 -> 1.10.17-0
 * ros-groovy-image-rotate: 1.10.15-0 -> 1.10.17-0
 * ros-groovy-image-view: 1.10.15-0 -> 1.10.17-0
 * ros-groovy-image-view-jsk-patch: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-image-view2: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-jsk-footstep-msgs: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-jsk-gui-msgs: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-jsk-hark-msgs: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-jsk-pr2eus: 0.1.5-0 -> 0.1.6-3
 * ros-groovy-jsk-roseus: 1.1.11-2 -> 1.1.18-0
 * ros-groovy-jsk-tools: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-jsk-topic-tools: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-laser-filters-jsk-patch: 1.0.18-0 -> 1.0.21-2
 * ros-groovy-libsiftfast: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-mln-robosherlock-msgs: 0.0.0-0 -> 0.0.2-0
 * ros-groovy-multi-map-server: 1.0.18-0 -> 1.0.21-2
 * ros-groovy-nao-bringup: 0.2.3-0 -> 0.2.3-1
 * ros-groovy-nao-description: 0.2.3-0 -> 0.2.3-1
 * ros-groovy-nao-driver: 0.2.3-0 -> 0.2.3-1
 * ros-groovy-nao-msgs: 0.2.3-0 -> 0.2.3-1
 * ros-groovy-nao-pose: 0.2.3-0 -> 0.2.3-1
 * ros-groovy-nao-robot: 0.2.3-0 -> 0.2.3-1
 * ros-groovy-object-recognition-core: 0.6.1-0 -> 0.6.2-0
 * ros-groovy-object-recognition-msgs: 0.4.0-0 -> 0.4.1-0
 * ros-groovy-octomap: 1.5.7-0 -> 1.5.7-1
 * ros-groovy-octomap-ros: 0.2.6-0 -> 0.2.6-1
 * ros-groovy-octomap-rviz-plugins: 0.0.4-0 -> 0.0.4-1
 * ros-groovy-octovis: 1.5.7-0 -> 1.5.7-1
 * ros-groovy-openni-tracker-jsk-patch: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-openrtm-ros-bridge: 1.0.11-0 -> 1.2.0-2
 * ros-groovy-openrtm-tools: 1.0.11-0 -> 1.2.0-2
 * ros-groovy-opt-camera: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-posedetection-msgs: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-pr2-groovy-patches: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-robot-localization: 0.1.0-0 -> 0.1.2-0
 * ros-groovy-rosapi: 0.5.4-0 -> 0.5.6-1
 * ros-groovy-rosbridge-library: 0.5.4-0 -> 0.5.6-1
 * ros-groovy-rosbridge-server: 0.5.4-0 -> 0.5.6-1
 * ros-groovy-rosbridge-suite: 0.5.4-0 -> 0.5.6-1
 * ros-groovy-roseus: 1.1.11-2 -> 1.1.18-0
 * ros-groovy-roseus-smach: 1.1.11-2 -> 1.1.18-0
 * ros-groovy-rosnode-rtc: 1.0.11-0 -> 1.2.0-2
 * ros-groovy-rospatlite: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-rosping: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-rqt-capabilities: 0.1.0-0 -> 0.1.2-3
 * ros-groovy-rtmbuild: 1.0.11-0 -> 1.2.0-2
 * ros-groovy-rtmros-common: 1.0.11-0 -> 1.2.0-2
 * ros-groovy-saphari-msgs: 0.0.0-0 -> 0.0.2-0
 * ros-groovy-scanning-table-msgs: 0.0.0-0 -> 0.0.2-0
 * ros-groovy-sherlock-sim-msgs: 0.0.0-0 -> 0.0.2-0
 * ros-groovy-stereo-image-proc: 1.10.15-0 -> 1.10.17-0
 * ros-groovy-stereo-synchronizer: 1.0.18-0 -> 1.0.24-0

Removed Packages [1]:
- ros-groovy-jsk-common

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:
 * AI Robotics
 * Andrei Haidu
 * Armin Hornung
 * Brandon Alexander
 * Ferenc Balint-Benczedi
 * Georg Bartels
 * Hiroyuki Mikita
 * Jack O'Quin
 * Jan Winkler
 * Julius Kammerl
 * KazutoMurase
 * Kei Okada
 * Rethink Robotics Inc.
 * Ryohei Ueda
 * Severin Lemaignan
 * Shohei Fujii
 * Takuya Nakaoka
 * Tom Moore
 * Vincent Rabaud
 * William Woodall
 * Yohei Kakiuchi
 * ferenc
 * ferko
 * furuta
 * jworch
 * winkler

Bloom 0.5.0 Released

| No Comments | No TrackBacks
Just in time before lots of people start releasing into Indigo, I am happy to announce bloom 0.5.0!

Here are some of the highest level changes to bloom:

- OAUTH is now used to open pull requests with, hopefully cutting down on the number of times you have to enter your password.
- Some additional checks have been added to prevent invalid pull requests from being opened.
- bloom also asks you to add doc and source information for your repository in addition to setting a maintenance status.
- Fedora rpm generation (they are not generated by default yet). Thanks to Scott K Logan and others for getting this into bloom.

There are a few more changes, but you can read the whole changelog here:

If you run into any bugs, please open issues on the issue tracker here:

rosc alpha released

| No Comments | No TrackBacks

From Nikolai Ensslen via ros-users@

Hi all,


in December we released "Subscribing Submarine" an alpha version of rosc, that was announced at last year's ROSCon. For some reason we forgot to mention this here and invite you to review and play around with it. - Hereby I'm catching up on this, and of course also encourage you to join the further development!


rosc is a dependency-free ROS client implementation in ANSI C which aims to support small embedded systems as well as any operating system. Its long-term goal is to become a hardened, efficient and highly portable implementation of the ROS middleware (including future evolutions of it), making it a good choice for use in industrial applications or product development.


Essential features:

  • XMLRPC communication
    • HTTP/XML parser
    • XMLRPC message generator
  • Port interface handling (services, topics, XMLRPC)
  • ROS message (msg-File) header/source generation
  • TCPROS (un-)marshalling

Planned future extensions:

  • Transport layer independency
  • Realtime capability
  • Development debugging features
  • Compiler optimization packages
    • special size optimizations
    • using special pragmas (like pack)
  • Multimaster/masterless concept

You can try out the alpha under Linux now. The code is beyond experimental, but not yet mature enough for critical setups.  


In ROS Wiki, see

Find the code at



Have fun,


RosJava & Android on Hydro

| No Comments | No TrackBacks
From Daniel Stonier via ros-users@

Hi all,

A quick javaland update. I know quite a few people have already dived in early with rosjava on hydro even though it hasn't actually bleeped on the ros news radar yet. 

This is finally that bleep to say that we're reasonably happy (and using it ourselves fairly actively) with the current state of the rosjava/android build environment for hydro and we'll endeavour to keep it stable 'as is' (apart from bugfixes) for the remainder of the hydro release.

So what is in the box?


  • Partially Catkinized - each gradle super project is a catkin package
    • You can now do entire workspace builds and CI with one command
  • Ros Gradle Plugins: take alot of the repitition out of the build.gradle files
  • Debs - you no longer need to build every stack to build your own sources
  • A Maven Repo - you don't even need ros to access/build with the rosjava jars, just point to our maven repo on github.
  • Messages - each package now compiles into its own jar (no superblob)

  • Android Studio/Gradle - uses the new adt build environment from google
    • IDE/Command Line/CI are now all compatible
  • AAR's : takes advantage of the new .aar's for android libraries
  • Partially Catkinized : can do entire workspace builds on these too.
    • with .aar's we can really scale up now
  • A Maven Repo : just point to this instead of having to build everything
    • don't need to build any sources to build your single application anymore!
Places to look for documentation are at:

And join us on the rosjava sig google group for feedback/questions/news!


PS A big thank you to Damon Kohler for assisting us in getting rosjava in better shape for hydro and also to the users who endured alot of rapid changes and gave great feedback early in the upgrade.

PPS What's coming for igloo? Expect a true rosjava message generator...somewhat awkwardly compiling rosjava messages is very quickly reaching an annoying threshold of unbearably biblical proportions!

The Mathworks has released a ROS Support package for Matlab. You can create ROS nodes directly in Matlab. As well as run a ROS Master from within Matlab. 

For more information see

Bloom 0.4.5 Released

| No Comments | No TrackBacks
From WIlliam Woodall on ros-users@

I just released a bug fix version of bloom, 0.4.5.

There are note worthy changes in this version:

- Added checks for rosdistro version to help with the REP-0141 rollout
- Python2/3 bilingual support, so bloom should be installable and usable with Python3

Expect another patch release soon (0.4.6) to support REP-0141, and then a new minor release soon after that with some improvements and features (0.5.0).

Also the documentation is now on


Announcing ROS Hydromedusa Beta Release

| No Comments | No TrackBacks
We are pleased to announce that ROS Hydromedusa Beta 1 is now available for download. 

ROS Hydro will be the transition distribution from the old 6 month cycle to the new 12 month cycle as discussed previously on ros-users@. 

Hyrdro marks the first widespread deployment of packages built on using the new catkin infrastructure.  So far over 500 packages are released and building in Hydro using catkin. 

What's in ROS Hydro

There have been many packages upgraded.  The Hydro release includes updates to core libraries including Gazebo 1.9, PCL 1.7, and tf2.  For packages with major updates there is a migration guide available at:

(Package maintainers please update the migration guide with any major changes from your packages.)

For the status of the builds in Hydro you can visit: http:// 

REP Updates

The release of Hydro has been facilitated by the centeralization of releases on the rosdistro repository on GitHub, .This repository tracks all the releases and viewing it's history you can see the many contributors to ROS from around the world.  This repository has over 100 committers with well over 1000 pull requests serviced in under a year of operation.  

Part of what has helped make the rosdistro repository effective has been that its operation is now standardized in REP 137
During the Hydro development cycle many REPs have been updated.  To see all REPs visit

A quick summary of updates to REPs is here: 
REP 100, 109, 122 have been updated for clarification 
REP 106 polled topics, has been withdrawn
REP 127 package.xml format has been accepted
REP 131 Groovy Variants has been made active
REP 132 Changelogs in packages has been accepted
REP 133 Seperation of build and source trees has been made active
REP 134 catkin_make_isolated has been made active
REP 135 Driver namespace practices has been made active
REP 136 Releasing 3rdparty packages has been made active
REP 137 ROS distribuition files has been accepted
REP 138 LaserScan standards has been made active
REP 140 package.xml format 2 is under development

Part of the process of releasing ROS which we are now formalizing is the concept of package maintainers which is distinct from package developers. These two roles are often performed by the same person, but it not necessary especially as packages become more mature.  For a summary of the responsibilities of a package maintainer see the Maintenance Guide on the wiki at:

Going forward we will be setting up a forum where maintainers can volunteer to maintain packages and the community can request maintainers for packages.  When this happens please consider volunteering to do so.  Right now there are a few people in the community who maintain a lot of packages.  By distributing this work across the community we can increase the sustainable size of our maintained system.  

Indigo Igloo

The next release of ROS has been chosen to be Indigo Igloo. The planning page for Indigo has been posted at: based on the new release schedule it will be the beginning of our new 12 month release cycle and will be syncronized with the Ubuntu LTS support 14.04.  

The upcoming release of Hydromedusa, along with the beginning of the development cycle for Indigo, will mark the End of LIfe for ROS Fuerte.  After the Hydro release the Fuerte buildfarm infrastructure will be torn down and no new releases will be made.  This follows our pattern of having two supported distributions plus one distribution under development at all times.  We will, however, continue to host the existing documentation and debian packages for ROS Fuerte.  

Hydromedusa Tshirt
As is tradition for ROS releases we have a great new logo from Josh Elingson.  For this release we are going to make t-shirts available to everyone. The proceeds from the t-shirt sales will cover the cost of the art work, and any additional funds will be used to cover ROS infrastructure costs and support future ROS maintainance. Look for an email early next week to see the new logo and order your own ROS Hydromedusa Tshirt.

Updated Packages

We have more than 100 new or updated packages.  see the full list below:
    Packages Added: 
ros-hydro-clearpath-base : 0.3.1
ros-hydro-desktop-full : 1.0.0
ros-hydro-force-torque-sensor-controller : 0.5.1
ros-hydro-imu-sensor-controller : 0.5.1
ros-hydro-joint-limits-interface : 0.5.1
ros-hydro-rocon : 0.5.3
ros-hydro-rosauth : 0.1.3
ros-hydro-simulators : 1.0.0
ros-hydro-turtlebot-apps : 2.1.0
ros-hydro-turtlebot-core-apps : 2.1.0
ros-hydro-turtlebot-panorama : 2.1.0

Packages Removed: 
ros-hydro-controllers-msgs : 0.4.0
ros-hydro-ros-control : 0.4.0
ros-hydro-test-roscpp : 1.9.47

Packages Updated: 
ros-hydro-actionlib-tutorials : 0.1.6 -> 0.1.7
ros-hydro-amcl : 1.11.1 -> 1.11.3
ros-hydro-base-local-planner : 1.11.1 -> 1.11.3
ros-hydro-carrot-planner : 1.11.1 -> 1.11.3
ros-hydro-catkin : 0.5.70 -> 0.5.71
ros-hydro-clear-costmap-recovery : 1.11.1 -> 1.11.3
ros-hydro-clearpath-bringup : 0.3.0 -> 0.3.1
ros-hydro-clearpath-common : 0.3.0 -> 0.3.1
ros-hydro-clearpath-teleop : 0.3.0 -> 0.3.1
ros-hydro-common-tutorials : 0.1.6 -> 0.1.7
ros-hydro-concert-conductor : 0.5.3 -> 0.5.4
ros-hydro-concert-orchestra : 0.5.3 -> 0.5.4
ros-hydro-controller-interface : 0.4.0 -> 0.5.1
ros-hydro-controller-manager : 0.4.0 -> 0.5.1
ros-hydro-controller-manager-msgs : 0.4.0 -> 0.5.1
ros-hydro-controller-manager-tests : 0.4.0 -> 0.5.1
ros-hydro-costmap-2d : 1.11.1 -> 1.11.3
ros-hydro-dwa-local-planner : 1.11.1 -> 1.11.3
ros-hydro-effort-controllers : 0.5.0 -> 0.5.1
ros-hydro-eigen-conversions : 1.10.4 -> 1.10.5
ros-hydro-eigen-stl-containers : 0.1.3 -> 0.1.4
ros-hydro-fake-localization : 1.11.1 -> 1.11.3
ros-hydro-forward-command-controller : 0.5.0 -> 0.5.1
ros-hydro-geometry : 1.10.4 -> 1.10.5
ros-hydro-global-planner : 1.11.1 -> 1.11.3
ros-hydro-hardware-interface : 0.4.0 -> 0.5.1
ros-hydro-interactive-marker-tutorials : 0.8.0 -> 0.8.1
ros-hydro-joint-state-controller : 0.5.0 -> 0.5.1
ros-hydro-kdl-conversions : 1.10.4 -> 1.10.5
ros-hydro-laser-filters : 1.6.10 -> 1.6.11
ros-hydro-librviz-tutorial : 0.8.0 -> 0.8.1
ros-hydro-map-server : 1.11.1 -> 1.11.3
ros-hydro-move-base : 1.11.1 -> 1.11.3
ros-hydro-move-base-msgs : 1.11.1 -> 1.11.3
ros-hydro-move-slow-and-clear : 1.11.1 -> 1.11.3
ros-hydro-nav-core : 1.11.1 -> 1.11.3
ros-hydro-navfn : 1.11.1 -> 1.11.3
ros-hydro-navigation : 1.11.1 -> 1.11.3
ros-hydro-nodelet-tutorial-math : 0.1.6 -> 0.1.7
ros-hydro-pcl-ros : 1.1.1 -> 1.1.3
ros-hydro-perception-pcl : 1.1.1 -> 1.1.3
ros-hydro-pluginlib-tutorials : 0.1.6 -> 0.1.7
ros-hydro-position-controllers : 0.5.0 -> 0.5.1
ros-hydro-redis : 0.5.3 -> 0.5.4
ros-hydro-robot-pose-ekf : 1.11.1 -> 1.11.3
ros-hydro-rocon-concert : 0.5.3 -> 0.5.4
ros-hydro-rocon-gateway : 0.5.3 -> 0.5.4
ros-hydro-rocon-gateway-tests : 0.5.3 -> 0.5.4
ros-hydro-rocon-hub : 0.5.3 -> 0.5.4
ros-hydro-rocon-hub-client : 0.5.3 -> 0.5.4
ros-hydro-rocon-multimaster : 0.5.3 -> 0.5.4
ros-hydro-rocon-test : 0.5.3 -> 0.5.4
ros-hydro-rocon-tf-reconstructor : 0.5.3 -> 0.5.4
ros-hydro-rocon-unreliable-experiments : 0.5.3 -> 0.5.4
ros-hydro-rocon-utilities : 0.5.3 -> 0.5.4
ros-hydro-ros-controllers : 0.5.0 -> 0.5.1
ros-hydro-rotate-recovery : 1.11.1 -> 1.11.3
ros-hydro-rviz-plugin-tutorials : 0.8.0 -> 0.8.1
ros-hydro-rviz-python-tutorial : 0.8.0 -> 0.8.1
ros-hydro-srdfdom : 0.2.5 -> 0.2.6
ros-hydro-tf : 1.10.4 -> 1.10.5
ros-hydro-tf-conversions : 1.10.4 -> 1.10.5
ros-hydro-turtle-actionlib : 0.1.6 -> 0.1.7
ros-hydro-velocity-controllers : 0.5.0 -> 0.5.1
ros-hydro-visualization-marker-tutorials : 0.8.0 -> 0.8.1
ros-hydro-visualization-tutorials : 0.8.0 -> 0.8.1
ros-hydro-voxel-grid : 1.11.1 -> 1.11.3

bloom 0.4.0 Released

| No Comments | No TrackBacks
From William Woodall on ros-users@

I am pleased to announce a new version of bloom!

First some things everyone using bloom needs to know:
  • Fuerte support has been dropped
  • The 'bloom' branch has been deprecated in favor of the master branch.
    • All repositories will be automatically updated to reflect this next time they are used.
    • I have updated all the tutorials/docs I can find, but please report anything that is inconsistent with this change.
Now some new features of bloom 0.4.0:
The full changelog can be seen here:

I highly recommend everyone update and give it a try next time you are releasing a package. Please report and any issues you encounter here:

Happy releasing!

Virtualized ROS Groovy Galapagos

| No Comments | No TrackBacks
From The NooTriX team on ROS Users

Dear Fellow ROS users,

Just as we did for ROS Fuerte, we built a virtual machine with ROS Groovy pre-installed. So, people can quickly experiment with it.
More on:

BTW, thanks to the ROS core team for all the energy they put in improving our favorite robotic infrastructure.

The NooTriX team

vcstools, rosinstall, wstools Patch Releases

| No Comments | No TrackBacks
There were several patch releases from the vcstools repository.  

vcstools 0.1.29 was released with patches to support newer versions of git. For the full changelog see:

rosinstall 0.1.25 was released with several minor patches. 

wstool 0.0.3 was released with a few minor patches as well. 

Thanks to Thibault Kruse for most of the updates as well as patches from Bob Teeter, Scott Logan and mmedvede.

Bloom version 0.3.0

| No Comments | No TrackBacks
The new version of bloom has some significant changes, including a slightly different command workflow. Please review the updated tutorials for information on how this workflow has changed:

This version of bloom has some usability improvements for releasing packages for multiple versions of ROS in the same release repository. Additionally, there are new features and modifications to the workflow to better support releasing third party packages into a specific ROS distribution, which is related to REP 136. See the updated third party package tutorial for more info:

One of the biggest changes is that the bloom configurations are stored in a new format. You can ensure that your bloom release repository is up-to-date by cloning it, running `git-bloom-config` in the repository, and pushing the changes made during the up conversion using `git push --all`.

For more details on what has changed in bloom 0.3 from previous versions see the change log:

Please tag any related questions on with the bloom tag and post any bugs discovered on the bloom issue tracker:

New Stack: Robotiq

| No Comments | No TrackBacks
From Nicolas Lauzier of Robotiq on ROS Users

Hi everyone,

I am pleased to announce that a ROS stack for the control of our Adaptive Robot Grippers is now available. The stack is released as part of ROS-Industrial, hosted on the SWRI repository.

The Robotiq stack provides drivers for accessing the control variables of our Grippers (TCP/IP protocol only for the moment), allowing ROS users to program high-level commands without having to handle low-level message creations and communication aspects. The objective of the stack is to reduce the integration time and help our research partners build innovative demos (such as this one).

For more information on the Robotiq stack, you can take a look at our blog article announcing the release and our website section presenting the research applications for our Adaptive Grippers. 

Please let me know if you have any question!


New Stack: RMS

| No Comments | No TrackBacks
From Russell Toris on ROS Users

Dear ROS Community:

I would like to take a moment to announce the early-release version of the Robot Management System (RMS). RMS (Robot Management System) is a remote lab management tool designed for use with controlling ROS enabled robots from the web. RMS itself refers to a web-management system written in PHP/HTML backed by a MySQL database. RMS is written in a robot-platform independent manner allowing for the control of a variety of robots. In addition to being cross-platform, RMS allows for basic user management, interface management, and content management. RMS is broken up into two separate stacks on

  • rms_www contains the web server code for the RMS and comes with a detailed installation tutorial --
  • rms contains server side (ROS-side) code such as example simulation environments. As of this email, example simulation environments are available for the Kuka youBot and PR2. In addition, example launch files are provided for the WowWee Rovio and Kuka youBot for control of physical robots. PR2 examples are soon to follow. --

Who Should Use the RMS?
RMS was designed to be an easy to use, easy to mange remote lab system for use by robotic researchers and enthusiasts. Developed in PHP/HTML with a MySQL backend, the RMS itself is not considered a light-weight system; however, by using a heavier system, tools such as user management, content management, and interface management become possible.

Does the RMS Itself Require ROS to Install?
No. The RMS was designed as a standalone system that can be easily installed on UNIX based web servers. The decision was made so that it is possible to host the RMS site itself on campus or third-party web servers without the need of maintaining and installing ROS on that server. RMS will point to ROS servers which are running rosbridge v2.0 in order to control the robot.

How Does the RMS Communicate with ROS?
The RMS uses the lastest version of ros.js to communicate with ROS servers. For the ROS server to communicate back to the RMS, a server running rosbridge v2.0 should be running.

Cool Widgets! Do I Need RMS to Use Them?
No. Most of the widgets available in the system were developed as standalone widgets as part of the rosjs effort. The RMS admin panel simply wraps these widgets and provides an easy-to-use GUI to customize them to fit your needs.

Is There More to Come?
Yes! The current released version of RMS is a very early-stage release of the system. The following are just a few of the features we hope to add soon:
  •   User scheduling for environments/interfaces
  •   2 examples and navigation widgets
  •   3D Interactive Widgets
  •   Additional, more complex, interface examples
  •   Additional tutorials
  •   Much more!

RMS is being released in its early stages in hopes of receiving feedback early in its developments to help shape the future of the system. That being said, the current release is stable and ready for use! Frequent updates will be made and documented on its wiki pages: and


Russell Toris

Announcement from Armin Hornung, Humanoid Robotics Lab, Uni Freiburg

I'm pleased to announce the release of OctoMap 1.4, along with the updated octomap_mapping ROS stack for electric (see and The updated viewer and visualization library "octovis" is available separately in the octomap_visualization stack.

The main new features since the latest stable 1.2 release are a new generalized IO functionality and file format for octrees, support for per-voxel color information in a specialized tree class (e.g. from the Kinect) and full support for Linux, Mac OS and Windows (the latter still experimental). The API remained mostly unchanged.

Ubuntu packages for ROS electric are being built and will be available in your package manager soon. Until then, you can get the octomap_mapping stack from

Your friendly neighborhood OctoMap team

OMPL 0.10 released

| No Comments | No TrackBacks

We are happy to announce a new release of OMPL, version 0.10. All OMPL users are recommended to update to the new version. It includes the following changes:

  • Windows support
  • Added a primer on sampling-based motion planning and OMPL.
  • Added an implementation of SyCLoP, a new multi-layered meta-planner that combines discrete search with a sampling-based motion planner. Implementations of Syclop with RRT and EST as the low-level planners are provided.
  • Added an implementation of EST for planning with controls.
  • New generic interface for parameter settings for almost anything that is user-configurable. This was done to simplify reading parameters from an input file (see next bullet).
  • New benchmark program that allows one to easily specify benchmark problems with simple configuration files.
  • New state spaces for Dubins vehicles and Reeds-Shepp vehicles. This allows one to use any geometric planner to compute feasible paths for such vehicles. See the demo program demo_GeometricCarPlanning.
  • Added state serialization, deserialization, state space signatures.
  • Added the notion of DirectedControlSampler.
  • Added path hybridization, a technique for combining several solutions to a motion planning query to form a better bath. We also introduced a utility class called ParallelPlan that runs several planner instances in parallel and (optionally) uses path hybridization.
  • Added a more advanced path shortcutting method.
  • Added support for FCL collision checking library. PQP is actually still faster, and is therefore still the default.
  • All versions of EST and SBL use the new PDF class to sample more efficiently from empirical probability distribution functions.
  • Added a wrapper for boost::numeric::odeint to support high-order numerical integration of ordinary differential equations.
  • Added support for multiple solution paths in a Goal datastructure.
  • Added StateSpace::getValueAddressAtLocation() to allow faster indexing in states using state space names.

Point your browser to to download the latest version.

Announcing humanoid_walk 0.1

| No Comments | No TrackBacks


Announcement by Thomas Moulard (LAAS) to ros-users

Dear ROS users,

I am pleased to announce the first release of humanoid_walk.

This release provides C++ and ROS interfaces to allow humanoid robot walking trajectories generation.

Humanoid walking algorithms often take a set of footprints as input and provide feet and center of mass trajectories as output. These reference trajectories are then forwarded to the real-time controller.

This stack provides generic interfaces in order to wrap walking generation algorithm into ROS. It also provides an easy to use trajectory generator which can be used to generate motion.

The stack is available here:
...and is hosted on GitHub:

Bug reports, comments and patches are welcomed!

motion_analysis_mocap released

| No Comments | No TrackBacks

Announcement from Thomas Moulard (LAAS) to ros-users

Dear all,

I am pleased to announce the release of the motion_analysis_mocap stack.

This stack aims at integrating data from the Motion Analysis motion capture system into ROS.

This first public release provides a node which retrieve information from Cortex, the software provided by Motion Analysis and publishes them as both ROS topics (geometry_msgs/TransformStamped) and TF transformations.

Patches and feedbacks are welcomed through or GitHub.

Thomas Moulard

iTaSC software release

| No Comments | No TrackBacks

Announcement by Dominick Vanthienen to ros-users

Dear ROS and OROCOS community,

The Robotics Group of the K.U.Leuven likes to announce the release of the new iTaSC software (iTaSC-2.0alpha). Information, documentation and installation instructions can be found on . More documentation and example code will be made available in the coming weeks.

Kind regards,

The K.U.Leuven Robotics Group

What is iTaSC?

iTaSC stands for instantaneous Task Specification using Constraints, which is developed at the K.U.Leuven during the past years. The framework generates motions by specifying constraints in geometric, dynamic or sensor-space between the robots and their environment. These motion specifications constrain the relationships between objects (object frames) and their features (feature frames). Established robot motion specification formalisms such as the Operational Space Approach, the Task Function Approach, the Task Frame Formalism, Cartesian Space control, and Joint Space control are special cases of iTaSC and can be specified using the generic iTaSC methodology.

Announcement by Armin Hornung, Humanoid Robots Lab, Albert-Ludwigs-Universität Freiburg to ros-users

I'm pleased to announce a major update and rewrite of Freiburg's footstep planner in the humanoid_navigation stack, mainly contributed by Johannes Garimort. The planner is now much faster and builds on SBPL. In addition to the previous D* Lite implementation, this now enables anytime planning e.g. with ARA* or AD*.

The ROS interface was largely kept compatible and you can interact with the planner using RViz as planning GUI (instruction on the wiki page). You can check out the humanoid_navigation stack from alufr-ros-pkg.

Best regards,

RoboEarth ROS stack released

| No Comments | No TrackBacks

Announcement to ros-users by the RoboEarth team

Dear All,

We are happy to announce the RoboEarth ROS stack.

This stack currently allows you to create 3D object models and upload them to RoboEarth. It also provides packages to download any model stored in RoboEarth and detect the described object using a Kinect or an RGB-webcam.

The main packages are:

  • re_object_recorder: Allows you to create your own 3D object model using Microsoft's Kinect sensor. By recording and merging point clouds gathered from different angles around the object, a detailed model is created, which may be shared with the world by uploading it to RoboEarth.
  • re_kinect_object_detector: Allows you to detect objects you download from RoboEarth using a Kinect.
  • re_vision: Allows you to detect objects you download from RoboEarth using a common RGB camera (i.e., no Kinect is required for detection).

For more information, please see the or our web site

Additionally, a demonstration video is available at:

We are looking forward to your feedback.

The RoboEarth Team

Announcement from Armin Hornung of Humanoid Robots Lab, Albert-Ludwigs-Universität Freiburg to ros-users

I'm pleased to announce the release of OctoMap 1.2, along with the updated octomap_mapping ROS stack for diamondback, electric, and unstable (see official octomap page and ROS wiki page). This is major step up from the OctoMap 1.0 release and features many under-the-hood improvements (speedup, leaner code, testing, bug fixes) as well as an improved interface for fellow developers. Key features of the new version are: an adjustable sensor model, node-iterators, time-stamped nodes, and an improved make system. A clean separation of the visualization library means that the octomap_mapping stack no longer depends on Qt or OpenGL (our visualization "octovis" will be released later as an additional ROS package). Furthermore, all output in the octomap package is now using proper ROS log levels (thanks to Eric Perko for the patch).

Detailed changelog

Download OctoMap (stand-alone library and visualization)

ROS packages for diamondback, electric, and unstable are being built and will be available soon. Until then, you can get the `octomap_mapping stack from alufr-ros-pkg

Your friendly neighborhood OctoMap team (Kai and Armin)

Announcement by Ivan Dryanovski of ccny-ros-pkg to ros-users

Hi everyone,

We pushed out new debian releases of the asctec_drivers, mav_tools, and scan_tools stacks, The stacks support diamondback, electric, and unstable.

Here are some highlights of the changes:


  • canonical_scan_matcher has been renamed to laser_scan_matcher;
  • laser_scan_matcher now supports multiple sources of predictive input such as imu, odometry, and alpha-beta velocity tracking; can work with laser scans or pcl pointclouds
  • laser_ortho_projector behavior significantly changed to match new laser_scan_matcher - check the wiki page for details


  • Imu messages published by asctec_proc now take data from the IMUCalcData/acc_*_calib fields (instead of previous incorrect acc_*). The values are measured in different frames of reference; if you are using the /mab/Imu messages, you will need to account for this change.

We also improved the nodelet support in all packages and fixed various bugs reported by the community.



rosserial for Arduino now available

| No Comments | No TrackBacks
We would like to announce the first release of a new rosserial library for the Arduino platform.  The rosserial library allows Arduinos to directly publish and subscribe to ROS messages. There are also demos ranging from controlling servos to using an Arduino and rxplot as an oscilloscope to reading temperature sensors into ROS.

In addition to support integration with the Arduino platform, the rosserial library provides a general point-to-point transport for ROS communication over serial, which is intended for hardware that cannot support the full ROS TCP/IP network stack.  This library can be used to easily integrate a wide-variety of low-cost hardware into ROS.

Debian packages are now available for diamondback and unstable.

See more at:

ubuntuDebian packages for ROS Diamondback are now available for Ubuntu Natty Narwhal. We have updated the Diamondback installation instructions so that you can now apt-get install ROS on your new Natty machines. Thanks to all in the community who have helped up upgrade ROS to the latest versions of GCC, Python, and other changes that came with Natty. A special thanks goes to Vincent Rabaud, who did a tremendous effort to get most of the 140+ ROS Diamondback stacks compatible with the latest Ubuntu release.

René Ladan has also updated the FreeBSD packages for ROS to the Diamondback versions, so you can now install the ros, ros_comm, documentation, and rx stacks.

The majority of stacks in ROS Unstable are now also compatible with the Natty release.

ROS C Turtle Update

| No Comments | No TrackBacks

Thumbnail image for cturtle_poster.jpgA new version of ROS C Turtle has been released. This update includes ROS 1.2.6, support for CCNY's MAV libraries, and several other updates listed below.


In Nao related news, Aldebaran is having an open house during National Robotics Week in Boston on the 11th of April and in Chicago on the 12th. Also for those who already have a Nao, the Nao Robot stack has been updated to version 0.3.

Announcement from Armin Hornung to ros-users

Dear ROS (and Nao) users,

I'm happy to announce the release of version 0.3 of the "nao" stack
( Along with many bugfixes and
improvements, it is now compatible to ROS cturtle and diamondback with
NaoQI 1.6-1.10. The packages were restructured with all messages now in
nao_msgs (more general and Nao-independent ones are in
humanoid_nav_msgs) for cleaner dependencies. The new nao_tactile node
allows access to Nao's bumpers and touch sensors (thanks to Stefan
Osswald), and a new base_footprint frame enables a better compatibility
with existing planning methods (thanks to Daniel Maier). For a complete
changelog, see:

The source package release is available at:

or via source checkout from Freiburg's ROS repository:

Best regards,

The octree-based mapping library OctoMap has just been released as stable version 1.0 . There is now full-blown doxygen documentation available.

Based on OctoMap 1.0, a new version of the octomap_mapping stack was also just released for cturtle, diamondback, and unstable. Debian packages will appear in the Ubuntu ROS repositories soon, diamondback builds should be already available in the shadow-fixed repository for those willing to try them out. New in the octomap_mapping stack is the octomap_ros package to ease the integration of OctoMap with ROS / PCL.

Your friendly neighborhood OctoMap team (Kai and Armin)


ROS Diamondback Launch!

| No Comments | No TrackBacks


ROS Diamondback has been released! This newest distribution of ROS gives you more drivers, more libraries, and more 3D processing. We've also worked on making it lighter and more configurable to help you use ROS on smaller platforms.

Install ROS Diamondback


The Kinect is a game-changer for robotics and is used on ROS robots around the world. ROS is now integrated with OpenNI Kinect/PrimeSense drivers and the Point Cloud Library (PCL) 3D-processing library has a new stable release for Diamondback. The ROS 3D contest entries showed the many creative ways you can integrate the Kinect with your robot, and we will continue to work on making the Kinect easier to use with ROS. We've also redone our C++ APIs to make OpenCV easier-to-use in ROS.

A Growing Community, More Robots

Diamondback is the first ROS distribution release to launch with stacks from the broader ROS community. Thank you to contributors from UT Austin, Uni Freiburg, Bosch, ETH Zurich, KU Leuven, UMD, Care-O-bot, TUM, University of Arizona and CCNY for making their drivers, libraries, and tools available. Many more robots are easier-to-use with ROS thanks to their efforts.

Now that there are over 50 different robots able to use ROS -- mobile manipulators, UAVs, AUVs, and more -- we are providing robot-specific portals to give you the best possible "out of the box" experience. If you have a Roomba, Nao, Care-O-bot, Lego NXT robot, Erratic, miabotPro, or PR2, there are now central pages to help you install and get the most out of ROS. Look for more robots in the coming weeks and months to be added to that list.

Smaller, lighter

We've reorganized ROS itself and broken it into four separate pieces: "ros", "ros_comm", "rx", and "documentation". This enables you to use ROS in both GUI and GUI-less configuration, which will enable you to install ROS on your robot with much smaller footprint. This separation will also assist with porting ROS to other platforms and integrating the ROS packaging system with non-ROS communication frameworks. For more details, see REP 100.

More open

Since ROS C Turtle, we've adopted a new ROS Enhancement Proposal (REP) process to make it easier for you to propose changes to ROS. We have also transitioned ownership of the ROS camera drivers to Jack O'Quin at UT Austin and look forward to enabling more people in the outside community to have greater ownership over the key libraries and tools in ROS. Please see our handoff list to find ways to become more involved as a contributor.


We launched the ROS Answers several weeks ago to make it easier for you to get in touch with a community of ROS experts. It is quickly becoming the best knowledge base on ROS with over 200 questions in a wide variety of topics.

Other highlights

For more information, please see the Diamondback release notes. Some of the additional highlights include:

  • Eigen 3 support, with compatibility for Eigen 2.
  • camera1394 now supports nodelets and has been relicensed as LGPL.
  • rosjava has been updated and is now maintained by Lorenz Moesenlechner of TUM.
  • bond makes it easier to let two ROS nodes monitor each other for termination.
  • rosh is a new experimental Python scripting environment for ROS.
  • New nodelet-based topic tools
  • PointCloud2 support in the ROS navigation stack.


From the numerous contributed stacks to patches to bug reports, this release would not have been possible without the help of the ROS community. In particular, we appreciate your help testing and improving the software and documentation for the Diamondback release candidates to make this the best release possible. We hope that Diamondback helps you get more done with your robots, and we look forward to your contributions in future releases.

ROS Diamondback Release Candidate 3

| No Comments | No TrackBacks

Thumbnail image for diamondback-top-640w.pngThe third candidate of ROS Diamondback is now available! We intend for this to be our final release candidate, so please report any critical issues that you find. We will be focusing on improving source-based install methods between now and the final release.

This update comes with PCL 0.10, which has the stable API that will be used in PCL 1.0. The ROS 3D contest demonstrated many useful applications of PCL with robotics, and we're excited to have this stable release for Diamondback. We encourage users to provide feedback on tutorials and example applications to help guide PCL to its 1.0 milestone, which we are targeting for the ROS Electric Emy release in August.

Thank you to the many users who have submitted patches and bug reports to help improve these release candidates, including (but not limited to): andrewstraw, mdesnoyer, timn, ryohei, snorri, soetens, nbutko, nevion, willylambert, stevenbellens, isucan, gbiggs, atr, rene, bouffard, dthomas, joq, and lorenz.

ROS Diamondback RC3 Installation Instructions

Major updates:

ROS Diamondback Release Candidate 2

| No Comments | No TrackBacks

Thumbnail image for diamondback-top-640w.pngThe second candidate of ROS Diamondback is now available! We invite members of the community to test this second release candidate and identify any potential integration issues. We anticipate doing one more release candidate before the official Diamondback release, which is slated for the end of this month.

In addition to several bug fixes, this release also includes stacks from ccny-ros-pkg, including drivers for AscTec quadrotors. We appreciate the efforts of the CCNY Robotics Lab in putting together these releases.

ROS Diamondback RC2 Installation Instructions

New stacks:


ROS Diamondback Release Candidate 1

| No Comments | No TrackBacks

Thumbnail image for diamondback-top-640w.pngThe first release candidate of ROS Diamondback is now available! Thanks to the help from the community, we've been able to make numerous improvements to our Diamondback Beta releases and are now ready to put out our first release candidate.

We have also been putting together new robot-centric API and installation guides, which we hope will help organize the various ROS libraries better for new ROS users. We have setup some example pages and welcome others in the community to do the same:

Stack contributors: You are now welcome to start releasing against Diamondback directly. We had disabled some stacks in Diamondback due to some integration issues that have now been resolved. You can view the build status to check whether or not your stack is currently included.

Known issues:

  • Integration is still on-going for OS X and other Non-Ubuntu platforms.
  • Final Diamondback release is awaiting PCL 1.0.

Orocos Toolchain ROS 0.2.1 released

| No Comments | No TrackBacks

Announcement by Ruben Smits to ros-users

The Orocos Toolchain ROS stack developers are pleased to announce a new release of the orocos_toolchain_ros stack.

Debian packages are already available for unstable, diamondback and cturtle (only for lucid and maverick) will be available soon.

Most important changes:

  • We moved the development to GIT: the stack is available here (only http protocol is supported). Since we use git submodules do not forget to use -- recursive if you clone or to issue git submodule init;git submodule update after cloning.

  • Integration of RTT/Properties and ROS/Parameters: a new RTT service is available in the rtt_ros_param package that allows RTT users to store component properties on the ROS parameter server or to refresh them using values on the ROS parameter server. The integration also works seamlessly for your complex types as long as a RTT/Typekit for the type exists. Check here for more details.

  • The RTT typekit and transportkit generation for messages now creates a single library/typekit/transportkit for each package instead of one for each message type.

  • RTT and OCL are now native ROS packages, which allows us to use rosmake directly on the RTT and OCL source.

  • OCL offers a orocreate-pkg tool to create a new Orocos package (which uses rosbuild behind the scenes if available) including template code for components, typekits, plugins and services.

  • the OCL/deployer can now be used with roslaunch, each deployed process becomes a single node, containing the different deployed components.

  • the OCL/deployer now uses rospack in its import functionality, to find new component libraries, services, plugins, typekits and transportkits.

What's still on the roadmap:

  • Nicer solution for sequence types in the rosparam integration
  • Integration of the RTT/logging with the ROS/logging
  • Integration of RTT/Operations and ROS/Services (This one is currently on a hold because the feasibility is still uncertain)

More information:

-- Your friendly Orocos-ROS integration team.

ROS Diamondback Beta 2 Release

| No Comments | No TrackBacks

diamondback-top-640w.pngOur second beta release of ROS Diamondback is now available (installation instructions). Thank you to the many users who have reported issues with the first beta release. We also appreciate the users who have updated Diamondback instructions for the many various platforms ROS is available on. A special thank you goes to Nicholas Butko, who provided numerous patches to improve OS X compatibility.

In addition to OS X updates, this release continues our rollout of Eigen 2/3 compatibility and also cleans up various stack dependencies and installation variants. There are still several fixes and updates we wish to deploy before we reach release candidate status.

Install ROS Diamondback Beta

ROS Diamondback Beta Release

| No Comments | No TrackBacks


A beta release of ROS Diamondback is now available (installation instructions). We encourage users to try this beta release out and report any issues. We also encourage users who were using "unstable" to switch to Diamondback at this time as they are equivalent. We expect a very short beta period before our first release candidate.

The release of Diamondback is currently delayed due to integration of Eigen 3. Eigen 3 has become an important library in the robotics community, but it was originally incompatible with Eigen 2. The Eigen developers have been very responsive in introducing backwards compatibility modes, and we've determined that it would be better integrate with the updated library than to attempt to implement custom workarounds.

We still anticipate releasing Diamondback release this month, but we need your help to test Diamondback early and often, especially our Eigen integration. We also request the help of our OS X/Arch/Fedora/Gentoo/OpenSUSE/Slackware community to test integration and installation instructions for those platforms.

Install ROS Diamondback Beta

ROS C Turtle Update

| No Comments | No TrackBacks

Thumbnail image for cturtle_poster.jpgROS C Turtle has been updated with new debian packages. This update is mainly to include compatibility with image_transport_plugins on Ubuntu Maverick.


ROS C Turtle Update: Now with Erratic

| No Comments | No TrackBacks

Thumbnail image for cturtle_poster.jpgA new update to C Turtle has been released. This new release contains the first release of the erratic_robot stack, which supports the Videre Erratic platform. This stack is now maintained by Antons Rebguns/ua-ros-pkg and includes drivers, robot description, and navigation configuration.

ROS C Turtle Update

| No Comments | No TrackBacks

Thumbnail image for cturtle_poster.jpgA new release of debian packages is out. We have updated our debian-building infrastructure in preparation for ROS Diamondback, so please report any issues to ros-users.

C Turtle Update

| No Comments | No TrackBacks

This is a minor update mainly to deal with integration issues with PCL and Eigen.

C Turtle Update: Now with Care-O-bot

| No Comments | No TrackBacks

Thumbnail image for cturtle_poster.jpgThis newest update of C Turtle now lets you get the various stacks necessary for running or simulating Fraunhofer IPA's Care-O-bot 3. PR2 and Care-O-bot have shared a dance together, and Care-O-bot is waving the Jolly Roger in the C Turtle poster, so we're excited to have the five Care-O-bot stacks join the official distribution. You can find out more on the care-o-bot wiki page.

This is also the first release of the experimental rosjava client for ROS. The existing client has been taken over by Lorenz Moesenlechner at TUM and has been updated to work with the upcoming Diamondback release.


cturtle_poster.jpgOur latest C Turtle update has octomap_mapping and freiburg_tools stacks from the University of Freiburg (alufr-ros-pkg). We have also updated the kinect stack to include the latest calibration code and our kinect calibration tutorials has more instructions.

Announcement from Stefan Holzer

Hi all,

We've been working very hard to get PCL to work in Windows for the past few days and we are happy to announce the release of PCL 0.6! Because one of our friends and colleagues is turning 30 tomorrow, we decided to dedicate this release to him. Happy Birthday Bastian!

The 0.6 release brings:

  • preliminary Windows support
  • FLANN 1.6.2
  • Cminpack 1.1.0
  • portability fixes for MacOS
  • functionality patches and bug-fixes

Complete change-list

Thanks to all the contributors!

With this release, the core PCL libraries (dependencies and ROS wrappers) moved to the perception_pcl stack, while the visualization tools and tutorials moved to the perception_pcl_addons stack. No further development of PCL will be done in the old point_cloud_perception stack.

PS. Remember to bookmark :)


Announcement from Armin Hornung of Albert-Ludwigs-Universität

The OctoMap 3D mapping library is now available as precompiled .deb package for Ubuntu in the ROS cturtle and unstable repositories. The octomap_mapping stack contains the actual octomap package for ROS and a map server. Detailed API documentation is available at the wiki page under "Code API".

This coincides with the release of OctoMap v0.8, which the octomap_mapping stack now builds on. Compared to previous versions, the optimizations in OctoMap 0.8 significantly speed up map building and queries on the map. As always, we're curious to hear how you use OctoMap and if there are suggestions for further improvements.

Best regards,
Armin Hornung and Kai M. Wurm


Just in the time for Thanksgiving, we've got some new things for the ROS and ROS-Kinect community to play with.

  • Access to Kinect's raw IR image
  • Kinect debians for C Turtle
  • ROS debians for Ubuntu Maverick on C Turtle

For the Kinect, we've achieved a major breakthrough: access to the IR camera image. Now that we have access to the raw IR camera image, instead of just the depth image, we can do monocular and stereo calibration using the regular ROS calibration tools and methods. We're taking a short break for Thanksgiving, but we should have RGB/depth calibration by the end of the week.

Regularly ROS-Kinect users can just update to the get these changes -- or you can try

sudo apt-get update
sudo apt-get install ros-cturtle-kinect

We have a lot more in the works, so stay tuned. Happy Thanksgiving!

OPENQBO Linux distro for Qbo robot

| No Comments | No TrackBacks

TheCorpora has put out their own Linux distribution, based on Ubuntu 10.04, that neatly packages everything you need to get up and running with Qbo. It comes with ROS, OpenCV, Festival speech synthesis, Julius speech recognition, Qbo-specific libraries, and more. This includes capabilities, like Qbo_Visual_Slam, shown below:

cturtle_poster.jpgIn this latest C Turtle update, we are now including two stacks from utexas-art-ros-pkg: art_vehicle and velodyne.

Other updates:

C Turtle Update: Now with Orocos

| No Comments | No TrackBacks

cturtle_poster.jpgA new C Turtle Update has been released. This update is significant in that we have the first externally managed ROS stack available for download: orocos_toolchain_ros. This stack, produced by kul-ros-pkg, provides integration between ROS and the Orocos software framework.

We also have several stacks related to Diamondback. roshpit allows users to download and test the upcoming rosh shell, which will officially debut in ROS 1.4. There are also new empty ros_comm and rx stacks, which have been added so that stacks can be compatible with both C Turtle and Diamondback packaging, once the "ros" stack has been split.

General Updates:

Diamondback-compatibility Updates:

PR2 and WG Updates:

ROS 1.3.0 Released, Unstable

| No Comments | No TrackBacks

ROS 1.3.0 has been released. This is an unstable release and is the first of the 1.3.x "odd-cycle" releases. During this release cycle, we expect to rapidly integrate new features and the stack is expected to be volatile.

In particular, much of the work for the ROS 1.3.x release cycle is related to REP 100, ROS Stack Separation. There are several major changes in this initial release, with more to come. For ROS 1.3.0, we have implemented the following changes:

  • genmsg_cpp has been deleted. This ends support for the current experimental rosoct and rosjava libraries.
  • All rx* packages have been moved to the rx stack. This was done to remove heavyweight WxWindows dependencies from the ROS stack.
  • rosdoc has been moved to the new documentation stack. This was done to remove heavyweight Doxygen, Epydoc, and Sphinx dependencies from the ROS stack.

The next major change will be to migrate the ROS middleware libraries to the ros_comm stack. This will mainly have impact on stack dependency declarations.

We've also included deprecation warnings in the rosrecord and rosbagmigration packages for this release. Use of these APIs should be ported to the new rosbag library, which has support for the latest bag format.

For more changes, please the ROS 1.3.0 changelist.

Also, you may wish to now consult the rx and documentation stack changelists for packages that were formerly in the ROS stack.

For more information on the ROS 1.3.x releases, you can see REP 101, ROS 1.4 Release Schedule.

FreeBSD package for ROS

| No Comments | No TrackBacks


Rene Ladan has been working hard over the past several months providing patches to ROS in order to improve FreeBSD compatibility. Now he's announced the first FreeBSD package for ROS, which makes installation patch-free and no-hassle.


The first FreeBSD package for ROS is now available, providing the equivalent of ros-cturtle-ros on Ubuntu (but without the build directories). The cleaned up instructions are available at the wiki.

Thanks go to the ROS developers for applying all the patches I sent to them.

I will probably add more ROS packages in the future, starting with the tutorials and the Lego NXT stacks (the latter because that's the only robot I have myself, apart from some webcams).


Camera pose estimation stack

| No Comments | No TrackBacks

Steven Bellens and Koen Buys from kul-ros-pkg have announced a new camera_pose_estimation stack

We've put a first version of our camera_pose_estimation stack online, available in the kul-ros-pkg repository.

The stack builds upon the ar_pose package, but allows tracking markers with multiple cameras taking into account measurement uncertainty as provided in the ARMarker message, as opposed to the ar_pose package which allows tracking one / multiple markers with a single camera. All available estimates are converted to world coordinates and fused using an Extended Kalman Filter as provided in BFL. If you have any suggestions/comments/questions about the stack, let us know!

best regards,

Steven Bellens
Koen Buys


On the heels of the Orocos RTT 2.0 release, Ruben Smits from KU Leuven has announced the first version of the new-and-improved Orocos/ROS integration

Hi orocos-dev, orocos-users, ros-users,

A first version of our Orocos/ROS integration is ready in the form of the orocostoolchainros stack.

The stack is available at:

  • released version:
    • tarball
    • svn: svn co orocos_toolchain_ros
  • developers version: svn co orocos_toolchain_ros

The stack contains all of the Orocos Toolchain v2.0.1 except for the autoproj build system. The orocos_toolchain_ros stack contains patched versions of orogen and utilmm to automatically create ros packages instead of autoproj packages for the automatic typekit generation for c++ classes.

On top of the Orocos Toolchain v2.0 this stack contains:

  • rtt_ros_integration: This package contains the following:
    • The ros-plugin: this RTT plugin allows Orocos/RTT components to contact the ROS master
    • CMake macro's to automatically create Orocos/RTT typekits and transport plugins from .msg files
  • rtt_ros_integration_std_msgs: This package shows how the CMake macro's have to be used, it creates the Orocos/RTT typekits and transport plugins for all roslib and std_msgs messages
  • rtt_ros_integration_example: This package shows how the rtt_ros_integration should be used from an Orocos/RTT user/developer point of view. It contains a HelloRobot component which can be contacted using rostopic echo

And last but not least the stack also includes the rtt_exercises package for Orocos/RTT new-commers.

The orocos_toolchain_ros stack itself still remains undocumented, I'm currently working on that, but documentation on the Orocos Toolchain can be found via: http://

If anyone has any questions please do not hesitate to contact the orocos-users, orocos-dev or ros-users mailing list.

C Turtle Update 1

| No Comments | No TrackBacks

We are happy to announce the release of a number of stacks that provide core functionality for grasping and manipulation tasks, as well as example applications on the PR2 robot. These include:

Additional details, tutorials and example application can be found on the ROS Wiki. Good places to start checking out the available functionality are:

Complementing the manipulation stacks is a database of household objects containing information relevant for manipulation tasks, along with its ROS interface. Details can be found on the household_objects_database page.

Please note that these are "research stacks", under active development. While we have put a lot of effort into reviewing and documenting them, they are likely to be less stable than "core" ROS stacks which have reached 1.x releases. That said, we believe that they will provide useful functionality for building towards complex mobile manipulation applications.

Any feedback, bug reports or success stories of using these stacks will be greatly appreciated.

Your Merry ROS Manipulation Mob

ROS C Turtle Release

| No Comments | No TrackBacks


ROS C Turtle has been released!

ROS C Turtle is the second ROS distribution release. ROS Box Turtle was released March 2, 2010 and included stable releases of ROS and core libraries and tools like navigation, rviz, hardware drivers, and an image-processing pipeline.

ROS C Turtle builds on Box Turtle with across-the-board improvements to these core libraries and numerous bug fixes. These improvements include a new "nodelet" architecture that provides low-latency, zero-copy message passing within C++ nodes, official support for a Lisp client library, and an official firewire camera driver (thanks to Jack O'Quin). Numerous third-party libraries have been upgraded in this release, including Stage 3.2.2, Bullet 2.76, and Eigen 2.0.15, as well as newer versions of KDL and Gazebo. There are many, many other improvements listed in the change list.

This release includes new experimental libraries for 3D perception, manipulation, grasping, and visual odometry. We encourage early adopters to test out these libraries and provide feedback so that they can be stabilized for future ROS releases.

Since the release of Box Turtle, the ROS community has grown immensely. There are over a dozen new public, open-source repositories of ROS code, and ROS has been ported to a variety of different robot platforms, from mobile manipulators to autonomous boats. Commercial robotics software libraries like Urbi and Karto now have open-source offerings that are compatible with ROS, and the list of robot platforms that can be used with ROS continues to grow. We're excited at these new opportunities to collaborate within the community and hope that you all enjoy this C Turtle release.

ROS distribution releases occur on a six-month cycle. The successor to C Turtle, Diamondback, is expected in February of 2011.

sea-turtle-hires.pngROS C Turtle Release Candidate 2 has been released, including ROS 1.2.0. All of the remaining stacks have also reached stable release, including geometry and pr2_ethercat_drivers. This bug also fixes a major problem with calibration of the PR2 grippers.

ROS 1.2.0 includes major updates to roscpp, roslaunch, and rosbag, as well as improvements to nearly every tool in the ROS toolchain. roslisp is now included as a supported client library. roslisp users should also install the roslisp_support stack. For a more complete list of changes, see the ROS 1.2.0 change list.

NOTE: Debian packages are currently building and will be available soon. The new debian packages have a "version 23" suffix, e.g. ros-cturtle-ros_1.2.0-23.

Change lists

EusLisp now open source

| No Comments | No TrackBacks

EusLisp is now open source with a BSD license! There are over two decades of robotics research built on top of EusLisp that can now more easily be shared with other researchers. All of this is accessible to ROS users as well: the JSK lab at Tokyo University has developed a roseus package that enables use of ROS within a EusLisp environment. Many robots, including the Kawada HRP-2, Aibo, Nao, and Willow Garage PR2 are compatible with EusLisp.

EusLisp is a Lisp-based programming environment for developing robotics programs. It combines a solid modeler, visualization, geometric libraries, simulation and more into a single development environment. EusLisp was originally developed by Toshihiro Matsui at AIST in 1986 and has been heavily used by the JSK Lab at Tokyo University in their humanoid robotics research.

EusLisp is an integrated programming system for the research on intelligent robots based on Common Lisp and Object-Oriented programming. The principal subjects in the field of robotics research are sensory data processing, visual environment recognition, collision avoiding motion planning, and task planning. In either problem, three dimensional shape models of robots and environment play crucial roles. A motivation to the development of EusLisp was a demand for an extensible solid modeler that can easily be made use of from higher level symbolic processing system. Investigations into traditional solid modelers proved that the vital requirement for their implementation language was the list processing capability to represent and manage topology among model components. Numerical computation power was also important, but locality of geometric computation suggested the provision of vector/matrix functions as built-ins would greatly ease programming.

From EusLisp Manual, Part I, EusLisp Basics, 1. Introduction

You can find out more about the open source Euslisp at, and you can download the code here.

ROS C Turtle Release Candidate 1

| No Comments | No TrackBacks

sea-turtle-hires.pngROS C Turtle Release Candidate 1 has been released. With this release, nearly all of the remaining ROS stacks have reached stable release: camera_drivers, common, common_msgs, driver_common, imu_drivers, joystick_drivers, laser_drivers, pr2_simulator, sound_drivers, visualization, visualization_common. This release also includes ROS 1.1.16, which is a minor update and is the release candidate for ROS 1.2.

As this is our release candidate for C Turtle, we encourage users to try this release out and note any issues they have with this release. You can consult our release notes that we are currently assembling to assist with any integration issues.

NOTE: Debian packages are currently building and will be available soon. The new debian packages have a "version 21" suffix, e.g. ros-cturtle-ros_1.1.16-21.

Change lists

Anton Rebguns of the University of Arizona has announced the release of a Videre Stereo Camera driver. NOTE: this package only works with ROS C Turtle. The announcement is below.

I'd like to announce an initial release of a driver for Videre Stereo cameras. The driver supports both STOC and non-STOC devices. Pretty much all settings can be controlled through the dynamic_reconfigure GUI, these include:

  • TF Frame
  • Processing Mode (for STOC devices)
  • Generic camera parameters (exposure, gain, brightness)
  • Stereo Processing parameters (uniqueness, texture thresholds, speckle size and range)

There are a few parameters that are present but don't currently work, like whitebalance and horopter settings. There are no tutorials yet, if people are using it and have problems just shoot me an email. I will be adding some documentation/tutorials fairly soon.

Thanks, Anton

ROS C Turtle Alpha 6 Released

| No Comments | No TrackBacks

sea-turtle-hires.pngROS C Turtle Alpha 6 has been released. This update includes ROS 1.1.15. Many new stacks reached stable release: image_common, image_pipeline, physics_ode, pr2_common, simulator_gazebo, and simulator_stage. We are getting close to our release candidate for the actual C Turtle release. As we approach this release candidate, we anticipate more rapid releases to quickly verify final code changes going into the system.

In addition to the new stable releases, several new unstable/research stacks are being included with this release, including vslam, slam_karto and graph_mapping.

NOTE: Debian packages are still building and will be available soon. The new debian packages have a "version 18" suffix, e.g. ros-cturtle-ros_1.1.15-18.

Change lists


Thanks to the efforts of Gostai, Urbi and ROS are now compatible! Urbi 2.1 has just been released, and this new release includes integration with ROS and Urbiscript.

For ROS users, Urbiscript provides users a powerful scripting environment that provides features like parallelism and event-triggers for creating behavior scripts for your robots. ROS users can also use the Gostai Studio Suite, which provides a graphical IDE. Gostai has released the Urbi kernel as open source (AGPL), which contributes the growing community of open-source platform technologies for robotics.

For Urbi users, ROS provides a quickly growing library of reusable and open-source software components with a wide range of capabilities, including navigation, perception, and manipulation.

To find out more about Urbi open source, check out Urbi Forge. To get started with Urbi + ROS, you can read the Urbi manual or try their Urbi + ROS tutorial.

ROS C Turtle Alpha 5 Released

| No Comments | No TrackBacks

sea-turtle-hires.pngROS C Turtle Alpha 5 has been released. This update is mainly to fix an issue with rxgraph and includes ROS 1.1.14. We are also now including ros_tutorials with the base distribution of C Turtle to simplify installation, and we are also testing builds of several new research stacks, including people, sql_database, object_manipulation, pr2_object_manipulation, tabletop_object_perception, pr2_tabletop_manipulation_apps. These research stacks are unstable and must be installed separately.

NOTE: Debian packages are still building and will be available soon. The new debian packages have a "version 15" suffix, e.g. ros-cturtle-ros_1.1.14-15.

Change lists

ROS C Turtle Alpha 4 Released

| No Comments | No TrackBacks

sea-turtle-hires.pngROS C Turtle Alpha 4 has been released. This update contains ROS 1.1.13, which contains important bug fixes for roscpp as well as for the relay node in topic_tools.

Two stacks have reached stable status with this release: navigation and diagnostics. They now have 1.2.x version numbers to indicate that they are now part of a stable update series (patch-only).

NOTE: The new debian packages have a "version 12" suffix, e.g. ros-cturtle-ros_1.1.13-12.

Change lists

ROS C Turtle Alpha 3 Released

| No Comments | No TrackBacks

sea-turtle-hires.pngC Turtle Alpha 3 has been released. This update includes numerous bug fixes, including a new ROS 1.1.12 release. This release also contains stable releases for robot_model and pr2_robot. If you are running a previous C Turtle release, we encourage you to update and report any issues that you find.

NOTE: The new debian packages have a "version 11" suffix, e.g. ros-cturtle-ros_1.1.12-11. We are currently having issues with Karmic 64-bit binaries, but other Ubuntu binaries should be available.

Change lists

ROS C Turtle Alpha 2 Released

| No Comments | No TrackBacks

sea-turtle-hires.pngC Turtle Alpha 2 has been released. This update includes numerous bug fixes, including a new ROS 1.1.10 release. This updates fixes bug reports with Gazebo permissions issues, ros::Time issues, tf, Lucid 32-bit binary packages, and more. We appreciate the efforts of the community to make C Turtle as stable as possible -- please keep those reports coming!

NOTE: The new debian packages have a "version 8" suffix, e.g. ros-cturtle-ros_1.1.10-8. They should finish building shortly.

Box Turtle updates:

Change lists

ROS C Turtle Alpha 1 Released

| No Comments | No TrackBacks

sea-turtle-hires.pngROS C Turtle Alpha 1 is now available for developers. The is an alpha release of the upcoming distribution that is being used to test the integration of the many new features and components that will be released with C Turtle. C Turtle is intended to be backwards compatible with Box Turtle, though many APIs that were deprecated in Box Turtle have been removed. This early release will allow developers to test compatibility.

Debian packages are available for this release, including binary builds for Ubuntu Lucid Lynx. Any of the current ROS installation instructions will work for C Turtle by simply substitution "cturtle" for "boxturtle". You can also use the SVN externals URLs that we have setup for each variant.

As this is an alpha release, we ask that developers who use it provide as much feedback as possible, including filing bug tickets for any issues found.

Armin Hornung from Albert-Ludwigs-Universität has announced version 0.2 of the nao stack:

Version 0.2 of Freiburg's "nao" stack for Aldebaran's Nao humanoid has just been released. Major changes are the compatibility with NaoQI version 1.6 and the new omnidirectional walking engine (detailed changelist: ).

Files are available packaged at:

or via source checkout from Freiburg's ROS repository:

The stack documentation at was extended and adjusted to this new version.

I'm open for feedback and suggestions!


ROS 1.1.8 released, feature frozen

| No Comments | No TrackBacks

ROS 1.1.8 has been released. This is the feature freeze release of ROS. Future releases in the ROS 1.1.x series will be bug-fix only, and ROS 1.2 will be based on the features and APIs of this release. Now that ROS is feature frozen, we encourage developers to test integration with ROS 1.1.8 and report any problems you find. This release should be backwards-compatible with ROS 1.0, though we have removed APIs that were deprecated in the ROS 1.0 release.

To report bugs, please use the ROS issue issue tracker.

This release focused on new features for rosbag and rxbag, as well as new APIs for rosbuild, new std_msgs/Time and Duration msgs, and a rosclean tool for easily removing log files. Please see the full change list for more details.

The SVN tag will will be using for testing the ROS 1.2 release candidates is:

We will soon be releasing an alpha version of ROS C-Turtle, so please stay tuned.

-- your friendly neighborhood ROS development team

We're getting close to being feature-complete for most of the C-Turtle stacks. There has been a flurry of releases with the expected functionality for the next distribution release, and we will be stabilizing these over the next several weeks as we finalize C-Turtle.

Change lists

ROS 1.0.4 Released

| No Comments | No TrackBacks

ROS 1.0.4 (stable/boxturtle) has been released. This release fixes a regression in roscpp's getParamCached() method that meant it hit the master every time it was called if the parameter didn't exist.

Full 1.0 changelist

Several patch releases have been made, including ROS 1.1.7, which fixes issues with roslaunch and paramiko on Ubuntu Jaunty. The rest of the patch releases are for Box Turtle and are listed below.

Change lists

ROS 1.1.6 has been released. This will be one of the last releases in the 1.1.x series as we are quickly approaching feature freeze. You can read the change list for more information. NOTE: ROS 1.1.5 contains an error with the gtest package and should not be used.

Several other stacks in the C-Turtle unstable development series have been updated as well, including:

Change lists

geometry 1.1.2 and robot_model 1.1.2

This announces geometry 1.1.2 and robot_model 1.1.2 are released into latest. These are unstable releases, with API changes. Unless you are working toward the next release it is recommended to remain on boxturtle.

Note: There are some permutations of updating which creates a linking error for undefined references into bullet. If you get these errors, use rosmake with the --pre-clean option and it will work fine. This has only been observed when following a specific sequence of updates.

point_cloud_perception 0.1.6

PCL (Point Cloud Library) 0.1.6 and the point_cloud_perception stack have been released!

We're slowly adding more functionality, fixing bugs, and writing documentation and tutorials for early adopters. Please check out for more information and don't forget to keep an eye on the tutorials section. PCL requires the latest branch, which is unstable and only recommended if you want to play with cutting edge features.

We are going to have two talks about PCL at ICRA (check out our schedule for details), so please stop by, and come talk to us afterwards. We're also going to showcase some of the PCL functionality at the Willow Garage booth. Looking forward to see you there!

Thanks to everyone that contributed!

point_cloud_perception change list

ROS 1.0.3 Released

| No Comments | No TrackBacks

ROS 1.0.3 has been released! This is a patch update for users of Box Turtle. We recommend that all Box Turtle users upgrade to this new version. This update also includes new compatibility with the recent release of Ubuntu Lucid Lynx. Our debian packages are currently building and should be ready soon. rosinstall and SVN users can update now.

We appreciate all the ROS users who have contributed bug reports and patches that have made this release possible. The list of changes is below.

-- your friendly neighborhood ROS team

Change list

  • rosmake patch to not try to clean rospack if ROS_NOBUILD present. r9156
  • roslib: bug fix to roslib.list_stacks_by_path() when following symlinks (#2638)
  • rxgraph: patch for xdot issue with certain dot files #2586 r9280
  • rospy: fix to handle double shutdown signal case better #2369 r9348
  • roslaunch: fixed name resolution of node command-line arguments and fixed usage statement #2309 r9361
  • rosrecord: fixed bug in rosplay timeshifting #1327
  • genmsg_cpp: fixed bug in string constant generation for rosjava, r9400.
  • updated top-level rosdep.yaml to include Ubuntu Lucid definitions r9409

We've updated quick a few stacks in the past week. As you can tell from the dual 1.0.x and 1.1.x releases, we are moving forward on our C-Turtle development, though we are continuing to patch problems with Box Turtle as necessary.

Change lists

Several stacks have been updated, including the unstable ROS 1.1 series. Both joystick_drivers and laser_drivers have also started 1.1.x unstable development releases to test new features for C-Turtle.

Change lists

ROS 1.1.3 Released

| No Comments | No TrackBacks

ROS 1.1.3 has been released as a minor update to the 1.1.2 release. This release fixes a minor issue with rosmake that affects shared installations of ROS.

ROS 1.1.2 Released, Unstable

| No Comments | No TrackBacks

ROS 1.1.2 has been released. This is an unstable release to test new features for ROS.

The major new feature with this release is integration of roslisp. roslisp is a full-featured Common Lisp client library for ROS that is being developed by Bhaskara Marthi (Willow Garage) and Lorenz Mösenlechner (TUM). We are now including it in the ROS stack to enable more easily access its capabilities, especially in shared install setups where ROS messages have already been built.

This update does not require ROS users to install Lisp. We have created a separate "roslisp_support" stack with a "roslisp_runtime" package that will trigger an install of SBCL, when required. Current users will have to make sure to add a dependency on the roslisp_runtime package so that installation scripts work properly.

Another major update in this release is performance updates for rospy message serialization. The new optimizations should result in performance improvement of 2x or better for many types of messages, mainly thank to James Bowman's patches.

As with our previous unstable releases, we ask that general users refrain from updating to this release unless they need to test integration for the upcoming C-turtle distribution. We do recommend that roslisp users test this new setup and provide feedback on this new roslisp core integration.

For more updates in this release, please see the full change list

-- your friendly neighborhood ROS team

ROS 1.0.2 Released

| No Comments | No TrackBacks

ROS 1.0.2 has been released! This is a patch update for users of Box Turtle. We recommend that all Box Turtle users upgrade to this new version. Our debian packages are currently building and should be ready soon. rosinstall and SVN users can update now.

We appreciate all the ROS users who have contributed bug reports and patches that have made this release possible. The list of changes is below.

-- your friendly neighborhood ROS team


visualization_common 1.1.0 and visualization 1.1.0 have been released. This is an unstable development release to try out features considered for inclusion in their 1.2 versions. visualization 1.0 will work with visualization_common 1.1, but visualization 1.1 requires visualization_common 1.1. The largest changes in these releases involve additions to the visualization_msgs/Marker API.

Change lists

navigation 1.1 unstable release

| No Comments | No TrackBacks

navigation 1.1.0 has been released. This is an unstable development release to try out features considered for inclusion in navigation 1.2. The 1.1.0 release contains a service call for navfn that allows plans to be made via ROS, a service call to move_base that clears unknown space in the costmap, and a fix to velocity computation in the base_local_planner that could allow robots to drive a bit faster but needs testing to be sure its safe. Unless you have an immediate need for features in the 1.1 series, it is recommended that you use the 1.0 series until things stabilize with a 1.2 release.

Hope all is well,


Change List:

  • move_base
    • Added a clear_unknown_space service to move_base that allows external users to clear unknown space around the robot in the costmap.
  • navfn
    • Adding a make_plan service to navfn that allows the use of the planner via ROS.
  • costmap_2d
    • Changing ROS_ASSERT to ROS_FATAL with a std::runtime_error when checking for legal configurations.
    • Costmap2DROS is now const correct
  • base_local_planner
    • Bug fix for how velocities were being computed. This fix will make the robot a bit more aggressive in how it drives and is going into the 1.1 series for testing.

The following stacks have been updated with patches:

Change lists

Unstable release: pr2_controllers 1.1

| No Comments | No TrackBacks

pr2_controllers 1.1.0 has been released. This is an unstable development release to try out features considered for inclusion in pr2_controllers 1.2. The 1.1.0 release contains some additional configuration options and a new joint trajectory controller with an action interface built in.

Change list

  • The projector controller now updates the projector current setting each time through the realtime loop. Otherwise, some lockout conditions were causing the current to be set to zero, and it was never being reset to the proper value.
  • pr2_controllers_msgs now autogenerates its action messages during build step. Removed the autogenerated files from version control
  • pr2_gripper_action now depends explicitly on pr2_mechanism_model.
  • Upped the tolerance for determining that a joint is stopped in the joint trajectory action to handle jittering in gazebo.
  • Removed push_back from the realtime part of the calibration controllers (#3949)
  • Made the stall velocity threshold configurable in pr2_gripper_action (#4073)
  • Created the joint trajectory action controller, which combines the joint spline trajectory controller and the joint trajectory action.
  • Upped tolerance for determining if the controller is following a different goal in the pr2_gripper_action (#4076)
  • Joint trajectory action controller now accepts goals with a timestamp of 0 (#3896)

Unstable release: slam_gmapping 1.1.0

| No Comments | No TrackBacks

slam_gmapping 1.1.0 has been released. As with all 1.1.x stacks, this release is unstable and not recommend for most users. This release adds a couple of features that help with autonomous exploration.

This is a good time to put in patches and requests for features to be added in the 1.1.x series:

Change lists

We've released several patch updates for our stacks. For Box Turtle, visualization and pr2_simulator has been updated. Several other development stacks have also been updated.

Change lists

The following stack have been updated:

These updates are mostly compatibility fixes for ROS 1.1 and minor bug fixes.

Change lists

ROS 1.1.1 Released

| No Comments | No TrackBacks


ROS 1.1 has been released. This is an unstable development release to test and develop features for ROS 1.2. This comes quickly on the heals of the 1.1 release yesterday due to a bug in the new service generators. It also has some other miscellaneous changes.

Change list

  • rosmaster: subscribers now declare topic types, though they cannot overriding existing type declarations (r8745)
  • rosmaster: roslib.masterapi: Added getTopicTypes() to support subscribers declaring types (r8745)
  • rospy: bug fix to on_shutdown() (#2536 r8746)
  • rospy: removed support for deprecated /time topic
  • rostopic: support for subscriber-declared types (uses new getTopicTypes()) Master method
  • roslib: Links against rt to fix linking with the gold linker
  • roscpp: Fixed service generators to work with concurrent builds
  • roscpp: Removed support for deprecated /time topic

    -- your friendly neighborhood ROS development team

ROS 1.1 Released (Unstable)

| No Comments | No TrackBacks


ROS 1.1 has been released. This is an unstable development release to test and develop features for ROS 1.2 (see version policy). Install at your own risk.


Major changes:

  • C++: There are major changes to roscpp, including a new message serialization API, custom allocator support, subscription callback types, non-const subscriptions, and fast intraprocess message passing. These changes are backwards-compatible, but require further testing and API stabilization.

  • Python: The rospy client library is largely unchanged, though the ROS Master has been moved to a separate package. There are many internal API changes being made to the Python code base to support the rosh scripting environment under active development.

For future development plans for the ROS 1.1.x branch, please see the ROS roadmap.

Please see the full changelist for a description of the many updates in this release.

Several stacks have transitioned to 1.1 unstable development branches: common_msgs 1.1.1, image_pipeline 1.1.0, and vision_opencv 1.1.0. These are unstable development releases: it is recommended for users to keep using the 1.0 branch in Box Turtle. Our stack version policy describes our general development model for stable and unstable releases.

common 1.1

The primary part of this release is the addition of the nodelet package. There was discussion on the ros-users mailing list earlier about how this can be used as an optimization. If you are interested please take a look at the documentation or code. Feedback is always appreciated.

image_pipeline 1.1

The major new features are in stereo_image_proc. It takes advantage of improvements to the OpenCV stereo block matcher, particularly to reduce fringe artifacts at edges. For comparison, the reference implementation of stereo block matching (on which OpenCV's was based) can be used instead, but they should now give roughly the same results. stereo_image_proc now advertises a separate point cloud topic using the new and improved PointCloud2 message type.

Change lists

Several stacks have been updated with patches for Box Turtle.

pr2_calibration, which is still in unstable development, was also updated to 0.3.0.

Change lists

There have been several new releases containing patches, new features, and unstable updates.

Two of our ROS stacks have gone to their "unstable" release cycle: common_msgs and vision_opencv. We will be using this release cycle to develop new features for the next stable release.

For our patch releases, web_interface and and laser_drivers have both been updated with bug fixes.

pr2_calibration, which is an unstable library still under active development, has reached it's 0.3.0 release.

Change lists

The following stacks have been updated with bug fixes:

Change lists

ROS 1.0.1 Released

| No Comments | No TrackBacks


The ROS 1.0.1 patch update has been released. This contains several patches, but no API changes. If you are using ROS 1.0.0, it is recommended to update.

Change list

  • rospy: fixed bug in service generator with transitive dependencies (#2378, r8077)
  • roscpp
    • Fixed bug where XmlRpcValue parameters were accidentally being cached when they shouldn't be (#2381, r8089)
    • Fixed bug where param::get()/NodeHandle::getParam() of XmlRpcValue parameters would always return true after the first call, even if the parameter didn't exist (r8091)
    • Fixed a crash on shutdown involving popping off an already-empty list (r8132)
    • Fixed bug in UDPROS XML/RPC exchange so that the subscriber receives the publisher's side of the connection header information (r8265)
  • rosmake
    • Fixed log directory permissions ticket
    • Fixed typo Exception/Exceptoin (#2377)
    • more verbose error on rosdep failure
  • roswtf: removed reference to netifaces, which has been disabled (r8152)
  • test_msgs: reworked layout to not confuse roswtf (r8154)
  • rossrv/rosmsg: fixed issue with field type resolution (r8191)
  • roslaunch: better error message on unrecognized tags inside of <node> tag (r8296) and better error message if another master is running (r8309)
  • rostest: creation of .ros directory fixed to use parent permissions (r8303 r8304)
  • roslisp message generation: added type specifiers for fields and made them immutable. If you update to ros 1.0.1, you also need to update in the ros_experimental repository.
  • rostopic: bug fix to -p option when printing empty fields
  • rosgraph: better suppression of /clock when using -q option with rxgraph
  • roswtf: better error message when connection to master lost during graph checks (r8420)
  • rosbuild:
    • Updated to use hashlib instead of deprecated md5 (#2385, r8128)
    • Fixed bug with cached build flags when moving packages (#2459, r8453).
  • rosdep.yaml: added missing Boost packages for Ubuntu 9.04
  • rosdep : improved robustness to invalid packages (#2406, r8250).

driver_common 1.0.1 and sound_drivers 1.0.3 have been released. These are patch updates and updating is recommended.

Change lists

navigation 1.0.4 released

| No Comments | No TrackBacks


The navigation 1.0.4 patch update has been released. This release contains minor bug fixes and patches as documented in the change list below.

Change List

  • move_base_msgs
    • Messages now automatically generated from a .action file instead of being manually generated and checked in
  • navfn
    • Fixed a problem where debugging information was saved all the time. This was especially troublesome on the shared install on the robot where users don't have write permissions.
    • Fixed a bug in the validPointPotential method that could cause it to return false incorrectly
  • map_server
    • Changed the map_saver to use a latched topic instead of a service call to get the map.
    • Fixed a bug where the map_saver would save unknown space with a color value that did not match the threshold it wrote out to its yaml file.

Hope all is well, Eitan

We've released patch updates to several stacks with bug fixes and minor updates.

Change lists

ROS stack patch releases

| No Comments | No TrackBacks

We've released several updates of ROS stacks. Most of these new releases are patch updates to fix various issues that have been reported.

Patch releases:


Change lists:

Thursday 1.0 Release: pr2_controllers

| No Comments | No TrackBacks


Today we released pr2_controllers 1.0. This stack contains our realtime controllers for the PR2, as well as actionlib interfaces for invoking these controllers.

As you can tell, the pace of our 1.0 releases is slowing down... because we're almost done! If you're waiting for ROS 1.0, don't worry -- the ROS team happens to like releasing on Fridays.

There were several other releases today. These were mostly for stacks that are under development, but provide useful functionality to PR2 users. We'll be releasing videos showing what the future has in store for these stacks. We also released a minor update to pr2_common.

Change lists:

Wednesday 1.0 Releases: pr2_gui

| No Comments | No TrackBacks


Today we released pr2_gui 1.0. pr2_gui provides the pr2_dashboard, which is an integral tool we use for understanding the state of our PR2 robots.

We are busy putting the final touches on our remaining 1.0 releases. We releases several more stack updates today, including two new stacks: robot_calibration and pr2_calibration. Although these calibration stacks are not mature, yet, they are already proving very useful in calibrating our new PR2 Beta robots.

Change lists:

laser_drivers.png driver_common.png pr2_ethercat_drivers.png pr2_power_drivers.png pr2_common.png

Today was a big day for releasing drivers. Our 1.0 releases today were:

We are nearly finished with our 1.0 release cycle. With today's releases, most commonly used functionality with ROS has been released as 1.0, which means that non-PR2 robots using navigation and perception capabilities have a solid base to build on top of.

We also wanted to note that ROS 1.0 is in final testing. You can preview our release candidate at:

driver_common provides common driver capabilities that we use in our laser and camera drivers, such as dynamic reconfiguration of parameters. Our laser_drivers stack provides drivers for common Hokuyo and SICK laser rangefinders. We also released pr2_ethercat_drivers and pr2_power_drivers, which support PR2-specific hardware.

Our non-driver release of the day was pr2_common 1.0, which contains description of the PR2 Beta robot, PR2-specific messages, and other common PR2 data.

We also released several other stacks today, including the new web_interface and pr2_web_apps stacks, which provide a user-friendly, browser-based environment for performing common robot tasks and monitoring.

Change lists:

pr2_mechanism.png image_pipeline.png

Today we released two more stacks as 1.0, including the first of our PR2-related stacks as 1.0:

Several other PR2-related stacks have hit release candidate status for 1.0 and will be released in the coming days.

diagnostics has been updated 1.0.1 to patch a problem seen on Ubuntu distributions prior to Karmic. We also put out updates of several other stacks, including:

Change lists:

diagnostics.png joystick_drivers.png imu_drivers.png

Today, three of our driver-related stack reached 1.0 status:

These stacks provide drivers and diagnostic capability for the Microstrain 3DM-GX2 IMU, PS3 joystick, and the Linux joystick. There is also experimental support for the Wiimote and 3Dconnexion SpaceNavigator. The diagnostics stack also provides GUIs for viewing diagnostic information from these and other drivers.

We also had several more releases today to test features and bug fixes for coming 1.0 releases:

Next week, we will start to transition towards 1.0 releases of PR2-related components -- we hope you enjoyed today's unveiling of the PR2 Beta robots!

Change lists:

navigation.png slam_gmapping.png simulator_gazebo.png

Today we released three more stacks with 1.0 status:

This set of releases, combined with our previous release, provides the complete ROS navigation stack, including SLAM, with stable APIs and support. The navigation stack is in use on a wide variety of robots, and we're excited that this fundamental and robust capability has reached this milestone.

Additionally, the release of simulator_gazebo, which wraps the open-source Gazebo simulator, lays the groundwork for our upcoming release of the pr2_simulator stack.

Several stacks were released today to test functionality prior to 1.0 release. Many of our driver stacks are nearing 1.0 release, with both joystick_drivers and imu_drivers already in 1.0 release candidate status.

Change lists:

navigation 0.8.1 released

| No Comments | No TrackBacks


navigation 0.8.1 has just been released. The primary purpose of this release is to move visualization topics into the namespace of the node instead of having them clutter the global namespace. This means that instead of rviz subscribing to local_costmap/obstacles to display obstacle information, it will instead subscribe to move_base_node_name/local_costmap/obstacles. For most people using the navigation stack, you won't have to change a thing, there are, however, a few exceptions to this:

  1. If you subscribe to any of the visualization topics that move_base publishes, and your code lives outside the patched WG repository, you'll have to prepend the name of the move_base node onto those subscriptions. If you're using launch files from the Willow Garage repositories, that name will be "move_base_node." If you're using launch files from your own repositories that will be whatever name you decided to give the move_base node.

  2. If you use the "make_plan" service provided by move_base, and your code lives outside the patched WG repository, you'll instead have to call "move_base_node/make_plan."

  3. If you command the local version of move_base that operates in the odometric frame (found in 2dnav_pr2/move_base_local), and your code lives outside of the patched WG repository, you'll need to change from using local_navigation/move_base_simple/goal> to move_base_local_simple/goal.

I apologize in advance for any pain that these changes cause, but the global namespace was just getting too cluttered on our robots here at WG, and I don't expect that these changes will affect too many people. If you have any questions, concerns, or problems with the migration please don't hesitate to let me know.

Ok, that's the annoying part of this release. The exciting part of this release is its inclusion of SLAM support for the navigation stack. The costmaps now subscribe to the map as a latched topic instead of using a service call and support dynamic updates. This means, running SLAM with the navigation stack is easy, to see things in action follow these three steps:

  1. Make sure you're running on the latest versions of the navigation and slam_gmapping stacks, and update in wg-ros-pkg
  2. rosmake 2dnav_slam_stage
  3. roslaunch 2dnav_slam_stage move_base_slam_5cm.launch (it may take a few seconds for the map to show up)

That's it, you should be able to send the robot goals in unknown space and it should build a map as it goes.

Hopefully, this release will just become navigation 1.0, but I'm going to give it the rest of the day to get some more testing in.

As always, let me know if you have any issues, questions, comments, concerns, etc.

Also, for those of you on OSX, nav_view has been patched so it should build and run correctly now.

Hope all is well, Eitan

robot_model.png visualization.png

Today we added two more 1.0 releases:

These releases mean that the rviz 3D visualization tool has officially reached 1.0 status. The visualization stack also recently added plugins for the ROS rxbag tool, which you will be able to use with the ROS 0.11 release. The robot_model stack is largely unchanged from its previous release.

Two other stacks also had releases today to do some final integration before they reach 1.0 status:

Change lists:

geometry 1.0 released!

| No Comments | No TrackBacks


We're glad to announce the first full release of geometry. The geometry stack provides important libraries in ROS, including the tf coordinate transform library, as well as ROS wrappers for the popular Bullet physics engine and KDL kinematics and dynamics library.

This release does mark the removal of several previously deprecated functions and methods. However, the APIs that are released are stable and the 1.0 series will be supported with patches in the upcoming ROS "Box Turtle" distribution.

Major Changes

Full changelist

  • Lots of new documentation on the wiki at tf
  • transform_sender has been replaced with static_transform_publisher, which has the same functionality.
  • New helper functions in "tf/transform_datatypes.h" for working around Bullet deprecations
  • New exception tf::InvalidArgument can be thrown for bad arguments. It inherits from tf::TransformException. This is used for things like unnormalized quaternions which would produce nan results.
  • tf::remap() methods have been deprecated. Replace them with tf::resolve() or tf::TransformListener::resolve().
  • Deprecated functions have been removed:
    • All tf::Stamped methods have been removed, there are drop in replacements supporting datatype tf::StampedTransform. This includes variants of lookupTransform(), data converter methods, setTransform(), and sendTransform()
    • tf::Stamped no longer has a child_frame_id field
    • MessageNotifier has been removed.
    • TransformListener::canTransform() with timeout has been removed, use waitForTransform() instead.
    • transformStampedTFToMsg()
    • transformStampedMsgToTF()
  • The topic "/tf_message" is no longer valid. If you are using bag files it is recommended to rebag them remapping the topic to "/tf". Playback can be remapped each time with "/tf_message:=/tf" on the command line. Please see the full changelist for a migration script for bags.

geometry.png laser_pipeline.png simulator_stage.png

Our 1.0 releases continue today with three new stacks hitting 1.0 status:

simulator_stage and laser_pipeline are largely unchanged from previous releases. geometry, in particular tf, has many changes worth noting, so they will be detailed in a separate announcement.

We are now a third of the way through our 1.0 release process and expect several more 1.0 releases this week.

Another major release today was pr2_controllers 0.3.0. That stack is now in our stable release process now that it has cleared user testing.

Several other stacks were released today in order to support the release process. With the exception of pr2_controllers, these were all patch updates. Although these releases contain new functionality and patches, we recommend waiting to update as many of these stacks will soon be reaching 1.0 status.

Change lists

-- your friendly neighborhood ROS distributors

vision_opencv.png image_common.png

To update on our ongoing process of 1.0 releases, two more stacks were released with the 1.0 label today:

  • vision_opencv 1.0
  • image_common 1.0

In order to prepare for upcoming 1.0 releases, many of the ROS stacks have been undergoing release updates to do final integration checks and ensure compatibility across stacks. We expect to see several more of these types of releases as we prepare release candidates for the remaining 1.0 stacks. Although these releases contain new functionality and patches, we recommend waiting to update as many of these stacks will soon be reaching 1.0 status. The new releases include:

  • camera_drivers 0.3.1
  • driver_common 0.2.2
  • imu_drivers 0.3.1
  • joystick_drivers 0.9.4
  • laser_drivers 0.3.0
  • pr2_simulator 0.2.7
  • simulator_stage 0.10.2
  • simulator_gazebo 0.6.10

There was also a minor update to physics_ode to add a dependency on the 'ros' stack:

  • physics_ode 1.0.1

Here are links to the change lists:

diagnostics 0.5.0 released

| No Comments | No TrackBacks


We've just released diagnostics 0.5.0. We're moving towards final integration later this week. With this release, we added a few new features to the diagnostic_aggregator, and focused on our documentation and tutorials for the other components. We'd like to see our diagnostic toolchain used on more robots as ROS spreads.

For complete changes, plase see the complete changelist.

Major Changes

  • diagnostic_aggregator
    • Added AnalyzerGroup class to group other Analyzers
    • Can discard stale diagnostic items
    • Analyzer function 'bool match(const string) const' is deprecated, new version is non-const.
  • robot_monitor
    • Reports status of diagnostics_agg topic, helps debug network issues
    • User testing feedback incorporated
  • diagnostic_updater, self_test
    • Deprecated functionality removed
    • Frequency status "errors" went to "warnings"


image_pipeline 0.9.0 released

| No Comments | No TrackBacks


image_pipeline-0.9.0 is now out. image_pipeline fills the gap between camera_drivers and higher-level vision processing. It includes a camera calibration GUI, a lightweight viewer for image topics, and nodes to perform color interpolation, rectification and stereo processing on camera images.

This is a stable release and has passed our user testing requirements. For changes see the changelist below. This release finally removes much long-deprecated code. In particular, the old stereoproc node is gone, as are all of the stereo messages excepting DisparityImage (which has a new definition).



  • Raw images may now be 8-bit mono, RGB, BGR, or any of the four bayer encodings.
  • Now using OpenCV for bayer interpolation.
  • Now using image_geometry for rectification.
  • Better error reporting when started in global namespace or input topics do not exist.


  • Inherited improvements from image_proc.
  • Now using OpenCV's block matching implementation to calculate the disparity image.
  • Parameters have changed to more closely follow OpenCV's options.
  • Publishing floating-point disparity image.
  • No longer publishing image_disparity, use stereo_view for visualization instead.
  • REMOVED deprecated stereoproc node and other obsolete files.


  • stereo_view shows color-mapped disparity image along with left/right.


  • New definition of DisparityImage. Disparities are now floating-point, not fixed-point. Better comments.
  • REMOVED all deprecated messages (RawStereo, DisparityInfo, StereoInfo).
  • Added script to convert RawStereo bags to Image & CameraInfo bags.


  • GUI improvements.


laser_drivers 0.3.0 released

| No Comments | No TrackBacks


laser_drivers 0.3.0 has been released. This release is intended to test final changes in anticipation of an upcoming 1.0 release.


  • Adjusted messages so that the driver will not spew messages when it manages to open a device but fails to get all the way running.
  • Updated licenses and package/stack descriptions.
  • Removed the node description from doxygen.


visualization 0.5.0

| No Comments | No TrackBacks


visualization 0.5.0 has been released. This release includes the new rxbag_plugins package, which provides visualization plugins for the new-in-ROS-0.11 rxbag tool, as well as a number of rviz bugfixes.


  • Fixed crash when loading old configs that had a top-down orthographic view (r26030, #3358)
  • Fixed Marker display memory leak which caused rviz to constantly increase in memory usage in certain situations (r26166, #3364)
  • Now validates input messages and discards those with nans/infs (r26286, #3360)
  • Fixed "Panels" menu checkboxes to be correct at startup instead of all-checked (r26611)
  • Fixed crash caused by laser scans/point clouds arriving in their separate thread and accidentally causing a GUI change in that thread instead of the GUI thread (r26639, #3422)
  • Added rxbag_plugins which contains message viewer plugins for the rxbag visualization tool


ROS 0.11 Released

| No Comments | No TrackBacks

ROS 0.11

ROS 0.11 has been released! ROS 0.11 includes many of the final features and API modifications that we wish to have in place for ROS 1.0. Our focus with this release was on improving consistency, better performance, and bug fixes. We are also removing much of the deprecated functionality with this release so that ROS 1.0 will have minimal deprecated functionality.

Some of the major updates in this release include new "wait for message" API routines in roscpp and rospy, bash tab-completion for most command-line tools, improvement in Python-related startup latency, and streamlining of the service API in rospy.

There were many other changes with this release as we work to improve and finalize the ROS feature set. You can find a complete list in the changelist.

You can download a tarball of the release, though we recommend that you start with the ROS installation instructions instead.

Notes on Updating from 0.10 or earlier in SVN: There are a number of previously installed programs which are now versioned scripts. SVN will error when updating and not delete the installed programs to add the scripts in their place. You will need to delete the program and svn up again. The error will read:

svn: Failed to add file 'FILENAME': an unversioned file of the same name already exists

The solution is to rm FILENAME && svn up again.

driver_common 0.2.1 released

| No Comments | No TrackBacks


driver_common 0.2.1 has been released. This is a patch release to fix a bug in dynamic_reconfigure introduced by changes in method names in 0.2.0.


camera_drivers 0.3.0 released

| No Comments | No TrackBacks


camera_drivers 0.3.0 has been released.


  • The packages dcam1394 and libdc1394v2 have been moved into camera_drivers_experimental. These packages are not yet considered stable and will likely change before the release of a stable driver for firewire cameras.
  • Bug fix: fix import of dynamic_reconfigure


driver_common.png camera_drivers.png laser_drivers.png imu_drivers.png image_pipeline.png

We have released several more stacks into our stable release process: driver_common 0.2.0, imu_drivers 0.2.0, camera_drivers 0.2.0, and laser_drivers 0.2.0. We have also released image_pipeline 0.1.1, which will soon be in stable release as well. These stacks contain drivers for publicly available sensors, such as Hokuyo and SICK laser range finders, firewire cameras, and the microstrain 3dmgx2 IMU.

With these releases, all driver-related components for our Milestone 3 effort are now stable. This means that feature development for these components is largely concluded for this release cycle and that every effort will be made to ensure that future modifications to the public APIs in these stacks will be done in a backwards-compatible manner.


pr2_common.png pr2_mechanism.png pr2_power_drivers.png pr2_gui.png pr2_ethercat_drivers.png

We have released several more stacks into our stable release process: pr2_common 0.2.0, pr2_gui 0.2.0, pr2_ethercat_drivers 0.2.0, pr2_power_drivers 0.2.0, and pr2_mechanism 0.5.0. These releases mainly affect users of the PR2 robot, including the PR2 simulator. Each of these stacks now has a stable API, which means that every effort will be made to provide backwards-compatiblity for any changes.


navigation 0.6.3 released

| No Comments | No TrackBacks


navigation 0.6.3 has been released. This release contains the standard bug fixes and patches and also adds some features to the costmap_2d package that begin to make it more compatible with SLAM systems. There is still a bit of work/testing to be done to allow easy integration of the navigation stack with a SLAM system, but look for the next few releases of navigation stack to add additional capabilities, culminating with the 0.7.0 release of the stack. I'm planning on getting the 0.7.0 release out sometime in mid to late January. In the meantime, please treat the additions to the costmap_2d package as experimental as they are fairly untested.


  • Removed use of deprecated rosbuild macros.


  • Added API for having a map coordinate frame that is different from the simulator coordinate frame.


  • Fix bug where nodehandle.getParam was used instead of nodehandle.pararm
  • fix test launch files to have names as required for ROS 0.11


  • The costmap now publishes information about what cells are unknown
  • Fixed a bug where the voxel version of the costmap was not retaining unknown space correctly when reset to the static map.
  • Built support for changing maps into the Costmap and Costmap2DROS objects. See the updateStaticMap method of the Cosmtap2DROS object.
  • Added support for copying only a window of a costmap. See the getCostmapWindowCopy method of the Costmap2DROS object.
  • Changed the default value for the min_obstacle_height parameter to be 0.0m from 0.05m.


  • Added a parameter that allows the user to configure whether or not navfn should consider unknown space as traversible.
  • Updated navfn to work with costmaps of changing size


image_common 0.6.1 released

| No Comments | No TrackBacks


image_common 0.6.1 has been released. This is a patch release to fix compilation under gcc 4.4.


laser_pipeline 0.6.0 released

| No Comments | No TrackBacks


laser_pipeline 0.6.0 has been released. There are only a few small changes with this release.



  • Adding support for inverted mode to laser projection
  • Removed use of deprecated rosbuild macros.


  • Removed use of deprecated rosbuild macros.


simulator_gazebo 0.6.4

| No Comments | No TrackBacks


simulator_gazebo 0.6.4 has been released. This is a patch release fixing a camera plugin bug where distortion parameters (k1,k2,k3,t1,t2) were not passed from Gazebo URDF extensions XML to the subsequently published CameraInfo message (D-matrix remained 0).


image_common 0.6.0 released

| No Comments | No TrackBacks


image_common 0.6.0 has been released.

There is one deprecation: creating an image_transport::SubscriberFilter now requires an image_transport::ImageTransport argument in place of a ros::NodeHandle. The constructor/subscribe() taking ros::NodeHandle will be removed in a later release.

image_transport::Subscriber now attempts to detect a common user error, passing in a transport-specific topic name (e.g. "/camera/image/compressed") in place of the base topic ("camera/image"), and print a useful warning.

Other changes are mostly bugfixes and making image_transport's publisher/subscriber classes more closely mimic the behavior of ros::Publisher and ros::Subscriber in edge cases.



  • Subscriber attempts to recognize and warn when the user passes in a transport-specific topic instead of the base topic.
  • ImageTransport constructor from NodeHandle is now explicit.
  • SubscriberFilter takes an ImageTransport argument in constructor and subscribe(). Old versions with a NodeHandle argument are deprecated.
  • (Camera)Publisher and (Camera)Subscriber methods now mimic roscpp behavior when the object is "invalid" (default-constructed or shutdown).
  • Publisher plugin parameter lookup correctly starts in the namespace defined by the base topic.


  • Added stream-based read/write functions for INI and YML representations.


geometry 0.4.5 released

| No Comments | No TrackBacks


geometry 0.4.5 has been released. This is a patch release. The changes are listed below.



  • new node tf_remap which will remap tf frames. Useful for bag file playback etc.
  • added experimental lookupVelocity method
  • Fix: Python methods lookupTransform and lookupTransformFull were failing on Python 2.6 (r25958,#3337)
  • Switch tf_prefix to use searchParam() #2921
  • Removed use of deprecated rosbuild macros
  • Python methods transformVector3Stamped added r26189


  • Removed use of deprecated rosbuild macros


  • create symbolic link called site-packages to dist-packages for compatibility with newer python versions


simulator_gazebo 0.6.3 released

| No Comments | No TrackBacks


simulator_gazebo 0.6.3 has been released. This release adds bayer image generation in simulation for modeling wide stereo camera pair on PR2.


pr2_simulator 0.1.1 released

| No Comments | No TrackBacks


pr2_simulator 0.1.1 has been released and contains a minor patch to startup a set of default controllers when starting PR2 in simulation. This is going to be the default behavior for the actual PR2 as well. Please see the ChangeList for more details.


pr2_simulator 0.1 release

| No Comments | No TrackBacks


The pr2_simulator 0.1 has been released. This initial release represents a transition into a stable release cycle. Future updates to this stack will be made backwards compatible, when possible. The pr2_simulator stack contains the necessary components for working with a simulated PR2.


simulator_gazebo 0.6.2 released

| No Comments | No TrackBacks


simulator_gazebo 0.6.2 has been released. This release contains a parallel make bug fix and (re)enables erratic_gazebo 2dnav-stack demo.

Change List

  • fixes to gazebo_ros_diffdrive for the erratic example. publishing '''erratic_odometry/odom''' topic and tf transform from '''base_link''' to '''odom''' frame.
  • fix parallel build error due to dependency bug #3349


robot_model.png simulator_gazebo.png

simulator_gazebo 0.6.1

simulator_gazebo 0.6.1 has been released with some patches to fix bugs in include guards. This release adds custom callback queue for the remaining of the plugins in gazebo plugins except for sim time publisher. GazeboRosF3D plugin now broadcasts both force and torque acting on a body using the WrenchStamped message.

Other changes:

  • removed joint force plugin

robot_model 0.6.4

We just released the 0.6.4 version of the robot model stack. Much like the last release of simulator_gazebo 0.6.1, this release changes how we deal with the world link in a tree. The robot state publisher no longer ignores the world link when it publishes to tf. The urdf package also got a visualizer tool to visualize the robot tree.

Other changes:

  • urdf
    • add visualizer tool for urdf tree
    • root link is always optional, not only when it is called "world"
    • fix bug where sphere init always fails
  • robot_state_publisher
    • Also publish the transform from the root link to its children
    • Only warn once when the tree that is provided contains fewer than two segments.
  • kdl_parser
    • add check_kdl_parser tool to verify parsing of urdf file
  • convex_decomposition:
    • add unzip as dependency


common.png common_msgs.png geometry.png visualization.png simulator_stage.png simulator_gazebo.png

In conjunction with the ROS 0.10 release, several ROS stacks have been released with compatibility updates and other changes.

common 0.7.1

The common 0.7.1 patches several issues with xacro:

  • Added a flag for only evaluating include tags in xacro
  • Allowing multiple blocks and multiple insert_blocks, fixing #3322 and #3323

common_msgs 0.9.6

common_msgs 0.9.6 contains a new sensor_msgs/SetCameraInfo service and updates to nav_msgs/OccupancyGrid.

  • nav_msgs:
    • Changed nav_msgs/OccupancyGrid to use int8 instead of deprecated byte (no code changes necessary it was an alias)
    • Updated migration rules to handle migration of nav_msgs/OccupancyGrid since md5sum changed.
  • sensor_msgs: Added service sensor_msgs/SetCameraInfo
  • Removed improperly added srv directory in root of stack.

geometry 0.4.4

The geometry 0.4.4 release patches several issues with tf and upgrades the version of eigen to 2.0.9:

  • tf: fixed usage of python to_seconds to to_sec
  • tf: fixed commandline parsing in view_frames for hudson build
  • tf: fixed ~ param usage in change_notifier
  • eigen: Upgraded to version 2.0.9

visualization 0.4.1

This is a minor patch release that fixes parsing orientation out of a URDF (thanks Lorenz).

simulator_stage 0.10.0

With the simulator_stage 0.10.0 release, robot link base_laser has been changed to base_laser_link to stay consistent with naming conventions of all other PR2 robot links (except frames). Please note that you will need wg-ros-pkg trunk r26633+ to work with this release.

simulator_gazebo 0.6.0

With the simulator_gazebo 0.6.0 release, the main API change is that the urdf2gazebo converter tool does not skip the first link if it's not the special "world"-link. Other changes in this release:

  • added custom callback queues for imu, p3d, bumper, camera, laser plugins
  • fix bumper, publish once per update call
  • change fixed axis pseudo-hinge joint to z-axis for better stability (heuristics)
  • support removal of world link from urdf


common.png navigation.png simulator_stage.png simulator_gazebo.png

In conjunction with the ROS 0.10 release, several ROS stacks have been released with compatibility updates and other changes.

common 0.7.0

The common 0.7.0 release introduces experimental python versions of both the ActionServer and SimpleActionServer. The API for the code mirrors that of the stable C++ code, so you should expect a fair amount of stability at the API level there, but the code is only lightly tested so there are bound to be some bugs to flush out. This release also fixes a number of deprectation warnings introduced by ROS 0.10.0.

  • Adding a blocking call for sending goals (actionlib::SimpleActionClient::sendGoalAndWait). This feature is still unstable & experimental
  • Added a shutdown method to the actionlib::SimpleActionServer allowing users to explicitly tell the server to shutdown
  • No longer relying on header.stamp fields to autofill with ros::Time::now() (in both C++ and Python).
  • Fixed race condition in C++ client causing spurious "Tried to create a handle to a list elem with refcount 0" errors
  • Created a Python action server and simple action server, mirroring the functionality of the C++ [simple] action server. This feature is still unstable & experimental.
  • Adding explicit copy constructor and equals operator to ServerGoal

navigation 0.6.2

navigation 0.6.2 is a patch release that has some minor bug fixes and gets rid of deprecation warnings that came along with ROS 0.10.0. There is also a patch to robot_post_ekf that fixex a crash when the covariance is zero.

simulator_stage 0.9.1

The simulator_stage 0.9.1 release switches simulator time message type from roslib::Time to roslib::Clock.

simulator_gazebo 0.5.0

The simulator_gazebo 0.5.0 release has some minor bug fixes and switches simulator time message type from roslib::Time to roslib::Clock. Additionally:

  • player CMake variable fix
  • reworked contact feedback messages.
  • fix LD_LIBRARY_PATHs for setup.tcsh and setup.bash


robot_model 0.6.3 released

| No Comments | No TrackBacks


robot_model 0.6.3 has been released. This release fixes a number of bugs in the 0.6.2 stable release. The changes are limited to the urdf and kdl_parser pacakges.


  • kdl_parser

    • Fix bug where kdl parser was not using inertia from urdf
    • Add regression test for inertia parsing
  • urdf

    • Make all "get" methods const
    • Give better error message when no links were found
    • Generate parse error when visual, collision or inertial is specified but fails to parse


ROS 0.10 Released

| No Comments | No TrackBacks

ROS 0.10

ROS 0.10 has been released. The focus of this release is preparing ROS for a 1.0 release. We have been making final reviews of the ROS APIs to address any essential feature gaps, API inconsistencies, and deprecations. Documentation is also being improved and reviewed. Final deprecations prior to 1.0 are described on the roadmap and are either being made in this release or 0.11.

There were many other changes with this release as we work to improve and finalize the ROS feature set. You can find a complete list in the changelist.

You can download a tarball of the release, though we recommend that you start with the ROS installation instructions instead.

simulator_gazebo 0.4.2 released

| No Comments | No TrackBacks


simulator_gazebo 0.4.2 has been released. The 0.4.2 releases contains patches for some additional bug fixes as mentioned in the change list: urdf2gazebo had a gimbal lock problem, joint axis transforms were missing and new model spawning tool. "gazebo_model" has been added, due to replace "spawn_gazebo_model".


simulator_gazebo 0.3.0 released

| No Comments | No TrackBacks


simulator_gazebo 0.3.0 has been released. This release contains patches for bug fixes as mentioned in the change list. Consolidation from other packages and some cleaning up were done for the default worlds and object models in gazebo_worlds. ROS time publisher for simulation time has been moved from PR2 robot description into the world. Non-PR2 specific Gazebo plugins from the unreleased pr2_simulator stack (originally under package pr2_gazebo_plugins) has been migrated into the simulator_gazebo stack under a new package named gazebo_plugins. Most/all of the changes should be transparent to end-users.


navigation 0.6.1 released

| No Comments | No TrackBacks


navigation 0.6.1 has been released. This is a patch release that fixes some bugs unearthed in the process of making sure the move_base node passes valgrind cleanly.

Minor Updates

  • costmap_2d: Added an example launch file that is up-to-date

Bug Fixes

  • nav_core: Destructors of the interfaces weren't virtual, causing all sorts of memory problems on shutdown of nodes. This is now fixed.
  • rotate_recovery: Added missing cleanup of a pointer on destruction.
  • move_base: Switched action server to be a pointer to avoid a race condition that will be fixed in trunk of common, but can be worked around.
  • move_base: Ran valgrind on the move_base node and got it passing cleanly.


geometry 0.4.3 released

| No Comments | No TrackBacks


geometry 0.4.3 has just been released. This is a patch release. One assert was replaced with in code error handling and one function has been deprecated in favor of using a constructor inline (see below) .



  • waitForTransform removed Assert, errors are now reported using return code and error string.
  • Deprecating sendTransform(tf::Transform, . . . ) due to backwards argument order. Replace call with sendTransform(tf::StampedTransform. . . ) Also fixing regression in 0.4.1 in that function.
    • b.sendTransform(transform, time, frameid, parentid); becomes b.sendTransform(tf::StampedTransform(transform, time, parentid, frameid));


navigation 0.6.0 released

| No Comments | No TrackBacks


navigation 0.6.0 has just been released. This release makes the recovery behaviors the navigation stack invokes when planning fails plugin based. This means that users of the move_base node now have the flexibility to write recovery behaviors that are appropriate for their robot. Documentation on how to configure the navigation stack to use these plugins can be found here, and two example recovery behaviors can be found here and here. These changes are all backwards compatible, so if you've been satisfied with the default recovery behaviors, they'll contiunue to work as they have in the past.

Full Changelist

New Features

  • move_base: Made the recovery behaviors that the navigation stack uses plugins so that users of the move_base node have more flexibility in how the robot behaves when planning fails. All the changes to the navigation stack are backwards compatible.
  • clear_costmap_recovery: Added this recovery behavior as a default plugin for the move_base node. Also, this package was API and Doc reviewed.
  • rotate_recovery: Added this recovery behavior as a default plugin for the move_base node. Also, this package was API and Doc reviewed.
  • nav_core: Added a !RecoveryBehavior interface and updated documentation accordingly.
  • voxel_grid: Added a few more tests for the voxel_grid package.

Bug Fixes

  • costmap_2d: Fixed build failure on Karmic/gcc4.4


visualization 0.4.0 released

| No Comments | No TrackBacks


visualization 0.4.0 has been released. This release is heavily focused on usability, and specifically on being able to easily debug what is going wrong when data is not showing up. The largest change in this regard is the addition of status elements in the "Displays" tree. These should show you if something is going wrong and attempt to heuristically diagnose what the problem is.

There are also a number of other changes, such as help text for each item in the displays tree.

The per-display documentation has also been filled out for all built-in displays, with video and property descriptions.

Full Changelist


image_common 0.5.2 released

| No Comments | No TrackBacks


image_common-0.5.2 has been released. This is a patch release with bug fixes and gcc 4.4 support; usage has not changed.


  • image_transport:
    • Fixed bug in connection callbacks that sometimes caused a segfault.
    • Publisher now throws if it fails to load any plugins.
    • Got rid of deprecation warning from getSubscriberCallerID.
  • camera_calibration_parsers:
    • Fix for gcc 4.4.


diagnostics 0.3.0 released

| No Comments | No TrackBacks


We've released diagnostics 0.3.0. This release is the first stable release for the diagnostic_aggregator and includes numerous bug fixes for the robot_monitor and other tools. The runtime_monitor monitor tool was renamed from "" to "", so you should now invoke it with rosrun runtime_monitor


  • diagnostic_aggregator
    • GenericAnalyzer has been completely redone, with subclassable base GenericAnalyzerBase
    • New OtherAnalyzer handles remaining diagnostic messages
    • API change for Analyzers, fully API reviewed
    • Stable API, all changes will have deprecation period from now on
    • Updated doxygen
    • Removed xmlrpc++ dependency
    • Regression test
  • robot_monitor
    • Fixed "has_message" function for pr2_dashboard
    • Fixed annoying scrolling behavior
    • Basic regression test (smoke test)
  • runtime_monitor: Basic regression tests added (smoke test)
  • diagnostic_analysis: renamed from "diagnostics_analysis" for consistency with other diagnostic packages.
  • diagnostic_updater/self_test: Minor documentation fixes and features. API review will be complete in 0.4.0.


simulator_gazebo.png physics_ode.png

physics_ode 0.2.0 and simulator_gazebo 0.2.0 have been released. physics_ode provides a rigid body physics engine for the open source Open Dynamics Engine (ODE). simulator_gazebo is a ROS wrapper for the open source Gazebo simulator (part of Player/Stage/Gazebo project). This stack also includes tools for interfacing with the simulator and a set of commonly used sample worlds and objects.


geometry 0.4.1 and common 0.6.1 released

| No Comments | No TrackBacks


geometry 0.4.1 and common 0.6.1 have been released. This is a patch release. If you are having performance issues are wish to use these stacks with gcc 4.4 (e.g. Karmic Koala), please update.

Minor Changes

  • tf
    • patched TransformBroadcaster.sendTransform(*) methods to consistently remap
    • Fixed tf_monitor display of current chain to show last link
    • MessageFilter now remaps target frames (r25194, #3119)
    • MessageFilter now warns and immediately throws out messages with an empty frame_id (r25194)
    • Changed compile mode to Release from Debug r25374
    • Fixed usage message for static_transform_sender r25375
  • common
    • Koala/gcc 4.4 compatability.
    • filters patch for karmic compilation


navigation 0.5.2 released

| No Comments | No TrackBacks

navigation 0.5.2 is a patch release that adds new tests and fixes a bug with a costmap_2d test.

New Features

  • voxel_grid: Added some basic tests, more to come soon
  • costmap_2d: Added a lot of tests

Bug Fixes

  • costmap_2d: Fixing test dependency on willow_maps which is not in the navigation stack


vision_opencv 0.3.0 released

| No Comments | No TrackBacks


vision_opencv 0.3.0 has been released. The new stack vision_opencv is a replacement for the old stack opencv. The stack opencv is now deprecated, as are its packages opencv_latest and opencvpython.

Please update your dependencies as follows: if your manifest.xml has opencv_latest, then replace it with opencv2 and cv_bridge. If you have scripts or launch files that reference opencv_latest, change to opencv2.


robot_model 0.6.1 released

| No Comments | No TrackBacks


robot_model 0.6.1 has been released. This release fixes a number of bugs in the 0.6.0 stable release. The most important fixes are in the urdf package: the parser now makes sure all required fields are present, and the parser now always fails when it finds a syntax error in a field, even when this field is optional. See the changelist below for more details.


  • robot_state_publisher:
    • Remove use of deprecated "~" in parameter names.
    • Add include of for g++ 4.4 compatibility
    • Fix warnings in regression tests
    • Increase buffer size for joint state from 1 to 500
    • Deal with an incomplete joint state by trimming corresponding tree branches
  • resource_retriever:
    • Add include of for g++ 4.4 compatibility
  • urdf:
    • Fix bugs in optional/required checks of fields
    • Fail parsing if optional field has invalid syntax


navigation 0.5.1 released

| No Comments | No TrackBacks

navigation 0.5.1 is a patch release that adds new tests and fixes a bug with a costmap_2d test.

New Features

  • amcl: Updating amcl so that the coordinate frames it uses can be set via parameters
  • costmap_2d: Can now save pgm files of the costmap to help with debugging if the user desires
  • costmap_2d: Added test to catch invalid costmap construction or updating due to improper raytracing or inflation

Bug Fixes

  • costmap_2d: Fixed a bug in obstacle re-inflation after raytracing
  • robot_pose_ekf: Update bag downloading and fix assert in regression test exit
  • base_local_planner: The local plan published by the planner for visualization purposes now includes orientation information
  • Fixed CMake deprecation warnings across all packages


ROS 0.9 Released

| No Comments | No TrackBacks

ROS 0.9

ROS 0.9 has been released! Our focus with this release was bringing ROS closer to 1.0 status. ROS has been undergoing user testing as part of our Milestone 3 efforts, which has allowed us to make improvements to numerous tools, clarify error messages, and fix bugs. The most notable change with this release is that we have officially ended support for the deprecated ros::Node API in roscpp. We have also introduced a new "bool" type for ROS message types.

There were many other changes with this release as we work to improve and finalize the ROS feature set. You can find a complete list in the changelist.

You can download a tarball of the release, though we recommend that you start with the ROS installation instructions instead.

image_common 0.5.0

| No Comments | No TrackBacks


image_common-0.5.0 has been released. This release removes all APIs deprecated in 0.2.0. The remaining APIs are stable. If you are still using ImagePublisher or ImageSubscriber, take a minute to update your code; see image_transport's Quickstart Guide or Tutorials for proper usage.

This is the first release to pass documentation review.


  • image_transport:
    • Removed all deprecated functions and classes.
    • Fixed compilation bugs in ImageTransport::subscribeCamera().
    • Improved output from list_transports.
  • camera_calibration_parsers:
    • Removed deprecated functions.


common 0.6.0 released

| No Comments | No TrackBacks


common-0.6.0 has been released. This is mostly a maintenance update to do the planned removal of the yaml-cpp package in favor of the yaml_cpp package introduced in 0.5.0. Below is the full changelist.

Major changes

  • yaml-cpp has been removed (use yaml_cpp instead)

Minor changes * actionlib * Removing deprecated version of SimpleActionClient::sendGoal. This only affects users who register a doneCallback when calling sendGoal * Shortened names of the python and C++ SimpleActionClient wait* calls * Switched internal references of deprecated ros::SingleSubscriberPublisher::getSubscriberCallerID to getSubscriberName * Shortened wait* method names in the python action client * waitForActionServerToStart and waitForGoalToFinish are now waitForServer and waitForResult. #3059 * Moved actionlibtutorials out of common and into rospkgtutorials * xacro * Added xacro.cmake file that exports new xacroaddxacrofile() macro, #3020


geometry 0.4.0 released

| No Comments | No TrackBacks


geometry-0.4.0 has been released. The main new feature in this release is an optional callback that has been added for when messages are dropped by the tf::MessageFilter. Debugging messages have also been updated for greater readability.

Major Changes

  • Make the error messages that tf prints more user friendly.
  • Add a failure callback to tf::MessageFilter

Minor Changes

  • bug fix: message notifier should listen to '/tf' and '/tf_message' topics.


navigation 0.5.0 released

| No Comments | No TrackBacks

navigation 0.5.0 has just been released. All packages in the navigation stack have now reached "doc review" status, which means that end-user documentation for all appropriate APIs has been documented and peer reviewed. Those wishing to use the navigation stack on their own robots are encouraged to use this release as the APIs are both stable and documented for us.

New Features
  • base_local_planner: Added "y_vels" parameter to allow holonomic robot users to control the y velocities that their robot will explore
  • All packages in the stack have passed documentation reviews
Minor Updates
  • robot_pose_ekf: Make parent-child tags in internal buffer consistent. Update to new tf::StampedTransform data type.
  • costmap_2d: Fixed many deprecation warnings resulting from new release of geometry stack
  • base_local_planner: Fixed many deprecation warnings resulting from new release of geometry stack
  • move_base: Fixed many deprecation warnings resulting from new release of geometry stack
  • base_local_planner: The min_vel_th, max_vel_th, and min_in_place_vel_th parameters have now been removed, update to max_rotational_vel and min_in_place_rotational_vel
  • costmap_2d The "inscribed_radius" and "circumscribed_radius" parameters have now been removed, switch to the "robot_radius" parameter or the "footprint" parameter.
Bug Fixes
  • costmap_2d: Fixed clearing the robot footprint of obstacles for circular robots.
Package Moves
  • All the tutorials for the navigation stack have moved to the ros_pkg_tutorials stack.


robot_model 0.6.0 released

| No Comments | No TrackBacks


robot_model 0.6.0 has been released. This is the first "stable" release of the robot model stack. This release removed the last pieces of deprecated functionality in urdf and kdl_parser.


  • Removed deprecated functionality from urdf:
    • parent_link shared pointer of link is removed
    • dom_parser is removed
    • treeFromRobotModel is removed
  • The resource_retriever got new tutorials.
  • The robot_model stack is documentation-reviewed.


robot_model 0.5.0 released

| No Comments | No TrackBacks


I am announcing the release of the robot_model.0.5.0. stack. The functionality of the kdl parser that was deprecated in the 0.3.0 release is removed in this release. To fix a memory leak in the urdf package, accessing the parent of a Link has changed, but this release maintains backwards compatibility.


  • Removed deprecated functionality form Kdl parser:
    • xml_parser is removed
  • Deprecated in urdf:
    • linkparent member variable in Link class is deprecated and replaced by the getParent() method. Once the linkparent member variable is completely removed (in the next release) the memory leak Ticket #2680 will be fixed.


common 0.5.0 released

| No Comments | No TrackBacks


common-0.5.0 has been released. There is one major change. The yaml-cpp package is being renamed yaml_cpp. For backwards compatability the old version of yaml-cpp will remain in the system until the next release which is targeted for next Wednesday.

Porting to the new package only requires changing the dependency in the manifest. Everything else is the same.

Major changes

  • yaml-cpp renamed to yaml_cpp as dashes are not allowed in package names

Minor changes

  • actionlib
    • Deprecating SimpleActionClient's getTerminalState() and getGoalState(). Replaced by getState()
    • SimpleActionClient's SimpleDoneCallback now provides a SimpleClientGoalState argument instead of a TerminalState. The TerminalState version is thus deprecated.
    • Deprecating the python SimpleActionClient's get_terminal_state() and get_goal_state(). Replaced by get_state()
    • The done callback passed to Python's SimpleActionClient now takes the terminal state as one of the enumerated constants in actionlib_msgs/GoalStatus


robot_model 0.4.0 released

| No Comments | No TrackBacks


I am announcing the release of the robot_model.0.4.0. stack. Since the last release, we've worked hard to review the API and documentation of all packages in this stack. This resulted in a lot of extra documentation and tutorials, and some minor API changes in the kdl parser.


  • API and Doc review: all packages in the robot_model stack have been through our API and Documentation review process.
    • Kdl parser
    • Deprecated xml_parser
    • Deprecated treeFromRobotModel method (replaced by treeFromUrdf). The deprecated functionality will be removed in the next release cycle.
    • URDF
    • Updated XML format documentation
    • New beginner tutorials to create and parse urdf files
    • Add command line tool to verify urdf file


image_common 0.3.0

| No Comments | No TrackBacks


This release is mainly for final testing before the 0.9.0 release. We expect no significant changes between 0.3.0 and 0.9.0 other than removal of already deprecated APIs. A reminder: please switch from image_transport::ImagePublisher and image_transport::ImageSubscriber to image_transport::Publisher and image_transport::Subscriber.

Changes in this release are primarily of interest to image_transport plugin developers; see the full changelist.

A couple notes on compatibility with outside packages (trunk versions):

  • compressed_image_transport has been updated for compatibility with post-0.1 image_common.
  • image_view now allows you to specify a transport name on the command line. The default transport is "raw".


  • image_transport:
    • Fixed bug in SimplePublisherPlugin making it unusable for non-trivial transports
    • Added internal subscription callback support to SimplePublisherPlugin
    • Parts of the documentation have been moved to the wiki


geometry 0.3.0 released

| No Comments | No TrackBacks


There are a number of changes. Most notably the usage of frame_id and parent_id, in Transform datatypes,have changed to child_frame_id and frame_id respectively to be consistent with all other data types.

There have been a few modifications to the bullet API. The goal is to converge onto bullet's API without patches. To get there please read about the patches applied.

Also, in geometry-0.2.0, the topic on which tf operates was changed from /tf_message to /tf. The library will continue listening on the old topic name for backwards compatibility.

Major Changes

  • tf:
    • Usage of tf::Stamped deprecated in favor of tf::StampedTransform
    • parent_id -> frame_id
    • frame_id -> child_frame_id
    • transform_sender replaced by static_transform_publisher to allow backwards compatibility with this change
  • bullet:
  • Updated patches. Highlights below.
  • Deprecated set/getEulerZYX methods
  • Added get/setRPY methods
  • cleaned up documentation
  • various bug fixes

Minor Changes

  • clean up of ~params
  • removal of deprecated Node API usage
  • tf_echo printouts cleaner
  • tf_monitor is working and has better display


With the releases of visualization 0.1 and robot_model 0.1, we are near the end of our core, robot-generic stack releases for ROS. With the initial release of pr2_mechanism 0.1, we are beginning our transition into PR2-specific capabilities. The 0.1 designation indicates that these stacks are still undergoing user testing and may have some API instability.

  • visualization contains the important rviz visualization tool. rviz is a 3D visualization environment that shows everything from the position of individual robot joints to the 3D sensor data to custom visualization markers for algorithms.
  • robot_model contains packages relating to representing information about the robot itself, including the robot description (urdf) and the current pose state of the robot (robot_state_publisher).
  • pr2_mechanism provides the lower-level software APIs for controlling the hardware of the PR2 robot.
visualization_common has also been updated to 0.9.1.



The slam_gmapping and navigation stack releases have been updated as part of today's release of the perception-related stacks.


Today we are releasing many of our perception-related libraries for ROS: image_common, image_pipeline, laser_pipeline, and opencv. All of these releases are 0.1 releases, which means that they are currently being user-tested for potential improvements.

  • image_common provides lower-level image-related dependencies, including image_transport, which provides a plugin architecture for transporting raw and compressed image data.
  • image_pipeline and laser_pipeline have very similar capabilities. laser_pipeline processes sensor data from laser range finders and can turn it into 3D point clouds. image_pipeline processes sensor data from mono and stereo cameras and can perform common image-processing tasks, like rectification and color processing. In the case of stereo, it can output 3D disparity images. These 3D representations can then be used in higher-level libraries.
  • opencv is a ROS wrapper for the popular OpenCV computer vision toolkit. OpenCV is heavily used in higher-level libraries to perform many common perception-related tasks. The version we are using in ROS is a pre-release version of the upcoming OpenCV 2.0 release.

driver_common.png joystick_drivers.png imu_drivers.png

Today we are releasing ROS Stacks representing many of the drivers we are supporting, as well as our common driver and diagnostics infrastructure. These drivers are being released with the 0.1 designation as we are currently performing user testing on them to make sure that they are easy-to-use and provide proper diagnostics information.

  • diagnostics: diagnostics provides a common infrastructure for reporting, aggregating, and analyzing diagnostic information from hardware and other sources.
  • driver_common: driver_common provides a common driver infrastructure that supports driver diagnostics and reconfiguration.
  • imu_drivers: 3dmgx2 IMU driver (based on the driver in Player).
  • joystick_drivers: joystick_drivers contains drivers for generic linux joysticks, the Playstation 3 SIXAXIS joystick and for 3Dconnection 3D input devices.
  • laser_drivers: laser_drivers contains Hokuyo drivers (SCIP2.0-compliant, 04LX) as well as a ROS wrapper for sicktoolbox (SICK LIDAR devices).
  • sound_drivers: driver for playing sounds over ROS Topics.


common_msgs 0.9.1

| No Comments | No TrackBacks

As part of our release of common and geometry, common_msgs has been updated to 0.9.1. This update contains actionlib_msgs, which are part of the actionlib API in common.


common.png geometry.png navigation.png

Today we are releasing our foundation ROS Stacks: Common and Geometry. We are also releasing initial versions of Navigation and Slam Gmapping, which are a critical pieces of functionality that have been heavily tested over the past year. Most recently, the Navigation Stack passed the Milestone 2 requirement of 26.2 miles of error-free indoor navigation. All of these stacks are being released with the 0.1 designation: we intend to have stable releases of each of these soon, but due to their central role in any robot software system, they are undergoing heavy user testing and their documentation is being improved.

We are also working on a new install system for ROS to handle automated installation of these stacks.

Summary of stacks:

  • common: Common contains ROS Packages that have common use across a wide variety of functional areas, including C++ plugins, a robot action API, and wrappers for bfl, yaml-cpp and tinyxml.
  • geometry: Geometry's most importantly provides the tf package, which defines how ROS nodes communicate about coordinate frames of the robot. Geometry also contains ROS wrappers for KDL, Eigen, and Bullet.
  • slam_gmapping: slam_gmapping contains the gmapping package, which is a ROS wrapper around GMapping from the OpenSLAM project. Gmapping enables you to use laser range data to construct maps.
  • navigation: The Navigation Stack provides autonomous navigation capabilities to differential drive and holonomic wheeled robots. It has been heavily tested on the PR2 robot within an indoor office environment.

As you can see from the descriptions above, these stacks incorporate code from many other open source projects, including Orocos, Eigen, Bullet, OpenSLAM, Poco, yaml-cpp, Player, and tinyxml. We are grateful to these projects for providing useful libraries to build upon.


ROS 0.7.2 Released

| No Comments | No TrackBacks

ROSROS 0.7.2 has been released (SVN tag)! This is a patch release that fixes various issues in preparation for our upcoming ROS Stack releases. We have also been focusing on improving error messages and performance based on ongoing user testing. The detailed change list is below.

-- Your friendly neighborhood ROS team


  • Fixed subscription callbacks to not starve other callbacks in a certain case.
  • Doxygen fixes for deprecated functions that were not pointing at the correct new locations.
  • Fixed `_param:=value` on anonymous nodes when `__name:=` was specified
  • Fixed race condition that would cause a "call to empty boost::function" exception


  • fixed bug with Time objects jumping to zero with simulated time on publish in certain cases
  • bug fix to numpy_msg
  • suppress error message stack trace for common case of connection refused


  • Fixed bug where checkbag incorrectly reports that a bag is up to date if it has moved without md5sum changing
  • Fixed bug where messages including messages from other packages where not populating migration rules fully
  • Stop displaying redundantly auto-generated rules boundary conditions where multiple scenarios lead to the same parallel generation
  • Programmatic use of checkbag/fixbag within a single script now cache initial load of message migrator. This gives huge savings when checking/fixing large numbers bags in batch, such as during testing.
  • Added "" script which operates on multiple bags more easily and efficiently


  • fixed major issues with generate_dynamic and Header messages
  • better error message in generate_dynamic
  • better cleanup of dynamically generated .py / .pyc files in roslib
  • Fixed manifest for rosrecord so external users can use librosrecorder now that it's been broken out from just a header.

roslib: fixed cache use of ROS_PACKAGE_PATH when it is not set
rostopic: bug fix to bw command and better error reporting
roswtf: numerous updates, including better offline behavior, and fix to duplicate node rule
topic_tools: export MuxSelect header
rosmsg: bug fix to indentation of constants with rosmsg show
roslaunch-deps: better handling of bad xml
rostest: suppress output from master during tests

  • Fixed assertion on page up/arrow up when the number of messages in the list control is 0
  • Fixed high CPU utilization when no new messages have arrived

rosdep: festival, libusb (r5530)
rosstack: bug fixes so that it works again, and handles unversioned stack dependencies. uses ROS_ROOT and ROS_PACKAGE_PATH if ROS_STACK_PATH is not defined. Expose librosstack via package manifest and moving rosstack.h into the package include directory

ROS 0.7.1 Released

| No Comments | No TrackBacks

ROSROS 0.7.1 has been released! This is a patch release, with the bulk of changes addressing regressions that occurred with the 0.7.0 update. If you have experienced issues with rosrecord, roslaunch, or rxplot, you may wish to install this update.


  • roslaunch: fix to printerrlog issue in
  • rosdep: mplement a one-step 'install' argument
  • rosrecord:
    • fix in time scaling related to playback of multiple bags.
    • fix in rpath being cleared on install to $ROS_ROOT/bin
    • fixed bug over-aggressively resizing a message buffer
  • rostopic: better error message if topic type is invalid and minor fixes
  • rxplot:
    • added missing time import
    • fix bad wxwidgets swig wrapper import
    • bug fixes to errors when invalid topic name or spec are given
  • rosbuild:
    • fix to dependency management for auto-generated source files
    • very probable fix for the delete-a-file problem
  • rospy: ignore spurious exception caused in receive_loop during interpreter shutdown
  • rosemacs: minor updates due to rostopic changes
  • rosdep: pygame, python-clearsilver, debian updates, qt3, log4cxx (OS X)
  • rosconfig: fix bug that was raising an exception in all non-svk installs

ROS 0.7 Released

| No Comments | No TrackBacks

ROS 0.7 has been released. The 0.7.x series introduces many new features and bug fixes. The two biggest changes are "Publisher latching" as well as the deprecation of the old roscpp "Node" API.

Publisher latching: Publisher latching lets you automatically send the last message published to new subscribers. This has many uses cases. For example, instead of writing a map Service, you could have a map Topic. A Topic is preferable as you can then record the map data using rosrecord. Another use for publisher latching is to reduce the publication rate for data that is slowly changing, as you can now more easily ensure that new subscribers will receive the latest data automatically. Previously this was possible using subscriber callbacks, but this streamlines implementations. By default, rostopic pub now latches, so you can use it to quickly 'latch' a value into the ROS Computation Graph.

Node API deprecated: roscpp's Node API is now deprecated in favor of the NodeHandle API. Some of the NodeHandle methods have been deprecated as well. Please update your code as the Node API will be removed in future releases. Please see the notes below for specific details on NodeHandle methods that have been deprecated.

For a more detailed list of changes, please see the changelist.

To download this release, please visit the download page.

We've also put together a new tutorial to introduce the ROS concepts and associated command-line tools. This is still a work-in-progress, but feel free to check it out.

ROS 0.6.1 Released

| No Comments | No TrackBacks

ROSROS 0.6.1 has been released. This is a minor bug-fix update. Updating is not essential unless you've encountered the problems mentioned below.


  • rosrecord: executable permission was not set. If you need to use script and you do not want to download the 0.6.1 release, you can simply set the executable bit manually by running:
    chmod +x `rospack find rosrecord`/scripts/
  • roscpp:
    • gcc 4.4 support
    • Added operator= overload on NodeHandle
    • Bug fix for serializing array of times
  • roslisp
    • Bug fix for dealing with lookup-hostname-ip-address
    • Bug fix for fixed-size arrays

ROS 0.6 Released

| No Comments | No TrackBacks

ROS 0.6

ROS 0.6.0 has been released! Our big goals for this release were to make bag files more robust, add in UDP transport for C++ users and prepare for our upcoming releases of stacks (e.g. navigation). With previous releases, bag files would become unreadable if the messages they were recorded from were changed. The new bag file format enables bag files to always be read and comes with tools for migrating them in the event of changes. As a result of these updates, all of your existing bag files will need to be updated. There are more instructions on our more detailed change list.

Related to our bag file changes, we've also changed our md5sum calculation for message versions to make it easier to move, rename, and add comments to messages. You can now perform these changes without altering the md5sum.

We've added in UDP as an experimental transport to our C++ library. This UDP transport is currently point-to-point and targeted at low-latency applications for ROS, such as teleoperation.

Another major update is the introduction of the searchParam API to the Parameter Server. In the past, it was difficult to push node down into child namespaces and still have them share common parameters. For example, you may wish to set a parameter like the robot description in a parent namespace and have all children easily read from it. The searchParam API solves this problem by allowing you to search for a parameter in parent namespaces, returning the parameter key that is closest to your node's namespace.

There are many other updates in this release, so please consult the detailed list of changes. You can also consult our roadmap to get a preview of the remaining features we are planning for ROS as we move towards a 1.0 release.

ROS 0.5.3 Released

| No Comments | No TrackBacks

ROSROS 0.5.3 has been released, which is a minor update to our ROS 0.5 release. Most of the changes in this release address installation and build compatibility issues. We are in the process of transitioning our build and installation process to better support a broader range of Linux platforms as well as provide for more automated installation. Release notes are below.

Change List

  • rosbuild: small fixes to support CMake 2.4.6
  • roslaunch: add dependency on rosout
  • rospy: bug fix to private command-line parameters
  • rosdep: updated dependency database with Debian package names
  • rosconfig: beginnings of a fully-automated installation method

ROS 0.5.1 Released

| No Comments | No TrackBacks

ROSROS 0.5.1 has been released, which is a minor update to our ROS 0.5 release. This release includes enhancements to roscpp, such as timer callbacks, that build upon the recently releaased Node Handle API. There have also been changes to roslaunch that group together log files from the same launch as well as changes to rospy to prepare for upcoming changes to "bag" files. Release notes are below, or you can view the full list of changes.

Change List

  • roslaunch: changed location of log files so that logs from the same launch are collected together in the same directory. This makes it easier to find results of a run and prevents log filename recycling.
  • roscpp
    • Timer callbacks allow you to receive a callback at a specified rate. See the "timers" tutorial in the roscpp_tutorials package.
    • Transport hints let you specify TCP_NODELAY per subscription.
    • All nodes now advertise "~get_loggers" and "~set_logger_level" services, which can be called through the rosservice tool.
    • Publish calls should no longer take a large amount of time (spikes up to 100ms were seen).
    • Subscriptions created through the NodeHandle API can no longer block the ROS thread. Queue size should now behave properly.
    • Added Publisher::getNumSubscribers() call
  • rospy
    • refactored much of the genmsg_py code to add dynamic message generators, fix handling of uint8[] types, fix handling of string constants, and add more tests.
    • bug fix to rospy.myargv() handling
    • get_time/get_rostime now throw an exception if init_node has not been called

  • rxtools: New rxloggerlevel tool which lets you change the logger levels of roscpp nodes while they are running
  • rostopic: rostopic hz now prints "no new messages" if no new messages have been received since last print
  • rosmsg: rosmsg show now properly includes constants
  • rospack
    • profile output marks directories that contain no manifest
    • recover from bad cache location of a package
  • rosbuild: recover from bad cache location of rospack
  • rosrecord: rosplay now complains clearly and exits if asked to play a non-existent .bag file

Cinco de ROS: ROS 0.5 Release

| No Comments | No TrackBacks

ROS 0.5

Time to celebrate! ROS 0.5 is here! You can download it from

We've been working furiously on ROS to incorporate new features and APIs to make ROS easier to use and more robust. The biggest change is the introduction of the roscpp "Node Handle" API, which is based on months of feedback from the ROS community and our own internal testing. There's also a new, experimental roswtf tool, which we hope to evolve into a powerful system-wide diagnosis tool. To find out more about this release, please read the list of changes.

This release also marks the start of our 'stack' releases. In the coming weeks, look for our first release of ROS Stacks, which are collections of ROS packages that are now mature enough for release to a wider audience. One of the first stacks that we will release will be the Navigation stack, which was heavily tested and refined during Milestone 1.

ROS 0.4 Release

| No Comments | No TrackBacks

ROS 0.4

ROS 0.4 ("Mango Tango") has been released at SourceForge. ROS is the "Robot Operating System" that is the basis of our PR2 robot software development. If you're new to ROS, you can head over to the ROS wiki, where you'll find an overview, installation instructions, tutorials, and more.

Our first milestone was a major test of the robustness of ROS, requiring multiple days of continued operation of a 2D navigation stack with many software components interacting across multiple computers. We now feel that ROS is ready for an official release to the wider robotics community. Although this is an 0.4 release, we are committed to a stable API as we march towards a 1.0 release. For you early adopters that have been using ROS via Subversion, we appreciate your patience through the changes we have been making these past several weeks and hope that you will find this release a stable platform on which to continue developing.

This is the first of many releases of ROS in the coming months. In addition to future updates, we will be working on releasing parts of our Personal Robots software stack. We hope that you will find these drivers and algorithms useful in building robotics applications and accelerating research. Please feel free to give us feedback on this release on our ros-users mailing list or by filing feature requests (or bugs) in our ticket system.

ROS grew out of work at Stanford University, and contains contributions from community members around the world. It is released under a BSD license, making it available for both commercial and non-commercial use.

Find this blog and more at

Monthly Archives

About this Archive

This page is an archive of recent entries in the releases category.

Find recent content on the main index or look in the archives to find all content.