Dmitry Berenson | 18 Apr 22:03 2014

Datalink Toolkit for Remote Operation with High-Latency and Low-Bandwidth Connections

The ARC Lab at WPI is releasing the Datalink Toolkit ROS package, designed to for remote operation of a robot over a high-latency and low-bandwidth datalink. The package was developed and extensively tested as part of the DARPA robotics challenge, though it is not specific to a type of robot.

The package allows the user to easily set up relays and compression methods for a single-master system. These relays avoid duplicating data sent over the datalink while compressing common datatypes (i.e. point-clouds and images) to minimize bandwidth usage.
The toolkit includes both message-based and service-based relays so that data can be sent on-demand or at a specified frequency. The service-based relays are more robust in low-bandwidth conditions, guaranteeing the synchronization of camera images and camera info messages, and allow more reconfiguration while running.

The key features of the package are:
- Generic relays with integrated rate throttling for all message types
- Dedicated relays with rate throttling for images and pointclouds
- Generic service-based relays with integrated rate throttling for all message types
- Dedicated service-based relays with integrated rate throttling for images and pointclouds
- Image resizing and compression using methods from OpenCV and image_transport
- Pointcloud voxel filtering and compression using methods from PCL, Zlib, and other algorithms. (Note: pointcloud compression is provided in a separate library that can be easily integrated with other projects)
- Launch files for easy use of the datalink software with RGBD cameras
- Works with ROS Hydro

Overall performance:
- Reliable data transfer for a wide range of bandwidths and latencies (e.g. at DRC Trials: 1Mb/s - 100 Kb/s bandwidth, 100ms - 1000ms latency)
- Pointcloud compression >8x depending on compression algorithm (without voxel filtering)
- Pointcloud compression >20x depending on compression algorithm (with voxel filtering)
- Image compression equivalent to image_transport (without image resizing) or better (with resizing)

Performance comparison with ROS for image transfer:
- 1.5x more images/second at 1Mb/s (grayscale image size 320x240)
- 2x more images/second at 100Kb/s (grayscale image size 320x240)
- 3x more images/second at 50Kb/s (grayscale image size 320x240)


For more information, please see the wiki here:

Get the package from our git repository here:



Dmitry Berenson
Assistant Professor
Robotics Engineering Program
Computer Science Department
Worcester Polytechnic Institute
<div><div dir="ltr">
<div>The ARC Lab at WPI is releasing the Datalink Toolkit ROS package, designed to for remote operation of a robot over a high-latency and low-bandwidth datalink. The package was developed and extensively tested as part of the DARPA robotics challenge, though it is not specific to a type of robot.</div>

<div><br></div>
<div>The package allows the user to easily set up relays and compression methods for a single-master system. These relays avoid duplicating data sent over the datalink while compressing common datatypes (i.e. point-clouds and images) to minimize bandwidth usage.<br>
</div>
<div>The toolkit includes both message-based and service-based relays so that data can be sent on-demand or at a specified frequency. The service-based relays are more robust in low-bandwidth conditions, guaranteeing the synchronization of camera images and camera info messages, and allow more reconfiguration while running.</div>

<div><br></div>
<div>The key features of the package are:<br>
</div>
<div>- Generic relays with integrated rate throttling for all message types<br>
</div>
<div>- Dedicated relays with rate throttling for images and pointclouds</div>

<div>- Generic service-based relays with integrated rate throttling for all message types</div>
<div>- Dedicated service-based relays with integrated rate throttling for images and pointclouds</div>
<div>- Image resizing and compression using methods from OpenCV and image_transport</div>

<div>- Pointcloud voxel filtering and compression using methods from PCL, Zlib, and other algorithms. (Note: pointcloud compression is provided in a separate library that can be easily integrated with other projects)</div>

<div>- Launch files for easy use of the datalink software with RGBD cameras</div>
<div>- Works with ROS Hydro</div>
<div><br></div>
<div>Overall performance:</div>
<div>- Reliable data transfer for a wide range of bandwidths and latencies (e.g. at DRC Trials: 1Mb/s - 100 Kb/s bandwidth, 100ms - 1000ms latency)<br>
</div>
<div>- Pointcloud compression &gt;8x depending on compression algorithm (without voxel filtering)</div>
<div>- Pointcloud compression &gt;20x depending on compression algorithm (with voxel filtering)</div>
<div>- Image compression equivalent to image_transport (without image resizing) or better (with resizing)</div>

<div><br></div>
<div>Performance comparison with ROS for image transfer:</div>
<div>- 1.5x more images/second at 1Mb/s (grayscale image size 320x240)<br>
</div>
<div>- 2x more images/second at 100Kb/s (grayscale image size 320x240)</div>

<div>- 3x more images/second at 50Kb/s (grayscale image size 320x240)</div>
<div><br></div>
<div><br></div>
<div>
<div>For more information, please see the wiki here:</div>
<div><a href="https://github.com/WPI-ARC/datalink_toolkit/wiki">https://github.com/WPI-ARC/datalink_toolkit/wiki</a></div>

<div><br></div>
<div>Get the package from our git repository here:</div>
<div><a href="https://github.com/WPI-ARC/datalink_toolkit">https://github.com/WPI-ARC/datalink_toolkit</a></div>
</div>
<div><br></div>
<div><br></div>
<div>

<br>
</div>
<div>Dmitry Berenson</div>
<div>Assistant Professor</div>
<div>
<div>Robotics Engineering Program<br>
</div>
<div>Computer Science Department</div>
<div>Worcester Polytechnic Institute</div>
</div>
<div><a href="http://users.wpi.edu/~dberenson/">http://users.wpi.edu/~dberenson/</a></div>

</div></div>
Daniel Stonier | 18 Apr 02:56 2014
Picon

Re: ROS J Turtle Naming Brainstorming




On 18 April 2014 05:28, Mike Purvis <mpurvis <at> clearpathrobotics.com> wrote:
Jade can still be a turtle, even if it's not an actual species: https://www.google.ca/search?q=jade+turtle&tbm=isch


In asia, Jade turtles have alot of strong connotations about endurance and longevity...something ROS is starting to grow into.

Daniel.
 
I like the sound of ROS Jade.


On 17 April 2014 16:21, William Woodall <william-GsQoM64suCGGJGYlWa3Ukdi2O/JbrIOy@public.gmane.org> wrote:
+0 on Jagged, it seems to imply some negative connotation about quality to me, like "rough around the edges". Even if it is "rough around the edges" :p we shouldn't name it as such.

I think Jade Turtle, ROS Jade is nice a nice adjective too.

On Thu, Apr 17, 2014 at 1:07 PM, Patrick Goebel <patrick-atf/XkzOxv5AfugRpC6u6w@public.gmane.org> wrote:
+1 Jagged

+1 to Bill's post in general (as another geezer...)

--patrick


On 04/17/2014 11:55 AM, Bill Smart wrote:
+1 Jagged
-1e10 Judo
still -1 for anything that's not actually a turtle

I'm a geezer, and fear change.  However, here are a couple of thoughts:
- we want companies to adopt ROS.  They will be significantly less likely to do so if the name is overly cute

We want something not too silly, but if we aren't having some fun with it, what the point? Also Ubuntu seems to do just fine on the business front with a similar naming pattern.
 
- we will have even less adoption if there's a whiff of legal action (Jedi Turtle, for instance) possible.

Obviously we aren't going to pick anything where legal action might be a concern, which means, as sad as I am to say it, Jedi is pretty much off the table.
 
