Recently in announcements Category

ROS Blog Retired

We've decided to retire the ROS New blog here.

We now have a better way of getting the news from the ROS community via ROS Discourse.

We recommend the General Channel you can browse it directly.

You can also create an account and subscribe to General or many of the other categories.

If you've been accessing this site via rss Discourse provides an rss feed as well You may also be interested in the feed from planet.ros.org which includes this as well as content from other ROS sources.

ROS 2 Crystal Clemmys Released

We're happy to announce the ROS 2 release Crystal Clemmys!

crystal.png

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!

Our ROS 2 distros, they grow up so fast. With the release of Crystal Clemmys we also bid farewell to Ardent Apalone which will retire with 191 packages, and Crystal is debuting with almost 300 (297 to be precise)!

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

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

Crystal Clemmys is the third 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 December 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!): https://index.ros.org/doc/ros2/Contact

We also invite you to release your ROS 2 packages in Crystal! Here's a tutorial to do so. A huge thanks to all those who've already participated in our pre-release testing and packaging effort.

We would also like to announce the name of the next ROS 2 release scheduled for June 2019:

Dashing Diademata

Your friendly ROS 2 Team

P.S. There's still a couple of weeks left on the T-Shirt campaign.

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!): https://github.com/ros2/ros2/wiki/Contact 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.

bouncy.gif

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:

http://wiki.ros.org/ROS/Installation

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 https://github.com/ros-infrastructure/reprepro-updater/pull/60 for details and the fix.

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

http://wiki.ros.org/melodic/Migration

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:

http://repositories.ros.org/statuspage/rosmelodic_default.html

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

http://repositories.ros.org/statuspage/comparekinetic_melodic.html

http://repositories.ros.org/statuspage/compareindigokineticlunar_melodic.html

If there's a package missing in Melodic that you'd like to see released, please: * check if the package can be released here:

http://repositories.ros.org/statuspage/blockedreleases_melodic.html * contact the maintainers to let them know: * by opening an issue on the source repository * posting on the ROS discourse release category: https://discourse.ros.org/c/release

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] https://en.wikipedia.org/wiki/WorldTurtleDay [2] http://wiki.ros.org/melodic

ROSCon 2018 Diversity Scholarships

The ROSCon 2018 organizing committee aims for ROSCon to represent the entire ROS community, which is diverse and global. In addition to promoting technology that is open source, we also strive to ensure that our communities themselves are as open and accessible as possible, since we recognize that diversity benefits the ROS ecosystem as a whole.

Whoever you are, whatever you do, and wherever you do it, if you're interested in ROS, then we want you to join us at ROSCon. To help reduce the financial barriers to conference attendance, the ROSCon organizing committee is offering a number of scholarships to members of traditionally underrepresented groups in the tech community. Thanks to the support of the program's sponsors, these scholarships each include a complimentary conference registration pass and three nights' accommodation shared with another recipient[1]. Limited travel support is available for participants whose travel to the conference would otherwise be infeasible[2]. Please note that all other expenses (including any visa requirements) will be the responsibility of the participant.

  • [1] To maximize the impact of the scholarship funds, scholarship recipients will be asked to share a room with another recipient. Under special circumstances alternative arrangements can be accommodated.
  • [2] Participants will be responsible for covering their travel expenses up-front, as the travel support will be provided at the conference.

Eligibility

We invite applications from members of groups that have been traditionally underrepresented in the robotics community (including but not limited to: women, LGBTQ+, people of color, people with disabilities, people from racial and/or ethnic minorities in the robotics community, and people from developing nations), who may not otherwise be able to attend ROSCon.

Previous ROSCon Diversity Scholarship recipients are not eligible to re-apply, but we are proud to share this feedback from a participant of the 2017 Diversity Program:

The ROSCon Diversity Scholarship Program provided me with an opportunity that would have been completely impossible without it. I was able to attend my first robotics conference and feel empowered to keep working to try and make a positive impact on this community. Also, it was very encouraging to see so many companies stepping up to promote and enable diversity within their companies and the robotics community. Thank you!

Sponsors

The ROSCon 2018 Diversity Program is made possible with support from the following sponsors:

amazon_logo

erle_logo

fetch_logo

google_logo

locus_logo

open_robotics_logo

If your organization is interested in getting involved in the Diversity Program, please get in contact.

How to Apply

To apply, fill out this form by May 6 2018, describing how you are involved with ROS and the robotics community and what you hope to get out of attending ROSCon. Scholarships will be awarded based on a combination of need and impact. Every applicant will be notified of the outcome of their application.

For more information about ROSCon 2018, including the program, code of conduct, and childcare options, please see http://roscon.ros.org/2018

Thank you to the conference Platinum Sponsor, Erle, and to our Gold Sponsors: Amazon, Clearpath, Fetch Robotics, Google, Locus, ROBOTIS, Tier IV, Universal Robots.

ROS Melodic Morenia Logo and Tshirt Campaign

With each release of ROS we have a tradition of having a logo and making t-shirts. ROS Melodic Morenia is coming out in May. To let you show your ROS colors and support this tradition, we have setup a Teespring Campaign in both the US and the EU. Note that both these campaigns can ship worldwide.

Ordering will be open until May 8th. Order now!

melodic_tshirt.jpg

Since this is the first public announcement, here's the full graphic for Melodic Morenia.

melodic_logo.jpg

Thanks to everyone who's been helping prepare the Melodic release. We're looking forward to the release in May. We expect the tshirts ordered in this campaign will arrive just before ROS Melodic Morenia is released!

ROS 2 Ardent Apalone released

We're happy to announce the ROS 2 release Ardent Apalone!

Installation instructions and tutorials can be found on the ROS 2 wiki.

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

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

  • The first non-beta release.
  • rviz including a few plugins (the Windows version will follow in a few weeks)
  • Different initialization options for message data structures in C++
  • Logging API improvements, now also used in the demos
  • Time support in C++ with different clocks
  • wait-for-service support in the Python client library
  • Draft implementation of REP 149 specifying format 3 of the package manifest files

While there is always more work to be done we consider several of the core components to be ready to be used by a broader audience. Therefore we have dropped the "beta" label and will support Ardent for one year, fixing bugs and keeping the release working, especially on platforms with rolling dependency releases (OS X / Windows). We'll start a regular six month release cycle for newer versions of ROS 2. While we do aim to keep the API as stable as possible, we can't guarantee 100% API compatibility between releases. That being said, whether or not ROS 2 is ready to be used for your application or if you can switch from ROS 1 to ROS 2 right now depends on the exact feature set and requirements of your use case. Please check the features page as well as the roadmap for more information.

As always, we invite you to try out the new software, give feedback, report bugs, and suggest features (and contribute code!): https://github.com/ros2/ros2/wiki/Contact

Your friendly neighborhood ROS 2 Team

ROS Turns 10!

We're happy to be celebrating the 10th anniversary of ROS today!

On this date in 2007 the first commit was made to the ROS project on SourceForge.

Since then, ROS has grown from that first public commit to over 200000 commits made by more than 2800 individuals from around the world. These contributions have built up to over 4.5 million significant lines of code which - following standard development effort estimators - would take 169 full time developers 8.5 years.



As an open source community it's sometimes very hard to quantify the involvement in the project. To help measure what we can, we started putting together an annual Metrics report. Using these snapshots the progress of ROS is quite striking.

Charting the information over time can be seen in this post. Showing things like Monthly Unique IPs or Total Downloads year over year.

unique_ips.png

total_downloads.png

This year being a large anniversary we're happy to see that there are many others who are recognizing this historic milestone. There is already coverage in Science Robotics, , ZDNet and IEEE Spectrum

To help highlight the greater ROS community we've running a series of blog posts about some of the ROS Contributors who have helped grow the community.

Another way that we're celebrating is by making anniversary edition t-shirts available for CTurtle, Indigo, and Kinetic. You can order from the:

CTurtle was our first release with a full logo. And Indigo and Kinetic are our new current Long Term Support Releases. Get your anniversary shirt to support the ROS community by showing how many of us there are. This is a limited campaign and will end on November 21.

Of course if you'd rather have stickers, they are available from Sticker Mule.

For those of us involved in ROS since its inception, these last 10 years have gone by in the blink of an eye. We've gone from a first commit to an industry standard. The enthusiasm of this community, the creativity of the work already accomplished, and the plans to come all combine to paint a very bright picture of the future of ROS. All of us at Open Robotics and very much looking forward to the next 10 years, and beyond.

ROSCon 2017 Diversity Scholarships

The ROSCon 2017 organizing committee aims for ROSCon to represent the entire ROS community, which is diverse and global. In addition to promoting technology that is open source, we also strive to ensure that our communities themselves are as open and accessible as possible, since we recognize that diversity benefits the ROS ecosystem as a whole.

Whoever you are, whatever you do, and wherever you do it, if you're interested in ROS, then we want you to join us at ROSCon. To help reduce the financial barriers to conference attendance, the ROSCon organizing committee is offering a number of scholarships to members of traditionally underrepresented groups in the tech community. Thanks to the support of the program's sponsors, these scholarships each include a complimentary conference registration pass and three nights' accommodation shared with another recipient*. Limited travel support is available for participants whose travel to the conference would otherwise be infeasible. Please note that all other expenses (including any visa requirements) will be the responsibility of the participant.

*To maximize the impact of the scholarship funds, scholarship recipients will be asked to share a room with another recipient. Under special circumstances alternative arrangements can be accommodated.

Eligibility

We invite applications from members of groups that have been traditionally underrepresented in the tech community (including but not limited to: women, LGBTQ+, people of color, people with disabilities, and people from ethnic minorities in their country of residence), who may not otherwise be able to attend ROSCon. Previous ROSCon Diversity Scholarship recipients are not eligible to re-apply.

Sponsors

The ROSCon 2017 Diversity Program has been made possible with support from the following sponsors:

Fetch.png

nvidia.png

openrobotics-logo-stacked.png

rapyuta.png

voyage.png

If your organization is interested in getting involved in the Diversity Program, please get in contact.

How to apply

To apply, fill out this form by June 25, describing how you are involved with ROS and the robotics community and what you hope to get out of attending ROSCon. Scholarships will be awarded based on a combination of need and impact. Every applicant will be notified of the outcome of their application.

For more information about ROSCon 2017, including the program, code of conduct, and childcare options, please see http://roscon.ros.org/2017

ROSCon 2017: Call for proposals

We're excited to announce that we are now accepting presentation proposals for ROSCon 2017!

Presentations on all topics related to ROS are invited. Examples include introducing attendees to a ROS package or library, exploring how to use tools, manipulating sensor data, and applications for robots.

Women, members of minority groups, and members of other under-represented groups are encouraged to submit presentation proposals to ROSCon.

Proposals will be reviewed by a program committee that will evaluate fit, impact, and balance.

We cannot offer presentations that are not proposed! If there is a topic on which you would like to present, please propose it. If you have an idea for an important topic that you do not want to present yourself, please post it for discussion at ROS Discourse. Topic areas

All ROS-related work is invited. Topics of interest include:

  • Best practices
  • New packages
  • Robot-specific development
  • Robot simulation
  • Safety and security
  • Embedded systems
  • Product development & commercialization
  • Research and education
  • Enterprise deployment
  • Community organization and direction
  • Testing, quality, and documentation
  • Robotics competitions and collaborations

To get an idea of the content and tone of ROSCon, check out the slides and videos from last year.

Proposal format

A session proposal must include:

  • Title
  • Presenter (name and affiliation)
  • Recommended duration: Short (~20 minutes) or Long (~40 minutes)
  • Summary [maximum 100 words]: to be used in advertising the presentation
  • Description [maximum 1000 words]: outline, goals (what will the audience learn?), pointers to packages to be discussed

Please be sure to include in your proposal enough information for the program committee to evaluate the importance and impact of your presentation. Links to publicly available resources, including code repositories and demonstration videos, are especially helpful.

Submit your proposal at the submissions site by June 25, 2017.

ARIAC Qualifier 3 is open!

We are happy to announce that Qualifier 3 is now open for the Agile Robotics for Industrial Automation Competition (ARIAC)!

ARIAC is a simulation-based competition is designed to promote agility in industrial robot systems by utilizing the latest advances in artificial intelligence and robot planning. The goal is to enable industrial robots on the shop floors to be more productive, more autonomous, and to require less time from shop floor workers. You can learn more about the competition here. The top performing teams will be invited to present at a workshop held during IROS 2017 in Vancouver.

So far we have completed Qualifiers 1 and 2, highlights of which you can see here:


and here:


While the first two Qualifiers are now closed, there's still time to join the competition. You have until May 15, 2017 to submit your results from Qualifier 3 and secure a spot in the final competition, to be held in early June. To learn how to participate, visit the ARIAC site.

Celebrating 9 Years of ROS!

This year marks the occasion of ROS turning 9 years old! Through these years ROS has grown into a strong world-wide community. It's a community with a large variety of interests: from academic researchers to robotic product developers as well as the many robot users. Academic use of ROS continues to grow. Citations of the first ROS paper "ROS: An Open-Source Robot Operating System" has grown to 2,871.

To get a better sense of what's happening in the ROS community, if you have not already done so, I highly recommend reviewing the ROSCon 2016 program. You can also find all the video recordings in this gallery. ROSCon 2016 was another great event bringing ROS community members together to share how they're using ROS to solve their challenges. As the goal of ROSCon is to share information between the entire community we record the talks and make them available online. We've sold out our venues the last two years and are looking forward to another ROSCon next fall!

roscon-group-thumb.png

Part of understanding our growing community is to try to measure it. For the last 6 years we've been generating metrics reports. These reports can give a sense of aggregate what's happening in the ROS community. Our most recent report is from July 2016. David Lu has put together plots of several of the metrics across the last 6 years which can be quite informative.

This year we wanted to dig a little deeper into the code metrics, so we downloaded the source of all of packages listed in the Indigo Igloo rosdistro and ran some analysis.

  • The total line count is over 14 million lines of code
  • There have been 2477 authors
  • And 181509 commits
  • Averaging 73.3 commits per author

You can see the commits as a function of month in this graph.

commits_by_year_month.png

Our committers are active around the world as evidenced by the commits coming in at all hours of the day.

hour_of_day.png

And the git commits record 24 different time zones (out of 39 possible).

Analyzing the repository for significant lines of code using SLOCCount shows:

  • 4,077,199 significant lines of code.
  • This represents an estimated 1,236 person-years of development.
  • For a sense of scale, that is an average of 137 developers contributing full time over the last 9 years!

For those of you curious about the breakdown by language lines of code, it is as follows:

  • cpp: 2608592 (63.98%)
  • python: 553332 (13.57%)
  • ansic: 297629 (7.30%)
  • xml: 280615 (6.88%)
  • lisp: 149439 (3.67%)
  • java: 135343 (3.32%)
  • ruby: 26484 (0.65%)
  • sh: 21120 (0.52%)

This only represents the packages publicly released into the Indigo rosdistro index.

Note that the tools only worked on Git repos so code from other source control systems was excluded. There are also a few projects which predate ROS but have ported to use ROS and their history is included.

We're looking forward to continuing growth through 2017 leading up to the 10-year anniversary of ROS. With the Beta 1 version of ROS 2.0 out, there will be space for new development. We're looking forward to our next release, Lunar Loggerhead, to coincide with Ubuntu's next release, Zesty Zapus. With both of these, the ROS community can continue to rely on the many libraries, tools, and capabilities they have come to know and enjoy, as well as begin to experiment with the new features in ROS 2.0

Another exciting project to watch is the upcoming TurtleBot 3! The TurtleBot and TurtleBot 2 have been great platforms for learning and prototyping. However by packing that same capability into a smaller platform with more punch we look forward to it providing another avenue to grow the ROS community.

We write these anniversary posts to help give you a sense of how ROS has been doing over the past year, but we'd certainly encourage you to find out for yourself. Get involved. Write or edit a wiki page. Answer a question on ROS Answers. Come to ROSCon. And, when you're ready, think about helping to maintain ROS itself, or even contributing a brand new ROS package.

OSRF is doing great, but the long-term success of ROS depends on every member of the incredibly awesome ROS community. If you're already an active part of the ROS community, we can't thank you enough; and if you're not, think about how you can help ROS grow and thrive for the next nine years, and beyond.

Towards ROS-native drones

From Medium:

Announcing alpha support for the PX4 flight stack in a path towards drones that speak ROS natively

The drones field is an interesting one to analyze from a robotics perspective. While capable flying robots are reasonably new, RC-hobbyists have been around for a much longer time building flying machines developing communities around the so called flight stacks or software autopilots.

Among these, there're popular options such as the Paparazzi, the APM (commonly known as ardupilot) or the PX4. These autopilots matured to the point of acquiring autonomous capabilities and turning these flying machines into actual drones. Many of these open source flight stacks provide a general codebase for building basic drone behaviors however modifications are generally needed when one has the intention of tackling traditional problems in robotics such as navigation, mapping, obstacle avoidance and so on. These modifications are not straightforward when performed directly in the autopilot code thereby, in an attempt to enhance (or sometimes just simplify) the capabilities of autopilots, abstraction layers such as DroneKit started appearing.

For a roboticist however, the common language is the Robot Operating System (ROS). Getting ROS to talk to these flight stacks natively would require a decent amount of resources and effort thereby, generally, roboticists use a bridge such as the mavros ROS package to talk to the flight stacks.

We at Erle Robotics have been offering services with flying robots using such architecture but we've always wondered what would be the path towards a ROS-native drone. In order to explore this possibility we've added support for the PX4 Pro flight stack. 


Supporting the PX4 Pro flight stack

The PX4 Pro drone autopilot is an open source (BSD) flight control solution for drones that can "fly anything from a racing to a cargo drone?--?be it a multi copter, plane or VTOL". PX4 has been built with a philosophy similar to ROS, composed by different software blocks where each one of these modules communicates using a publish/subscribe architecture (currently, a simplified pub/sub middleware called uORB).

In an internal attempt to research the path of getting ROS-native flight stacks and to open up this work to the community I'm happy to announce official alpha support for the PX4 Pro in all our products meant for developers such as the PXFmini, Erle-Brain 2 or Erle-Copter. Our team has put together a new set of Operating System images for our products that will help you switch between flight stacks easily.

To install PX4 Pro, just type the following:

sudo apt-get purge -y apm-* # e.g.: apm-copter-erlebrain 
sudo apt-get update 
sudo apt-get install px4-erle-robotics


ROS-native flight stacks 

Using the PX4 Pro flight stack as a starting point, our team will be dedicating resources to prototype the concept of a drone autopilot that speaks ROS natively, that is, that uses ROS nodes to abstract each submodule within the autopilot's logic (attitude estimator, position control, navigator, ...) and ROS topics/services to communicate with the rest of the blocks within the autopilot. Ultimately, this initiative should deliver a software autopilot capable of creating a variety of drones that merges nicely with all the traditional ROS interfaces that roboticists have been building for over a decade now. 

If you're interested in participating with this initiative, reach us out at http://erlerobotics.com/blog/contact/.

Originally published in Medium:

1--XgoPd36umkXi6lXTGkCng.png

I'm delighted to announce a new game-changing standard for building robot components, H-ROS: the Hardware Robot Operating System. H-ROS provides manufacturers tools for building interoperable robot components that can easily be exchanged or replaced between robots.

H-ROS is about supporting a common environment of robot hardware components, where manufacturers comply with standard interfaces built upon ROS.

Powered by the popular Robot Operating System (ROS) and built with industry and developers in mind, H-ROS classifies robot components in 5 types: sensing?--?used to perceive the world, actuation?--?allow interaction with the environment, communication?--?provide a means of interconnection, cognition?--?the brain of the robot and hybrid?--?components that group together different sub-components under a common interface. This building-block-style parts come as reusable and reconfigurable components allowing developers, to easily upgrade their robots with hardware from different manufacturers and add new features in seconds.

Motivation and origin

Building a robot is accepted as a harsh task thereby it makes sense to reuse previous work to reduce this complexity. Unfortunately, nowadays there are little efforts that reuse hardware in both academy and industry. Robots are generally built by multidisciplinary teams (generally a whole research group or a company division) where different engineers get involved in the mechanical, electrical and logical design. Most of the time is spent dealing with the hardware/software interfaces and little is put into behavior development or real-world scenarios. Existing hardware platforms, although starting to become more common, lack extensibility.

Examples can be seen in several commercial and industrial robots that hit the market recently and already include a common software infrastructure (generally the Robot Operating System(ROS)) but lack of a hardware standard.

With H-ROS, building robots will be about placing H-ROS-compatible hardware components together to build new robot configurations. Constructing robots won't be restricted to a few with high technical skills but it will be extended to a great majority with a general understanding of the sensing and actuation needed in a particular scenario.

H-ROS was initially funded by the US Defense Advanced Research Projects Agency (DARPA) through the Robotics Fast Track program in 2016. It is now available for selected industry partners and will soon be released for the wider robotics community. Additional information can be requested through its official web page at https://h-ros.com/. H-ROS was first unveiled and showcased at ROSCon 2016 (October 8th-9th) in Seoul, South Korea.

ROSCon 2016 Diversity Scholarships

The ROSCon 2016 organizing committee aims for ROSCon to represent the entire ROS community, which is diverse and global. In addition to promoting technology that is open source, we also strive to ensure that our communities themselves are as open and accessible as possible, since we recognize that diversity benefits the ROS ecosystem as a whole.

Whoever you are, whatever you do, and wherever you do it, if you're interested in ROS, then we want you to join us at ROSCon. To help reduce the financial barriers to conference attendance, the ROSCon organizing committee is offering a number of scholarships to members of traditionally underrepresented groups in the tech community. These scholarships will include a complimentary conference registration pass and two nights' twin-share* accommodation. Please note that all other expenses (including travel and any visa requirements) will be the responsibility of the participant.

*To maximize the impact of the scholarship funds, scholarship recipients will be asked to share a room with another recipient.

Eligibility

We invite applications from members of groups that have been traditionally underrepresented in the tech community (including but not limited to: women, LGBTQ+, people of color, people with disabilities, and people from ethnic minorities in their country of residence), who may not otherwise be able to attend ROSCon.

How to apply

To apply, please fill out this form by the 14th of August, describing how you are involved with ROS and the robotics community and what you hope to get out of attending ROSCon 2016. Scholarships will be awarded based on a combination of need and impact. Every applicant will be notified of the outcome of their application by the 20th of August.

For more information about ROSCon 2016, including the program, code of conduct, and childcare options, please see http://roscon.ros.org/2016/

ROS Kinetic Kame Released

Happy World Turtle Day!

I am pleased to announce that the 10th ROS distribution, Kinetic Kame, is now available on Ubuntu Xenial 16.04, Ubuntu Wily 15.10, and Debian Jessie. Packages for 32-bit ARM (armhf) are available on Xenial, and 64-bit ARM (aarch64) is supported on Debian Jessie.

kinetic.png

To install ROS Kinetic, refer to the Installation page on the Wiki:
Check out the Migration guide for a changelog of new features and API changes:

http://wiki.ros.org/kinetic/Migration

524 packages in the ROS ecosystem are in the initial release of Kinetic, compared to 2149 currently in Indigo and 1016 in Jade. You can see the released packages on the status page for Kinetic:

http://repositories.ros.org/status_page/ros_kinetic_default.html

And you can compare the versions of packages in Indigo, Jade, and Kinetic here (thanks William for making changes to the new compare pages):

http://repositories.ros.org/status_page/compare_indigo_jade_kinetic.html

If there's a package missing in Kinetic that you'd like to see released, contact the maintainers to let them know. Even though we've made the initial Kinetic release, it's never too late to add packages to Kinetic (or Jade or Indigo) for upcoming syncs.

Kinetic 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, which you can look forward to downloading a year from now: Lunar Loggerhead!

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

- Jackie and the ROS Team

[1] https://en.wikipedia.org/wiki/World_Turtle_Day

ROS Kinetic Kame Tshirt and Logo Announced

| No Comments | No TrackBacks
With each release of ROS we have a tradition of having a logo and making t-shirts. ROS Kinetic Kame is coming out in May. Show your ROS colors and support this tradition!  Visit the Teespring Campaign page here to order your shirt. 