- I personally think that consistency outweights cool (of course, I'm old and British)

We've done a pretty good job at staying on theme, but sometimes it's hard when there is only one or two actual turtle related names.

I'd say just as important as being turtle related, if not more important, is that the code name is short, easy to spell and type, recognizable, and searchable. That's mostly why we ended up with Indigo in the last go around.
 

I've done judo since the 70's (no, really, since the 70s).  While I don't think it's a great name for J-turtle, over the past year ROS *has* thrown me to the mat, sat on me, and forced me to submit more than once, so maybe it *is* a viable option.

-- Bill


_______________________________________________
ros-users mailing list
ros-users <at> lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users



_______________________________________________
ros-users mailing list
ros-users <at> lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users



_______________________________________________
ros-users mailing list
ros-users-g9ZBwUv/Ih8gsBAKwltoeQ@public.gmane.org
http://lists.ros.org/mailman/listinfo/ros-users




--
Phone : +82-10-5400-3296 (010-5400-3296)
Home: http://snorriheim.dnsdojo.com/
<div><div dir="ltr">
<br><div class="gmail_extra">
<br><br><div class="gmail_quote">On 18 April 2014 05:28, Mike Purvis <span dir="ltr">&lt;<a href="mailto:mpurvis@..." target="_blank">mpurvis <at> clearpathrobotics.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote"><div dir="ltr">Jade can still be a turtle, even if it's not an actual species:&nbsp;<a href="https://www.google.ca/search?q=jade+turtle&amp;tbm=isch" target="_blank">https://www.google.ca/search?q=jade+turtle&amp;tbm=isch</a><div>
<br>
</div>
</div></blockquote>
<div><br></div>
<div>In asia, Jade turtles have alot of strong connotations about endurance and longevity...something ROS is starting to grow into.</div>
<div><br></div>
<div>Daniel.</div>
<div>&nbsp;</div>
<blockquote class="gmail_quote">
<div dir="ltr">
<div></div>

<div>I like the sound of ROS Jade.</div>
</div>
<div class="HOEnZb"><div class="h5">
<div class="gmail_extra">
<br><br><div class="gmail_quote">On 17 April 2014 16:21, William Woodall <span dir="ltr">&lt;<a href="mailto:william@..." target="_blank">william@...</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">
<div dir="ltr"><div class="gmail_extra">
<div class="gmail_quote">+0 on Jagged, it seems to imply some negative connotation about quality to me, like "rough around the edges". Even if it is "rough around the edges" :p we shouldn't name it as such.</div>

<div class="gmail_quote"><br></div>
<div class="gmail_quote">I think Jade Turtle, ROS Jade is nice a nice adjective too.</div>
<div class="gmail_quote"><br></div>
<div class="gmail_quote">
<div>On Thu, Apr 17, 2014 at 1:07 PM, Patrick Goebel <span dir="ltr">&lt;<a href="mailto:patrick <at> pirobot.org" target="_blank">patrick@...</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">+1 Jagged<br><br>
+1 to Bill's post in general (as another geezer...)<span><br><br>
--patrick</span><div>
<br><br>
On 04/17/2014 11:55 AM, Bill Smart wrote:<br><blockquote class="gmail_quote">
+1 Jagged<br>
-1e10 Judo<br>
still -1 for anything that's not actually a turtle<br><br>
I'm a geezer, and fear change. &nbsp;However, here are a couple of thoughts:<br>
- we want companies to adopt ROS. &nbsp;They will be significantly less likely to do so if the name is overly cute<br>
</blockquote>
</div>
</blockquote>
<div><br></div>
</div>
<div>We want something not too silly, but if we aren't having some fun with it, what the point? Also Ubuntu seems to do just fine on the business front with a similar naming pattern.</div>

<div>

<div>&nbsp;</div>
<blockquote class="gmail_quote"><div><blockquote class="gmail_quote">

- we will have even less adoption if there's a whiff of legal action (Jedi Turtle, for instance) possible.<br>
</blockquote></div></blockquote>
<div><br></div>
</div>
<div>Obviously we aren't going to pick anything where legal action might be a concern, which means, as sad as I am to say it, Jedi is pretty much off the table.</div>

<div>

<div>&nbsp;</div>
<blockquote class="gmail_quote"><div><blockquote class="gmail_quote">

- I personally think that consistency outweights cool (of course, I'm old and British)<br>
</blockquote></div></blockquote>
<div><br></div>
</div>
<div>We've done a pretty good job at staying on theme, but sometimes it's hard when there is only one or two actual turtle related names.</div>

<div><br></div>
<div>I'd say just as important as being turtle related, if not more important, is that the code name is short, easy to spell and type, recognizable, and searchable. That's mostly why we ended up with Indigo in the last go around.</div>

<div>

<div>&nbsp;</div>
<blockquote class="gmail_quote">
<div>
<blockquote class="gmail_quote">

<br>
I've done judo since the 70's (no, really, since the 70s). &nbsp;While I don't think it's a great name for J-turtle, over the past year ROS *has* thrown me to the mat, sat on me, and forced me to submit more than once, so maybe it *is* a viable option.<br><br>
-- Bill<br><br>
</blockquote>
<br>
</div>
<div><div>
_______________________________________________<br>
ros-users mailing list<br><a href="mailto:ros-users@..." target="_blank">ros-users <at> lists.ros.org</a><br><a href="http://lists.ros.org/mailman/listinfo/ros-users" target="_blank">http://lists.ros.org/mailman/listinfo/ros-users</a><br>
</div></div>
</blockquote>
</div>
</div>
<br><br clear="all"><div>
<div><br></div>-- <br>William Woodall<div>ROS Development Team</div>
<div><a href="mailto:william@..." target="_blank">william@...</a></div>

<div>

<a href="http://williamjwoodall.com/" target="_blank">http://williamjwoodall.com/</a>
</div>
</div>
</div></div>
<br>_______________________________________________<br>
ros-users mailing list<br><a href="mailto:ros-users@..." target="_blank">ros-users <at> lists.ros.org</a><br><a href="http://lists.ros.org/mailman/listinfo/ros-users" target="_blank">http://lists.ros.org/mailman/listinfo/ros-users</a><br><br>
</blockquote>
</div>
<br>
</div>
</div></div>
<br>_______________________________________________<br>
ros-users mailing list<br><a href="mailto:ros-users@...">ros-users@...</a><br><a href="http://lists.ros.org/mailman/listinfo/ros-users" target="_blank">http://lists.ros.org/mailman/listinfo/ros-users</a><br><br>
</blockquote>
</div>
<br><br clear="all"><div><br></div>-- <br>Phone : +82-10-5400-3296 (010-5400-3296)<br>Home: <a href="http://snorriheim.dnsdojo.com/" target="_blank">http://snorriheim.dnsdojo.com/</a><br><div>Yujin R&amp;D: <a href="http://rnd.yujinrobot.com/" target="_blank">http://rnd.yujinrobot.com/<br></a><br>
</div>
</div>
</div></div>
Tully Foote | 17 Apr 21:32 2014

ROS Kong 2014 Speakers Announced

We're happy to announce the lineup of invited speakers for ROS Kong 2014:

We're thrilled to host such an esteemed group of speakers who represent so many different aspects of the Australasian ROS community, from research to product development.

Reminder: the early registration deadline is April 30th.


ROS Kong 2014 Organizing Committee 

roskong-2014-oc <at> osrfoundation.org

<div><div dir="ltr">
<p>We're happy to announce the lineup of invited speakers for&nbsp;<a href="https://events.osrfoundation.org/ros-kong-2014/">ROS Kong 2014</a>:</p>

<ul>
<li>

<a href="http://www.jsk.t.u-tokyo.ac.jp/~k-okada/index-e.html">Kei Okada</a>, University of Tokyo</li>
<li>
<a href="http://www.ict.csiro.au/staff/paulo.borges/">Paulo Borges</a>, CSIRO</li>

<li>
<a href="http://engineering.case.edu/profiles/wsn">Wyatt Newman</a>, Case Western University / University of Hong Kong</li>
<li>
<a href="https://staff.aist.go.jp/n-ando/index.html">Noriaki Ando</a>, METI / AIST</li>

<li>
<a href="https://github.com/stonier">Daniel Stonier</a>, Yujin Robot Innovation</li>
</ul>
<p>

We're thrilled to host such an esteemed group of speakers who represent so many different aspects of the Australasian ROS community, from research to product development.</p>
<p>

Reminder: the early&nbsp;<a href="https://events.osrfoundation.org/ros-kong-2014/#registration">registration</a>&nbsp;deadline is April 30th.</p>
<p>

<br></p>
<p>ROS Kong 2014 Organizing Committee&nbsp;</p>
<p>

<span>roskong-2014-oc</span><span> <at> <a href="http://osrfoundation.org">osrfoundation.org</a></span></p>

</div></div>
Dan Greenwald | 16 Apr 17:41 2014

The First LRN ROS Drinks

Calling all London ROS Users! You are warmly invited to the first London Robotics Network "ROS Drinks" on the evening of 23/4/14. Put another way, come and meet up for beer, food and talking about robots.

We thought should have a regular meetup to talk about ROS and robots in general. This month we'll be at the Craft Beer Co in Angel (55 White Lion Street N1 9PP)
from about 6pm in the back room. 

The pub does food as well as really excellent beers.

Here is the flyer for event on the LRN group.


Feel free to contact me (Dan - dg-JJwpZlUREJ7ZI5Z/Ik8r6w@public.gmane.org) for more info/any questions.

Hope to see you there.

Shadow Robot Company Ltd.
251 Liverpool Road, N1 1LX, UK
Registered Number 3308007 (England & Wales)

RoNeX - Building Robots with ROS Made Easy 
<div>
<div dir="ltr">
<div>Calling all London ROS Users! You are warmly invited to the first London Robotics Network "ROS Drinks" on the evening of 23/4/14. Put another way, come and meet up for beer, food and talking about robots.</div>
<div><br></div>
<div>We thought should have a regular meetup to talk about ROS and robots in general. This month we'll be at the Craft Beer Co in Angel (55 White Lion Street N1 9PP)</div>
<div>from about 6pm in the back room.&nbsp;</div>
<div><br></div>
<div>The pub does food as well as really excellent beers.<br>
</div>
<div><br></div>
<div>Here is the flyer for event on the LRN group.</div>
<div><br></div>
<div><a href="https://connect.innovateuk.org/web/london-robotics-network/events-view/-/events/14013278?p_p_auth=xGU0Fyax">https://connect.innovateuk.org/web/london-robotics-network/events-view/-/events/14013278?p_p_auth=xGU0Fyax</a></div>
<div><br></div>
<div>Feel free to contact me (Dan - <a href="mailto:dg <at> shadowrobot.com">dg@...</a>) for more info/any questions.</div>
<div><br></div>
<div>Hope to see you there.<br>
</div>
<div><div dir="ltr"><div>
<div><div dir="ltr"><div></div></div></div>
</div></div></div>
</div>

<br>Shadow Robot Company Ltd.<br>251 Liverpool Road, N1 1LX, UK<br>Registered Number 3308007 (England &amp; Wales)<div>
<br><div><span>RoNeX - Building Robots with ROS Made Easy&nbsp;</span></div>
<div>
<a href="http://www.shadowrobot.com/products/ronex/" target="_blank">http://www.shadowrobot.com/products/ronex/</a><br><br>
</div>
</div>
</div>
Vincent Rabaud | 16 Apr 18:07 2014
Picon

improving ROS on wikipedia

Hi all,

I had a look at the wikipedia page for ROS and it is fairly dull:
https://en.wikipedia.org/wiki/Robot_Operating_System
(and it's not even on http://en.wikipedia.org/wiki/Robotics_middleware )

Nothing about :
- the build system
- the fact that parts of it are in distros now (urdfdom in Ubuntu)
- about the companies that use it
- no screenshots (about RViz, rQt, robotWebTools ...)
- the latest stats (7k registered on answers.ros.org)
- ROSCon
...

So please, let's brainstorm here about what is needed and let's contribute to the page !

Vincent
<div><div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>Hi all,<br><br>
</div>I had a look at the wikipedia page for ROS and it is fairly dull:<br><a href="https://en.wikipedia.org/wiki/Robot_Operating_System">https://en.wikipedia.org/wiki/Robot_Operating_System</a><br>
</div>(and it's not even on <a href="http://en.wikipedia.org/wiki/Robotics_middleware">http://en.wikipedia.org/wiki/Robotics_middleware</a> )<br><br>
</div>Nothing about :<br>- the build system<br>- the fact that parts of it are in distros now (urdfdom in Ubuntu)<br>

- about the companies that use it<br>
</div>
<div>- no screenshots (about RViz, rQt, robotWebTools ...)<br>- the latest stats (7k registered on <a href="http://answers.ros.org">answers.ros.org</a>)<br>
</div>
<div>- ROSCon<br>
</div>
<div>...<br>
</div>
<br>
</div>So please, let's brainstorm here about what is needed and let's contribute to the page !<br><br>
</div>Vincent<br>
</div></div>
Vinay Kushwaha | 15 Apr 10:25 2014
Picon

ROS Source Code

Hi,
    I have been working into Robotics and automation. Recently while
working on some project i came across ROS. I found it very helpful
tool. But some of my sensors and devices come only with Windows
driver. I found that ROS windows is still experimental.
    I just wanted to know, how this ROS is implemented in Linux. I
could see ros::init, etc. so on many APIs. Where can i get the source
code for them ? I could find ros.h, init.h but can`t find the
respective C or C++ file.

I have been working on writing OS Agnostic applications. So i was like
if ROS is written in Posix then i already have a way to directly run
it on windows with little effort. This way i would be very happy to
utilize this tool. Once done, same can be used by other people who are
waiting for ROS windows.

Can anyone please help me on the same. So that we can have a great
solution for ROS Windows as well.

Best Regards,
Vinay
Georg Bartels | 15 Apr 09:49 2014
Picon
Picon

Re: ROS J Turtle Naming Brainstorming

+1 for ROS Judo Turtle.

On 04/15/2014 01:56 AM, Jonathan Bohren wrote:
> ROS Judo Turtle.
> 
> 
> On Mon, Apr 14, 2014 at 7:54 PM, Jonathan Bohren
> <jonathan.bohren@...>wrote:
> 
>> Jazz Turtle
>> Juicy Turtle...
>>
>>
>>
>> On Mon, Apr 14, 2014 at 7:46 PM, Daniel Stonier <d.stonier@...>wrote:
>>
>>>  Acknowledging the dearth of potential J turtle names
>>>>>>>
>>>>>>
>>> Do other languages have interesting turtle names starting with a 'J'
>>> sound? Korean has Jangsu (leatherback sea turtle) and Jala (chinese soft
>>> shelled turtle), though neither of them are really 'exciting' to me.
>>>
>>> Daniel.
>>>
>>> _______________________________________________
>>> ros-users mailing list
>>> ros-users@...
>>> http://lists.ros.org/mailman/listinfo/ros-users
>>>
>>>
>>
>>
>> --
>> Jonathan Bohren
>> Laboratory for Computational Sensing and Robotics
>> http://dscl.lcsr.jhu.edu/People/JonathanBohren
>>
>>
> 
> 
> 
> 
> _______________________________________________
> ros-users mailing list
> ros-users@...
> http://lists.ros.org/mailman/listinfo/ros-users
> 

NooTriX | 11 Apr 14:39 2014

Trouble downloading ROS Hydro Virtual Machine

Hi,

Many ROS users reported that they couldn't download the Hydro Virtual Machine.
Indeed we have some problems with our servers. We're trying to fix them and getting things back on track.

Sorry for the inconvenience,
NooTriX Team
--
http://nootrix.com
http://twitter.com/NooTriX
http://www.facebook.com/nootrix

Tully Foote | 11 Apr 04:59 2014

New Indigo Packages

Hi Everyone, 

We bring you another update to the Indigo packages. This update includes 76 new packages and 43 updated packages. Thanks to all the contributors who have released packages. 

Your ROS Release Team


Updates to indigo

Added Packages [76]:
 * ros-indigo-calibration: 0.10.9-0saucy-20140409-0506-+0000
 * ros-indigo-calibration-estimation: 0.10.9-0saucy-20140409-0452-+0000
 * ros-indigo-calibration-launch: 0.10.9-0saucy-20140409-0504-+0000
 * ros-indigo-calibration-msgs: 0.10.9-0saucy-20140409-0450-+0000
 * ros-indigo-camera-calibration: 1.12.2-0saucy-20140408-2220-+0000
 * ros-indigo-concert-service-msgs: 0.7.1-0saucy-20140409-0909-+0000
 * ros-indigo-depth-image-proc: 1.12.2-0saucy-20140408-2216-+0000
 * ros-indigo-diagnostic-aggregator: 1.8.2-0saucy-20140408-1146-+0000
 * ros-indigo-diagnostic-analysis: 1.8.2-0saucy-20140408-1155-+0000
 * ros-indigo-diagnostic-common-diagnostics: 1.8.2-0saucy-20140408-1201-+0000
 * ros-indigo-diagnostic-updater: 1.8.2-0saucy-20140408-1159-+0000
 * ros-indigo-diagnostics: 1.8.2-0saucy-20140408-1205-+0000
 * ros-indigo-ecl: 0.60.0-0saucy-20140408-1853-+0000
 * ros-indigo-ecl-build: 0.60.1-0saucy-20140405-0609-+0000
 * ros-indigo-ecl-command-line: 0.60.9-0saucy-20140408-1827-+0000
 * ros-indigo-ecl-concepts: 0.60.9-0saucy-20140408-1834-+0000
 * ros-indigo-ecl-config: 0.60.1-0saucy-20140406-2222-+0000
 * ros-indigo-ecl-containers: 0.60.9-0saucy-20140408-1841-+0000
 * ros-indigo-ecl-converters: 0.60.9-0saucy-20140408-1836-+0000
 * ros-indigo-ecl-converters-lite: 0.60.1-0saucy-20140406-2226-+0000
 * ros-indigo-ecl-core: 0.60.9-0saucy-20140408-1852-+0000
 * ros-indigo-ecl-core-apps: 0.60.9-0saucy-20140408-1849-+0000
 * ros-indigo-ecl-devices: 0.60.9-0saucy-20140408-1843-+0000
 * ros-indigo-ecl-eigen: 0.60.9-0saucy-20140408-1828-+0000
 * ros-indigo-ecl-errors: 0.60.1-0saucy-20140406-2232-+0000
 * ros-indigo-ecl-exceptions: 0.60.9-0saucy-20140408-1829-+0000
 * ros-indigo-ecl-formatters: 0.60.9-0saucy-20140408-1838-+0000
 * ros-indigo-ecl-geometry: 0.60.9-0saucy-20140408-1843-+0000
 * ros-indigo-ecl-io: 0.60.1-0saucy-20140406-2235-+0000
 * ros-indigo-ecl-ipc: 0.60.9-0saucy-20140408-1833-+0000
 * ros-indigo-ecl-license: 0.60.1-0saucy-20140405-0607-+0000
 * ros-indigo-ecl-linear-algebra: 0.60.9-0saucy-20140408-1842-+0000
 * ros-indigo-ecl-lite: 0.60.1-0saucy-20140406-2242-+0000
 * ros-indigo-ecl-manipulation: 0.60.0-0saucy-20140408-1851-+0000
 * ros-indigo-ecl-manipulators: 0.60.0-0saucy-20140408-1848-+0000
 * ros-indigo-ecl-math: 0.60.9-0saucy-20140408-1836-+0000
 * ros-indigo-ecl-mobile-robot: 0.60.0-0saucy-20140408-1850-+0000
 * ros-indigo-ecl-mpl: 0.60.9-0saucy-20140408-1830-+0000
 * ros-indigo-ecl-navigation: 0.60.0-0saucy-20140408-1852-+0000
 * ros-indigo-ecl-sigslots: 0.60.9-0saucy-20140408-1840-+0000
 * ros-indigo-ecl-sigslots-lite: 0.60.1-0saucy-20140406-2237-+0000
 * ros-indigo-ecl-statistics: 0.60.9-0saucy-20140408-1845-+0000
 * ros-indigo-ecl-streams: 0.60.9-0saucy-20140408-1846-+0000
 * ros-indigo-ecl-threads: 0.60.9-0saucy-20140408-1839-+0000
 * ros-indigo-ecl-time: 0.60.9-0saucy-20140408-1831-+0000
 * ros-indigo-ecl-time-lite: 0.60.1-0saucy-20140406-2240-+0000
 * ros-indigo-ecl-tools: 0.60.1-0saucy-20140405-0614-+0000
 * ros-indigo-ecl-type-traits: 0.60.9-0saucy-20140408-1832-+0000
 * ros-indigo-ecl-utilities: 0.60.9-0saucy-20140408-1838-+0000
 * ros-indigo-ecto-openni: 0.4.0-0saucy-20140404-0618-+0000
 * ros-indigo-ecto-pcl: 0.4.0-0saucy-20140410-1512-+0000
 * ros-indigo-image-cb-detector: 0.10.9-0saucy-20140409-0455-+0000
 * ros-indigo-image-pipeline: 1.12.2-0saucy-20140408-2233-+0000
 * ros-indigo-image-proc: 1.12.2-0saucy-20140408-2226-+0000
 * ros-indigo-image-rotate: 1.12.2-0saucy-20140408-2227-+0000
 * ros-indigo-image-view: 1.12.2-0saucy-20140408-2227-+0000
 * ros-indigo-interval-intersection: 0.10.9-0saucy-20140409-0455-+0000
 * ros-indigo-joint-states-settler: 0.10.9-0saucy-20140409-0500-+0000
 * ros-indigo-laser-cb-detector: 0.10.9-0saucy-20140409-0500-+0000
 * ros-indigo-mjpeg-server: 1.1.1-0saucy-20140405-0618-+0000
 * ros-indigo-monocam-settler: 0.10.9-0saucy-20140409-0502-+0000
 * ros-indigo-moveit-setup-assistant: 0.5.9-0saucy-20140410-1559-+0000
 * ros-indigo-rail-maps: 0.2.1-0saucy-20140404-0627-+0000
 * ros-indigo-robot-pose-publisher: 0.2.3-0saucy-20140404-0637-+0000
 * ros-indigo-rosauth: 0.1.4-0saucy-20140404-0635-+0000
 * ros-indigo-self-test: 1.8.2-0saucy-20140408-1202-+0000
 * ros-indigo-settlerlib: 0.10.9-0saucy-20140409-0456-+0000
 * ros-indigo-stereo-image-proc: 1.12.2-0saucy-20140408-2230-+0000
 * ros-indigo-test-diagnostic-aggregator: 1.8.2-0saucy-20140408-1158-+0000
 * ros-indigo-tf2-web-republisher: 0.2.1-0saucy-20140409-0458-+0000
 * ros-indigo-vision-visp: 0.7.2-0saucy-20140410-1249-+0000
 * ros-indigo-visp-auto-tracker: 0.7.2-0saucy-20140410-1244-+0000
 * ros-indigo-visp-bridge: 0.7.2-0saucy-20140410-1237-+0000
 * ros-indigo-visp-camera-calibration: 0.7.2-0saucy-20140410-1245-+0000
 * ros-indigo-visp-hand2eye-calibration: 0.7.2-0saucy-20140410-1240-+0000
 * ros-indigo-visp-tracker: 0.7.2-0saucy-20140410-1237-+0000


Updated Packages [43]:
 * ros-indigo-concert-msgs: 0.7.0-0saucy-20140330-0635-+0000 -> 0.7.1-0saucy-20140409-0901-+0000
 * ros-indigo-ecto: 0.6.2-0saucy-20140304-2030-+0000 -> 0.6.3-0saucy-20140404-0046-+0000
 * ros-indigo-ecto-ros: 0.4.1-0saucy-20140321-1808-+0000 -> 0.4.1-0saucy-20140404-0320-+0000
 * ros-indigo-gateway-msgs: 0.7.0-0saucy-20140330-0619-+0000 -> 0.7.1-0saucy-20140409-0841-+0000
 * ros-indigo-moveit-commander: 0.5.6-0saucy-20140402-1455-+0000 -> 0.5.6-0saucy-20140410-1549-+0000
 * ros-indigo-moveit-planners: 0.5.5-0saucy-20140402-0931-+0000 -> 0.5.5-0saucy-20140410-1612-+0000
 * ros-indigo-moveit-planners-ompl: 0.5.5-0saucy-20140401-2051-+0000 -> 0.5.5-0saucy-20140410-1527-+0000
 * ros-indigo-moveit-ros: 0.5.18-0saucy-20140402-1515-+0000 -> 0.5.18-0saucy-20140410-1605-+0000
 * ros-indigo-moveit-ros-benchmarks: 0.5.18-0saucy-20140402-1443-+0000 -> 0.5.18-0saucy-20140410-1536-+0000
 * ros-indigo-moveit-ros-benchmarks-gui: 0.5.18-0saucy-20140402-1509-+0000 -> 0.5.18-0saucy-20140410-1559-+0000
 * ros-indigo-moveit-ros-manipulation: 0.5.18-0saucy-20140402-1442-+0000 -> 0.5.18-0saucy-20140410-1536-+0000
 * ros-indigo-moveit-ros-move-group: 0.5.18-0saucy-20140402-0935-+0000 -> 0.5.18-0saucy-20140410-1528-+0000
 * ros-indigo-moveit-ros-perception: 0.5.18-0saucy-20140325-0446-+0000 -> 0.5.18-0saucy-20140410-1512-+0000
 * ros-indigo-moveit-ros-planning: 0.5.18-0saucy-20140401-2041-+0000 -> 0.5.18-0saucy-20140410-1518-+0000
 * ros-indigo-moveit-ros-planning-interface: 0.5.18-0saucy-20140402-1448-+0000 -> 0.5.18-0saucy-20140410-1542-+0000
 * ros-indigo-moveit-ros-robot-interaction: 0.5.18-0saucy-20140402-0947-+0000 -> 0.5.18-0saucy-20140410-1528-+0000
 * ros-indigo-moveit-ros-visualization: 0.5.18-0saucy-20140402-1457-+0000 -> 0.5.18-0saucy-20140410-1549-+0000
 * ros-indigo-moveit-ros-warehouse: 0.5.18-0saucy-20140402-0937-+0000 -> 0.5.18-0saucy-20140410-1529-+0000
 * ros-indigo-pcl-conversions: 0.1.5-0saucy-20140325-0439-+0000 -> 0.2.0-0saucy-20140410-1508-+0000
 * ros-indigo-pcl-msgs: 0.1.0-1saucy-20140321-0629-+0000 -> 0.2.0-0saucy-20140410-1506-+0000
 * ros-indigo-rocon-annotation-msgs: 0.7.0-0saucy-20140330-0622-+0000 -> 0.7.1-0saucy-20140409-0843-+0000
 * ros-indigo-rocon-app-manager-msgs: 0.7.0-0saucy-20140330-0632-+0000 -> 0.7.1-0saucy-20140409-0859-+0000
 * ros-indigo-rocon-bubble-icons: 0.1.2-0saucy-20140402-1906-+0000 -> 0.1.3-0saucy-20140409-0843-+0000
 * ros-indigo-rocon-console: 0.1.2-0saucy-20140402-1910-+0000 -> 0.1.3-0saucy-20140409-0846-+0000
 * ros-indigo-rocon-ebnf: 0.1.2-0saucy-20140402-1912-+0000 -> 0.1.3-0saucy-20140409-0847-+0000
 * ros-indigo-rocon-icons: 0.1.2-0saucy-20140402-1915-+0000 -> 0.1.3-0saucy-20140409-0848-+0000
 * ros-indigo-rocon-interaction-msgs: 0.7.0-0saucy-20140330-0634-+0000 -> 0.7.1-0saucy-20140409-0859-+0000
 * ros-indigo-rocon-interactions: 0.1.2-0saucy-20140402-1931-+0000 -> 0.1.3-0saucy-20140409-0904-+0000
 * ros-indigo-rocon-launch: 0.1.2-0saucy-20140402-1924-+0000 -> 0.1.3-0saucy-20140409-0904-+0000
 * ros-indigo-rocon-master-info: 0.1.2-0saucy-20140402-1926-+0000 -> 0.1.3-0saucy-20140409-0906-+0000
 * ros-indigo-rocon-msgs: 0.7.0-0saucy-20140330-0646-+0000 -> 0.7.1-0saucy-20140409-0911-+0000
 * ros-indigo-rocon-python-comms: 0.1.2-0saucy-20140402-1918-+0000 -> 0.1.3-0saucy-20140409-0856-+0000
 * ros-indigo-rocon-python-redis: 0.1.2-0saucy-20140402-1919-+0000 -> 0.1.3-0saucy-20140409-0849-+0000
 * ros-indigo-rocon-python-utils: 0.1.2-0saucy-20140402-1922-+0000 -> 0.1.3-0saucy-20140409-0902-+0000
 * ros-indigo-rocon-python-wifi: 0.1.2-0saucy-20140402-1926-+0000 -> 0.1.3-0saucy-20140409-0851-+0000
 * ros-indigo-rocon-semantic-version: 0.1.2-0saucy-20140402-1922-+0000 -> 0.1.3-0saucy-20140409-0851-+0000
 * ros-indigo-rocon-service-pair-msgs: 0.7.0-0saucy-20140330-0625-+0000 -> 0.7.1-0saucy-20140409-0853-+0000
 * ros-indigo-rocon-std-msgs: 0.7.0-0saucy-20140330-0630-+0000 -> 0.7.1-0saucy-20140409-0857-+0000
 * ros-indigo-rocon-tools: 0.1.2-0saucy-20140402-1934-+0000 -> 0.1.3-0saucy-20140409-0907-+0000
 * ros-indigo-rocon-tutorial-msgs: 0.7.0-0saucy-20140330-0640-+0000 -> 0.7.1-0saucy-20140409-0903-+0000
 * ros-indigo-rocon-uri: 0.1.2-0saucy-20140402-1928-+0000 -> 0.1.3-0saucy-20140409-0853-+0000
 * ros-indigo-scheduler-msgs: 0.7.0-0saucy-20140330-0644-+0000 -> 0.7.1-0saucy-20140409-0907-+0000
 * ros-indigo-visp: 2.9.0-2saucy-20140401-1410-+0000 -> 2.9.0-5saucy-20140410-1223-+0000


Removed Packages [1]:
- ros-indigo-rocon-service-msgs


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:
 * Austin Hendrix
 * Brice Rebsamen
 * Daniel Stonier
 * Fabien Spindler
 * Ioan Sucan
 * Paul Bovbel
 * Russell Toris
 * Sachin Chitta
 * Vincent Rabaud
 * piyushk

<div><div dir="ltr">Hi Everyone,&nbsp;<div><br></div>
<div>We bring you another update to the Indigo packages. This update includes 76 new packages and 43 updated packages. Thanks to all the contributors who have released packages.&nbsp;</div>

<div><br></div>
<div>Your ROS Release Team</div>
<div><br></div>
<div><br></div>
<div>
<div>Updates to indigo</div>
<div><br></div>
<div>Added Packages [76]:</div>
<div>&nbsp;* ros-indigo-calibration: 0.10.9-0saucy-20140409-0506-+0000</div>

<div>&nbsp;* ros-indigo-calibration-estimation: 0.10.9-0saucy-20140409-0452-+0000</div>
<div>&nbsp;* ros-indigo-calibration-launch: 0.10.9-0saucy-20140409-0504-+0000</div>
<div>&nbsp;* ros-indigo-calibration-msgs: 0.10.9-0saucy-20140409-0450-+0000</div>

<div>&nbsp;* ros-indigo-camera-calibration: 1.12.2-0saucy-20140408-2220-+0000</div>
<div>&nbsp;* ros-indigo-concert-service-msgs: 0.7.1-0saucy-20140409-0909-+0000</div>
<div>&nbsp;* ros-indigo-depth-image-proc: 1.12.2-0saucy-20140408-2216-+0000</div>

<div>&nbsp;* ros-indigo-diagnostic-aggregator: 1.8.2-0saucy-20140408-1146-+0000</div>
<div>&nbsp;* ros-indigo-diagnostic-analysis: 1.8.2-0saucy-20140408-1155-+0000</div>
<div>&nbsp;* ros-indigo-diagnostic-common-diagnostics: 1.8.2-0saucy-20140408-1201-+0000</div>

<div>&nbsp;* ros-indigo-diagnostic-updater: 1.8.2-0saucy-20140408-1159-+0000</div>
<div>&nbsp;* ros-indigo-diagnostics: 1.8.2-0saucy-20140408-1205-+0000</div>
<div>&nbsp;* ros-indigo-ecl: 0.60.0-0saucy-20140408-1853-+0000</div>
<div>&nbsp;* ros-indigo-ecl-build: 0.60.1-0saucy-20140405-0609-+0000</div>

<div>&nbsp;* ros-indigo-ecl-command-line: 0.60.9-0saucy-20140408-1827-+0000</div>
<div>&nbsp;* ros-indigo-ecl-concepts: 0.60.9-0saucy-20140408-1834-+0000</div>
<div>&nbsp;* ros-indigo-ecl-config: 0.60.1-0saucy-20140406-2222-+0000</div>
<div>

&nbsp;* ros-indigo-ecl-containers: 0.60.9-0saucy-20140408-1841-+0000</div>
<div>&nbsp;* ros-indigo-ecl-converters: 0.60.9-0saucy-20140408-1836-+0000</div>
<div>&nbsp;* ros-indigo-ecl-converters-lite: 0.60.1-0saucy-20140406-2226-+0000</div>

<div>&nbsp;* ros-indigo-ecl-core: 0.60.9-0saucy-20140408-1852-+0000</div>
<div>&nbsp;* ros-indigo-ecl-core-apps: 0.60.9-0saucy-20140408-1849-+0000</div>
<div>&nbsp;* ros-indigo-ecl-devices: 0.60.9-0saucy-20140408-1843-+0000</div>
<div>&nbsp;* ros-indigo-ecl-eigen: 0.60.9-0saucy-20140408-1828-+0000</div>

<div>&nbsp;* ros-indigo-ecl-errors: 0.60.1-0saucy-20140406-2232-+0000</div>
<div>&nbsp;* ros-indigo-ecl-exceptions: 0.60.9-0saucy-20140408-1829-+0000</div>
<div>&nbsp;* ros-indigo-ecl-formatters: 0.60.9-0saucy-20140408-1838-+0000</div>
<div>

&nbsp;* ros-indigo-ecl-geometry: 0.60.9-0saucy-20140408-1843-+0000</div>
<div>&nbsp;* ros-indigo-ecl-io: 0.60.1-0saucy-20140406-2235-+0000</div>
<div>&nbsp;* ros-indigo-ecl-ipc: 0.60.9-0saucy-20140408-1833-+0000</div>
<div>&nbsp;* ros-indigo-ecl-license: 0.60.1-0saucy-20140405-0607-+0000</div>

<div>&nbsp;* ros-indigo-ecl-linear-algebra: 0.60.9-0saucy-20140408-1842-+0000</div>
<div>&nbsp;* ros-indigo-ecl-lite: 0.60.1-0saucy-20140406-2242-+0000</div>
<div>&nbsp;* ros-indigo-ecl-manipulation: 0.60.0-0saucy-20140408-1851-+0000</div>

<div>&nbsp;* ros-indigo-ecl-manipulators: 0.60.0-0saucy-20140408-1848-+0000</div>
<div>&nbsp;* ros-indigo-ecl-math: 0.60.9-0saucy-20140408-1836-+0000</div>
<div>&nbsp;* ros-indigo-ecl-mobile-robot: 0.60.0-0saucy-20140408-1850-+0000</div>
<div>
&nbsp;* ros-indigo-ecl-mpl: 0.60.9-0saucy-20140408-1830-+0000</div>
<div>&nbsp;* ros-indigo-ecl-navigation: 0.60.0-0saucy-20140408-1852-+0000</div>
<div>&nbsp;* ros-indigo-ecl-sigslots: 0.60.9-0saucy-20140408-1840-+0000</div>
<div>&nbsp;* ros-indigo-ecl-sigslots-lite: 0.60.1-0saucy-20140406-2237-+0000</div>

<div>&nbsp;* ros-indigo-ecl-statistics: 0.60.9-0saucy-20140408-1845-+0000</div>
<div>&nbsp;* ros-indigo-ecl-streams: 0.60.9-0saucy-20140408-1846-+0000</div>
<div>&nbsp;* ros-indigo-ecl-threads: 0.60.9-0saucy-20140408-1839-+0000</div>
<div>

&nbsp;* ros-indigo-ecl-time: 0.60.9-0saucy-20140408-1831-+0000</div>
<div>&nbsp;* ros-indigo-ecl-time-lite: 0.60.1-0saucy-20140406-2240-+0000</div>
<div>&nbsp;* ros-indigo-ecl-tools: 0.60.1-0saucy-20140405-0614-+0000</div>
<div>&nbsp;* ros-indigo-ecl-type-traits: 0.60.9-0saucy-20140408-1832-+0000</div>

<div>&nbsp;* ros-indigo-ecl-utilities: 0.60.9-0saucy-20140408-1838-+0000</div>
<div>&nbsp;* ros-indigo-ecto-openni: 0.4.0-0saucy-20140404-0618-+0000</div>
<div>&nbsp;* ros-indigo-ecto-pcl: 0.4.0-0saucy-20140410-1512-+0000</div>
<div>&nbsp;* ros-indigo-image-cb-detector: 0.10.9-0saucy-20140409-0455-+0000</div>

<div>&nbsp;* ros-indigo-image-pipeline: 1.12.2-0saucy-20140408-2233-+0000</div>
<div>&nbsp;* ros-indigo-image-proc: 1.12.2-0saucy-20140408-2226-+0000</div>
<div>&nbsp;* ros-indigo-image-rotate: 1.12.2-0saucy-20140408-2227-+0000</div>
<div>

&nbsp;* ros-indigo-image-view: 1.12.2-0saucy-20140408-2227-+0000</div>
<div>&nbsp;* ros-indigo-interval-intersection: 0.10.9-0saucy-20140409-0455-+0000</div>
<div>&nbsp;* ros-indigo-joint-states-settler: 0.10.9-0saucy-20140409-0500-+0000</div>

<div>&nbsp;* ros-indigo-laser-cb-detector: 0.10.9-0saucy-20140409-0500-+0000</div>
<div>&nbsp;* ros-indigo-mjpeg-server: 1.1.1-0saucy-20140405-0618-+0000</div>
<div>&nbsp;* ros-indigo-monocam-settler: 0.10.9-0saucy-20140409-0502-+0000</div>

<div>&nbsp;* ros-indigo-moveit-setup-assistant: 0.5.9-0saucy-20140410-1559-+0000</div>
<div>&nbsp;* ros-indigo-rail-maps: 0.2.1-0saucy-20140404-0627-+0000</div>
<div>&nbsp;* ros-indigo-robot-pose-publisher: 0.2.3-0saucy-20140404-0637-+0000</div>

<div>&nbsp;* ros-indigo-rosauth: 0.1.4-0saucy-20140404-0635-+0000</div>
<div>&nbsp;* ros-indigo-self-test: 1.8.2-0saucy-20140408-1202-+0000</div>
<div>&nbsp;* ros-indigo-settlerlib: 0.10.9-0saucy-20140409-0456-+0000</div>
<div>&nbsp;* ros-indigo-stereo-image-proc: 1.12.2-0saucy-20140408-2230-+0000</div>

<div>&nbsp;* ros-indigo-test-diagnostic-aggregator: 1.8.2-0saucy-20140408-1158-+0000</div>
<div>&nbsp;* ros-indigo-tf2-web-republisher: 0.2.1-0saucy-20140409-0458-+0000</div>
<div>&nbsp;* ros-indigo-vision-visp: 0.7.2-0saucy-20140410-1249-+0000</div>

<div>&nbsp;* ros-indigo-visp-auto-tracker: 0.7.2-0saucy-20140410-1244-+0000</div>
<div>&nbsp;* ros-indigo-visp-bridge: 0.7.2-0saucy-20140410-1237-+0000</div>
<div>&nbsp;* ros-indigo-visp-camera-calibration: 0.7.2-0saucy-20140410-1245-+0000</div>

<div>&nbsp;* ros-indigo-visp-hand2eye-calibration: 0.7.2-0saucy-20140410-1240-+0000</div>
<div>&nbsp;* ros-indigo-visp-tracker: 0.7.2-0saucy-20140410-1237-+0000</div>
<div><br></div>
<div><br></div>
<div>Updated Packages [43]:</div>
<div>

&nbsp;* ros-indigo-concert-msgs: 0.7.0-0saucy-20140330-0635-+0000 -&gt; 0.7.1-0saucy-20140409-0901-+0000</div>
<div>&nbsp;* ros-indigo-ecto: 0.6.2-0saucy-20140304-2030-+0000 -&gt; 0.6.3-0saucy-20140404-0046-+0000</div>
<div>&nbsp;* ros-indigo-ecto-ros: 0.4.1-0saucy-20140321-1808-+0000 -&gt; 0.4.1-0saucy-20140404-0320-+0000</div>

<div>&nbsp;* ros-indigo-gateway-msgs: 0.7.0-0saucy-20140330-0619-+0000 -&gt; 0.7.1-0saucy-20140409-0841-+0000</div>
<div>&nbsp;* ros-indigo-moveit-commander: 0.5.6-0saucy-20140402-1455-+0000 -&gt; 0.5.6-0saucy-20140410-1549-+0000</div>

<div>&nbsp;* ros-indigo-moveit-planners: 0.5.5-0saucy-20140402-0931-+0000 -&gt; 0.5.5-0saucy-20140410-1612-+0000</div>
<div>&nbsp;* ros-indigo-moveit-planners-ompl: 0.5.5-0saucy-20140401-2051-+0000 -&gt; 0.5.5-0saucy-20140410-1527-+0000</div>

<div>&nbsp;* ros-indigo-moveit-ros: 0.5.18-0saucy-20140402-1515-+0000 -&gt; 0.5.18-0saucy-20140410-1605-+0000</div>
<div>&nbsp;* ros-indigo-moveit-ros-benchmarks: 0.5.18-0saucy-20140402-1443-+0000 -&gt; 0.5.18-0saucy-20140410-1536-+0000</div>

<div>&nbsp;* ros-indigo-moveit-ros-benchmarks-gui: 0.5.18-0saucy-20140402-1509-+0000 -&gt; 0.5.18-0saucy-20140410-1559-+0000</div>
<div>&nbsp;* ros-indigo-moveit-ros-manipulation: 0.5.18-0saucy-20140402-1442-+0000 -&gt; 0.5.18-0saucy-20140410-1536-+0000</div>

<div>&nbsp;* ros-indigo-moveit-ros-move-group: 0.5.18-0saucy-20140402-0935-+0000 -&gt; 0.5.18-0saucy-20140410-1528-+0000</div>
<div>&nbsp;* ros-indigo-moveit-ros-perception: 0.5.18-0saucy-20140325-0446-+0000 -&gt; 0.5.18-0saucy-20140410-1512-+0000</div>

<div>&nbsp;* ros-indigo-moveit-ros-planning: 0.5.18-0saucy-20140401-2041-+0000 -&gt; 0.5.18-0saucy-20140410-1518-+0000</div>
<div>&nbsp;* ros-indigo-moveit-ros-planning-interface: 0.5.18-0saucy-20140402-1448-+0000 -&gt; 0.5.18-0saucy-20140410-1542-+0000</div>

<div>&nbsp;* ros-indigo-moveit-ros-robot-interaction: 0.5.18-0saucy-20140402-0947-+0000 -&gt; 0.5.18-0saucy-20140410-1528-+0000</div>
<div>&nbsp;* ros-indigo-moveit-ros-visualization: 0.5.18-0saucy-20140402-1457-+0000 -&gt; 0.5.18-0saucy-20140410-1549-+0000</div>

<div>&nbsp;* ros-indigo-moveit-ros-warehouse: 0.5.18-0saucy-20140402-0937-+0000 -&gt; 0.5.18-0saucy-20140410-1529-+0000</div>
<div>&nbsp;* ros-indigo-pcl-conversions: 0.1.5-0saucy-20140325-0439-+0000 -&gt; 0.2.0-0saucy-20140410-1508-+0000</div>

<div>&nbsp;* ros-indigo-pcl-msgs: 0.1.0-1saucy-20140321-0629-+0000 -&gt; 0.2.0-0saucy-20140410-1506-+0000</div>
<div>&nbsp;* ros-indigo-rocon-annotation-msgs: 0.7.0-0saucy-20140330-0622-+0000 -&gt; 0.7.1-0saucy-20140409-0843-+0000</div>

<div>&nbsp;* ros-indigo-rocon-app-manager-msgs: 0.7.0-0saucy-20140330-0632-+0000 -&gt; 0.7.1-0saucy-20140409-0859-+0000</div>
<div>&nbsp;* ros-indigo-rocon-bubble-icons: 0.1.2-0saucy-20140402-1906-+0000 -&gt; 0.1.3-0saucy-20140409-0843-+0000</div>

<div>&nbsp;* ros-indigo-rocon-console: 0.1.2-0saucy-20140402-1910-+0000 -&gt; 0.1.3-0saucy-20140409-0846-+0000</div>
<div>&nbsp;* ros-indigo-rocon-ebnf: 0.1.2-0saucy-20140402-1912-+0000 -&gt; 0.1.3-0saucy-20140409-0847-+0000</div>
<div>

&nbsp;* ros-indigo-rocon-icons: 0.1.2-0saucy-20140402-1915-+0000 -&gt; 0.1.3-0saucy-20140409-0848-+0000</div>
<div>&nbsp;* ros-indigo-rocon-interaction-msgs: 0.7.0-0saucy-20140330-0634-+0000 -&gt; 0.7.1-0saucy-20140409-0859-+0000</div>

<div>&nbsp;* ros-indigo-rocon-interactions: 0.1.2-0saucy-20140402-1931-+0000 -&gt; 0.1.3-0saucy-20140409-0904-+0000</div>
<div>&nbsp;* ros-indigo-rocon-launch: 0.1.2-0saucy-20140402-1924-+0000 -&gt; 0.1.3-0saucy-20140409-0904-+0000</div>

<div>&nbsp;* ros-indigo-rocon-master-info: 0.1.2-0saucy-20140402-1926-+0000 -&gt; 0.1.3-0saucy-20140409-0906-+0000</div>
<div>&nbsp;* ros-indigo-rocon-msgs: 0.7.0-0saucy-20140330-0646-+0000 -&gt; 0.7.1-0saucy-20140409-0911-+0000</div>

<div>&nbsp;* ros-indigo-rocon-python-comms: 0.1.2-0saucy-20140402-1918-+0000 -&gt; 0.1.3-0saucy-20140409-0856-+0000</div>
<div>&nbsp;* ros-indigo-rocon-python-redis: 0.1.2-0saucy-20140402-1919-+0000 -&gt; 0.1.3-0saucy-20140409-0849-+0000</div>

<div>&nbsp;* ros-indigo-rocon-python-utils: 0.1.2-0saucy-20140402-1922-+0000 -&gt; 0.1.3-0saucy-20140409-0902-+0000</div>
<div>&nbsp;* ros-indigo-rocon-python-wifi: 0.1.2-0saucy-20140402-1926-+0000 -&gt; 0.1.3-0saucy-20140409-0851-+0000</div>

<div>&nbsp;* ros-indigo-rocon-semantic-version: 0.1.2-0saucy-20140402-1922-+0000 -&gt; 0.1.3-0saucy-20140409-0851-+0000</div>
<div>&nbsp;* ros-indigo-rocon-service-pair-msgs: 0.7.0-0saucy-20140330-0625-+0000 -&gt; 0.7.1-0saucy-20140409-0853-+0000</div>

<div>&nbsp;* ros-indigo-rocon-std-msgs: 0.7.0-0saucy-20140330-0630-+0000 -&gt; 0.7.1-0saucy-20140409-0857-+0000</div>
<div>&nbsp;* ros-indigo-rocon-tools: 0.1.2-0saucy-20140402-1934-+0000 -&gt; 0.1.3-0saucy-20140409-0907-+0000</div>

<div>&nbsp;* ros-indigo-rocon-tutorial-msgs: 0.7.0-0saucy-20140330-0640-+0000 -&gt; 0.7.1-0saucy-20140409-0903-+0000</div>
<div>&nbsp;* ros-indigo-rocon-uri: 0.1.2-0saucy-20140402-1928-+0000 -&gt; 0.1.3-0saucy-20140409-0853-+0000</div>

<div>&nbsp;* ros-indigo-scheduler-msgs: 0.7.0-0saucy-20140330-0644-+0000 -&gt; 0.7.1-0saucy-20140409-0907-+0000</div>
<div>&nbsp;* ros-indigo-visp: 2.9.0-2saucy-20140401-1410-+0000 -&gt; 2.9.0-5saucy-20140410-1223-+0000</div>
<div><br></div>
<div><br></div>
<div>Removed Packages [1]:</div>
<div>- ros-indigo-rocon-service-msgs</div>
<div><br></div>
<div><br></div>
<div>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:</div>

<div>&nbsp;* Austin Hendrix</div>
<div>&nbsp;* Brice Rebsamen</div>
<div>&nbsp;* Daniel Stonier</div>
<div>&nbsp;* Fabien Spindler</div>
<div>&nbsp;* Ioan Sucan</div>
<div>&nbsp;* Paul Bovbel</div>
<div>&nbsp;* Russell Toris</div>
<div>&nbsp;* Sachin Chitta</div>
<div>

&nbsp;* Vincent Rabaud</div>
<div>&nbsp;* piyushk</div>
</div>
<div><br></div>
</div></div>
Daniel Stonier | 10 Apr 19:14 2014
Picon

Sphinx docs for python packages


We've recently dived into sphinx for documenting our python ros packages and had a whole bunch of notes on a private server. This is of not much use to many so I just updated the outdated and somewhat sparse notes that were previously on the ros wiki. 


If you're interested in using something a whole lot better than doxygen for python, you might like to take a look.

Cheers,
Daniel.

<div><div dir="ltr">
<div><br></div>
<div>We've recently dived into sphinx for documenting our python ros packages and had a whole bunch of notes on a private server. This is of not much use to many so I just updated the outdated and somewhat sparse notes that were previously on the ros wiki.&nbsp;</div>
<div><br></div>
<div><div>
<a href="http://wiki.ros.org/Sphinx">http://wiki.ros.org/Sphinx</a><br>
</div></div>
<div><br></div>
<div>If you're interested in using something a whole lot better than doxygen for python, you might like to take a look.</div>
<div><br></div>
<div>Cheers,</div>
<div>Daniel.</div>
<div><br></div>
</div></div>
Tully Foote | 9 Apr 19:32 2014

Call for maintainers

Hi everyone,

The ROS Indigo release is coming up (expected release date in May of 2014) and we here at OSRF have taken stock of which packages we can reasonably maintain ourselves and for which packages we will need community help. Here is a list of packages required for the variants “desktop” as well as “desktop_full”  for Indigo:


The lists on the above wiki page have many holes, but fortunately we have excellent community members who are helping us maintain parts of the ROS packages and that is not yet captured in the above wiki page. However, even with their contributions, there is a shortfall in the maintenance coverage of packages. 

These listings are based on the drafted REP 142 definitions of the metapackages. 


We understand that historically it has been difficult to know what packages need help being maintained, so we added the maintenance status to the debbuild status page for each ROS distribution. Here are the packages currently released into Indigo (sorted by maintenance status):


Here is a page which shows a side-by-side comparison of the packages and versions released into the Groovy, Hydro and Indigo distributions:


This is where you all come in! We encourage everyone to look through that list and consider a few things:

 * If you are the maintainer of a package that has a status of 'unknown', please update the status. You can run `bloom-release -r indigo -t indigo <package name> -p` to have bloom set the status and open a pull request for you or you can edit the distro file directly and let github open the pull request for you: https://github.com/ros/rosdistro/edit/master/indigo/distribution.yaml

 * If you see that a package you commonly use is marked as 'unknown' or 'unmaintained', then consider contacting the listed maintainer by email and/or the ros-release-g9ZBwUv/Ih8gsBAKwltoeQ@public.gmane.org mailing list, to see how you can help with maintenance.

 * If you see that a package you commonly use is not listed at all, consider contacting the maintainer and/or the ros-release mailing list to see if you can help with maintenance. You can see which packages are released into Hydro but not Indigo here: http://www.ros.org/debbuild/compare_hydro_indigo.html

Even if a package that you find useful is released into Indigo and marked as maintained, we encourage you to contact the maintainer or visit the issue tracker for the package and see if you can help out. Issue trackers for the packages can usually be found on the wiki page for that package, e.g. 'http://wiki.ros.org/<package name>'.

When reporting bugs or suggesting enhancements (whether big or small), keep in mind that package maintainers, including those of us here at OSRF, have limited time to devote to servicing incoming issues.  As a general rule, we’ll try to attend to serious bugs quickly, but enhancements, especially for mature packages, will take lower priority.  You’ll almost always get a quicker result if the bug report / feature request comes paired with a working implementation of the fix.

ROS is a community effort and it needs help from the community to succeed. So, if you find something useful then we strongly encourage you to try and give back!

Thanks,
Your ROS Team

<div><div dir="ltr">
<div>Hi everyone,</div>
<div><br></div>
<div>The ROS Indigo release is coming up (expected release date in May of 2014) and we here at OSRF have taken stock of which packages we can reasonably maintain ourselves and for which packages we will need community help. Here is a list of packages required for the variants &ldquo;desktop&rdquo; as well as &ldquo;desktop_full&rdquo; &nbsp;for Indigo:</div>

<div><br></div>
<div><a href="http://wiki.ros.org/indigo/Planning/Maintenance">http://wiki.ros.org/indigo/Planning/Maintenance</a></div>
<div><br></div>
<div>The lists on the above wiki page have many holes, but fortunately we have excellent community members who are helping us maintain parts of the ROS packages and that is not yet captured in the above wiki page. However, even with their contributions, there is a shortfall in the maintenance coverage of packages.&nbsp;</div>

<div><br></div>
<div>These listings are based on the drafted REP 142 definitions of the metapackages.&nbsp;</div>
<div><br></div>
<div><a href="http://www.ros.org/reps/rep-0142.html">http://www.ros.org/reps/rep-0142.html</a></div>

<div><br></div>
<div>We understand that historically it has been difficult to know what packages need help being maintained, so we added the maintenance status to the debbuild status page for each ROS distribution. Here are the packages currently released into Indigo (sorted by maintenance status):</div>

<div><br></div>
<div><a href="http://www.ros.org/debbuild/indigo.html?s=5&amp;r=1">http://www.ros.org/debbuild/indigo.html?s=5&amp;r=1</a></div>
<div><br></div>
<div>Here is a page which shows a side-by-side comparison of the packages and versions released into the Groovy, Hydro and Indigo distributions:</div>

<div><br></div>
<div><a href="http://www.ros.org/debbuild/compare_groovy_hydro_indigo.html">http://www.ros.org/debbuild/compare_groovy_hydro_indigo.html</a></div>
<div><br></div>
<div>This is where you all come in! We encourage everyone to look through that list and consider a few things:</div>

<div><br></div>
<div>&nbsp;* If you are the maintainer of a package that has a status of 'unknown', please update the status. You can run `bloom-release -r indigo -t indigo &lt;package name&gt; -p` to have bloom set the status and open a pull request for you or you can edit the distro file directly and let github open the pull request for you: <a href="https://github.com/ros/rosdistro/edit/master/indigo/distribution.yaml">https://github.com/ros/rosdistro/edit/master/indigo/distribution.yaml</a>
</div>

<div><br></div>
<div>&nbsp;* If you see that a package you commonly use is marked as 'unknown' or 'unmaintained', then consider contacting the listed maintainer by email and/or the <a href="mailto:ros-release <at> lists.ros.org">ros-release@...</a> mailing list, to see how you can help with maintenance.</div>

<div><br></div>
<div>&nbsp;* If you see that a package you commonly use is not listed at all, consider contacting the maintainer and/or the ros-release mailing list to see if you can help with maintenance. You can see which packages are released into Hydro but not Indigo here: <a href="http://www.ros.org/debbuild/compare_hydro_indigo.html">http://www.ros.org/debbuild/compare_hydro_indigo.html</a>
</div>

<div><br></div>
<div>Even if a package that you find useful is released into Indigo and marked as maintained, we encourage you to contact the maintainer or visit the issue tracker for the package and see if you can help out. Issue trackers for the packages can usually be found on the wiki page for that package, e.g. '<a href="http://wiki.ros.org/">http://wiki.ros.org/</a>&lt;package name&gt;'.</div>

<div><br></div>
<div>When reporting bugs or suggesting enhancements (whether big or small), keep in mind that package maintainers, including those of us here at OSRF, have limited time to devote to servicing incoming issues. &nbsp;As a general rule, we&rsquo;ll try to attend to serious bugs quickly, but enhancements, especially for mature packages, will take lower priority. &nbsp;You&rsquo;ll almost always get a quicker result if the bug report / feature request comes paired with a working implementation of the fix.</div>

<div><br></div>
<div>ROS is a community effort and it needs help from the community to succeed. So, if you find something useful then we strongly encourage you to try and give back!</div>
<div><br></div>
<div>Thanks,</div>
<div>

Your ROS Team</div>
<div><br></div>
</div></div>

Gmane