kinetic_tshirt_front.png
Proceeds from shirt sales go to supporting the costs associated with developing and maintaining ROS, including hosting the wiki and running the build farm. 

There are both mens and womens sizes as well as hoodies, v-necks and triblends available. 

Order now and if this campaign is funded we expect the shirts to arrive approximately when ROS Kinetic Kame is released. The campaign closes on May 9th don't wait too long to order. 

Here's a high resolution version of the Kinetic logo. 

kinetic.png

Note that we have two providers one in the US and one in Europe. The main link: http://bit.ly/KinteicKame redirects based on your IP address. If you want to access the individual pages you can visit: https://teespring.com/ros-kinectic-kame and https://teespring.com/ros-kinetic-kame-eu directly. 




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:
  https://github.com/ros2/ros2/wiki

To get an idea of what's in (and what's not in) this release, be sure
to read the overview page:
  https://github.com/ros2/ros2/wiki/Alpha3-Overview

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
release:
  https://github.com/ros2/ros2/wiki/Roadmap

As always, we invite you to try out the new software, give feedback,
report bugs, and suggest features (and contribute code!):
  https://github.com/ros2/ros2/wiki/Contact

ROS Turns 8

| No Comments | No TrackBacks
Thumbnail image for ROS 8 Years.png
Eight years ago, Morgan Quigley, Eric Berger and Andrew Ng published a paper that was not about ROS. It was about STAIR, the STanford Artificial Intelligence Robot, which used a library called Switchyard to pass messages between software modules to perform complex manipulation tasks like stapler grasping. Switchyard was a purpose-built framework that was designed to be modular and robot-independent, and it was such a good idea that in 2009, "ROS: An Open-Source Robot Operating System" was presented at the IEEE International Conference on Robotics and Automation (ICRA) in Japan. As of this month, the paper introducing ROS has been cited 2,020 times, an increase of more than 50% over last year.

The popularity of one single paper is only a minor indicator of the popularity of the robot operating system that it introduced. At eight years old, ROS is growing faster than ever, and helping the robotics community to grow along with it. We're especially excited to see how brand new startups have been taking advantage of the open source nature of ROS to help them develop useful, reliable robots that are creating entirely new markets. In 2015 alone, more than $150 million in VC funding (that we know of) was invested in businesses that utilize ROS.

Large, established companies have been taking more and more notice of ROS as well. At ROSCon this year, Fetch Robotics was joined as a platinum sponsor by Ubuntu, and a record number of gold sponsors included NVIDIA, Bosch, and Qualcomm and attendees from companies such as BMW, DJI, Intel and more. ROSCon 2015 was by far the largest conference we've ever had: it sold out weeks in advance.  Clearly next year we're going to have to find a much bigger venue to make room for more attendees, more speakers, and more exhibitors.

Taking a look at how much our community has grown this year, it's easy to see why ROSCon has become so popular: it's a reflection of the enthusiasm and engagement of the ROS user base. In May 2015 alone, nearly nine million ROS packages were downloaded from over 70,000 unique IP addresses, and these numbers don't even count mirrors. This suggests that ROS probably has hundreds of thousands of active users. We also have a very robust developer community: 1,840 people have contributed to ROS' 10 million lines of code, averaging 20 commits per day. The ROS wiki has gotten 10% bigger since last year, and there are over 11,000 users on ROS Answers, a 32% increase over last year, with a total of more than 5,000 questions answered. It's numbers like these that make us so confident in the long term future of ROS.

Counting ROS
Because of the nature of the ROS license, we actually don't know how many users, robots, and developers there are utilizing ROS.  Many of the numbers that we are citing throughout are likely to be much larger.  For example, we specifically know of approximately 80 types of robots using ROS, but almost every day we hear about new ones.  And not every company using ROS discloses so publicly, so our estimates on venture capital investment can be better characterized as lower bounds than estimates.

If you're not part of the ROS community yet, there's never been a better time to get involved. Even if you don't have experience with robots or programming, there's a wide variety of low-cost robots and helpful online tutorials that can get you started, and we're also delighted to announce (just in time for the holidays!) that O'Reilly Media has published "Programming Robots with ROS: A Practical Introduction to the Robot Operating System," by Morgan Quigley, Brian Gerkey, and Bill Smart, which will take you from zero to ROS expert in just 448 pages.

Learning ROS will allow you to do all kinds of cool stuff with more than 80 robotic platforms. You can choose from the capable, affordable TurtleBot, one of the many sophisticated humanoid robots that competed in the DARPA Robotics Challenge, or even NASA's Robonaut, currently undergoing testing on the International Space Station. Robots powered by ROS are everywhere, and here are just a few of them:




For full frame clips see the long version of the montage. 

Of course, we have no idea how many robots are actually running ROS, or how many people or companies are using it, because ROS is open source and completely free. We're often surprised to learn that cutting edge robots that we're already familiar with are powered by ROS, as when BMW announced at ROSCon that they've been using ROS in their autonomous cars for the past few years. We weren't at all surprised to hear why BMW chose ROS for its autonomous driving research, though: they appreciate its popularity, its stability and reliability based on a large user base, the fact that it makes it easy to collaborate, and its open source nature. 

As the ROS community has grown, various special interest groups have organized to promote ROS for specific application domains. The ROS Industrial Consortium is one such group.  ROS-I is a software library that builds on ROS and leverages its power and flexibility to control manufacturing automation equipment including industrial robot arms. It is supported by the 36-member organizations comprised of companies such as 3M, ABB, BMW, Ford, Boeing, Siemens and more.  Representatives from Boeing, Caterpillar, Yaskawa and more speak on behalf of ROS and ROS-I in this video.

2016 is poised to be the biggest year ever for ROS, and we'd like to highlight two things that are worth getting particularly excited about. The first is ROS 2.0, which we've been developing for the past few years. ROS 2 will support the growth of the ROS community by making it much easier to work with small embedded systems, teams of multiple robots, and robots that require real-time control. We'd also like to make sure you're familiar with Robotics Fast Track (RFT), which is  a program that we're working on with DARPA. It's an easy way for you to get government funding for your awesome robotics ideas without having to give up any of your IP, and absolutely anyone can apply. 

We write these anniversary posts to help give you a sense of how ROS has a whole has been doing over the past year, but we'd certainly encourage you to find out for yourself, by getting involved. Write or edit a Wiki page. Answer a question on ROS Answers. Come to ROSCon. And, when you're ready, think about helping to maintain ROS itself, or even contributing a brand new ROS package. OSRF is doing great, but the long-term success of ROS depends on all of the incredibly awesome ROS users themselves. If you're already an active part of the ROS community, we can't thank you enough, and if you're not, think about it: you can help ROS grow and thrive for eight more years, and beyond.

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:
  https://github.com/ros2/ros2/wiki

To get an idea of what's in (and what's not in) this release, be sure
to read the overview page:
  https://github.com/ros2/ros2/wiki/Alpha2-Overview

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
release:
  https://github.com/ros2/ros2/wiki/Roadmap

As always, we invite you to try out the new software, give feedback,
report bugs, and suggest features (and contribute code!):
  https://github.com/ros2/ros2/wiki/Contact

2015 Metrics Report Available

| No Comments | No TrackBacks
You can now download our 2015 ROS Metrics report from: http://download.ros.org/downloads/metrics/metrics-report-2015-07.pdf 

It's the 5th edition of the report. Links to all of them can be found at: http://wiki.ros.org/Metrics

One metric which stood out to me how strong the adoption of Indigo has been. Over half our users are now using the LTS release. 

And all of these numbers do not count the any statistics for mirrors either private or public of which we've seen an increase in availability. http://wiki.ros.org/Mirrors

Demonstrating the challenge of understanding metrics, the downward change in download volume reflects the more stable core packages. During the sample period there were fewer core releases. Including no catkin, ros, or ros_comm releases in July 2015 versus one or more of each of those in July 2014.

ROS Hydromedusa Final Release

| No Comments | No TrackBacks
Hi Everyone, 

We again have reached another milestone which is the End of Life ROS Hydromedusa. We have reached the final release with 223 updated packages and 15 new packages. Full details are below. 

Hydro has had a long history over 877 days with commits on 743 of those days. We had 241 individual contributors submitting 4879 commits which is an average of 5.4 commits per day. There were 1690 packages released and built into debian packages in the hydro rosdistro as well as uncounted packages maintained outside the public release pipeline.

Here's a visualization of the public rosdistro releases for Hydro over the course of it's development cycle:

As we've reached EOL we will begin the process of tearing down the Hydro buildfarm. 

Please take a moment and thank anyone you know who has released packages into Hydro. The thousands of releases into the rosdistro are what drives our community and helps create value for everyone.

You ROS Release Team


Updates to hydro

Added Packages [15]:
 * ros-hydro-cob-scan-unifier: 0.5.3-0
 * ros-hydro-eusurdf: 0.1.13-0
 * ros-hydro-ir-trans-drivers: 0.0.4-0
 * ros-hydro-jsk-201504-miraikan: 0.0.11-0
 * ros-hydro-jsk-3rdparty: 2.0.8-0
 * ros-hydro-jsk-common-msgs: 2.0.0-1
 * ros-hydro-jsk-recognition-utils: 0.3.6-0
 * ros-hydro-jsk-robot-utils: 0.0.11-0
 * ros-hydro-libcmt: 2.0.8-0
 * ros-hydro-roseus-mongo: 1.3.9-0
 * ros-hydro-roseus-remote: 0.0.11-0
 * ros-hydro-rosjava: 0.1.1-0
 * ros-hydro-rosjava-core: 0.1.6-0
 * ros-hydro-rosjava-extras: 0.1.5-0
 * ros-hydro-rosjava-messages: 0.1.345-0


Updated Packages [223]:
 * ros-hydro-ackermann-msgs: 0.9.1-0 -> 1.0.0-0
 * ros-hydro-app-manager: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-assimp-devel: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-baxtereus: 0.0.6-0 -> 0.0.11-0
 * ros-hydro-bayesian-belief-networks: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-catkinize-this: 0.2.3-0 -> 0.2.4-0
 * ros-hydro-checkerboard-detector: 0.2.12-0 -> 0.3.6-0
 * ros-hydro-cob-linear-nav: 0.5.1-2 -> 0.5.3-0
 * ros-hydro-cob-mapping-slam: 0.5.1-2 -> 0.5.3-0
 * ros-hydro-cob-navigation: 0.5.1-2 -> 0.5.3-0
 * ros-hydro-cob-navigation-config: 0.5.1-2 -> 0.5.3-0
 * ros-hydro-cob-navigation-global: 0.5.1-2 -> 0.5.3-0
 * ros-hydro-cob-navigation-local: 0.5.1-2 -> 0.5.3-0
 * ros-hydro-cob-navigation-slam: 0.5.1-2 -> 0.5.3-0
 * ros-hydro-collada-urdf-jsk-patch: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-depthcloud-encoder: 0.0.4-0 -> 0.0.5-0
 * ros-hydro-diagnostic-aggregator: 1.8.7-0 -> 1.8.8-0
 * ros-hydro-diagnostic-analysis: 1.8.7-0 -> 1.8.8-0
 * ros-hydro-diagnostic-common-diagnostics: 1.8.7-0 -> 1.8.8-0
 * ros-hydro-diagnostic-updater: 1.8.7-0 -> 1.8.8-0
 * ros-hydro-diagnostics: 1.8.7-0 -> 1.8.8-0
 * ros-hydro-downward: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-dynamic-tf-publisher: 1.0.71-0 -> 2.0.3-0
 * ros-hydro-easy-markers: 0.2.3-0 -> 0.2.4-0
 * ros-hydro-ethercat-hardware: 1.8.11-0 -> 1.8.15-0
 * ros-hydro-eus-assimp: 0.1.12-0 -> 0.1.13-0
 * ros-hydro-eus-nlopt: 0.1.5-0 -> 0.1.6-1
 * ros-hydro-eus-qp: 0.1.5-0 -> 0.1.6-1
 * ros-hydro-eus-qpoases: 0.1.5-0 -> 0.1.6-1
 * ros-hydro-euscollada: 0.1.12-0 -> 0.1.13-0
 * ros-hydro-eusgazebo: 0.1.8-0 -> 0.1.9-0
 * ros-hydro-euslisp: 9.12.2-0 -> 9.15.1-0
 * ros-hydro-ff: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-ffha: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-fingertip-pressure: 1.8.11-0 -> 1.8.15-0
 * ros-hydro-geneus: 2.2.2-0 -> 2.2.4-0
 * ros-hydro-hironx-calibration: 1.0.31-0 -> 1.0.37-0
 * ros-hydro-hironx-moveit-config: 1.0.31-0 -> 1.0.37-0
 * ros-hydro-hironx-ros-bridge: 1.0.31-0 -> 1.0.37-0
 * ros-hydro-hrpsys: 315.4.0-0 -> 315.7.0-2
 * ros-hydro-hrpsys-gazebo-general: 0.1.8-0 -> 0.1.9-0
 * ros-hydro-hrpsys-gazebo-msgs: 0.1.8-0 -> 0.1.9-0
 * ros-hydro-hrpsys-ros-bridge: 1.2.12-0 -> 1.2.14-0
 * ros-hydro-hrpsys-tools: 1.2.12-0 -> 1.2.14-0
 * ros-hydro-image-view2: 1.0.71-0 -> 2.0.3-0
 * ros-hydro-imagesift: 0.2.12-0 -> 0.3.6-0
 * ros-hydro-imu-filter-madgwick: 1.0.4-0 -> 1.0.5-0
 * ros-hydro-imu-tools: 1.0.4-0 -> 1.0.5-0
 * ros-hydro-joy-listener: 0.2.3-0 -> 0.2.4-0
 * ros-hydro-joy-mouse: 0.1.5-0 -> 0.1.6-1
 * ros-hydro-jsk-baxter-desktop: 0.0.6-0 -> 0.0.11-0
 * ros-hydro-jsk-baxter-startup: 0.0.6-0 -> 0.0.11-0
 * ros-hydro-jsk-baxter-web: 0.0.6-0 -> 0.0.11-0
 * ros-hydro-jsk-calibration: 0.1.5-0 -> 0.1.6-1
 * ros-hydro-jsk-common: 1.0.71-0 -> 2.0.3-0
 * ros-hydro-jsk-data: 1.0.71-0 -> 2.0.3-0
 * ros-hydro-jsk-footstep-controller: 0.1.5-0 -> 0.1.6-1
 * ros-hydro-jsk-footstep-msgs: 1.0.71-0 -> 2.0.0-1
 * ros-hydro-jsk-footstep-planner: 0.1.5-0 -> 0.1.6-1
 * ros-hydro-jsk-gui-msgs: 1.0.71-0 -> 2.0.0-1
 * ros-hydro-jsk-hark-msgs: 1.0.71-0 -> 2.0.0-1
 * ros-hydro-jsk-ik-server: 0.1.5-0 -> 0.1.6-1
 * ros-hydro-jsk-interactive: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-jsk-interactive-marker: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-jsk-interactive-test: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-jsk-model-tools: 0.1.12-0 -> 0.1.13-0
 * ros-hydro-jsk-nao-startup: 0.0.6-0 -> 0.0.11-0
 * ros-hydro-jsk-network-tools: 1.0.71-0 -> 2.0.3-0
 * ros-hydro-jsk-pcl-ros: 0.2.12-0 -> 0.3.6-0
 * ros-hydro-jsk-pepper-startup: 0.0.6-0 -> 0.0.11-0
 * ros-hydro-jsk-perception: 0.2.12-0 -> 0.3.6-0
 * ros-hydro-jsk-planning: 0.1.3-0 -> 0.1.4-1
 * ros-hydro-jsk-pr2-calibration: 0.0.6-0 -> 0.0.11-0
 * ros-hydro-jsk-pr2-startup: 0.0.6-0 -> 0.0.11-0
 * ros-hydro-jsk-pr2eus: 0.1.10-0 -> 0.1.11-0
 * ros-hydro-jsk-recognition: 0.2.12-0 -> 0.3.6-0
 * ros-hydro-jsk-recognition-msgs: 0.2.12-0 -> 0.3.6-0
 * ros-hydro-jsk-robot-startup: 0.0.6-0 -> 0.0.11-0
 * ros-hydro-jsk-roseus: 1.3.5-0 -> 1.3.9-0
 * ros-hydro-jsk-rqt-plugins: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-jsk-rviz-plugins: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-jsk-teleop-joy: 0.1.5-0 -> 0.1.6-1
 * ros-hydro-jsk-tilt-laser: 1.0.71-0 -> 2.0.3-0
 * ros-hydro-jsk-tools: 1.0.71-0 -> 2.0.3-0
 * ros-hydro-jsk-topic-tools: 1.0.71-0 -> 2.0.3-0
 * ros-hydro-jsk-visualization: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-jskeus: 1.0.6-0 -> 1.0.10-0
 * ros-hydro-julius: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-kalman-filter: 0.2.3-0 -> 0.2.4-0
 * ros-hydro-katana: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-katana-arm-gazebo: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-katana-description: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-katana-driver: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-katana-gazebo-plugins: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-katana-moveit-ikfast-plugin: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-katana-msgs: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-katana-teleop: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-katana-tutorials: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-kni: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-laser-filters-jsk-patch: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-laser-tilt-controller-filter: 0.1.23-0 -> 0.1.26-0
 * ros-hydro-librms: 0.0.2-0 -> 0.0.3-0
 * ros-hydro-libsiftfast: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-maggie-serial-comm-drivers: 0.0.1-0 -> 0.0.4-0
 * ros-hydro-manifest-cleaner: 0.2.3-0 -> 0.2.4-0
 * ros-hydro-mavlink: 2015.6.12-0 -> 2015.9.9-0
 * ros-hydro-mini-maxwell: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-multi-map-server: 1.0.71-0 -> 2.0.3-0
 * ros-hydro-multisense: 3.4.3-0 -> 3.4.4-0
 * ros-hydro-multisense-bringup: 3.4.3-0 -> 3.4.4-0
 * ros-hydro-multisense-cal-check: 3.4.3-0 -> 3.4.4-0
 * ros-hydro-multisense-description: 3.4.3-0 -> 3.4.4-0
 * ros-hydro-multisense-lib: 3.4.3-0 -> 3.4.4-0
 * ros-hydro-multisense-ros: 3.4.3-0 -> 3.4.4-0
 * ros-hydro-nextage-description: 0.6.2-0 -> 0.6.3-0
 * ros-hydro-nextage-moveit-config: 0.6.2-0 -> 0.6.3-0
 * ros-hydro-nextage-ros-bridge: 0.6.2-0 -> 0.6.3-0
 * ros-hydro-nlopt: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-object-recognition-ros-visualization: 0.3.6-1 -> 0.3.7-0
 * ros-hydro-openrtm-ros-bridge: 1.2.12-0 -> 1.2.14-0
 * ros-hydro-openrtm-tools: 1.2.12-0 -> 1.2.14-0
 * ros-hydro-opt-camera: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-pddl-msgs: 0.1.3-0 -> 0.1.4-1
 * ros-hydro-pddl-planner: 0.1.3-0 -> 0.1.4-1
 * ros-hydro-pddl-planner-viewer: 0.1.3-0 -> 0.1.4-1
 * ros-hydro-peppereus: 0.0.6-0 -> 0.0.11-0
 * ros-hydro-posedetection-msgs: 1.0.71-0 -> 2.0.0-1
 * ros-hydro-pr2-base-trajectory-action: 0.0.6-0 -> 0.0.11-0
 * ros-hydro-pr2-ethercat-drivers: 1.8.11-0 -> 1.8.15-0
 * ros-hydro-pr2-move-base: 0.1.23-0 -> 0.1.26-0
 * ros-hydro-pr2-navigation: 0.1.23-0 -> 0.1.26-0
 * ros-hydro-pr2-navigation-config: 0.1.23-0 -> 0.1.26-0
 * ros-hydro-pr2-navigation-global: 0.1.23-0 -> 0.1.26-0
 * ros-hydro-pr2-navigation-local: 0.1.23-0 -> 0.1.26-0
 * ros-hydro-pr2-navigation-perception: 0.1.23-0 -> 0.1.26-0
 * ros-hydro-pr2-navigation-self-filter: 0.1.23-0 -> 0.1.26-0
 * ros-hydro-pr2-navigation-slam: 0.1.23-0 -> 0.1.26-0
 * ros-hydro-pr2-navigation-teleop: 0.1.23-0 -> 0.1.26-0
 * ros-hydro-pr2eus: 0.1.10-0 -> 0.1.11-0
 * ros-hydro-pr2eus-moveit: 0.1.10-0 -> 0.1.11-0
 * ros-hydro-resized-image-transport: 0.2.12-0 -> 0.3.6-0
 * ros-hydro-rosapi: 0.7.8-0 -> 0.7.13-0
 * ros-hydro-rosauth: 0.1.6-0 -> 0.1.7-0
 * ros-hydro-rosbaglive: 0.2.3-0 -> 0.2.4-0
 * ros-hydro-rosbridge-library: 0.7.8-0 -> 0.7.13-0
 * ros-hydro-rosbridge-server: 0.7.8-0 -> 0.7.13-0
 * ros-hydro-rosbridge-suite: 0.7.8-0 -> 0.7.13-0
 * ros-hydro-roseus: 1.3.5-0 -> 1.3.9-0
 * ros-hydro-roseus-smach: 1.3.5-0 -> 1.3.9-0
 * ros-hydro-roseus-tutorials: 1.3.5-0 -> 1.3.9-0
 * ros-hydro-rosjava-bootstrap: 0.1.23-0 -> 0.1.24-0
 * ros-hydro-rosnode-rtc: 1.2.12-0 -> 1.2.14-0
 * ros-hydro-rospatlite: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-rosping: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-rostwitter: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-roswiki-node: 0.2.3-0 -> 0.2.4-0
 * ros-hydro-rqt-action: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-bag: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-bag-plugins: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-common-plugins: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-console: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-dep: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-graph: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-image-view: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-launch: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-logger-level: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-msg: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-plot: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-publisher: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-py-common: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-py-console: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-reconfigure: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-service-caller: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-shell: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-srv: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-top: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-topic: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-web: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rtmbuild: 1.2.12-0 -> 1.2.14-0
 * ros-hydro-rtmros-common: 1.2.12-0 -> 1.2.14-0
 * ros-hydro-rtmros-hironx: 1.0.31-0 -> 1.0.37-0
 * ros-hydro-rtmros-nextage: 0.6.2-0 -> 0.6.3-0
 * ros-hydro-rtt-actionlib: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-actionlib-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-common-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-diagnostic-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-dynamic-reconfigure: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-geometry-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-kdl-conversions: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-nav-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-ros: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-ros-comm: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-ros-integration: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-ros-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-rosclock: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-roscomm: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-rosdeployment: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-rosgraph-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-rosnode: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-rospack: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-rosparam: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-sensor-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-shape-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-std-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-std-srvs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-stereo-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-tf: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-trajectory-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-visualization-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rviz: 1.10.19-0 -> 1.10.20-0
 * ros-hydro-rviz-imu-plugin: 1.0.4-0 -> 1.0.5-0
 * ros-hydro-self-test: 1.8.7-0 -> 1.8.8-0
 * ros-hydro-semantic-point-annotator: 0.1.23-0 -> 0.1.26-0
 * ros-hydro-sklearn: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-speech-recognition-msgs: 1.0.71-0 -> 2.0.0-1
 * ros-hydro-staro-moveit-config: 0.1.8-0 -> 0.1.9-0
 * ros-hydro-task-compiler: 0.1.3-0 -> 0.1.4-1
 * ros-hydro-test-diagnostic-aggregator: 1.8.7-0 -> 1.8.8-0
 * ros-hydro-ueye-cam: 1.0.9-0 -> 1.0.11-0
 * ros-hydro-usb-cam: 0.3.3-0 -> 0.3.4-0
 * ros-hydro-virtual-force-publisher: 1.0.71-0 -> 2.0.3-0
 * ros-hydro-voice-text: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-wu-ros-tools: 0.2.3-0 -> 0.2.4-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
 * Anqi Xu
 * Austin Hendrix
 * Brice Rebsamen
 * Carnegie Robotics
 * Damon Kohler
 * Dan Lazewatsky
 * Daniel Stonier
 * Dash
 * David Gossow
 * David V. Lu!!
 * Devon Ash
 * Dorian Scholz
 * Florian Mirus
 * Henning Deeken
 * Isaac Isao Saito
 * Isaac Saito
 * Jim Rothrock
 * KazutoMurase
 * Kei Okada
 * Maintained by Carnegie Robotics LLC
 * Martin Günther
 * Matthias Gruhler
 * MoveIt Setup Assistant
 * Noda Shintaro
 * Orocos Developers
 * Raul Perula-Martinez
 * Russell Toris
 * Ryohei Ueda
 * Scott K Logan
 * Shohei Fujii
 * Shunichi Nozawa
 * Social Robots
 * TORK
 * Takuya Nakaoka
 * Vincent Rabaud
 * Vladimir Ermakov
 * Yohei Kakiuchi
 * YoheiKakiuchi
 * Youhei Kakiuchi
 * Yuki Furuta
 * Yusuke Furuta
 * Yuto Inagaki
 * furuta
 * inagaki
 * k-okada
 * saito

Official Docker Hub repo for ROS and Gazebo!

| No Comments | No TrackBacks
From Ruffin White via ros-users@

Hello everyone,

I'm happy to announce that ROS now has an official Docker Hub repository for ROS images [1].

You may remember earlier this year I asked the ROS community if there was any interest in starting such project [2]. Well, a few months and an OSRF internship later, OP is here to delver!

The official repository has been up for some time now, and it seems word has already gotten around as the project currently has +1000 downloads (and I know that wasn't just me), but I waited on announcing this until I had a bit of documentation and tutorials to go with it. So I'd also like to point out the Docker section that has been added to the ROS Wiki [3].

Another thing to add is that I have done the same for the Gazebo community as well, so if you'd like to start building your cloud based simulation clusters or quickly play with the latest version of Gazebo, v6.0, regardless of the dependencies you may not have installed on your workstation, you can download the official Docker Hub image for Gazebo [4].

The available ROS tags include supported distros, both Jade and Indigo, along with a hierarchy tags based off the most common meta-package dependencies:
  • ros-core: barebone ROS install
  • ros-base: basic tools and libraries (also tagged with distro name with LTS version as `latest`)
  • robot: basic install for robots
  • perception: basic install for perception tasks 
The rest of the common meta-packages such as desktop and desktop-full are hosted on automatic build repos under OSRF's Docker Hub oginsanal profile [5]. These meta-packages include graphical dependencies and hook a host of other large packages such as X11, X server, etc. So in the interest of keep the official images lean and secure, the desktop packages and perhaps more will just be hosted with OSRF's profile.

And as another plug for ROSCon 2015 [6], I'll also be giving a short presentation on this topic:
ROS + Docker: Enabling Repeatable, Reproducible, and Deployable robotic software via Linux Containers. So if you'd like to meet up and talk about shipping software containers in robots, I'll see you there.

If you have any technical questions feel free to ask on answers.ros.org with the tag "Docker", give me a ping @ruffsl, and feel free to help me flesh out the wiki docs!

Special thanks to OSRF for making this possible,
Ruffin

ROS Jade Turtle Release

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

jadeturtle_LoRes.jpg

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:

http://wiki.ros.org/ROS/Installation

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 prerelease.ros.org 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!

Jade Beta

| No Comments | No TrackBacks
We're happy to announce we're now in the Jade Beta! We're a few days behind schedule, but thanks to the hard work of all our contributors we've now got all of desktop-full released into Jade and available on packages.ros.org.

Even though we're a bit behind schedule, we would like to try and keep the original release date of May 23rd (also world turtle day [1] :D). That gives us just under 23 days until the release. We'll keep that date unless we run into a show stopper within desktop-full.

So between now and then I would encourage everyone who is able to:
  • Install `ros-jade-desktop-full` on Ubuntu and test out packages you regularly use.
    • Testing on other platforms is also appreciated!
  • Try out any documentation that you can, including tutorials, package wiki pages, and generated code docs.
  • Continue releasing packages and fill out the gaps between Jade and Indigo where possible.
If you find any issues while testing, please locate the issue tracker (usually on the corresponding wiki page for the package, e.g. wiki.ros.org/rviz) and report the issue there.

Auditing documentation is more challenging just because there is so much of it and searching on the wiki does not always make it easy to find pages with distribution specific content. So to help with this, I've done some special searches locally on the wiki's web server and compiled a list of pages which _may_ need to be updated for Jade:


So if you have time, please look at that list, and do a spot check on any pages that you use or have used in the past. Many of the core documentation pages are absent from that list because I've compiled them separately in a GitHub issue here:


Finally, if you are trying to release a package for Jade and the dependencies are not there yet, please contact the maintainers or ask for help on ros-release@lists.ros.org.

Thanks again to everyone who helped get the Jade beta out (mostly) on time.

Cheers,

P.S. Only ros-jade-desktop is available on armhf right now, we're waiting on an updated set of gazebo5 debs and then we'll have desktop-full on armhf as well. Also, armhf is Trusty only right now.

P.S.S. If you are testing gazebo-ros integration, we are aware of an issue with the launch files and are tracking it here:


A work around is to install `libgazebo5-dev` manually. We hope to have a proper fix out soon.

ROS Jade Turtle Logo and Release T-shirt

| No Comments | No TrackBacks
With each release of ROS we have a tradition of having a logo and making t-shirts. ROS Jade Turtle is coming out in May. Show your ROS colors and support this tradition!  Visit the Teespring Campaign page here to order your shirt.

jade_tshirt_mockup.png
Proceeds from shirt sales go to supporting the costs associated with developing and maintaining ROS, including hosting the wiki and running the build farm. 

There are both mens and womens sizes as well as hoodies available. 

Order now and if this campaign is funded we expect the shirts to arrive approximately when ROS Jade Turtle is released. The campaign closes on May 11th don't wait too long to order.

Here's a copy of the full logo:
jadeturtle.jpg

Jade Build Farm Kick-Off

| No Comments | No TrackBacks
I wanted to give an update on the next distribution of ROS, which we are calling ROS Jade! We've been working on getting things ready for people to start releasing packages into Jade at their convenience.

We have many of the system dependencies spec'ed out for Jade and we've catalogued them in REP-0003 [1]. So far we have over 140 packages released into Jade, including many of the core ROS packages, with binaries for Ubuntu Trusty, Utopic, and Vivid [2]. You can compare what's in Jade versus other distributions as well [3].

At this point I think it is safe for maintainers to start releasing their packages into Jade. Necessarily, you'll need the packages which you depend on to be released before you can release your packages, but some recent improvements to bloom should make it easier to check that, so make sure you have bloom version 0.5.17 or greater before trying to release!

If you find that some of your dependencies are not released yet, I encourage you to work with the maintainers for those packages and ask them to do so.

The Jade release it targeted for May 2015, so we have several months to get things released and tested, but we should avoid procrastinating.

There are few things still missing for the Jade kick-off, but we are tracking them on GitHub [4].
For example, we are still working on the pre-release instructions for Jade, but I've decided to make this announcement anyways because the pre-release is designed to make sure your release doesn't break packages which depend on your packages.
Since your packages should not have any downstream dependencies yet, releasing without a pre-release right now is okay.
So, when releasing a package for the first time into Jade, releasers should run the local deb build test [5] or just release without a pre-release test.

Thanks, and happy releasing!






















Yaskawa Motoman Robotics is pleased to announce sponsorship of the Amazon Picking Challenge to be held in conjunction with ICRA 2015. This open competition will further the development of robot skills required for e-commerce and other material handling. Yaskawa Motoman is offering consignment robots to select teams entering the challenge. Selected teams will receive their choice of robot model in January, 2015 and may keep them through June, subject to model availability. To apply for a Motoman consignment robot, please submit the following items via this form by midnight PST December 17, 2014 January 16, 2015 (extended deadline).

Video of a simulated robot executing a picking task

Link to your team/organization website

Completed application describing your Motoman hardware utilization plan


Yaskawa Motoman will provide robots, software (including our MotoROS driver), and onsite technical support both at the team's location and the event.


To support your development efforts, the ROS-Industrial Consortium will be updating its pick and place tutorial to include the Motoman MH5 II model. The tutorial will also be updated to ROS Indigo.


Additional resource links:

Support OSRF!

| No Comments | No TrackBacks
Cross posted from osrfoundation.org

When we started the ROS project back in 2007, our goal was to build an open robotics software platform for students, engineers, entrepreneurs, and anyone else to freely use and modify. In 2012, we took the next step by founding OSRF as an independent non-profit organization to pursue that mission, with responsibility for both ROS and Gazebo. Today, we see these tools used worldwide to teach concepts, solve problems, and build products in ways that we couldn't have imagined at the beginning.

We couldn't be happier with the size and breadth of the collaborative community that we've built together, and we're grateful to everyone in the community for the roles that you've played.

You won't be surprised to hear that it costs money to run OSRF. We employ a small team of amazing individuals, we operate an office in the Bay Area, and we run a suite of online services on which the community depends.

Since our founding, OSRF has enjoyed generous financial support from government agencies and private industry, for which we're very grateful. We hope and anticipate that that support will continue in the future. But now, as we approach the end of OSRF's third year, we're trying something new: asking you, our users, for support.

If you rely on ROS and/or Gazebo in your lab, your startup company, your weekend projects, or elsewhere, please consider donating to OSRF. Your donation will support our people and infrastructure so that we can spend (even) more time developing and maintaining the software and services on which you depend.

As one example, if everyone who visits the ROS wiki between now and the end of the year donates just $2, we'll have our costs covered for next year to manage, update, and host all of our online services, including the wiki. Donations in any amount are welcome. Give more, and we can do more.

Donate to OSRF today.

Thank you for your support.

Contributions to the Open Source Robotics Foundation, a 501(c)(3) non-profit organization, will be used at its discretion for its charitable purposes. Such donations are tax-deductible in the U.S. to the extent permitted by law.

Call for authors for a ROS Handbook

| No Comments | No TrackBacks

From Anis Koubaa via ros-users@

I am coordinating with Springer publisher to edit a handbook on Robot Operating System. There are only a few books on ROS http://wiki.ros.org/Books which mainly represent a brief introduction to ROS and a few basic applications. This does not translate the huge amount of work being done in the community and I feel the need to have a complete reference on the topic.

The prospective handbook will cover ROS from foundations and basics to advanced research works from both academia and industry. Tutorials and research papers will both be sought. The book should cover several robotics areas including but not limited to robot navigation, UAVs, arm manipulation, multi-robot communication protocols, Web and mobile interfaces using ROS, integration of new robotic platform to ROS, computer vision applications, development of service robots using ROS, development of new libraries and packages for ROS, etc. Every book chapter should be accompanied with a working code to be put later in a common repository for the readers.

To express your interest to the handbook and your intention of a chapter proposal, I would like to invite you fill in the following form. The proposed chapters are just considered as an initial expression of interest and will be included in the handbook proposal. It does not mean any kind of commitment for the author at this stage. An official call for chapters with instructions and deadline will be announced soon.

Thank you and look forward to receive your feedback,

Anis

NavVis presents new large scale mapping technology: The impressive shipping exhibition at Deutsches Museum can now be explored online and in 3D.

NavVis utilizes a trolley that's equipped with three laser scanners and six cameras. As a human operator wheels that trolley through the area to be mapped, the scanners record the horizontal and vertical dimensions of the hallway while the cameras record panoramas. The software framework is based on ROS, which allowed for a very modular design, as Suat Gedikli, Chief Software Architect at NavVis, says. One of the main advantages of their mapping device is its efficiency: In contrast to Google's mapping trolley, the operator does not have to crouch to move out of the field of view of the panoramic camera. With the patented NavVis camera head, the six cameras are assembled in a way such that the trolley operator is in their blind spot and therefore not visible. Hence 360-degree panoramas can be continuously recorded while moving the trolley.

[NavVis]TrolleyM3_total_3.png

The start-up recently teamed up with Deutsches Museum to digitize their impressive shipping exhibitions, which were mapped in less than one hour. The result is a 3D map of the exhibition, overlaid with photos of every square inch of all the surfaces.

Bildschirmfoto 2014-09-_opt.png

Similar to Google Street View, their HTML5 based IndoorViewer allows people to virtually explore the museum online. Additionally, administrators can add content like text, images, video to various points on the map, which can then be accessed by users. This interactive feature also lets users do things like obtaining measurements between different points in the building (which is important for architects and in construction site monitoring applications).

NavVis, which was only founded in May of last year, is focused on public-oriented showcases and business-to-business applications. Felix Reinshagen, co-founder and managing director: "As the first step, our application is aimed at companies in the building management segment that are confronted with challenges such as documentation, inventory, path-finding and task management. We make our hardware, software and service available to them so that they can have their building and industrial plants digitized while handling the usage of their data according to their own requirements. An area the size of the Deutsches Museum is mapped and posted online within three working days for a four-figure amount."

Bridging the Gap between ROS and JAUS

| No Comments | No TrackBacks
from Danny Kent, via ros-users@

Hello ROS Users!

One of the questions we've heard quite often lately is how to bridge the gap between ROS and JAUS. The Joint Architecture for Unmanned Systems (JAUS) is an SAE International Standard for command and control of robots. A lot of people have built solutions based on ROS and need to quickly and reliably integrate those solutions using JAUS or vice versa. Previously, the learning curve to do has been difficult as there has been a lack of software to solve the problem. To assist with this problem we decided to build a software bridge between ROS and JAUS. We call it jROS and we've just finished our first cut at it!

jROS allows users to combine the power and flexibility of ROS with the maturity and robustness of the JAUS standard. The software consists of a set of ROS messages and services which are defined with respect to the JAUS message structure. This creates a 1-to-1 mapping of data in JAUS and ROS via our jROS Package. Adding the jROS topics to an existing ROS system is trivial. Once integrated, the ROS data can be exchanged with the JAUS network in a well-defined way. 

Take a closer look at jROS here: http://www.openjaus.com/products/jros

Best,
~Danny Kent, PhD
Co-Founder
OpenJAUS, LLC

2014 ROS Metrics Report Available

| No Comments | No TrackBacks
The 2014 edition of the ROS Metrics Report is now posted at: http://download.ros.org/downloads/metrics/metrics-report-2014-07.pdf

This is the 4th version of the ROS Metrics report. All are versions are available at: http://wiki.ros.org/Metrics 

The ROS community has grown in almost every metric. The one exception is that the number of wiki pages has dropped. This is due to a concerted cleanup effort earlier this year which removed a lot of empty pages with little to no content. 

The other metric which warrants note is the large growth in the number of unique IPs per month, up to 49,153 from last years sampling of 11,078.  And the total downloads of packages more than doubled to 3,570,374 downloads. 

And all of these numbers do not count the any statistics for mirrors either private or public

If you have a moment we recommend you take a look. There are many interesting statistics such as ROS users by country and the top 40 most downloaded packages. 

Related to this look for more information on the ROS ecosystem from William Curran's talk next week at ROSCon 2014.  Event Program


Lasers, anyone?

| No Comments | No TrackBacks

We're happy to announce that SICK has donated hardware to OSRF for the ROS community to use in testing and development. We're now the proud owners of one each of the following laser scanners: TiM551, LMS111, and LMS511.

tim551.jpg lms111.jpg lms5xx.jpg

This generous donation was motivated by SICK's longstanding commitment to robotics, combined with their desire to see first-class support for their sensors in ROS. The LMS series is best known for providing reliable LiDAR data in tough conditions including the DARPA Urban Challenge and Boston Dynamics' LS3 AlphaDog. The TiM is a smaller version designed for great performance with low power consumption in indoor or outdoor environments.

The sensors are available for loan to members of the ROS community who want to use them for testing and development, and especially for improvement of the ROS drivers and associated tools. If you'd like to borrow one of these devices to try it out in your project, please let us know: info@osrfoundation.org

Thank you to our friends at SICK, and we look forward to even more robotics applications that are enabled by SICK sensors and ROS software!

ROS Indigo Igloo Released!

| No Comments | No TrackBacks

indigoigloo_600.png

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 answers.ros.org. 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

from Roberto Guzmán via ros-users@


Hi all :)

We are pleased to announce AGVS: the new Open ROS Platform for Logistics Transport. 

AGVS is an autonomous robot for indoor logistic intra-hospital transport. The robot has Ackermann kinematics and is provided with ROS architecture for simulation and control. 

This robot is currently serving in several European hospitals, and this is the first open version released. 

The provided software includes the packages for simulating the robot in several environments, generating maps, localize and define routes through a rviz interactive marker based interface.

It is an excellent starting point for anyone developing new generation logistics applications. 

You can find more info in:

Some additional information about the robot can be found in:

Enjoy it!,

  Roberto


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].

[1] http://wiki.ros.org/indigo/Migration

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 Aaron Sims via ros-users@

Dear ROS News & ROS Users,

We recently released our Java based ROS Client in our RMDMIA Framework with the addition of functional UDPROS support. We currently are releasing our ROS Client under our Preview Evaluation License for free. We intend to use a much more open license on the ROS Client version of it after we deal with IP on our Autonomous framework. A list of tutorials is below. To enable UDP, specify UDPROS in the Preferred Protocol Column in the Configuration Manager, Save and Restart.

Thanks for any assistance you may be able to provide!

Sincerely,

Aaron Sims

Release Announcement - 6/24/2014
UDPROS protocol support added to RMDMIA slipstream 8 release. This release includes major bug fixes, new functionality, and feature enhancements.
We are building the most flexible, developer friendly, high performance ROS Client for Java. Its time to share our ROS Client with the Java Development Community. We need input on our new Robotic Controller platform, and we will be releasing incremental components to our autonomous robotic framework to Java developers. Developer registration will be required to download and use our new components. We will strongly encourage Java developers to make the RMDMIA Framework their Robotics platform for Java (Registration required).
Features:
  • Java based ROS Client integrated with TCPROS & UDPROS protocol implementations. (UDPROS is broken until the next slipstream).
  • Automated performance tuning for autonomous robotic systems (will be included in next slipstream).
  • Automated Topic/Service Discovery
  • Graphical Configuration Tool (Java only)
  • Low level datastream reader
  • A single consistent API for ROS that does not require compilation or complicated configurations to run.
  • RCSM ROS Provider API Documentation
Here is a screenshot of the ROS Configuration Manager.
ROS_Configuration_Manager.png

The Java based Robotic Software Controller Framework for the RMDMIA for Android/Java(Robotic Mission Decision Manager Intelligent Agent). API Documentation, and framework included. The RMDMIA Framework is a plugin/provider framework that is flexible enough that a developer can write a User Interface plugin that works across multiple Robotic Hardware Control Systems. This Technology Preview Release includes a configurable Timer Service, RCSM (Robot Control System Messenger) API, and ROCI (Robot Operator Control Interface) API. Implementers of ROCI, & RCSM interfaces will be able to post there plugins/providers/RMDMIA components to the Happy Artist Marketplace in the near future. 
Happy_Artist_Visio_1a.jpg

New Tutorial Announcement - 5/27/2014
  1. Tutorial: RMDMIA Client Configuration for ROS Turtlesim
  2. Tutorial: Howto build a teleoperation controller for  ROS Turtlesim with a PS/3 Joystick using the RMDMIA ROCI Provider
  3. Tutorial: Howto implement a ROS Topic Subscriber Message Handler
  4. Tutorial: Howto Publish to a ROS Topic
  5. Tutorial: Howto to call a ROS Service
  6. Tutorial: Howto to call a persistent ROS Service
  7. Tutorial: Howto implement a ROCI (Robot Operater Control Interface) Provider 

Robopeak announces ROS Drivers for the RPLIDAR

| No Comments | No TrackBacks
From ShiKai Chen

Descriptions & Images:
=====================
RPLIDAR is a low cost LIDAR sensor suitable for indoor robotic SLAM application. It provides 360 degree scan field, 5.5hz rotating frequency with guaranteed 6 meter ranger distance.  By means of the high speed image processing engine designed by RoboPeak, the whole cost are reduced greatly, RPLIDAR is the ideal sensor in cost sensitive areas like robots consumer and hardware hobbyist.

The RPLIDAR core engine performs high speed distance measurement with more than 2000 samples per second. For a scan requires 360 samples per rotation, the 5.5hz scanning frequency can be achieved. Users can customized the scanning frequency from 2hz to 10hz freely by control the speed of the scanning motor. RPLIDAR will self-adapt the current scanning speed.

ROS Node:
=====================

Videos:
====================
Odometer Free Hector map building using RPLIDAR

Scan Record:

About RoboPeak
~~~~~~~~~~~~~~~
RoboPeak is a research & development team in robotics platforms and applications, founded in 2009. Our team members are Software Engineers, Electronics Engineers and New Media Artists that all come from China.

RoboPeak develops both software and hardware, which include personal robotic platforms, Robot Operating System and related devices.

Our vision is to enrich people's daily-life with the ever-changing development and innovation in robotic technologies.

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
 * OSRF
 * Ryohei Ueda
 * Sachin Chitta
 * Scott Niekum
 * Sebastian Kasperski
 * Severin Lemaignan
 * Shadow Robot's software team
 * Shaun Edwards
 * Shohei Fujii
 * Stuart Glaser
 * TODO
 * 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
 * TODO
 * Takuya Nakaoka
 * Tom Moore
 * Vincent Rabaud
 * William Woodall
 * Yohei Kakiuchi
 * ferenc
 * ferko
 * furuta
 * jworch
 * winkler

Occipital committed to support OpenNI

| No Comments | No TrackBacks
From Nicolas Burrus at Occipital via ros-users@

You may have noticed that openni.org has shut down today, as
previously announced. However at Occipital we committed to support
OpenNI when we launched our Structure Sensor, so we have created an
online resource with OpenNI2 source code, binaries and documentation.
We will also do our best to keep supporting other Primesense-based
sensors such as Carmine and Asus Xtion.

Since the project will remain open source, any help to maintain or
improve OpenNI is welcome!

You can check out the webpage here: http://structure.io/openni

ROS Indigo Igloo Logo and Release T-shirt

| No Comments | No TrackBacks
With each release of ROS we have a tradition of having a logo and making t-shirts. ROS indigo Igloo is coming out in May. To let you show your ROS colors and support this tradition, we have setup a Teespring Campaign here.  Ordering will be open until May 13th.

indigo_front.jpg

Proceeds from shirt sales go to supporting the costs associated with developing and maintaining ROS, including hosting the wiki and running the build farm. 

We're also happy to announce that there are a few variants such as long sleeved and v-necked shirts as well as hoodies are also available. 

Order now and if this campaign is funded we expect the shirts to arrive approximately when ROS Indigo Igloo is released. 

Update 2014-04-26: The campaign has exceeded the minimum of 100 t-shirts. It will be produced!

Here's a copy of the full logo too: 
indigoigloo_600.png

ROS Indigo Igloo buildfarm running

| No Comments | No TrackBacks
We're pleased to announce the ROS build farm for Indigo Igloo is now available.  It includes over 180 packages already for Ubuntu 13.10, Saucy Salamander, and Ubuntu 14.04, Trusty Tahr. We expect that number to continue to grow rapidly. Installation instructions already exist for Ubuntu using debians or for compiling from source [1], and you can see the status of Indigo packages on this page:


If you are a maintainer please look at what packages have been released and consider releasing yours as soon as your upstream dependencies have been satisfied.  If you are blocked on another package being released please contact the maintainer.  And if you cannot reach the maintainer please email ros-release@lists.ros.org (join if you aren't a member already).

If you are planning to release into Indigo please read the information provided in the migration guide [2] and refer to the bloom tutorials [3] for doing the release. Please also contribute to the migration guide for updates relating to your package.

After releasing your packages the build farm will keep you notified of the status of the individual jobs. Please pay attention to the automated emails from the buildfarm, if jobs are failing they block downstream packages from releasing and waste our build resources. 

New Package: ROS Glass Tools

| No Comments | No TrackBacks
From Adam Taylor via ros-users@

We would like to announce ros_glass_tools, an open source project that aims to provide easy voice control, topic monitoring, and background alerts for robot systems running ROS using the Google Glass.  It communicates with ROS using the rosbridge_suite.  


More information about the tools can be found at the following links.


ROS...launch!

| No Comments | No TrackBacks
Crossposted from www.osrfoundation.org


Albert II is famous for being the first monkey in space, in June 1949. Laika is equally renowned for being the first animal to orbit the Earth, in 1957. On Sunday, March 16th, at 4:41am (unless inclement weather intervenes), ROS will celebrate its own celestial milestone when it is launched into space aboard a SpaceX rocket as part of a resupply mission to the International Space Station (ISS).

Albert II
Laika

In conjunction with NASA's Robot Rocket Rally March 14-16 at the Kennedy Space Center in Florida, SpaceX's third mission will include a set of robotic legs for the Robonaut 2 (R2) humanoid torso that is currently aboard the ISS. Once those legs are attached to R2, ROS will officially be running in space.

For the last few years, the NASA/GM team at the Johnson Space Center has been using ROS for R2 development here on Earth. We first heard about that at ROSCon 2012 in Stephen Hart's keynote presentation, where he described how they combine ROS and OROCOS RTT to achieve flexible, real-time control of R2. Following the launch this weekend, that open source software will be running on the R2 that's on ISS.

Robonaut 2 legs
Robonaut 2 simulation

The R2 team also uses the open source Gazebo simulator to simulate R2 when they're doing development and testing. They've released their models of R2 and ISS as open source for the community to work with. We recently integrated those models into an immersive teleoperation Gazebo demonstration that we'll be running at the Robot Rocket Rally this weekend. Drop by our booth and find out what it's like to "be" Robonaut 2!

ROS has already powered robots in the air, on the ground, on and under the water, and on every continent, but we at OSRF couldn't be more excited about ROS journeying to outer space.


From Kel Guerin at Johns Hopkins University

)

At the Laboratory for Computational Sensing and Robotics at Johns Hopkins University, we have utilized the extensive visualization tools available in ROS to create an immersive virtual reality environment for interacting with robots. The versatile plug-in system for the RVIZ visualization package has allowed us to create virtual user interfaces, information displays, and interactive objects that co-exist with other resources in the RVIZ environment. Additionally, the excellent Oculus Rift RVIZ plugin gave us the perfect starting point for using RVIZ as a VR environment. This provides us an excellent test-bed for virtually teleoperating an teleprogramming our robots. Finally, the flexibility of ROS lets us deploy IVRE on several robots in our lab, including industrial systems and surgical robots. For more information on the tools we used, checkout the oculus rviz plugin and the RVIZ plugin API.

From Angel Merino Sastre & Simon Vogl via ros-users@

Hi all,

We are happy to announce the sentis-tof-m100 ros package:

https://github.com/voxel-dot-at/sentis_tof_m100_pkg

This package provides support for the Bluetechnix Sentis ToF M100 camera
based on the software API that is provided with the camera, along with
a detailed installation how-to and a ready-to-use launch file with a
visualization example based on rviz.


Any comment/suggestions are welcome
SPI1-400x312.jpg

The Shadow Robot Company is excited to announce the next module in the RoNeX range - the RoNeX SPI Module!


This Module allows the connection of multiple SPI (Serial Peripheral Interface) devices to ROS. It provides 4 discrete SPI ports, plus 6 Analogue inputs and 6 General Purpose Digital I/O lines. The Digital I/O can be used as additional SPI chip select lines, allowing the module to interface with up to 10 SPI devices in total.


RoNeX makes data from these SPI devices directly accessible via ROS topics, and of course a single RoNeX stack can comprise a mix of GIO Modules and SPI Modules that best suits your project.


The RoNeX ROS wiki page can be found here and source here. More details on RoNeX here.


Introducing ROStful: ROS over RESTful web services

| No Comments | No TrackBacks
From Ben Kehoe via ros-users@

Hello all,
ROStful is a lightweight web server for making ROS services, topics, and actions available as RESTful web services. It also provides a client proxy to expose a web service locally over ROS.

Here at Berkeley we are working to bring Software as a Service (SaaS) paradigms into robotics. We have created ROStful as a starting point for creating SaaS tools using existing ROS services and actions.

ROStful web services primarily use the rosbridge JSON mapping for ROS messages. However, binary serialized ROS messages can be used to increase performance.

The purpose of ROStful is different from rosbridge: rosbridge provides an API for ROS through JSON using web sockets. ROStful allows specific services, topics, and actions to be provided as web services (using plain get and post requests) without exposing underlying ROS concepts.
The ROStful client proxy, however, additionally provides a modicum of multi-master functionality. The client proxy is a node that connects to a ROStful web service and exposes the services, topics, and actions locally over ROS.

The ROStful server is WSGI-compatible and can therefore be used with most web servers like Apache and IIS.

Try it out (there are no dependencies!), and let us know what you think! https://github.com/benkehoe/rostful

Two minor notes:
Serialized ROS messages are sent with the MIME type 'application/vnd.ros.msg'. If there's a standard anyone else is using, let us know.
In the absence of a standard component description format, ROStful uses an INI-based format that may be of interest for creating such a standard description. See here for details.

RoNeX and Matlab

| No Comments | No TrackBacks
ronex.jpeg

RoNeX, the latest product from the Shadow Robot Company, enables sensors and actuators to be connected seamlessly to ROS.

Thanks to the guys at Mathworks, data from sensors attached to RoNeX devices can now be easily accessed from Matlab. We are very excited about this Matlab and ROS based Rapid Prototyping Platform, especially when complex sensors are required.

Please don't hesitate to contact us if you want more info:contact@shadowrobot.com

ROS Answers reaches 15,000 questions

| No Comments | No TrackBacks
We're excited to share that answers.ros.org has grown to over 15,000 questions, submitted by over 6,000 registered users!

ros_answers_15k.png

The site has matured into an excellent crowd-sourced resource for the ROS community. There are over 10,000 questions with accepted answers and another approximately 2,000 questions with at least one proposed answer. The site has recently maintained a sustained velocity of over 15 questions per day. It's been only eleven months since we hit 10,000 questions last March

The answers.ros.org site is a community effort and everyone's participation, from asking or answering questions, to cleaning up tags, is greatly appreciated . Each and every contribution improves the site for the ROS community.  If you have not yet joined us on answers.ros.org, give it a try and help us get to 20,000!

Updated ROS cheat-sheet for Hydro + Catkin

| No Comments | No TrackBacks
From Ryan Gariepy via ros-users@

Hi all,

We've put together an updated ROS cheat-sheet for Hydro+catkin. Check it out here.

Feedback and suggestions are always welcome!

Ryan

matlab_ros_thumb.png

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 www.mathworks.com/ros

Shadow Robot's RoNeX available for ROS Hydro

| No Comments | No TrackBacks

ronex.jpeg

The Shadow Robot Company is excited to announce ROS Hydro support for RoNeX, a scalable, industrial strength fieldbus for robots.


RoNeX allows ROS users to prototype and build ROS robots quickly and easily, providing a seamless link between ROS and a variety of sensors and actuators.


"At Shadow we use ROS in almost every project, so ROS Hydro drivers were our first priority" said Ugo Cupcic, Head of Software at Shadow. "We have been using RoNeX internally for prototyping new robots and our engineers all needed great ROS support, so that really set a high bar for the software team to meet!"


Devices connected via RoNeX can be directly accessed via ROS topics. Custom transmissions have also been implemented for ROS Hydro, so it's incredibly simple to control joint based robots just by adding a few extra lines to a URDF description.


ROS Hydro drivers are available now from your standard ROS repositories for the RoNeX General Input/Output Module. Shadow expects to announce an SPI Module very soon, with ROS Hydro drivers to follow shortly afterwards.


The RoNeX ROS wiki page can be found here and source here. More details on RoNeX here.


Release of catkinized nao_robot stack 0.2

| No Comments | No TrackBacks
From Armin Hornung via ros-users@

Dear ROS users,

it's my pleasure to announce a new release of packages for the Nao robot. Most notably, that's v0.2 of the nao_robot stack (or now, metapackage), which is now catkinized for ROS groovy and hydro thanks to Miguel Sarabia. The stacks nao_robot and nao_common also saw a complete reorganization of packages and an overhaul to enable easier usage on the robot, thanks to Séverin Lemaignan. Parts of the nao_common stack have moved into nao_robot, with the remainder in the new stack nao_extras (still rosbuild as of now).

All code should be compatible with ROS groovy and hydro, as well as NaoQI 1.12 and 1.14.

Grab the latest versions (tagged release / source package, or clone the master branch) here:
https://github.com/ahornung/humanoid_msgs
https://github.com/ahornung/nao_robot
https://github.com/ahornung/nao_extras/

Source install instructions are available at http://wiki.ros.org/nao/Installation/remote

Thanks to Séverin, it's now really easy to compile ROS and the Nao packages to run directly on the robot:
http://wiki.ros.org/nao/Installation/local

Precompiled binary packages for the Nao and Debian packages to run your machine are in preparation.

You can find separate changelogs in the packages, the complete lists of changes are available here:
https://github.com/ahornung/nao_robot/compare/0.1.0...0.2.1
https://github.com/ahornung/nao_extras/compare/0.1.0...0.2.0

If you want to discuss future development or contribute, consider jointing the ros-sig-aldebaran mailing list:
https://groups.google.com/forum/?fromgroups#!forum/ros-sig-aldebaran

Since this was a combined community effort, I would like to thank thank Miguel Sarabia, Séverin Lemaignan, Daniel Maier, and Sebastian Boettcher for their contributions.

Best Regards

ROS for Labview Preview from Tufts CEEO

| No Comments | No TrackBacks
The Mechanical Engineering Department and the Center for Engineering Education and Outreach at Tufts University are releasing an alpha version of a ROS client library for Labview with the goal of creating a platform independent and intuitive ROS environment. 

labview_diagram3.png
In its current state, the library supports publishers, subscribers, and service clients on predefined topics and contains a partial implementation for the Baxter Research Robot from Rethink Robotics. The library was built in Labview 2010 on OS X and has been tested successfully in Windows 7.

labview_diagram.png

This is a prerelease and should not be expected to remain stable. UI and structural changes should e expected along with further feature support. If you are interested please try it out and give us feedback at ros-sig-rosforlabview@googlegroups.com You can find the package on github at https://github.com/chris-smith/ROSforLabview


From Lukas Bulwahn on ros-users@

Hi everyone,

Since we kicked off the OpenEmbedded Layer meta-ros project in January this year, we have made much progress and are now happy to announce our first release of the OpenEmbedded Layer meta-ros. You can download the first release from https://github.com/bmwcarit/meta-ros/releases, or
follow the installation instructions on the ros wiki at http://wiki.ros.org/hydro/Installation/OpenEmbedded.

The OpenEmbedded Layer meta-ros features
  - a general cross-compilation tool chain for catkin packages,
  - 78 ROS packages, including all ros-comm packages, actionlib, nodelet_core, common_msgs, tf and image_transport,
  - recipes for roscpp_tutorials and common_tutorials as examples for your own tool chain, and
  - all provided packages are Hydro release versions (as set in hydro/release.yaml [4]).

With the OpenEmbedded Layer meta-ros, you can
  - define the cross-compilation tool chain for your ROS packages with just a few lines, and
  - build an embedded Linux system with your ROS application by typing a one-line shell command.

Standing on the shoulders of giants, the OpenEmbedded Layer meta-ros can be incorporated with the tools, board support packages and infrastructure of the OpenEmbedded/Yocto environment. For example, the OpenEmbedded/Yocto environment provides
  - Board support packages for various architectures, boards, devices and emulators [5].
  - The Hob graphical user interface that enables you to build and deploy a custom OS image easily.
  - The Eclipse IDE Plug-in that integrates the application development and its toolchain into the Eclipse IDE.

The OpenEmbedded Layer meta-ros
  - was tested for architectures arm, ppc, x86, x86-64 and on the Beagleboard and on the Trimslice board, and
  - works with the OpenEmbedded-Core development branch, the Angstrom distribution and the Poky-dylan distribution with some minor patches.

Please report problems and issues to our github issue tracker [1], and follow our mailing list [2] or star the github project [3].

Enjoy ROS on your favorite embedded device!


Lukas Bulwahn, BMW Car IT GmbH


References:

[1] https://github.com/bmwcarit/meta-ros/issues
[2] https://groups.google.com/forum/#!forum/meta-ros
[3] https://github.com/bmwcarit/meta-ros
[4] https://raw.github.com/ros/rosdistro/770d0ac9ac549a255210c0aa83902e2dc0d0e4da/hydro/release.yaml
[5] http://layers.openembedded.org/layerindex/machines/

ROS Hydro Medusa Released!

| No Comments | No TrackBacks
Hydromedusa_web1.jpg

Hi Everyone, 

We are happy to announce the release for ROS Hydro Medusa! [0] This is the 7th official release of ROS and thanks to the large growing community it is by far the most capable.  [1]

This is the result of many contributors.  Over 50 maintainers released packages into Hydro during the pre-release cycle.  Resulting in over 700 packages available in the initial release on all three supported platforms (Ubuntu Precise, Ubuntu Quantal, Ubuntu Raring)[2]  However the publicly released packages is a small portion of the greater ROS ecosystem.  The rosdistro repository has 248 public forks where people are working on their own customizations and the repository has already integrated over 1000 pull requests from these contributors.  [3][4]  We expect people to continue releasing new packages to be built on top of the already released hydro packages as they have done for Groovy and other distributions in the past.  

For a quick visualization of the many people committing over the course of the Hydro development cycle we generated a video here:

With Hydro released we can officially start planning for Indigo Igloo which is targeted for release in April 2014.  If you would like to bring up a topic of interest for the Indigo development cycle I suggest you take a look at existing Special Interest Groups(SIG) [5] or start a discussion here on ros-users if you cannot find an appropriate SIG. Indigo will be the first release on the new 12 month cycle as discussed on ROS Users.  [6] 

Also with the release of Hydro and the beginning of looking at Indigo development we officially drop support for ROS Fuerte.  There are several patches which we expect to backport from the Hydro development however in the not to distant future new builds of Fuerte packages will no longer be possible.  

The final release also includes many updated packages.  For the full list please see below.  

Your ROS Hydro Medusa Release Team







Packages Updates:
Packages Added: 
ros-hydro-cmvision : 0.4.1
ros-hydro-declination : 0.0.1
ros-hydro-hector-gazebo : 0.3.0
ros-hydro-hector-gazebo-plugins : 0.3.0
ros-hydro-hector-gazebo-thermal-camera : 0.3.0
ros-hydro-hector-gazebo-worlds : 0.3.0
ros-hydro-hector-models : 0.3.0
ros-hydro-hector-object-tracker : 0.3.0
ros-hydro-hector-sensors-description : 0.3.0
ros-hydro-hector-sensors-gazebo : 0.3.0
ros-hydro-hector-worldmodel : 0.3.0
ros-hydro-hector-worldmodel-geotiff-plugins : 0.3.0
ros-hydro-hector-worldmodel-msgs : 0.3.0
ros-hydro-hector-xacro-tools : 0.3.0
ros-hydro-kobuki-core : 0.5.2
ros-hydro-kobuki-dock-drive : 0.5.2
ros-hydro-kobuki-random-walker : 0.5.2
ros-hydro-media-export : 0.1.0
ros-hydro-mjpeg-server : 1.1.0
ros-hydro-openni2-camera : 0.1.0
ros-hydro-rocon-conductor-graph : 0.5.3
ros-hydro-rqt-cpp-common : 0.3.0
ros-hydro-tf2-web-republisher : 0.2.0
ros-hydro-um6 : 0.0.1
ros-hydro-usb-cam : 0.1.3

Packages Removed: 
ros-hydro-test-rosbag : 1.9.47
ros-hydro-test-rosgraph : 1.9.47
ros-hydro-test-roslaunch : 1.9.47
ros-hydro-test-roslib-comm : 1.9.47
ros-hydro-test-rosmaster : 1.9.47
ros-hydro-test-rosparam : 1.9.47
ros-hydro-test-rospy : 1.9.47
ros-hydro-test-rosservice : 1.9.47

Packages Updated: 
ros-hydro-actionlib : 1.10.2 -> 1.10.3
ros-hydro-calibration : 0.10.0 -> 0.10.2
ros-hydro-calibration-estimation : 0.10.0 -> 0.10.2
ros-hydro-calibration-launch : 0.10.0 -> 0.10.2
ros-hydro-calibration-msgs : 0.10.0 -> 0.10.2
ros-hydro-camera-calibration : 1.11.1 -> 1.11.2
ros-hydro-chatter-concert : 0.5.5 -> 0.5.6
ros-hydro-cmd-vel-mux : 0.3.0 -> 0.4.0
ros-hydro-concert-conductor : 0.5.4 -> 0.5.5
ros-hydro-concert-msgs : 0.6.0 -> 0.6.1
ros-hydro-concert-orchestra : 0.5.4 -> 0.5.5
ros-hydro-create-dashboard : 2.1.0 -> 2.2.0
ros-hydro-create-description : 2.1.0 -> 2.2.0
ros-hydro-create-driver : 2.1.0 -> 2.2.0
ros-hydro-create-gazebo-plugins : 2.1.0 -> 2.2.0
ros-hydro-create-node : 2.1.0 -> 2.2.0
ros-hydro-depth-image-proc : 1.11.1 -> 1.11.2
ros-hydro-ecto-image-pipeline : 0.4.12 -> 0.4.13
ros-hydro-ecto-pcl : 0.3.13 -> 0.3.14
ros-hydro-eigen-conversions : 1.10.5 -> 1.10.6
ros-hydro-eigen-utils : 1.0.1 -> 1.0.2
ros-hydro-gateway-msgs : 0.6.0 -> 0.6.1
ros-hydro-gazebo-msgs : 2.3.0 -> 2.3.1
ros-hydro-gazebo-plugins : 2.3.0 -> 2.3.1
ros-hydro-gazebo-ros : 2.3.0 -> 2.3.1
ros-hydro-gazebo-ros-control : 2.3.0 -> 2.3.1
ros-hydro-gazebo-ros-pkgs : 2.3.0 -> 2.3.1
ros-hydro-geometry : 1.10.5 -> 1.10.6
ros-hydro-geometry-experimental : 0.4.5 -> 0.4.7
ros-hydro-image-cb-detector : 0.10.0 -> 0.10.2
ros-hydro-image-pipeline : 1.11.1 -> 1.11.2
ros-hydro-image-proc : 1.11.1 -> 1.11.2
ros-hydro-image-rotate : 1.11.1 -> 1.11.2
ros-hydro-image-view : 1.11.1 -> 1.11.2
ros-hydro-interval-intersection : 0.10.0 -> 0.10.2
ros-hydro-joint-states-settler : 0.10.0 -> 0.10.2
ros-hydro-kdl-conversions : 1.10.5 -> 1.10.6
ros-hydro-kobuki : 0.4.0 -> 0.5.2
ros-hydro-kobuki-auto-docking : 0.4.0 -> 0.5.2
ros-hydro-kobuki-bumper2pc : 0.4.0 -> 0.5.2
ros-hydro-kobuki-controller-tutorial : 0.4.0 -> 0.5.2
ros-hydro-kobuki-dashboard : 0.2.0 -> 0.3.0
ros-hydro-kobuki-description : 0.4.0 -> 0.5.2
ros-hydro-kobuki-desktop : 0.2.0 -> 0.3.0
ros-hydro-kobuki-driver : 0.4.0 -> 0.5.2
ros-hydro-kobuki-ftdi : 0.4.0 -> 0.5.2
ros-hydro-kobuki-gazebo : 0.2.0 -> 0.3.0
ros-hydro-kobuki-gazebo-plugins : 0.2.0 -> 0.3.0
ros-hydro-kobuki-keyop : 0.4.0 -> 0.5.2
ros-hydro-kobuki-msgs : 0.4.0 -> 0.5.0
ros-hydro-kobuki-node : 0.4.0 -> 0.5.2
ros-hydro-kobuki-qtestsuite : 0.2.0 -> 0.3.0
ros-hydro-kobuki-safety-controller : 0.4.0 -> 0.5.2
ros-hydro-kobuki-testsuite : 0.4.0 -> 0.5.2
ros-hydro-laser-cb-detector : 0.10.0 -> 0.10.2
ros-hydro-linux-hardware : 2.1.1 -> 2.2.0
ros-hydro-monocam-settler : 0.10.0 -> 0.10.2
ros-hydro-multinav-concert : 0.5.5 -> 0.5.6
ros-hydro-object-recognition-ros : 0.2.2 -> 0.2.3
ros-hydro-object-recognition-transparent-objects : 0.3.17 -> 0.3.18
ros-hydro-oculus-rviz-plugins : 0.0.6 -> 0.0.7
ros-hydro-opencv-candidate : 0.1.8 -> 0.1.9
ros-hydro-openrtm-aist : 3.1.5 -> 1.1.0
ros-hydro-openrtm-aist-python : 3.1.5 -> 1.1.0
ros-hydro-pano-core : 2.1.1 -> 2.2.0
ros-hydro-pano-py : 2.1.1 -> 2.2.0
ros-hydro-pano-ros : 2.1.1 -> 2.2.0
ros-hydro-pcl-conversions : 0.1.4 -> 0.1.5
ros-hydro-pcl-ros : 1.1.4 -> 1.1.5
ros-hydro-perception-pcl : 1.1.4 -> 1.1.5
ros-hydro-realtime-tools : 1.8.1 -> 1.8.2
ros-hydro-redis : 0.5.5 -> 0.6.0
ros-hydro-rocon : 0.5.3 -> 0.6.0
ros-hydro-rocon-app-manager : 0.5.4 -> 0.6.0
ros-hydro-rocon-app-manager-msgs : 0.6.0 -> 0.6.1
ros-hydro-rocon-app-platform : 0.5.4 -> 0.6.0
ros-hydro-rocon-apps : 0.5.4 -> 0.6.0
ros-hydro-rocon-concert : 0.5.4 -> 0.5.5
ros-hydro-rocon-gateway : 0.5.5 -> 0.6.0
ros-hydro-rocon-gateway-graph : 0.5.2 -> 0.5.3
ros-hydro-rocon-gateway-tests : 0.5.5 -> 0.6.0
ros-hydro-rocon-gateway-tutorials : 0.5.5 -> 0.5.6
ros-hydro-rocon-hub : 0.5.5 -> 0.6.0
ros-hydro-rocon-hub-client : 0.5.5 -> 0.6.0
ros-hydro-rocon-msgs : 0.6.0 -> 0.6.1
ros-hydro-rocon-multimaster : 0.5.5 -> 0.6.0
ros-hydro-rocon-rqt-plugins : 0.5.2 -> 0.5.3
ros-hydro-rocon-test : 0.5.5 -> 0.6.0
ros-hydro-rocon-tf-reconstructor : 0.5.4 -> 0.5.5
ros-hydro-rocon-tutorials : 0.5.5 -> 0.5.6
ros-hydro-rocon-unreliable-experiments : 0.5.5 -> 0.6.0
ros-hydro-rocon-utilities : 0.5.5 -> 0.6.0
ros-hydro-rosjava-tools : 0.1.10 -> 0.1.12
ros-hydro-rqt-action : 0.2.17 -> 0.3.0
ros-hydro-rqt-bag : 0.2.17 -> 0.3.0
ros-hydro-rqt-bag-plugins : 0.2.17 -> 0.3.0
ros-hydro-rqt-common-plugins : 0.2.17 -> 0.3.0
ros-hydro-rqt-console : 0.2.17 -> 0.3.0
ros-hydro-rqt-dep : 0.2.17 -> 0.3.0
ros-hydro-rqt-graph : 0.2.17 -> 0.3.0
ros-hydro-rqt-image-view : 0.2.17 -> 0.3.0
ros-hydro-rqt-launch : 0.2.17 -> 0.3.0
ros-hydro-rqt-logger-level : 0.2.17 -> 0.3.0
ros-hydro-rqt-moveit : 0.2.16 -> 0.3.0
ros-hydro-rqt-msg : 0.2.17 -> 0.3.0
ros-hydro-rqt-nav-view : 0.2.16 -> 0.3.0
ros-hydro-rqt-plot : 0.2.17 -> 0.3.0
ros-hydro-rqt-pose-view : 0.2.16 -> 0.3.0
ros-hydro-rqt-publisher : 0.2.17 -> 0.3.0
ros-hydro-rqt-py-common : 0.2.17 -> 0.3.0
ros-hydro-rqt-py-console : 0.2.17 -> 0.3.0
ros-hydro-rqt-reconfigure : 0.2.17 -> 0.3.0
ros-hydro-rqt-robot-dashboard : 0.2.16 -> 0.3.0
ros-hydro-rqt-robot-monitor : 0.2.16 -> 0.3.0
ros-hydro-rqt-robot-plugins : 0.2.16 -> 0.3.0
ros-hydro-rqt-robot-steering : 0.2.16 -> 0.3.0
ros-hydro-rqt-runtime-monitor : 0.2.16 -> 0.3.0
ros-hydro-rqt-rviz : 0.2.16 -> 0.3.0
ros-hydro-rqt-service-caller : 0.2.17 -> 0.3.0
ros-hydro-rqt-shell : 0.2.17 -> 0.3.0
ros-hydro-rqt-srv : 0.2.17 -> 0.3.0
ros-hydro-rqt-tf-tree : 0.2.16 -> 0.3.0
ros-hydro-rqt-top : 0.2.17 -> 0.3.0
ros-hydro-rqt-topic : 0.2.17 -> 0.3.0
ros-hydro-rqt-web : 0.2.17 -> 0.3.0
ros-hydro-rtshell : 3.1.5 -> 1.0.0
ros-hydro-rtsprofile : 3.1.5 -> 1.0.0
ros-hydro-rviz : 1.10.3 -> 1.10.6
ros-hydro-segbot : 0.1.6 -> 0.1.7
ros-hydro-segbot-apps : 0.1.4 -> 0.1.5
ros-hydro-segbot-bringup : 0.1.6 -> 0.1.7
ros-hydro-segbot-description : 0.1.6 -> 0.1.7
ros-hydro-segbot-gazebo : 0.1.4 -> 0.1.5
ros-hydro-segbot-navigation : 0.1.4 -> 0.1.5
ros-hydro-segbot-sensors : 0.1.6 -> 0.1.7
ros-hydro-segbot-simulator : 0.1.4 -> 0.1.5
ros-hydro-settlerlib : 0.10.0 -> 0.10.2
ros-hydro-stage-ros : 1.7.0 -> 1.7.1
ros-hydro-stereo-image-proc : 1.11.1 -> 1.11.2
ros-hydro-tf : 1.10.5 -> 1.10.6
ros-hydro-tf-conversions : 1.10.5 -> 1.10.6
ros-hydro-tf2 : 0.4.5 -> 0.4.7
ros-hydro-tf2-bullet : 0.4.5 -> 0.4.7
ros-hydro-tf2-geometry-msgs : 0.4.5 -> 0.4.7
ros-hydro-tf2-kdl : 0.4.5 -> 0.4.7
ros-hydro-tf2-msgs : 0.4.5 -> 0.4.7
ros-hydro-tf2-py : 0.4.5 -> 0.4.7
ros-hydro-tf2-ros : 0.4.5 -> 0.4.7
ros-hydro-tf2-tools : 0.4.5 -> 0.4.7
ros-hydro-turtle-concert : 0.5.5 -> 0.5.6
ros-hydro-turtle-stroll : 0.5.5 -> 0.5.6
ros-hydro-turtlebot : 2.1.1 -> 2.2.0
ros-hydro-turtlebot-actions : 2.1.1 -> 2.2.0
ros-hydro-turtlebot-apps : 2.1.1 -> 2.2.0
ros-hydro-turtlebot-bringup : 2.1.1 -> 2.2.0
ros-hydro-turtlebot-calibration : 2.1.1 -> 2.2.0
ros-hydro-turtlebot-core-apps : 2.1.1 -> 2.2.0
ros-hydro-turtlebot-create : 2.1.0 -> 2.2.0
ros-hydro-turtlebot-create-desktop : 2.1.0 -> 2.2.0
ros-hydro-turtlebot-dashboard : 2.1.1 -> 2.2.0
ros-hydro-turtlebot-description : 2.1.1 -> 2.2.0
ros-hydro-turtlebot-follower : 2.1.1 -> 2.2.0
ros-hydro-turtlebot-gazebo : 2.0.0 -> 2.1.0
ros-hydro-turtlebot-interactive-markers : 2.1.1 -> 2.2.0
ros-hydro-turtlebot-msgs : 2.1.0 -> 2.2.0
ros-hydro-turtlebot-navigation : 2.1.1 -> 2.2.0
ros-hydro-turtlebot-panorama : 2.1.1 -> 2.2.0
ros-hydro-turtlebot-rviz-launchers : 2.1.1 -> 2.2.0
ros-hydro-turtlebot-simulator : 2.0.0 -> 2.1.0
ros-hydro-turtlebot-teleop : 2.1.1 -> 2.2.0
ros-hydro-turtlebot-viz : 2.1.1 -> 2.2.0
ros-hydro-velodyne-height-map : 0.4.0 -> 0.4.1
ros-hydro-yocs-controllers : 0.3.0 -> 0.4.0
ros-hydro-yocs-diff-drive-pose-controller : 0.3.0 -> 0.4.0
ros-hydro-yocs-velocity-smoother : 0.3.0 -> 0.4.0
ros-hydro-yujin-ocs : 0.3.0 -> 0.4.0

State of URDF

| No Comments | No TrackBacks
From Dave Coleman on ros-users@

I'd like to update the ROS community on the current status of the Unified Robotic Description Format (URDF). As ROS matures some packages are being moved out of the ROS ecosystem into stand-alone projects. With URDF, this has caused a number of package naming changes between Fuerte, Groovy, and Hydro that have made the situation a little confusing, especially on the ROS wiki. 

I've made a diagram that outlines the current components of URDF and shows how they work together:

urdf_diagram.png

Current Status:

1) The core URDF parser and data structures (urdfdomurdfdom_headers) have been pushed upstream into stand alone (no ROS-dependencies) software packages that will in the future be released into Ubuntu completely separate from ROS. 

2) There is now a distinction between a URDF file and a URDF data structure. A URDF file follows the XML format as described on the ros.org wiki. A URDF data structure is a set of generic classes that various formats (currently URDF and Collada) can be parsed into.

3) A new plugin abstraction layer (urdf_parser_plugin) allows the URDF data structures to be populated with various file formats (currently URDF and Collada)

4) The ROS packages urdf_parser and urdf_interface have been deprecated in Groovy and removed in Hydro.

5) As of today, urdfdom and urdfdom_headers have been moved to Github from Bitbucket.

6) An update to the <transmission> element has been made to the URDF spec that is a revisit of the old pr2_mechanisms format generalized for all robots. It currently lives in the new ros_control package but should soon be moved into urdfdom.

Related Topics:

1) The Gazebo simulator can use either URDF or its own (more feature-filled) SDF format. SDFormat was also recently released upstream into a stand alone software package available in Ubuntu separate from ROS. SDFormat also currently contains a copy of the URDF parser.

2) Very preliminary discussions have begun on the needs of URDF 2.0 and potential merging of SDF and URDF. There are several significant limitations in the current URDF specification that need to be addressed. This is targeted for ROS-I or later.

Links:

Thanks to Ioan Sucan, John Hsu, and Wim Meeussen for their continued maintenance and support of these urdf components.


I hope this helps clarify things for everyone!

ROS Hydromedusa Logo and Tshirt Campaign

| No Comments | No TrackBacks

With the imminent release of ROS Hydromedusa, we are happy to continue the tradition of releasing great artwork to accompany great software.

Hydromedusa_web1.jpg

This time we're trying something new: to make ROS Hydromedusa T-shirts available to everyone, we're running a campaign on TeeSpring. This is a limited time offer; by pooling resources and ordering shirts at the same time, we can keep costs down for everyone.

Please show your support of ROS by ordering a shirt! Proceeds from shirt sales will primarily cover the cost of the logo design, with any excess to be used for future ROS maintenance and development.

It's a 3-week campaign, with 2 weeks and 6 days left. We need at least 150 shirt orders by the end of the campaign to make the purchase. Orders in the US should arrive within 2 weeks of the end of the campaign; allow an extra week for international orders.

There are a variety of men's and women's sizes and TeeSpring supports international shipping.

Get your ROS Hydromedusa Tshirt

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: http://www.ros.org/wiki/hydro/Migration

(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:// www.ros.org/debbuild/hydro.html 

REP Updates

The release of Hydro has been facilitated by the centeralization of releases on the rosdistro repository on GitHub, https://github.com/ros/rosdistro .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 http://ros.org/reps/rep-0137.html
During the Hydro development cycle many REPs have been updated.  To see all REPs visit http://ros.org/reps/rep-0000.html

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: http://www.ros.org/wiki/MaintenanceGuide

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: http://www.ros.org/wiki/indigo/Planning 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

Announcing matlab_rosbag v0.3

| No Comments | No TrackBacks
From Benjamin Charrow via ros-users@

Greetings!


I just released v0.3 of matlab_rosbag, a small library for reading ROS bags in matlab.

There are more features and things are much faster than they were.  I never publicly advertised v0.2, so I've included the full changelog below.

Cheers,
Ben

The repo:
https://github.com/bcharrow/matlab_rosbag

The compiled library from sourceforge (Linux + Mac):
https://sourceforge.net/projects/matlabrosbag/files

The (REP 132 compliant?) changelog entries:

0.3.0 (2013-06-09)
------------------
* Add equivalents of 'rosbag info', 'rosmsg show', and 'rosmsg show --raw' to ros.Bag
* Rename ros.Bag functions readMessage() to read() and readAllMessages() to readAll()
* By default, return simple messages as matrices instead of structs
* Improve overall performance; depending on the message type, reading messages is 2x-20x faster than v0.2
* Update build to use Groovy; much easier to compile everything

0.2.0 (2012-02-11)
------------------
* Improve performance for fixed size messages
* Various bugfixes (constants, primitive aliases, 0 length arrays)

0.1.0 (2012-02-04)
------------------
* Initial release using ROS electric

Announcing Vanderbilt University Repositories

| No Comments | No TrackBacks
Vanderbilt University's Hunter Allen is proud to announce the official Vanderbilt University ROS repository!

This is the github repository for the full repository: https://github.com/allenh1/vanderbilt-ros-pkg

This is the github repository for P2OS on Groovy. We have updated the software to work with the new ROS. We will continue to improve as we can! https://github.com/allenh1/p2os

We'll get right on the documentation. :) 

Enjoy!

ROSCon slides and videos posted

| No Comments | No TrackBacks

Cross posted from osrfoundation.org

ROSCon2013_color1-300x207.jpg

We're happy to announce that we've posted videos of the ROSCon 2013 talks, along with speakers' slides. They're linked from the program page. Clear your calendar; that's over 16 hours of ROSCon content.

Slides and/or video are missing for a few of the talks. They'll trickle in over time. We're also expecting to get photos from the official photographer soon. In the meantime, attendee photos are coming together on G+.

The final registration count was 288, up 37% from 2012. Thanks again to everybody for coming! And thanks to our sponsors, without whom we couldn't put on such an event.

Cross posted from osrfoundation.org

OSRF folks know that students love Open Source software, Robotics and flip flops. If you would like to expose to real-world software development during the summer, contribute to Gazebo, ROS or CloudSim projects, and be engaged with the Robotics community while get paid, check out the GSoC 2013 [1] and the OSRF dedicated site [2]. We have created an ideas page [3] with some potential projects. Feel free to ask questions and propose suggestions at gsoc2013@osrfoundation.org. The student application period starts on April  22. Be ready for a Robotics coding summer!.

We're pleased to announce that the ROS project will soon be hosted by Oregon State University's Open Source Lab (OSL) (http://osuosl.org/). The OSL provides services to many open source communities. We are pleased to join the ranks of projects like Drupal and kernel.org. We'd like to thank Willow Garage for providing hosting and infrastructure for the entire ROS community for over 5 years.

We'd also like to thank Lance Albertson, Carlos Jensen, and Bill Smart for welcoming us to the OSL. We look forward to working with Oregon State and the OSL to provide ongoing hosting as well as exploring ways to improve ROS infrastructure for the greater community.

In the coming weeks, we'll migrate the wiki, ROS Answers, and the Ubuntu package repository from Willow Garage to the OSL. We'll announce more detailed plans as they come together and we'll do our best to minimize disruptions during the migration.

As you might imagine, hosting for these critical services, which are heavily used around the world and around the clock, costs money. We need your help! A big thank you to the ROS-Industrial Consortium, which has stepped up to support part of this cost. If your organization can financially support ROS project hosting, please contact us at info@osrfoundation.org.

ROS Industrial Consortium Driver Program

| No Comments | No TrackBacks
From Shaun Edwards on ros-users@


All,

 

ROS-Industrial (http://rosindustrial.org/ ) is an exciting new program to leverage ROS for industrial automation and robotics.  The program is a result of my work as a visiting researcher at Willow Garage last year.  What started as a simple project has grown into a community driven effort over the past year (much like ROS but not as big, yet).  With the goal of growing the ROS-Industrial community and increasing the support for industrial robot platforms, I would like to solicit your help.  We have two needs, basic driver development and advanced driver development.

 

 

Basic Driver Development (http://ros.org/wiki/Industrial/Industrial_Robot_Driver_Spec ):

 

Over the past year we have worked to create basic drivers for the major industrial robot vendors.  We are well on our way with current support for ABB, Adept, Fanuc, Motoman, and Universal.  We are currently in need of developers for Kuka, Comau, and Kawasaki robots.  We have developed tools and libraries to facilitate development, so the amount of driver development can be minimal. 

 

 

Advanced Driver Development(http://ros.org/wiki/Industrial/Industrial_Robot_Driver_Spec/future ):

 

The goal of advanced driver development is to add functions and capabilities to the basic drivers that would be needed to deploy a real-life robot work cell.  We have brainstormed some of these requirements (see link above), but would like to get community input as well.  We'd also like community help in adding these capabilities to the existing drivers for all supported robot vendors.

 

 

If you have an interest in helping, please contact me(or reply to this email).  Thank you for your consideration,

 

Shaun

Hydro Fork Update

| No Comments | No TrackBacks
From ros-users@

Hi Everyone,

This email is to give an update on the ROS Hydro development.

In perparation for Hydro there has been lots of activity preparing the infrastructure for the new release [1].  There also has been significant patch releases for Groovy happening  [4].  Two major requirements for the Hydro fork were the upgrades to bloom and the development of a REP for 3rdparty package releases which are being finished up [5] [6].


= Updated Hydro Schedule =

As we are now ready to fork the rosdisto for Hydro development we need to review the Hydro development cycle.  We will not be able to catch up to the standard release cycle.

New Schedule Goals:

- March 5th: Hydro Fork
- April   2nd: Hydro Alpha
    The first version of all packages are released into Hydro.
- April  25th: Hydro Beta
    All major changes have been completed for stable packages.  
- May  22nd: Hydro Medusa Release


This means that in the next 4 weeks we hope that all released packages can be released into Hydro to form the Alpha Release on April 2nd.  There will be 3 more weeks for upgrades before the Beta release on April 25th.

If you are a maintainer please watch for when it will be appropriate to make your first release into Hydro.

= Ongoing REPs =

Already there has been quite a bit of activity developing REPs for the Hydro cycle with discussions ongoing for REPs in ros-users, ros-sig-drivers, and ros-sig-buildsystem and the pull requests in the rep repository [3].   I encourage everyone to watch for REP discussions and consider joining them.  

The REPs under review can be found at these locations:
- 132 Incorporation of Changelogs into Package Source Tree https://github.com/ros-infrastructure/rep/blob/master/rep-0132.rst
- 133 Separation of build environment and source tree tools https://github.com/tkruse/rep/tree/repwstool
- 134 catkin_make_isolated for non-standard catkin packages https://github.com/tkruse/rep/blob/repisolated/rep-0134.rst
- 135 Driver Namespace Practices  https://github.com/chadrockey/rep/blob/namespace/rep-0135.rst
- 136 Releasing Third Party, Non catkin Packages https://github.com/ros-infrastructure/rep/blob/release_third_party/rep-0136.rst
- 137 ROS distribution files https://github.com/po1/rep/blob/rep137/rep-0137.rst
- 138 LaserScan Common Topics, Parameters, and Diagnostic Keys https://github.com/chadrockey/rep/blob/laserscanner/rep-0138.rst
 
They all have pull requests pointing to their discussions at [3].

= Outstanding Issues =

One major change in Ubuntu which will effect Hydro is that In Raring Ringtail (13.04) Ubuntu will switch to use Python 3 by default.  This will require a large audit of the Python codebase to test for compatability.  There's an issue open to keep track of this at the rosdistro level [7].  We plan to follow Ubuntu's recommendation which is to make scripts Python 2.7+ and Python 3.3+ compatible.  For more information on what is required see the Ubuntu Python 3 wiki page [8].



= Maintainer Status =

One of the initiatives we plan for Hydro is to keep more up to date maintainer information for packages.  This is covered in draft REP 137 [2].   There are a large number of released packages which over time the original authors have moved to new situations where they do not have the ability to maintain their packages.   Historically many of these packages were picked up and carried forward by a few individuals.  However this approach is not sustainable.  

To keep the quality of ROS packages as high as possible we will be looking for new maintainers to distribute the burdon throughout the community. We will ask that all packages released into Hydro have clear maintenance status.  

Announcing MORSE 1.0

| No Comments | No TrackBacks
Dear ROS community,

After 4 years of worldwide development by over 20 people in 10 different labs, we are extremely excited to announce the immediate availability of MORSE-1.0, a novel versatile simulator for academic robotics, with full ROS support.

Amongst the prominent features:

  * Versatile 3D simulator for mobile robots simulation (single or multi robots),

  * Realistic ('modern' OpenGL) and dynamic environments (interaction with other agents like humans or objects),

  * Based on well known and widely adopted open source projects (Blender for real-time 3D rendering, Bullet for physics simulation, dedicated robotic middlewares for communications),

  * Command-line oriented (with optional scene editing in Blender), entirely scriptable in Python,

  * Adaptable to various level of simulation abstraction (e.g. simulate cameras as video-streams, depth-streams or semantic maps depending on your needs),

  * > 20 classes of sensors (including depth sensors, cameras, IMU, laser scanners...), > 15 classes of actuators (including kinematic chains, quadrirotor control, force control...) are available. Detailed documentation explain how to add new ones (in C or Python),

  * Currently supports ROS, YARP, MOOS and Pocolibs + direct socket interface

  * Extensive documentation, available here:
        http://www.openrobots.org/morse/doc/stable/morse.html

And as a collaborative academic project, the source code is available under a permissive BSD license. Grab your copy fromhttp://www.github.com/laas/morse !


Last but not least, Michael and Pierrick will be present at ROSCon in May to present the project. Feel free to pop-up to meet the team!

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 answers.ros.org with the bloom tag and post any bugs discovered on the bloom issue tracker:





ROS Groovy Galapagos Released

| No Comments | No TrackBacks

ellingson_groovygalapagos.jpg

Hello ROS Community, 


As we close out 2012 we're happy to announce the release of ROS Groovy Galapagos.  The theme of this release has been building infrastructure to support the growing ROS development community.

Using the new rosdistro repository on GitHub as a microcosm, you can get a sense of scale for the Groovy development  There are 118 public forks of the project publicly available with 73 people having contributed commits to the repository.  Running a script over the history of just the releases/groovy.yaml file in the repository finds that during the groovy development cycle there have been over 1100 commits changing the revisions of packages. And counting each changed version number there have been more than 3500 releases submitted to be built on the build farm.   This means that there have been more than 10 releases every day for the last 9 months on average.  

These statistics only count the packages which have been converted to use the new build and release system which currently stands as about half the released repositories.  One of the goals going forward in Hydro development will be convert the majority of the unconverted packages. 

All these releases have been submitted to our upgraded build farm infrastructure.  The over 450 packages are built into binary packages on 6 different architectures.  The binary builds for packages take between 3 and 90 minutes each, and if run on a single computer would take more than 2 weeks to complete running continuously.  The automatic documentation jobs likewise would take several days to run if run on a single computer.  

The Groovy release cycle ran longer than originally planned however giving it the extra development time has allowed us to produce a much more polished release which will support us better as we start considering how ROS should progress forward.  Going forward the Hydro cycle is expected to be shortened to bring the releases back into sync with the Ubuntu releases with a target of Hydro Medusa for April 2013.  

In the near future we will begin the Hydro planning cycle and kick off a new round of SIGs.  If you have been thinking about something you would like to see in ROS the SIGs will be a great opportunities to find others interested in collaborating to make those thoughts reality.  

Below are the Release Notes.  They have been filled in for the core packages and anyone who sent me information has been integrated. If you have updates stacks or packages, please add your information to the version on the wiki to make it as complete as possible.  

In the final release there have been 82 packages patched since Beta 3.  Most of the focus in the run-up to the release has been on documentation and tutorials.  

Happy New Year!

Your ROS Groovy Release Team

ROS Groovy Galapagos

ROS Groovy Galapagos will be the sixth ROS distribution release and was released December 31st 2012. In this release we have focused on the core infrastructure of ROS to make it easier to use, more modular, more scalable, work across a larger number of operating systems/hardware architectures/robots and most importantly to further involve the ROS community.

Platforms

ROS Groovy Galapagos will be primarily targeted at the Ubuntu 12.04 (Precise) release, though compatibility with other Linux systems as well as Mac OS X, Android, and Windows is anticipated. For more information on compatibility, please see REP 3: Target Platforms.

Installation

Please see the installation instructions. There are binary packages available for Ubuntu distributions, Oneiric, Precise, and Quantal for both 32 and 64 bit architectures. There is also improved infrastructure for building from source, most heavily tested on OSX. And experimental instructions for other platforms.

Ubuntu Users: Please make sure to use the Python tools from apt and not pip. The pip based installs tend to go out of date and not get updated with the rest of the system.

Major Updates

Mass migration of code to GitHub

Traditionally, ROS code has been scattered across numerous version control systems (git, svn, hg, etc) across different hosting services throughout the world. Though the ROS wiki has acted as a central point of documentation, issue/ticket tracking has been just as disparate as the usage of VCS tools.

With ROS Groovy, an effort has been made to move core packages to GitHub along with all issue tracking. This has brought several benefits including making ROS more available to the wider open source community and providing VCS consistency for ROS packages. Most importantly, utilizing GitHub has involved the ROS community more and given it more ownership of the codebase. GitHub's pull requests have made it much easier for the core ROS development team to apply patches from the community as well as respond to design feedback more rapidly. In the last development cycle there have been 71 people who have contributed to the rosdistro file, using 239 pull requests and there exist 115 public forks of the rosdistro project on GitHub. The ease of forking and submitting pull requests has made this higher level of community engagement possible. GitHub additionally provides excellent tools for navigating code, managing issues/milestones, and increasing developer communication. All ROS package developers are highly encouraged, but not required, to utilize GitHub for their own repositories so as to further unify both the ROS codebase and community.

On GitHub, ROS repositories are spread across several GitHub "organizations" to group related repositories in an intuitive manner:

New Build System - catkin

The most striking and significant change in Groovy is the introduction of a new build system called catkin which will eventually fully replace the original rosbuild build system. catkin was developed to address several drawbacks inrosbuild so that ROS can continue to grow and scale. As opposed to rosbuild catkin promotes Filesystem Hierarchy Standard (FHS) compliance, making it much easier to distribute ROS packages on other operating systems and architectures.

Though a prototype version was already introduced in fuerte for a only few packages, catkin is now the official build system of ROS. rosbuild will continue to be supported for the forseeable future, but in time will be deprecated. catkin has been designed to be backwards compatible with existing rosbuild packages and stacks that have not yet migrated. Most of the core packages have already been migrated and new packages should utilize catkin.

The workflow of catkin is somewhat different from rosbuild, but great care has been taken to make the transition as smooth as possible. Here are some resources for getting started with catkin:

Removal of Stacks

With the new version of catkin in Groovy, the concept of Stacks has been removed. One of the main reasons for this was that there was a duplication of dependency tracking between packages and stacks. Previously packages only depend on packages, and stacks only depend on stacks, so the stack which contains a package must depend on all of the stacks which contain the dependencies of that package. Additionally, by removing stacks the code base has become more modular because you can install any package and its dependencies, where as in the past a package would often unnecessarily pull in its stack and other unused dependencies.

To preserve some of the benefits of stack, the concept of "metapackages" replaces the concept of stacks. A metapackage is not a container of packages like rosbuild stacks were, but a named set of references to packages. It can be used to preserve some structure using a catkin metapackage replacing an old rosbuild stacks (this helps with for backwards compatibility of documentation with rosbuild, e.g. in wikis). A metapackage can depend on packages which don't necessarily reside in the same folder or source repository. This allows for more flexibility of development workflows, allowing to have separate repositories for packages that belonged to a single stack.

This is captured more formally in REP 127

New Package Release System - bloom

With catkin also comes a new package release system known as bloombloom not only simplifies your workflow when releasing ROS packages to the world, but also provides features to make it easier to maintain released packages, version them, and patch/backport changes.

bloom takes your catkin packages and releases them to a "release repository". All of the ROS release repositories are hosted in the ros-gbp organization on https://github.comhttps://github.com/ros-gbp. The release repository contains snapshots of your source repository (the repository you develop on) and provides tags to the snapshots. Additionally it creates a "release" branch for each package in your upstream repository on which you can make patches and it provides tags for each released version of your packages. Finally, bloom can generate files for building Debian .debs on the ROS build farm. Because we host our release repositories on https://github.com, there are known urls for each release of each package. This makes the release repositories a good source for building released ros packages from source.

bloom allows a source code repository to contain any number of packages, related or not. The only caveat to having multiple packages in a single repository is that they must be released with a common version number, i.e. one release version number per repository.

New GUI Tools - rqt

In Groovy, core ROS GUI tools (rxconsole, rxgraph, etc) have been significantly refined. These tools have been replaced by a single new tool called rqt. rqt is a software framework that implements the various GUI tools in the form of plugins. One can run all the existing GUI tools as dockable windows within rqt -- even rviz! The tools can still run in a traditional standalone method, but rqt makes it easier to manage all the various windows on the screen at one moment.

Users can create their own plugins for rqt with either Python or C++. Over 20 plugins have already been created and more are slated for development.

rviz

rviz has been significantly redesigned with a cleaner user interface and and a new plugin API covering all major functions. RViz is now "on its own" and so can be installed directly (on Ubuntu for example) as ros-groovy-rviz. It no longer depends on visualization_common, instead depends directly on standard OS installations of OGRE, easing compilation from source. Python support has been greatly expanded, so rviz windows, displays, viewpoints, and tools can all be manipulated from Python now.

The "save" file format has also changed: it now saves into "*.rviz" files which are in YAML format, easing manual editing, comparison, and automatic generation.

pluginlib and class_loader

pluginlib, the library for creating plugins in C++ code, has been almost completely rewritten while retaining 100% backwards compatibility. New features include thread-safety, simplified API, and true library class introspection. pluginlibis now built on top of a new ROS-independent package called class_loader which can be used to work with plugins in software that does not utilize the ROS build system.

Gazebo

The Gazebo simulator project, the simulation engine used within the simulator_gazebo ros stack, has recently undergone major improvements and re-factoring as it went from version 1.0 to 1.3The Groovy release of Gazebo has been updated to run with gazebo 1.2.x with pending updates to upgrade to gazebo 1.3.x in the near future.

All changes in the underlying simulator can be found on gazebosim.org, as well as commonly asked questions and answers for gazebo via gazebo answers page.

Other New Packages:

Tutorials

The significant overhaul of core ROS infrastructure has meant a significant change in fundamental ROS documentation, primarily in the tutorials. It is recommended to review them again, even if you are a ROS veteran, at http://www.ros.org/wiki/ROS/Tutorials. All the Tutorials beyond Creating A Package have been converted to support the new and old build system.

Automatic Documentation Jobs

One of the valuable services provided to the ROS community is the public indexing of packages and automatic documentation generation onto ros.org. The entire system has been overhauled to parallelize and isolate failures of individual repositories from stopping other repositories from being documented. The new infrastructure now also provides properly versioned documentation for each ROS distro. For more information on how to be indexed in the new system see the Get Involved page.

Migrating

As with any release there have been some areas which will require updating. In this cycle most of the changes have been adding APIs while maintaining backwards compatibility for the old APIs.

Moving From rosbuild To catkin

The biggest change is the switch from rosbuild to catkin. This switch has been done while providing backwards compatibility, such that legacy packages can depend on converted packages without being changed. However catkin based packages cannot depend on rosbuild based packages. This leads to what has been called the rising tide where the conversion to catkin must propogate up the dependency tree. Wet packages, catkin based, are always below the dry packages, rosbuild based, as the tide rises.

A detailed guide to converting packages can be found in the catkin documentation. catkin/migrating_from_rosbuild

Change from Wx to Qt

One significant change is the transition from Wx to Qt. If you have been using Wx graphical toolkits it is recommended to switch. Most of our primary visualization tools have been ported to Qt. And there are many plugins for them. There are tutorials on the [[rqt] page on how to write new Qt based plugins.

laser_drivers REP 117 Deprecation Completed

If you have been using the laser_drivers the changes made by REP 117 have now become the default option. For more information see REP 117

Change Lists of Note

Plans and Special Interest Groups

The planning for the Groovy release was coordinated on the planning page.

Sigs

A significant amount of the Groovy development was coordinated by Special Interest Groups. These groups are summarized at the bottom of the planning page.

ROS Enhancement Proposals (REP)

Four REPs have been finalized during the Groovy development cycle:

ROS Groovy Beta 3 Available

| No Comments | No TrackBacks
We are converging on the ROS Groovy release.  ROS Groovy Beta 3 is available now from the public apt repositories.  For installations see: http://www.ros.org/wiki/groovy/Installation

This brings us to over 450 packages building on all 6 supported Ubuntu distro arch combinations.  

There are also new source based installation instructions: http://www.ros.org/wiki/groovy/Installation/Source  These have been tested on Ubuntu and OSX.  It would be great to get more testing on other platforms.  The most common issue expected to be encountered on other platforms will be missing rosdep definitions.  Documentation for how to contribute rules can be found at: http://ros.org/doc/api/rosdep2/html/contributing_rules.html

We are waiting on a couple of packages to be patched and are working hard on documentation. Our milestone for the release can be seen at: https://github.com/ros/rosdistro/issues?milestone=2&state=open

Draft release notes are available at: http://www.ros.org/wiki/groovy

Your ROS Release Team

ROS Groovy Beta 2 Available

| No Comments | No TrackBacks

Hi Everyone,

We're pleased to announce ROS Groovy Beta 2 has been released.

Since Beta 1 there have been over 150 packages released including approximately 40 new packages. Bringing our total to over 380 packages building into debian releases on both oneiric and precise.

Please give it a try and give your feedback. On ubuntu if you installed Beta 1 from debian packages you can just "sudo apt-get update && sudo apt-get dist-upgrade" to get the new release.

We have a new build status page available at http://www.ros.org/debbuild/groovy.html Please be patient, it's a lot of data to download at once but it gives a good sense of what the status of the builds are.

ROS: Five Years

| No Comments | No TrackBacks

ROS turned five years old in November, so it's time for our sort-of-annual State of ROS.  If you recall, we took a deep dive into the growth of ROS in our third-year anniversarypost.  We won't be as prolific this time around, but suffice it to say that the past two years have built on the excitement, growth, and adoption of ROS.

Numbers don't tell the entire story, but it's a good place to start.

·      There are 175 organizations or individuals who have publicly release ROS software in our indexed repositories, up from 50 in 2009 (through October)

ros_repositories_5_year.png

·      Not counting the approximately 40 PR2s all over the world, there are many hundreds of robots running ROS.  We are aware of more than 90 types of robots that are running ROS, up from 50.  With 28 robots with supported installation instructions.  



robots_5_year.png


·      We had 3699 public ROS packages as of April, compared to 1600 three years ago

·      ROS continues to have a strong impact in the worldwide academic community, with 439 citations on Google Scholar for the paper: ROS: an open-source Robot Operating System

·      There are now people working on ROS on every continent.  Africa, South America, and Antarctica are new to the community this time around.  Yes, Antarctica.

 ROSAntarctica.jpg

·      You can now buy a book on ROS

·      One, and counting.  This is the number of industry conferences dedicated to ROS.  More than 200 individuals attended the ROSCon 2012 debut last year in St. Paul, MN.  ROSCon 2013 heads to Stuttgart, Germany next year.

·      People often ask how many users are there of ROS.  Due to the open source nature of ROS, we simply don't know how many ROS users there are in the world. What we can tell you is that the ros.org wiki has had over 55,000 unique visitors in the last month.  This doesn't include traffic to our many worldwide mirrors.  

The latest version of ROS, Groovy Galapagos, is currently in Beta 1 Release.  Groovy will be the sixth full release of ROS.  This release is laying the foundations for enabling ROS to continue to grow the number of platforms supported.   

Inspired by The Mozilla FoundationThe Apache Software Foundation, and The GNOME Foundation, our three-year anniversary blog post discussed the possibility of a ROS Foundation.  In May of this year, Willow Garage announced the debut of the Open Source Robotics Foundation, Inc. OSRF is an independent non-profit organization founded by members of the global robotics community whose mission is to support the development, distribution, and adoption of open source software for use in robotics research, education, and product development.

Because of the BSD license for ROS, we often have no idea who is using ROS in their commercial deployments.  We suspect there are a few we are missing, but two major new products were announced this year that are built using ROS.  First is Baxter from Rethink Robotics.  Baxter was announced just a few months ago and the company has set their sites on manufacturing industries.  Check out IEEE Spectrum's article on Rethink here.  Also built on ROS is Toyota's Human Support Robot (HSR), which is designed to help those with limited mobility within the home.  ROS has even made inroads within the industrial robot world of late, specifically through the ROS-Industrial Consortium.

We can't discuss commercial deployments of ROS without mentioning TurtleBot, originally released in April 2011.  Recognizing that not everyone can afford, or even needs, a $280,000 PR2 robot, TurtleBot was brought to market for the express purpose of letting as many people as possible get their hands on ROS.  TurtleBot 2.0 was recently featured on Engadget and is now available for pre-order at www.turtlebot.com

At Willow Garage, we often refer to ourselves as a software company disguised as a robot company, and we can point to the ongoing growth of ROS as proof of that assertion.   We have also been stating for some time that we need a LAMP stack for robotics.  With the latest developments in commercial robots built on ROS, it feels like we are in the beginning stages of that process.  We can't predict what ROS will look like in five year, or twenty-five, but if we continue to see the adoption, innovation, and excitement from the ROS community that we have seen in the first five years, then things are certainly looking Rosey.


rosie_cbs.png

ROS Groovy Beta Release 1

| No Comments | No TrackBacks

Hi Everyone,

We are pleased to announce the ROS Groovy Galapagos Beta 1 Release is available for download!

In this release we have focused on core infrastructure. The core build tools prototyped in Fuerte have been significantly refined. We have upgrade the continuous integration and documentation infrastructure to be more modular and enable scaling better.

One of the core upgrades has been the buildsystem catkin, which is based on CMake. It has been designed to provide the core usability of the rosbuild ecosystem but converge to more standard software engineering practices. For more information on catkin please see the catkin wiki page and the associated tutorials](http://www.ros.org/wiki/catkin/Tutorials)

There has also been a significant overhaul of the core tutorials. It is recommended to review and reference back to them: http://www.ros.org/wiki/ROS/Tutorials all the Tutorials beyond Creating A Package have been converted to support the new and old build system.

For instructions installing please visit the Groovy installation page. There are currently well over 300 packages building successful on all three supported Ubuntu distros (Oneiric, Precise, Quantal) with over 200 of them being built using catkin. This constitutes over 75% of the released packages from Fuerte. During the beta is a great time for maintainers of the stacks which are not currently building to release their stacks for Groovy. The status of the builds can be found on the debbuild status page

There have been many other upgrades in the groovy development process. One of the larger upgrades involved changing the recommended gui framework from Wx to Qt. There is a new rqt_gui which can embed Python and C++ plugins. Rviz has been ported and has a new plugin API. Almost all the core Wx based visualization tools have been switched to have Qt equivalents, and those that have not switched yet are expected to be ported very soon.

Three REPs have been released during the Groovy development cycle:
REP 127 Specification of package manifest format
REP 128 Naming Conventions for Catkin Based Workspaces
REP 131 ROS Groovy Variants

Ubuntu Users: Please make sure to use the Python tools from apt and not pip. The pip based installs tend to go out of date and not get updated with the rest of the system.

Note: For the beta we have disabled 32 bit binaries to decrease the load on the build farm. They will be re-enabled during the beta testing cycle before the full release.

ROSCon 2013: Call for Proposals

| No Comments | No TrackBacks

ROSCon2013_color1-300x207.jpg

Call for Proposals: ROSCon 2013
Stuttgart, Germany
11-12 May 2013
(immediately following ICRA)

Details: http://roscon.ros.org/
Proposals: submit@roscon.ros.org
Questions: info@roscon.ros.org

ROSCon 2013 is a chance for ROS developers of all levels, beginner to expert, to spend an extraordinary weekend learning from and networking with the ROS community. Get tips and tricks from experts, network, and share ideas with fellow developers from around the globe.

ROSCon is a developers' conference, in the model of PyCon and BoostCon. Following the success of the inaugural ROSCon in St. Paul, Minnesota http://roscon.ros.org/2012 ) this year's ROSCon will be held in Stuttgart, Germany. Similar to last year, the two-day program will com prise technical talks and tutorials that will introduce you to new tools and libraries, as well as teach you more about the ones you already know. The bulk of the program will be 30-40 minute pre sen tations (some may be longer or shorter).

Want to present at ROSCon? Submit a proposal! For details on proposing, go to http://roscon.ros.org/

If you don't want to make a formal presentation, you should still bring your new project or idea to ROSCon!

There will be several sessions of Lightning Talks, which are 5-minute mini-talks that are scheduled just-in-time at the conference. There will also be open space for Birds-of-a-Feather (BoF) meetings, impromptu hacking sessions, and informal presentations.

On behalf of the ROSCon 2013 Organizing Committee:

Alexander Bubeck, Fraunhofer IPA
Tully Foote, Willow Garage
Ryan Gariepy, Clearpath Robotics
Brian Gerkey, Open Source Robotics Foundation
Florian Weisshardt, Fraunhofer IPA
Matthew Williamson, Rethink Robotics

From the ROS Industrial Consortium

With input from the industrial robotics and automation community, Southwest Research Institute has set a low-cost membership model for the ROS-Industrial Consortium (RIC). This model encourages a broad base of membership and gives participants more control over how development funds are used. In conjunction with the launch of the consortium, SwRI has funded a special internal research program to accelerate ROS-Industrial development and benefit the technical needs of the Consortium.

Southwest Research Institute is launching the ROS-Industrial Consortium to conduct foundational, precompetitive research and code development and apply advanced ROS software to industrial applications. "As an early adapter of ROS, SwRI has been successfully leveraging it for industrial robotics applications," explained Shaun Edwards, a senior research engineer in SwRI's Automation and Data Systems Division. ROS (Robot Operating System) is an open-source project providing a common framework of libraries and tools for a wide range of applications, particularly in service and research robotics. In January, SwRI established the ROS-Industrial repository, an open-source resource providing a common industrial control platform to facilitate technology transfer from research labs to industry.

"Following other successful open-source projects as models, SwRI is initiating a precompetitive commercial collaborative research consortium, exclusively focused on the needs of industrial robot users," said Paul Evans, director of SwRI's Manufacturing Systems Department. RIC full membership is set at $10,000, with lesser levels of membership available (see membership table). "RIC will accelerate the development of ROS-Industrial. RIC members will work together to develop an application roadmap for ROS-Industrial, set near-term technical goals and participate in spinoff focused technical projects."

"We are excited about a multi-year, internal research program SwRI funded to capitalize on recent research and allow us to accelerate hardware integration tasks," Edwards continued. "The funding allows us to implement ROS-I interfaces for industrial robots to enable users to reuse software for advanced robotics applications. The program will also fund a significant effort to develop advanced functionality and add new capabilities to highly reliable industrial robot platforms."

To date, ROS-Industrial has demonstrated capabilities unmatched using conventional industrial robot control for applications such as material handling in dynamic environments with on-the-fly object segmentation and grasp planning http://youtu.be/_WG-45cZSUQ. Standard interfaces allow high-level software to work with any robot. ROS-Industrial supports robotic workcell visualization and simulation capabilities such as RViz, allowing system development and testing with or without physical hardware.

ROS-Industrial allows advanced 2D-vision and 3D-point cloud sensor processing. Rich software development tools (based on standard Linux tools) include universal logging, debuggers and automated coding. Multiple robot path planners and optimizations allow developers to choose and customize systems that support high-degree-of-freedom systems coordinating multiple arms.

"It's an exciting time in industrial robotics," continued Edwards. "After the economic downturn, the U.S. is now seeing a new government focus on manufacturing, a surge of venture capital spending in this area, and a trend toward returning manufacturing to the U.S. due to rising labor costs in other countries."

For more information about the ROS-Industrial Consortium, see http://rosindustrial.org/ric/default-ric.htm or contact Evans at paul.evans@swri.org or (210) 522-2994.

Crosspost from willowgarage.com

Clearpath Robotics aims to progress robotics development by providing universities with robust platforms for prototyping and research. To give robotics research an extra boost, Clearpath Robotics introduced the PartnerBot Grant Program this summer.

ParnerBot Pic2 small.png

The PartnerBot Grant Program is a one-year commitment during which a prestigious research team will use the Clearpath Robotics Husky A200 to pursue its research goal, publish for public review, and add code to the rapidly growing open source ROS (Robot Operating System) community. Initially aimed at donating $25,000 worth of equipment, the sheer number of applicants and outstanding quality of the submissions prompted Clearpath Robotics to increase the total value to $100,000.

The Husky A200 is a rugged, all-terrain robotic platform for rapid prototyping and research applications. In the past we've seen it used for prototyping planetary rovers, researching autonomous navigation, environment mapping, and countless other applications. The Husky A200 integrates seamlessly with the free and open source ROS robotics framework that offers full control of the Husky, including (but definitely not limited to) autonomous navigation, perception, and mapping. Using the standardized platform and open software allows researchers to cooperate, share findings, and repeat experiments.

More than 150 universities world wide showed interest in the PartnerBot Grant Program. Clearpath Robotics has received submissions from every continent on the planet (except from Antarctica) with applications ranging from mine clearing, to agricultural robots, to planetary rovers, and everything in between. With such a great turnout and impressive applications it seemed a shame to support only one research project, so Clearpath Robotics has worked feverishly over the past month to scrape together enough money to support the following 10 distinguished research teams.

  • University of California, Santa Cruz
  • University of Coimbra
  • Orebro University
  • Universidad de Chile
  • Drexel University
  • Federal University of Minas Gerais
  • University of Hohenheim
  • University of Michigan
  • Queensland University of Technology
  • University of Bremen

Clearpath Robotics would like to thank everyone who invested time and energy to submit a proposal. The judging process was tough, selecting only one would have been impossible - even 10 was difficult. To read more about the outstanding research projects and PartnerBot recipients, visit the PartnerBot site.

Rethink ROS

| No Comments | No TrackBacks
Cross Posted from the Open Source Robotics Foundation Blog

There's exciting news out of Boston today with the launch of Rethink Robotics's new robot. Rethink Robotics is developing a family of low cost and highly intelligent robots that can perform simple tasks in a manufacturing environment, increasing the productivity of the people around them. Rethink Robotics was founded by Rodney Brooks, former Director of the MIT Computer Science & Artificial Intelligence Laboratory, and co-Founder of iRobot Corporation.

Rethink's robots can be taken out of the box, taught a task by anyone, and start work in a few hours, eliminating the need for systems integration. They are safe to interact with people at close range and are easy to train and retrain on the fly. They are nothing like any existing industrial robots.

While all of this is very exciting for the robotics industry, and certainly for our friends at Rethink, what we personally find most exciting is the role played by ROS in today's news. Rethink's new Baxter robot is, in the words of CEO Scott Eckert, "built upon ROS." We had some hint from Rethink's (then Heartland's) support of ROSCon 2012 that they were doing something with ROS, but we were very pleasantly surprised today to hear that ROS is such a central part of Baxter.

Rethink's
Baxter

As ROS edges closer to its five-year anniversary, this is a great milestone for the ROS community. Rethink is actively hiring for a Senior Developer Relations Engineer with expertise in ROS, and expects that individual to play an important role as part of the ROS community.

Congratulations to everyone at Rethink Robotics, and we are looking forward to their contribution to the ROS community.

ROS Fuerte!

| No Comments | No TrackBacks

ROSFuerte_poster1.jpgROS Fuerte is now officially available!

With each ROS distribution, we've focused on making great robotics libraries work together easily, and with this release we've made many changes under the hood to make it simpler and cleaner for you to integrate your software into the ROS ecosystem.

ROS Fuerte includes major new releases of Gazebo 1.0 and PCL 1.5, and the core ROS libraries have been rewritten to be standalone: you can now easily use ROS messages in non-ROS frameworks. These standalone messages are made possible by a brand new, CMake-based build system and release toolchain that also greatly improve cross-platform and cross-compilation support. Cross-platform support has also been improved by an RViz port to Qt.

ROS aims to make robotics code more reusable, and this release is a strong new foundation for the next generation of great robotics libraries.

Install ROS Fuerte

Please see the ROS Fuerte page for more information on what's new in Fuerte, how to migrate from Electric, and how to download the release.

ROS Fuerte Release Candidate 3

| No Comments | No TrackBacks

fuerte2.pngROS Fuerte Release Candidate 3 is now available. This update contains bug fixes to rospack and roscore.

Ubuntu users: If you have a previous install of ROS Fuerte Beta, please use "sudo apt-get update; sudo-apt-get upgrade" to make sure that all packages are properly updated.

Non-Ubuntu users: Installation instructions for the experimental platforms like OS X and Arch are still in progress, so we encourage users of those platforms to help test and contribute.

ROS Fuerte Release Candidate 2

| No Comments | No TrackBacks

fuerte2.pngROS Fuerte Release Candidate 2 is now available. This in a minor update that includes new versions of RViz and Gazebo.

Ubuntu users: If you have a previous install of ROS Fuerte Beta, please use "sudo apt-get update; sudo-apt-get upgrade" to make sure that all packages are properly updated.

Non-Ubuntu users: Installation instructions for the experimental platforms like OS X and Arch are still in progress, so we encourage users of those platforms to help test and contribute.

Open Source Robotics Foundation

| No Comments | No TrackBacks
Open Source Robotics Foundation

Willow Garage has announced the Open Source Robotics Foundation, which will sponsor the development of ROS and Gazebo and aims to generally "support the development, distribution, and adoption of open source software for use in robotics research, education, and product development."

From the announcement:

The mission of the OSR Foundation is "to support the development, distribution, and adoption of open source software for use in robotics research, education, and product development." You will find this mission on the new OSR Foundation Web site, but not much else. In the coming weeks, we will be expanding on our goals, our short- and long-term plans, and the individuals and organizations that will be leading the OSR Foundation. For now, contact OSRF for more information or to get involved.

The first initiative of the OSRF will be participation in the DARPA Robotics Challenge, announced recently. The DARPA Robotics Challenge, or DRC, will launch in October 2012 and offers a $2 million prize "to whomever can help push the state-of-the-art in robotics beyond today's capabilities in support of the DoD's disaster recovery mission." The full announcement of the initiative specifically mentions the Fukushima nuclear accident as a recent example of a potential robotic application although other recent disasters such Hurricane Katrina and the oil spill at Deepwater Horizon also quickly come to mind.

DARPA today sponsored a Proposer's Day Workshop where more information about the Robotics Challenge is available via Webcast. During the Webcast, Nate Koenig from Willow Garage gave a brief talk on the current and future state of the open source Gazebo robot simulator, which will be extended by the OSR Foundation to support the DARPA Robot Challenge.

The DARPA Robotics Challenge supports the National Robotics Initiative announced by the Obama Administration in June 2011.

ROS Fuerte Release Candidate 1

| No Comments | No TrackBacks

fuerte2.pngROS Fuerte Release Candidate 1 is now available. Thanks to all who have filed bug reports and provided patches to fix issues during the ROS Fuerte Beta process. Barring any last-minute issues, this release candidate will be the official ROS Fuerte release, so we encourage all users to try this release out.

Ubuntu users: If you have a previous install of ROS Fuerte Beta, please use "sudo apt-get update; sudo-apt-get upgrade" to make sure that all packages are properly updated.

Non-Ubuntu users: Installation instructions for the experimental platforms like OS X and Arch are still in progress, so we encourage users of those platforms to help test and contribute.

ROS Fuerte Beta 2 Released

| No Comments | No TrackBacks

ROS Fuerte Beta 2 is now available. Many thanks to all who have contributed bug reports. A special thanks to following individuals, who have improved Fuerte compatibility on non-Ubuntu platforms:

  • Arch (+ GCC 4.7): Traveler Hauptman
  • OS X: William Woodall
  • Fedora: Steven Bellens

Installation instructions for ROS Fuerte Beta 2

Ubuntu Fuerte Beta 1 Users: in order to update to Beta 2, please run:

sudo apt-get update
sudo apt-get upgrade

(or uninstall Beta 1 first)

ROS Fuerte Beta 1 now available

| No Comments | No TrackBacks

ROS Fuerte Beta 1 is now available. ROS Fuerte provides a new build system foundation for ROS, with low-level ROS libraries, including ROS messages, now much more accessible to non-ROS frameworks. Installation instructions for both apt-based (Ubuntu) and source installation are available on the ROS wiki. We appreciate your assistance in improving installation instructions for non-Ubuntu platforms.

A migration guide is available that covers ROS Fuerte changes, including migration from deprecated features that were removed in this release. ROS Fuerte features major changes to the build system that are mostly backwards compatible, but will eventually require more significant migration in future releases like ROS Groovy Galapagos. Tools like rosdep and roslaunch have more significant changes.

Please report any issues on the relevant bug trackers, which are usually linked from the bottom of wiki pages for a particular library/stack/package/tool.

More technical descriptions of the changes in ROS Fuerte Beta 1 are available here:

Link: ROS Fuerte Beta 1 Installation

rosinstall 0.6 series released

| No Comments | No TrackBacks

Announcement from Tully Foote (rosinstall maintainer) to ros-users

Hi Everyone,

Thanks to the work of Thibault Kruse we have released an upgraded version of rosinstall we have bumped it up to the 0.6 series to indicate the significant overhaul. The basic command line usage has not changed.

The following changes have been incorporated:

  • prevention duplicate sourcing and path appending actions in combination with fuerte
  • No recursion into rosinstall files other than those provided with the Command line interface (was defunct anyway)
  • Giving a .rosinstall as a CLI argument is equivalent to giving its folder
  • elements in rosinstall files are checked to be valid folders (files for setup-file)
  • Duplicate path detection improved
  • It is now illegal to have any two SCM entries with overlapping paths
  • rosinstall will now change relative path "uri"s in rosinstall file SCM elements to absolute paths uris
  • Python code is now split up into modular design, allowing proper unit testing and using rosinstall code as library
  • Many more Unit-tests, more code documentation
  • usage of the yaml structure within the code was wrapped in a Wrapper class
  • setup.sh now parses .rosinstall to generate ROSPACKAGEPATH
  • parallel install, update, diff and stat

If you find problems please submit them at: https://kforge.ros.org/vcstools/trac/newticket

Tully

Announcement from simulator_gazebo maintainer John Hsu to ros-users

Hi All,

The new simulator_gazebo 1.6 release and the pr2_simulator 1.8 release shipped with ROS Fuerte, are based on the Gazebo 1.0.0 release candidate which is now considered API stable.

On the Gazebo side, major changes from Electric simulator_gazebo (pre gazebo-1.0.0-RC) to the Fuerte version (gazebo-1.0.0-RCX) can be found on the Gazebo change list wiki page. Notably, the new Gazebo plugins have been redesigned to be more flexible to the end-users, but unfortunately, this means the new plugin API is not backwards compatible with the old version. To convert old style plugins to the 1.0.0-RC plugin, please take a quick look at the plugin tutorials, in particular, this tutorial tries to provide an overview on the conversion process. For additional reference, you can also take a look at the updates in gazebo_plugins and pr2_gazebo_plugins packages. For questions or troubleshooting the conversion process, please make use of ROS Answers or the gazebo mailing list.

Lastly, you might have noticed that the gazebo project has been migrated from sourceforge to kforge (see the gazebo project page on kforge), please submit gazebo-specific tickets to the new trac and feel free to checkout the mercurial repository.

Thanks, John

crossposted from WillowGarage.com

Willow Garage is proud to announce our collaboration with Adept Technology. Along with Southwest Research Institute (SwRI), the three organizations are working together to contribute to the ROS-Industrial project. There is more information in Adept's official announcement.

ROS-Industrial has now demonstrated control of an Adept Viper 650, 6-axis industrial robot arm. This is the second robot vendor that has demonstrated a ROS-Industrial interface. This achievement demonstrates the ability of ROS-Industrial to leverage the functionality and capablities within ROS across different robot vendor hardware and configurations. Because ROS-Industrial aims to standardize the interfaces to industrial arms in general, high level application functionality will be able to be deployed across hardware platforms. Even today, the capabilities within ROS-Industrial, including path planning and dynamic pick and place, far exceed the capabilities of any commercially available robot software. ROS-Industrial enables new applications and broadens the industrial robot market.

Please see the ROS-Industrial site to find out more.

roscon19-20 May 2012 (immediately following ICRA)
St. Paul, Minnesota, USA

Important links:

Please join us this May for the inaugural edition of ROSCon!

ROSCon 2012 is a chance for ROS developers of all levels, beginner to expert, to spend an extraordinary weekend learning from and networking with the ROS community. Get tips and tricks from experts, network, and share ideas with fellow developers from around the globe.

ROSCon is a developers' conference, in the model of PyCon and BoostCon. The two-day program will comprise tech talks and tutorials that will introduce you to new tools and libraries, and teach you more about the ones you already know.

We received an overwhelming number of session proposals, which made for some tough decisions in the review process, and an acceptance rate of 27%. The program includes in-depth coverage of fundamentals, like tf and URDF, and introductions to higher-level concepts, like motion planning and multi-robot systems. We'll also hear about interesting applications of ROS, from teaching to field robotics. And we have two excellent keynotes, from Morgan Quigley of Stanford (and original author of ROS) and Julia M. Badger of NASA JSC.

We have some great sponsors to thank: Bosch, Motoman, Clearpath, Heartland, Willow Garage, CoroWare, Schunk, and Yujin. We're excited to have such strong industry support!

Registration is now open at roscon.ros.org.

If you have any questions, send email to info@roscon.ros.org.

dvds.jpg
We are please to announce the availability of ROS as a DVD installer that will install Ubuntu 10.04 and a basic configuration of ROS. The disk is also bootable as a LiveDVD, so you can get started without reformatting your hard drive.
64-bit ROS DVD
32-bit ROS DVD

electric-shirt-blog.jpg
In addition to this exciting news, we are also happy to be able to make available these great ROS t-shirts.
ROS Electric Emys t-shirt
ROS Diamondback t-shirt

We are setting aside $10 per DVD and $3 per shirt for the creation of a ROS Foundation which would be modeled after the Mozilla foundation. In the event that there are problems creating the foundation, we will donate the funds to the EFF. If you have any questions or feedback let us know.

Thanks,
I Heart Engineering



planet.ros.org is live

| No Comments | No TrackBacks

Hi ROS community,

We finally created a planet (an aggregation of developer blogs) as is common among big open source projects (kernel, python, ubuntu, fedora, apache ...).

Please enjoy: planet.ros.org/

Wanna join ? have any comment/bug to report ? Please follow the instructions on the website !

Regards,
Vincent Rabaud

Zeroconf on Android Review

| No Comments | No TrackBacks

Announcement by Daniel Stonier of Yujin to ros-users

Hi all,

Just a quick bump for those that might be interested in zero-configuration on android. I've got a rough working implementation with a couple of demo apps. The underlying jmdns still has a few rough edges, but am currently working with the developer to fix these. Since we're actively looking at issues now, it is probably an appropriate time to query others who might have an interest in seeing feature x or y to be implemented.

There is a review page at on the ROS wiki. Links to docs, code and demos can be found there.

If you have any comments, please add them there.

Regards,
Daniel Stonier

Announcement by Filip Muellers to ros-users

Hi all,

I would like to announce a new ROS repository:

http://code.google.com/p/rxdeveloper-ros-pkg/

It contains one package with some useful example files and a graphical tool for creating and editing launch files. You can easily compose computation graphs with a few mouse clicks, connect ROS nodes, run, test and change them. For more details including more pictures and a tutorial video please also visit http://code.google.com/p/rxdeveloper-ros-pkg/wiki/Tutorial

Thanks for your attention.
Filip Muellers

By popular demand, the deadline for submitting a proposal for a ROSCon session has been extended to 11 December 2011. Please send proposals to submit@roscon.ros.org.

Call for Proposals: ROSCon 2012

Hilton Garden Inn St. Paul City Center
St. Paul, Minnesota
19-20 May 2012 (immediately following ICRA)

Details: http://roscon.ros.org/ Proposals: submit@roscon.ros.org Questions: info@roscon.ros.org

ROSCon 2012 is a chance for ROS developers of all levels, beginner to expert, to spend an extraordinary weekend learning from and networking with the ROS community. Get tips and tricks from experts, network, and share ideas with fellow developers from around the globe.

ROSCon is a developers' conference, in the model of PyCon and BoostCon. The two-day program will comprise tech talks and tutorials that will introduce you to new tools and libraries, and teach you more about the ones you already know. The bulk of the program will be 30-40-minute presentations (some may be longer or shorter).

Want to present at ROSCon? Submit a proposal! For details on proposing, go to roscon.ros.org/

If you don't want to make a formal presentation, you should still bring your new project or idea to ROSCon!

There will be several sessions of Lightning Talks, which are 5-minute mini-talks that are scheduled just-in-time at the conference. There will also be open space for Birds-of-a-Feather (BoF) meetings, impromptu hacking sessions, and informal presentations.

On behalf of the ROSCon 2012 Organizing Committee:

Ryan Gariepy, Clearpath Robotics
Brian Gerkey, Willow Garage
Cédric Pradalier, ETH Zürich
Matthew Williamson, Heartland Robotics

fliercolor2.jpg

This year ROS celebrates another anniversary--four years of a great community building open-source libraries for robotics.

We're excited to celebrate this milestone by announcing ROSCon 2012, the first ROS developer's conference. On May 19-20 in St. Paul, Minnesota (following ICRA), ROS developers from around the globe will gather to learn, share, exchange, and network on all topics ROS.

The conference features:

  • Presentations by ROS experts, including robot-specific development, useful packages and stacks, developer tools, and embedded systems.
  • Tech talks and tutorials on the new tools and libraries.
  • Updates and discussion about the tools and libraries you already use.
  • Lightning talks and many informal sessions to learn more and share ideas.

The call for presentation proposals is now open, and the deadline for submissions is 12/4/2011. To learn more, go to http://roscon.ros.org/.

Continued Growth

By all measures, the ROS community has doubled in size since last year. The number of open-source, public code repositories grew from 50 in 2010 to 126 in 2011, and the number of ROS packages increased from 1643 to 3128. This explosive growth was driven in large part by the release of the Microsoft Kinect and has resulted in many new innovative applications.

2011-ros-growth.png

If you're interested in more information on the growth of ROS, you can see your community metrics report from 2011.

Improved Libraries and New Platforms

The third ROS distribution release, Diamondback, kicked off 2011 with Kinect and OpenNI compatibility, as well as smaller, easier-to-use libraries. Diamondback also introduced our open stack release system, which enables contributors around the world to provide their libraries as part of the ROS distributions.

The fourth and most recent release, Electric Emys, marked a milestone by providing complete, stable libraries for arm_navigation and PCL to complement upgraded build, communication, navigation, and image processing libraries.

Electric Emys also expanded ROS support so you can use it on various low-powered platforms and more operating systems. There are much-improved capabilities on:

  • Android and Java (Damon Kohler, Keith Hughes, and Lorenz Mösenlechner)
  • Arduino (Michael Ferguson and Adam Stambler)
  • Windows (Daniel Stonier)
  • OS X (William Woodall)
  • Python 3 (Michael Karg, Severin Lemaignan, and Lorenz Mösenlechner)

Thanks to the developers above that made this possible. Thanks also go to the many institutions and individuals that have used the new stack release system to contribute libraries to the Diamondback and Electric releases, including:

Open Processes

ROS is now in use on so many platforms and in such a variety of applications that it's difficult to have a centralized planning process for releases. Building on the ROS Enhancement Proposal (REP) process, the special interest groups (SIGs) you've created now plan future releases of ROS. Anyone can create one. Anyone can participate and contribute.

In addition to the REP and SIG processes, more community members are stepping forward to take over core ROS libraries to guide their development. Thank you to Chad Rockey (laser_drivers), Brett Grandbois (dynamic_reconfigure), and Ruben Smits (orocos_kinematics_dynamics) for taking on this important responsibility, as well as thanks to Jack O'Quin (camera_drivers) for his continued and excellent stewardship.

A final thank you goes to the many, many people that make answers.ros.org happen -- it is the primary resource for helping users get things done. In particular, thanks to the frequent contributors: Christian Dornhege, Eric Perko, Jack O'Quin, Martin Günther, Lorenz Mösenlechner, Michael Carroll, Koen Buys, Ivan Dryanovski, Chad Rockey, Andy Somerville, Mac Mason, Felix Endres, Patrick Goebel, Dimitri Prosser, David Lu, Antons Rebguns, Stefan Kohlbrecher, and Raphael Favier.

What's New for 2012: ROS Fuerte, Groovy Galapagos and ROSCon

ROS Fuerte Turtle and ROS Groovy Galapagos will be released in 2012. Fuerte, the March 2012 release, has 16 SIGs in the open-source robotics community collaborating on many improvements to ROS communication protocols and tools, as well as the libraries for motion planning, perception, manipulation, and simulation. Fuerte focuses on making libraries better and easier to use, both with and without ROS middleware. The build infrastructure will undergo major changes, and hopefully you can use these numerous libraries in more applications.

ROSCon 2012 happens in May, and we hope the many people that make ROS happen -- REP writers, SIG participants, stack maintainers, answers.ros.org participants -- can meet all under one roof and carry us on to ROS Groovy Galapagos!

Announcement from Daniel Stonier (Yujin Robot) to ros-users

Hi Ros userland,

This is an announcement to offiicially update the status of ros electric on windows. To summarize what is there:

Mingw Ros

For those who want to make windows apps (namely qt apps) whilst still developing in linux. This is working with the basic ros, ros comms and any message (msgs/srv) package. 

The status is fairly complete for what it is intended to handle - mostly development of testing/debugging apps. However if you have an itch, feel free to scratch it.

Msvc Ros

Getting ros to natively compile with the ms compilers.

  • Currently using the ms express 2010 compiler to build a 32-bit sdk (libs and headers) for the core ros/ros_comm/message packages
  • Uses rosbuild2 & nmake for a complete msvc build environment.

Call for Helpers

As you can see, the basics are functional (namely rosbuild2 functionality) and we've done some testing here at Yujin/Korean government groups to sort out a few of the porting issues. However, there's still quite a few areas that really need some work. You can see a list of the primary jobs we're targeting on the roadmap

I've posted a stack proposal review on the win_ros pages - if you want to be involved in the direction of the stack, feel free to ramble on the review page.

If you would also like to be involved more directly with development, please get in touch with me via email. A good linux/ros developer + windows developer should be able to push this in a good direction as it needs good integration on both sides. I'm a linux control engineer, so if you are an experienced windows developer it would be especially useful - I can bridge whatever gaps there are to the linux world and ros build framework.

Regards,
Daniel Stonier (Yujin Robot).

We'd like to welcome two new maintainers to the ROS core system. Chad Rockey from NREC will be maintaining imu_drivers and laser_drivers, and Brett Grandbois from CSIRO will be maintaining dynamic_reconfigure. We're excited to see members of the community stepping up to perform this important role. Stack maintainers direct and facilitate the development of the libraries they oversee -- releases like ROS Electric can't happen without their hard work, so thanks to Chad and Brett for stepping up.

Motoman-1.jpg

SwRI and the Motoman Robotics Division of Yaskawa America have announced that they will be collaborating to integrate Motoman® robots and ROS. SwRI's work with autonomous cars and ROS was featured in the ROS 3rd anniversary clip. The press release is included below:

SAN ANTONIO--(BUSINESS WIRE)--Southwest Research Institute (SwRI) and the Motoman Robotics Division of Yaskawa America, Inc. have entered into a memorandum of understanding to collaborate on integrating Motoman Robotics' line of industrial robots with the open-source ROS (Robot Operating System) software.

The collaboration will seek to develop, demonstrate and release to the open-source community an interface between Motoman® robots and ROS.

Motoman Robotics' line of industrial robots covers a variety of industrial automation applications in nearly every industry. ROS provides an open framework for developing advanced robotic solutions. It has a growing community of developers focusing on open-source software stacks for all aspects of robotic systems.

SwRI, as an independent, non-profit applied research and development organization, provides expertise in bringing fundamental research and technology to bear in industrial applications.

It's Electric!

| No Comments | No TrackBacks

electric_640w.png

ROS Electric Emys is now officially available! This amped up, current release of ROS features new, stable libraries for arm navigation and point cloud processing. There is also improved support for Android, Arduino, Windows, ARM, and Python 3. Please see the release page for some of the cool new tools and libraries in Electric, such as "interactive markers" for creating custom GUIs in RViz.

Many thanks to the ROS community for making this release possible. In order to better recognize your contributions, we have started an authors and contributors list. The numerous libraries, features, and bug fixes that you have provided enable ROS to run faster, better and on more platforms. We also appreciate the many contributors on answers.ros.org who make using ROS a better experience for everyone.

Getting Electrified

Please see the ROS Electric Emys page for more information on what's new in Electric, how to migrate from Diamondback, and how to download the release.

ROS Electric RC 1 Now Available

| No Comments | No TrackBacks

electric_rc1_200w.pngROS Electric Release Candidate 1 is now available. Thanks to all of you who have participated in the ROS Electic Beta process. We have been able to fix numerous issues as well as bring many more stacks into compatibility with Electric.

During this release candidate, we ask users of platforms like OS X, Arch, Fedora, Gentoo, OpenSUSE, Debian, and Slackware to please verify the ROS Electric installation instructions for those platforms.

A super mega thanks for this RC1 goes to:

  • Michael Karg, Severin Lemaignan, and Lorenz Mösenlechner: Python 3 support for major ROS libraries in order to support MORSE
  • William Woodall: OS X integration efforts
  • Thibault Kruset: widespread efforts with rosinstall, roslisp, and elsewhere
  • Chris Mansley: rosinstall patches.

This RC1 is limited to robot-generic software. Users of specific robot platforms like the PR2 should wait for system integrators to give the go-ahead on those platforms.

For a list of updates that ROS Electric provides, please see the ROS Electric Beta announcement.

ROS Electric Beta Now Available

| No Comments | No TrackBacks

Debian packages are now available for the ROS Electric Beta release. This beta release is in feature freeze: stacks that have reached "1.0" status will only receive bug fixes from this point forward so that others can easily integrate with this new release.

non-Ubuntu Linux users: We are still completing integration of Electric with non-Ubuntu Linux platforms, we do not recommend you use this release on those platforms.

stack maintainers: now is a good time to test your stacks for compatibility with Electric as we are in feature freeze. You can check the debian build status page to see if your stack is currently compatible with Electric.

ROS Electric is one of our biggest releases in terms of new features, so we will need your help making the final release as good as possible. We have always strived to integrate mobility, manipulation, and perception libraries together in ROS, so we are very proud that perception_pcl, based on the PCL 1.1 release, and arm_navigation are both reaching their first stable release in ROS. There are also great new features like "interactive markers" in RViz, improved URDF/COLLADA libraries, tf optimizations, and more.

You will be able to use ROS Electric on more platforms than ever before: Android, Arduino, and even Windows. All three are still very unstable and will need a lot of community support to get to stable releases in Fuerte, but we encourage you to try them out and give feedback. We have also updated rosdep (REP 111, REP 112) to make it more extensible and provide more integration options on platforms like OS X.

Changes in Electric may require updating your software for compatibility. One of the biggest changes we are making is moving more thirdparty ROS packages to be standard system installs. For example, OpenCV is now installed via the same debian package provided in the standalone release. This move towards standard system installs enables greater code portability and streamlines integration, but it does in some cases require changes to your build files in order to integrate properly. Also, although we strive for backwards compatibility, changes in thirdparty libraries as well as removal of deprecated features may require updates to code.

Many of the other updates are to reorganize software to be smaller, more modular, and easier to maintain. We have taken advantage of the new 'unary stacks' feature to release pluginlib, filters, xacro, and stage separately. In general, we have broken apart the common and geometry stacks into smaller components and we have also transferred ownership of the kdl package (orocos_kinematics_dynamics stack) to the Orocos developers -- this is a trend that we hope to continue moving forward.

What's new (More at http://www.ros.org/wiki/electric/Planning):

  • tinyxml, yaml-cpp, eigen, and opencv are now installed as normal system dependencies. This means that you will have to build against them explicitly. An example of what this looks like is documented here: yaml_cpp
  • Eigen is now fully on version 3
  • common and geometry stacks have been broken apart, though are still backwards compatible
  • interactive_markers in rviz
  • PCL 1.1
  • OpenCV 2.3
  • Lots of deprecated stuff was removed (ros::Message base class, rosrecord package, roslib/Header|Clock|Log)

As this is still the beta period, documentation is still in flux. We appreciate your support and contributions with finding out-of-date documentation in addition to filing tickets for any bugs or other issues that you may find.


io2011.pngYesterday at Google I/O, developers at Google and Willow Garage announced a new rosjava library that is the first pure-Java implementation of ROS. This new library was developed at Google with the goal of enabling advanced Android apps for robotics.

The library, tools, and hardware that come with Android devices are well-suited for robotics. Smartphones and tablets are sophisticated computation devices with useful sensors and great user-interaction capabilities. Android devices can also be extended with additional sensor and actuators thanks to the Open Accessory and Android @ Home APIs that were announced at Google I/O,

The new rosjava is currently in alpha release mode and is still under active development, so there will be changes to the API moving forward. For early adopters, there are Android tutorials to help you send and receive sensor data to a robot.

This announcement was part of a broader talk on Cloud Robotics, which was given by Ryan Hickman and Damon Kohler of Google, as well Ken Conley and Brian Gerkey of Willow Garage. This talk discusses the many possibilities of harnessing the cloud for robotics applications, from providing capabilities like object recognition and voice services, to reducing the cost of robotics hardware, to enabling the development of user interfaces in the cloud that connect to robots remotely. With the new rosjava library, ROS developers can now take advantage of the Android platform to connect more easily to cloud services.

100 Repositories

| No Comments | No TrackBacks

100.png

ROS just reached a new milestone: 100 public, open-source repositories! From top robotics research labs around the world to companies to hobbyists, these repositories hold the many contributions of the quickly growing ROS community. Back in November when we celebrated the third anniversary of ROS, we had just hit 52 repositories. In six months, that number has nearly doubled.

The 100th repository is rl-texplore-ros-pkg from the University of Texas at Austin and focuses on the area of reinforcement learning. We look forward to their contributions, along with the many other members of the ROS community that have helped us reach this milestone.

nao_rviz.png

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
(http://www.ros.org/wiki/nao). 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:
http://www.ros.org/wiki/nao/ChangeList

The source package release is available at:
http://code.google.com/p/alufr-ros-pkg/downloads/list

or via source checkout from Freiburg's ROS repository:
http://alufr-ros-pkg.googlecode.com/svn/trunk/nao/

Best regards,
Armin

ROS on Windows

| No Comments | No TrackBacks
winmaster.jpg

Progress towards full windows support for ROS continues. This should help provide critical support for making personal robotics more accessible to consumers running Windows. Congrats to Daniel and everyone else who has contributed on getting things like roscore running, your efforts are appreciated. Below is the official announcement.

Announcement from Daniel Stonier to ros-users

Hi ros users,

Ok, something more of an official announcement for the
win-ros-pkg<http://code.google.com/p/win-ros-pkg/>
repository.

We have a mingw compiled ros working (minimally for windows) and also
started a stack to handle development of the tools and utilities. Some links
if you are interested in diving in::

Some tutorials

- http://www.ros.org/wiki/diamondback/Installation/Windows
- http://www.ros.org/wiki/win_ros
- http://www.ros.org/wiki/mingw_cross/Tutorials/Mingw Build Environment
- http://www.ros.org/wiki/win_ros/Tutorials/Mingw Runtime Environment
- http://www.ros.org/wiki/win_ros/standalone_clients

To contact us, bug reporting, feature requests:

- http://www.ros.org/wiki/win-ros-pkg/Contact

Note that this is only early days yet - only the core packages have been
patched and we're also working on native msvc support, but any and all are
welcome to test and even better, contribute.

Regards,
Daniel Stonier.

Announcement from Radu Rusu/Willow Garage

The Point Cloud Library (PCL) moved today to its new home at PointClouds.org. Now that quality 3D point cloud sensors like the Kinect are cheaply available, the need for a stable 3D point cloud-processing library is greater than ever before. This new site provides a home for the exploding PCL developer community that is creating novel applications with these sensors.

PCL contains numerous state-of-the art algorithms for 3D point cloud processing, including filtering, feature estimation, surface reconstruction, registration, model fitting and segmentation. These algorithms can be used, for example, to filter outliers from noisy data, stitch 3D point clouds together, segment relevant parts of a scene, extract keypoints and compute descriptors to recognize objects in the world based on their geometric appearance, and create surfaces from point clouds and visualize them -- to name a few.

First Anniversary: a brief history of PCL

This new site also celebrate the one year anniversary of PCL. The official development for PCL started in March 2010 at Willow Garage. Our goal was to create a library that can support the type of 3D point cloud algorithms that mobile manipulation and personal robotics need, and try to combine years of experience in the field into coherent framework. PCL's grandfather, Point Cloud Mapping, was developed just a few months earlier, and it served as an important building block in Willow Garage's Milestone 2. Based on these experiences, PCL was launched to bring world-class research in 3D perception together into a single software library. PCL would enable developers to harness the potential of the quickly growing 3D sensor market for robotics and other industries.

For this occasion, we put together a video that present the development of PCL over time.

Towards 1.0: PCL and Kinect

The launch of the Kinect sensor in November 2010 turned many eyes on PCL, and its user community quickly multiplied. We turned our focus on stabilizing and improving the usability of PCL so that users would be able to develop applications on top. We are now proud to announce that the upcoming release of PCL features a complete Kinect (OpenNI) camera grabber, which allows users to get data directly in PCL and operate on it. PCL has already been used by many of the entries in the ROS 3D contest, showing the potential of Kinect and ROS. Please check our website for tutorials on how to visualize and integrate Kinect data directly in your application.

The PCL development team is current working hard towards a 1.0 release. PCL 1.0 will focus on modularity and enable deployment of PCL on different computational devices.

A Growing Community

We are proud to be part of an extremely active community. Our development team spawns over three continents and five countries, and it includes prestigious engineers and scientists from institutions such as: AIST, University of California Berkeley, University of Bonn, University of British Columbia, ETH Zurich, University of Freiburg, Intel Research Seattle, LAAS/CNRS, MIT, NVidia, University of Osnabrück, Stanford University, University of Tokyo, TUM, Vienna University of Technology, Willow Garage, and Washington University in St. Louis.

Support

PCL is proudly supported by Willow Garage, NVidia, and Google Summer of Code 2011. For more information please check http://www.pointclouds.org/about.html.

Thanks

PCL wouldn't have become what it is today without the help of many people. Thank you to our tremendous community, especially our contributors and developers who have worked so hard to make PCL more stable, more user friendly, and better documented. We hope that PCL will help you solve more 3D perception problems, and we look forward to your contributions!

While often neglected, documentation helps make your project usable, so here is a contest for making great documentation!

contest-pnf.png

Have you seen this page? Now there is a contest to fix it!

To provide some motivation for you to complete your project, I Heart Robotics and Willow Garage have teamed up for the ROS Documentation Contest.

contest-prizes.jpg

We have prizes of official ROS Diamondback and I Heart Robotics T-Shirts available for the best new documentation. Tell us how your code works and you could win both shirts!

How to Enter
To enter, add your documentation to the ROS.org wiki and email contest@iheartrobotics.com with a link to your recently updated documentation.

Rules
  • All entries must be documented on the ROS.org wiki and the documentation must be licensed under Creative Commons Attribution 3.0.
  • Integrated API Documentation must be open source using an OSI-approved license and be hosted on a publicly accessible server.
  • Entries must for open source packages that work directly with ROS.
  • Videos must be Creative Commons licensed and embeddable on the ROS.org and I Heart Robotics blogs.
  • You may enter as many entries as you like and as early as you like.

Deadline
Prizes will be awarded on a rolling basis until supplies are exhausted. The first winners will be announced within the next 30 days, subsequent winners will be announced at least once every 30 days until the end of the contest.

Eligibility
Contributors from most countries are eligible where ever legally and financially possible. You can quickly check if you can receive shipments via US Postal Service Flat Rate Priority Mail International or can email questions to contest@iheartrobotics.com.

Judging Criteria
  • Package documentation
  • Description
  • Examples
  • Installation
  • Topics / Services
  • Parameters 
  • Videos
  • Pictures
  • Tutorials
  • API documentation
Since this contest is designed to motivate contributors to document their code, only documentation with significant improvements after March 27th will be considered. For equally well-documented projects, priority will be given to which ever is more useful.

More information can be found at the ROS Documentation Contest page.

inversekinematics_thumb.jpg
Here is some good news for all of the robot arms out there.

Announcement from Rosen Diankov of OpenRAVE to ros-users

Dear ROS Users,

OpenRAVE's ikfast feature has been seeing a lot of attention from
ros-users recently, so we hope that making this announcement on
ros-users will help get a picture of what's going on with ROS and
OpenRAVE:

We're pleased to announce the first public testing server of
analytical inverse kinematics files produced by ikfast:

http://www.openrave.org/testing/job/openrave/

The tests are run nightly and tagged with the current openrave and
ikfast versions. These results are then updated on the openrave
webpage here:

http://openrave.programmingvision.com/en/main/robots.html

The testing procedures are very thorough and are explained in detail here:

http://openrave.programmingvision.com/en/main/ikfast/index.html

Navigating the "robots" openrave page, you'll be able to see
statistics for all possible permutations of IK and download the
produced C++ files. For example the PR2 page has 70 different ik
solvers:

http://openrave.programmingvision.com/en/main/ikfast/pr2-beta-static.html#robot-pr2-beta-static

For each result, the "C++ Code" link gives the code and the "View"
link goes directly to the testing server page where the full testing
results are shown. If the IK failed to generate or gave a wrong
solution, the results will show a stack trace and the inputs that gave
the wrong solution.

For example, when generating 6D IK for the PR2 leftarm and setting the
l_shoulder_lift_joint as a free parameter, 0.1% of the time a wrong
solution will be given:

http://www.openrave.org/testing/job/openrave/lastSuccessfulBuild/testReport/%28root%29/pr2-beta-static__leftarm/_Transform6D_free__l_shoulder_lift_joint_16___/?

By clicking on the "wrong solution rate" link, a history of the value
will be shown that is tagged with the openrave revision:

http://openrave.org/testing/job/openrave/48/testReport/junit/%28root%29/pr2-beta-static__leftarm/_Transform6D_free__l_shoulder_lift_joint_16___/measurementPlots/wrong%20solutions/history/

In any case all these results are autogenerated from these robot repositories:

http://openrave.programmingvision.com/en/main/robots_overview.html#repositories

They are stored in the international standard COLLADA file format:

http://www.khronos.org/collada/

and OpenRAVE offers several robot-specific extensions to make the
robots "planning-ready":

http://openrave.programmingvision.com/wiki/index.php/Format:COLLADA

The collada_urdf package in the robot_model trunk should convert the
URDF files into COLLADA files that use these extensions.

Our hope is that eventually the database will contain all of the
world's robot arms. So, if you have any robot models that you want
included on this page please send an email to the openrave-users list!

In order to keep the openrave code and documentation more tightly
synchronized, we have unified all the OpenRAVE documentation resources
into one auto-generated  (from sources) homepage:

http://www.openrave.org

Some of the cool things to note are the examples/databases/interfaces gallery:

http://openrave.programmingvision.com/en/main/examples.html

http://openrave.programmingvision.com/en/main/databases.html

http://openrave.programmingvision.com/en/main/plugin_interfaces.html

Finally, just to assure everyone we're working on tighter integration
with ROS and have begun to offer some of the standard
planning/manipulation services through the orrosplanning package.

rosen diankov,


kinect_news.jpg

If you needed motivation or were waiting for the right time to upgrade to the new Diamondback release of ROS, this might be what you were looking for.

Announcement from Suat Gedikli of Willow Garage to ros-users

Hi everyone,

As part of our rewrite of the Kinect/PrimeSense drivers for ROS,
we're happy to announced that there are now debian packages
available for i386/amd64 on Ubuntu Lucid and Maverick. This
means that you can now:

sudo apt-get install ros-diamondback-openni-kinect

We hope this will simplify setting up your computer with the
Kinect. The documentation for the new openni_kinect stack can be
found here:

http://www.ros.org/wiki/openni_kinect

The new stack is compatible with the old 'ni' stack. We have
renamed the stack to provide clarify for new users and also to
maintain backwards compatibility with existing installations.

As an alternative, you can download, compile and install
these libraries from the sources, which are available here:

https://kforge.ros.org/openni/openni_ros

Other sample applications in the old "ni" stack are still
available there, but will be moved to other stacks in the near
future. The "ni" stack is deprecated and we encourage developers
wishing to use the latest updates to switch to the openni_kinect
stack.

FYI: developers on non-ROS platforms can find our scripts for
generating debian packages for OpenNI here:

https://kforge.ros.org/openni/drivers

Cheers,
Suat Gedikli
Tully Foote

iheartrobotics.png

The ROS News Voltron-bot has grown by one: I Heart Robotics is now writing news, tutorial, and other posts on ROS. Like ROS itself, we want the ROS News site to be for the community, by the community, and we're excited to have a regular contributor to ROS help join that effort.

I Heart Robotics has long been a great resource for the ROS and the broader robotics community. From regular news posts, to reviews of ROS drivers, to tutorials for ROS, iheartrobotics.com is full of great content for ROS users. There is also iheart-ros-pkg, which provides drivers, tools, and demos.

I Heart Robotics will still be running posts over at IHeartRobotics.com, so be sure to add it to your news reader (if you haven't already). You may also drop by store.iheartengineering.com to see if there's anything useful you can use to build your robot (or look good while doing it).

mingw_demo.png

While not yet complete, ROS is now one step closer to working on Windows using the Minimal GNU compiler toolchain thanks to the work of Daniel Stonier and Yujin Robot. If you are a windows user and have experience using MinGW or cross compiling there is a tutorial showing how to use Qt with ROS on Windows up for people interested in testing and improving ROS support for Windows.


Announcement from Daniel Stonier of Yujin Robot to ros-users

Greetings all,

We've had a need to develop test and debugging apps for our test and factory
engineers, who, unfortunately (for them!), only use windows. While service
robotics' patched ros tree could give us msvc apps, it wasn't patched into
ros mainstream and it couldn't let us share our own testing apps on linux
with the test engineers on windows without building two of each application.

So...enter mingw cross <http://mingw-cross-env.nongnu.org/>! We've now got
this patched in eros/ros up to being able to run a talker/listener and add
int server/client along with inbuilt support for qt as well.

If you're interested in being a guinea pig to test this, or just curious,
you can find a tutorial on the ros wiki here:

http://www.ros.org/wiki/eros/Tutorials/Qt-Ros on Windows

If you come across any bugs (in the tutorial or the installation), reply to
this email, or contact me on irc in OFTC #ros so we can squash the buggers.

Hopefully as time goes by we can patch support in for other commonly used
ros packages as well as adding rosdeps upstream to the mingw cross
environment. We also aim to get ros running on msvc in a more complete way,
but that will need to wait for the rebuild of the ros build environment that
is looming.

Cheers!
Daniel Stonier (Yujin Robot)

Announcing ROS Answers

| No Comments | No TrackBacks

Screen shot 2011-02-15 at 7.28.14 PM.png

There's a brand-new answers.ros.org site to help you ask questions about ROS and have them answered by a community of ROS experts. It's like Stack Overflow, but all the questions are about ROS, and it's powered by the open-source AskBot platform.

Melonee and Tully have been hard at work on this the past couple of weeks and explained their motivation in their announcment to ros-users:

Over the last couple months we've seen an increase in the volume of emails on ros-users and no one likes too many emails. So we put together answers.ros.org to provide an alternative forum for asking and answering questions. If you really love getting all that email you can still have it by signing up for answers.ros.org and setup your profile to receive all traffic like before. However if you prefer lower volume you can filter based on tags (whitelist or blacklist). This does not mean we're doing away with ros-users, we would like to use this mailing list more for announcements and general discussion rather than individual troubleshooting. We would to like to encourage everyone to signup at answers.ros.org. Go ask questions and provide answers as usual.

Some of you may be wondering, "Why don't you just use Stack Overflow?"

The ROS Answers site, we hope, will provide a better experience for users. All of the tags will be related to ROS -- you can even subscribe to questions about a particular package/stack. We also hope that we will be able to use the open-source AskBot platform to have tight integration with the ROS wiki. In the future, look for wiki macros and other navigation tweaks to help you find the information you need more effectively.

Also, you may be wondering "When should one use answers.ros.org vs. the ros-users mailing list?" Well, there's an answer for that.

Lastly:

If you have questions or feedback about the site use "answers.ros.org" as the tag so that we get your feedback.

ROS 3D Contest: The Results!

| No Comments | No TrackBacks

Thumbnail image for 3Dturtle.jpgWe were absolutely thrilled with eighteen entries to the ROS 3D Contest. The community really impressed us with creativity and technical prowess in these entries, and choosing the prizes was a difficult process. In fact, so difficult that we bent the rules and created two new prizes: 4th Overall and 2nd place Most Useful.

For the Overall prizes, we selected the entries that both amazed us and embraced the spirit of the contest: inspiring and providing building blocks for future Kinect hackers. We've been able to try many of these entries on our own thanks to the great code and documentation, and we hope that others will as well. It was hard to pick a favorite, but we kept coming back to Garratt Gallagher's Customizable Buttons. We tried it on our own desks, and it just puts a smile on your face: you draw a button whereever you please and press it. It made us feel like we were in a cartoon world where we could bend the rules of the universe. Garratt was also the most prolific -- with his six different entries, you can deconstruct the various components that he was able to assemble to produce very different results.

For second place, we selected Quadrotor Altitude and Obstacle Avoidance by the STARMAC project at Berkeley. We loved seeing what a Quadrotor with an Atom processor could do, and they went the extra mile to make sure others with quadrotors had a good starting point. For third place, Taylor Veltrop's Humanoid Teleoperation entry just kept getting better and better. He recently used his library to win best performance in the Robot Athlete Cup 2011 competition by doing robo-ikebana. We added a fourth place for Person Tracking and Reconstruction from a Mobile Base with a 7 DOF Manipulator by Chris Burbridge & Lorenzo Riano. Using a robot to turn a Kinect into a 3D scanner holds many possibilities.

For Most Useful, we were wowed. First prize went to RGBD-6D-SLAM from the University of Freiburg. SLAM with a Kinect holds the potential to unlock many applications, from creating 3D maps and 3D models to cheap autonomous navigation and much, much more. Normally "bleeding edge" means no one else can run it, but, in their case, they produced a 6D-SLAM solution that we were able to download and use in our own offices. There is much to improve, but the potential is huge. For second place, we chose ETH Zurich's Automatic Calibration of Extrinsic Parameters. Anyone mounting a Kinect on their robot should take a look at using their library.

Finally, our PrimeSense Dev Kit 5.0 Awards (thanks PrimeSense) go to Michael Ferguson and the Chemnitz University of Technology. We are confident, from their entries, that they will be able to put them to good use.

Thanks everyone!

Overall:

1st Place ($3000): Customizable Buttons, Garratt Gallagher
2nd Place ($2000): Quadrotor Altitude and Obstacle Avoidance, Patrick Bouffard
3rd Place ($1000): Humanoid Teleoperation, Taylor Veltrop
4th Place ($500): Person Tracking and Reconstruction from a Mobile Base with a 7 DOF Manipulator, Chris Burbridge & Lorenzo Riano

Most Useful:

1st Place ($2000): RGBD-6D-SLAM, Felix Endres, Juergen Hess, Nikolas Engelhard, Juergen Sturm, Daniel Kuhner, Philipp Ruchti, and Wolfram Burgard
2nd Place ($1000): Automatic Calibration of Extrinsic Parameters, François Pomerleau, Francis Colas and Stéphane Magnenat

PrimeSense Dev Kit 5.0 Awards:

OpenNI Developer Challenge

| No Comments | No TrackBacks

opennidevchall.jpg

ROS 3D Contest not enough for you? PrimseSense is sponsoring a contest to develop a natural interaction interface for a Web browser, with $20K as the top prize. For more details, see the OpenNI Developers Challenge.

ROS 3D Contest: Entries Due!

| No Comments | No TrackBacks

Thumbnail image for 3Dturtle.jpg

Today is the deadline for entries in the ROS 3D Contest. There's already a lot of great entries and we're looking forward to the judging.

We continue to strive to make the ROS development process more open, from REPs to exploring a ROS Foundation. One need identified by the community was making it easier to get involved in the core ROS development. It hasn't been clear what features could be developed by those looking to get into ROS core development. To facilitate that, we've setup a simple mechanism to expose open issues which are not actively being worked of to the community.

These new "Handoff Lists" link to feature enhancements that we think are good places to get started as a ROS hacker. We have only just started on adding tickets to this list and will hopefully add even more over time. If you'd like to contribute, these tickets are a good way to get familiar with parts of the code base and development process.

One More Thing... A Contest!

| No Comments | No TrackBacks

3Dturtle.jpg

We promised you some early holiday Kinect presents, and we hope you like what you've seen:

We've been impressed with what we've seen from you:

In fact, hacks based on ROS, PCL, or OpenCV took three out of the seven "best kinect hacks" on TechCrunch.

Now, it's time to take it up a notch.

ROS 3D Contest

We invite you to combine an RGB-D sensor (e.g. Kinect, PSDK5.0) with ROS to produce something new, interesting, and fun. It could be anything, from a novel robot control interface to a data-driven art project to pure computer vision. Bonus points if it's also useful (see below). We're offering $8K in prizes.

As we promote open-source software, we encourage participants to share, and our rules and judging will reward participants who act in the spirit of collaboration.

Rules

  • All entries must be open source using an OSI-approved license and be hosted on a publicly accessible server.
  • Entries must compatible with ROS and an RGB-D sensor (e.g. Kinect, PSDK5.0).
  • Videos must be Creative Commons licensed. In submitting the video, you give Willow Garage permission to include snippets of your video in a montage video (with attribution).
  • You can use whatever additional hardware you want. Entries that include custom hardware modifications are encouraged to post instructions for reproducing.
  • You may enter as many entries as you like and as early as you like.

Deadline: All entries must be submitted by January 23, 2011.

Helpful Links

Judging Criteria

We will be using the Iron Chef judging system to rate each entry:

Taste (10 pts)
Presentation (i.e. Documentation) (5 pts)
Originality (5 pts)

For the "taste" score, judges will take into account how well each entry uses the "secret ingredients" (ROS + RGB-D).

For the "originality" score, credit will go to the first entry (by date) to demonstrate a particular idea. Your entry can still be "original" even if subsequent entries use the same idea.

Prizes

  • First Place: $3000
  • Second Place: $2000
  • Third Place: $1000
  • "Most Useful": $2000

A special "Most Useful" prize will be awarded to the entry that provides the most useful, re-usable capabilities to the open-source community. As evidence of usefulness, judges will be biased towards entries that are used by other contest participants. This includes contributions to the underlying ROS drivers and OpenNI integration.

How to Enter

Contest Deadline: January 23, 2011

Entry page

Enter early, enter often!

openni.pngPrimeSenseâ„¢ is launching the OpenNIâ„¢ organization, an open effort to help foster "Natural Interaction"â„¢ applications. As part of this effort, PrimeSense is releasing open source drivers for the RGB-D sensor that powers the Kinectâ„¢ and other devices such as PrimeSense's Development Kit 5.0 (PSDK 5.0) and are making the HW available for the OpenNI developers community! This will unlock full support for their sensor and also provide a commercially supported implementation. They are also releasing an open-source OpenNI API, which provides a common middleware for applications to access RGB-D sensors. Finally, they are releasing Windows and Linux binaries for the NITE skeleton-tracking library, which will enable developers to use OpenNI to create gesture and other natural-interaction applications. We at Willow Garage have been working with PrimeSense to help launch the open-source drivers and are happy to join PrimeSense in leading the OpenNI organization.

PrimeSense's RGB-D sensor is the start of a bright future of mass-market available 3D sensors for robotics and other applications. The OpenNI organization will foster and accelerate the use of 3D perception for human-computer/robot interaction, as well as help future sensors, libraries, and applications remain compatible as these technologies rapidly evolve.

For the past several weeks, we've been working with members of the libfreenect/OpenKinect community to provide open-source drivers, and we have already begun work to quickly integrate PrimeSense's contributions with these efforts. We will be using the full sensor API to provide better data for computer vision libraries, such as access to the factory calibration and image registration. We are also working on wrapping the NITEâ„¢ skeleton and handpoint tracking libraries into ROS. Having access to skeleton tracking will bring about "Minority Report" interfaces even faster. The common OpenNI APIs will also help the open-source community easily exchange libraries and applications that build on top. We've already seen many great RGB-D hacks -- we can't wait to see what will happen with the full power of the sensor and community unleashed.

This release was made possible by the many efforts of the open-source community. PrimeSense was originally planning on releasing these open-source drivers later, but the huge open-source Kinect community convinced them to accelerate their efforts and release now. They will be doing a more "formal" release in early 2011, but this initial access should give the developer community many new capabilities to play with over the holidays. As this is an early "alpha" release, we are still integrating the full capabilities and the ROS documentation is still being prepared. Stay tuned for some follow-up posts on how to start using these drivers and NITE with ROS.

PrimeSense's PSDK 5.0 is available separately and has several advantages for robotics: it is powered solely by USB, and the sensor package is smaller and lighter than the Kinect. This simplifies integration and will be important for use in smaller robots like quadrotors. PrimeSense is making a limited number of PrimeSense developer kits available for purchase. Please visit here to sign up to purchase the PSDK5.0.

You can visit OpenNI.org to find out more about the OpenNI organization and get binaries builds of these releases. Developers interested in working with the source code can checkout the repositories on GitHub and join the discussion groups at at groups.google.com/group/openni-dev. For more information about OpenNI, please visit OpenNI.org. To follow the efforts of the ROS community and Kinect, please join the ros-kinect mailing list.

Find this blog and more at planet.ros.org.


Monthly Archives

About this Archive

This page is an archive of recent entries in the announcements category.

book is the next category.

Find recent content on the main index or look in the archives to find all content.