Celebrating 9 Years of ROS!

From ros.org

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](http://www.dwheeler.com/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.

ROSCon 2016: The State of ROS is Strong

Every year, we’re impressed and humbled by the enthusiastic support we get from the ROS community. This year was certainly no exception. After ROSCon 2015 sold out weeks in advance, we knew we had to find an even larger venue for this year’s conference in Korea. The Conrad Hotel in Seoul turned out to be not quite big enough, however, as ROSCon 2016 sold out anyway. We hosted more than 450 attendees (a 20% increase over last year), 44% of whom came from the Asia Pacific region. Visitors from China now make up the second-largest group accessing the ROS wiki, and five out of the top eight countries using the wiki are in Asia Pacific as well. This level of engagement is one of the reasons we decided to host ROSCon in Korea in the first place, and Asia as a whole is a big part of why ROS package downloads are up by 150% over the last year.

Statistics like these only tell part of the story. What’s more significant for us is how ROS is changing from a way to make robotics research simpler and more collaborative to a foundation that encourages and facilitates a rapidly-maturing robotics industry. Nearly two thirds of ROSCon 2016 participants were from industry (as opposed to academia), and the selection of talks included topics such as calibration, testing, deployment, security, and support of ROS-based robots in operational environments. One highlight was the introduction of H-ROS (Hardware Robot Operating System), which leverages ROS 2 to make hardware from different manufacturers interoperable with a minimum amount of hassle.

Another trend we noticed this year was a substantial and wide-ranging effort at making ROS simpler and more accessible to new users. We had presentations on Gazebo usability upgrades, drones optimized for ROS development, and a new ROS package that lets you visually program robots by moving around graphical blocks. Intel showed up with an all-in-one robotics perception device called Euclid, which is an integrated 3D sensing and computing platform (based on a RealSense camera and Atom processor) that makes sophisticated computer vision easy and affordable. Also introduced at ROSCon 2016 was the Turtlebot 3, a collaboration between OSRF and ROBOTIS, which shrinks the Turtlebot research and education platform down to something backpack-sized while making it more customizable and much more affordable.

We’d also like to highlight a new diversity program that we began this year; one designed to help enable participation in ROSCon by those typically underrepresented in the tech community. We set aside a full 10% of the ROSCon 2016 conference budget to help sixteen roboticists who otherwise wouldn’t have been able to make it to Seoul for the conference. To get a sense of the impact that the diversity program had this year, we’d encourage you to watch this lightning talk from Ahmed Abdalla and Husam Salih, two students at the University of Khartoum in Sudan, who are starting a robotics lab from scratch under severe government sanctions.

Thanks to our fantastic organizing team, all of the ROSCon videos and presentations are already available. You can find them on the ROSCon 2016 website here. We’re already looking forward to ROSCon 2017.

Happy Halloween!

pic1-50
pic2-50

Another year, another collection of creative and sometimes topical costumes. Happy Halloween, everybody!

Goodbye, ROSCon 2016

Following an exciting weekend, we bid farewell to ROSCon 2016 in Seoul. It was record-breaking in every way, with over 450 attendees and a 60% increase over last year in sponsorship. Thanks to everyone for coming and for your support! Stay tuned for details on the next event. We anticipate posting videos of the presentations by October 20.

roscon-group

Photo credit: Evan Ackerman

Bosch Research and Technology Center Joins Forces with Open Source Robotics Foundation to Advance the Development of ROS

Bosch Underwrites Full-Time Developer for ROS 2 Research

A full-time developer sponsored by Bosch’s Research and Technology Center in North America will begin working with Open Source Robotics Foundation (OSRF) this month to advance the development of Robotics Open Source 2, the two organizations announced today. This announcement not only demonstrates the mutual commitment of Bosch and OSRF to the development of ROS 2 but also to the worldwide community of ROS developers and supporters.

ROS 2 is the next generation of ROS, a set of libraries and tools that simplify the task of creating and programming robotic platforms and applications. An update on ROS 2 will be made by Deanna Hood and William Woodall at ROSCon, the upcoming developer conference October 8-9 in Seoul, Korea.

“The development of ROS has been a collaborative effort from the beginning, and we are thrilled to continue that tradition with the support of Bosch,” said Brian Gerkey, CEO of Open Source Robotics Foundation. “We look forward to welcoming our newest ROS 2 team member.”

“We are honored to be a part of the movement that’s helping developers to create groundbreaking robotics technologies for industries all over the world,” said Axel Wendt, group manager for Robotics at the Research and Technology Center in Palo Alto. “This partnership delivers on our objective to cultivate and to drive innovation from the ground up.”

“The collaboration with OSRF is well aligned with our worldwide efforts in robotics research at Bosch,” said Kai Arras, head of robotics research at Robert Bosch GmbH. “We are glad to contribute back to the open source community in this way and look forward to new, exciting features of ROS 2 that are relevant to the industry.”

We’re collaborating with the Toyota Research Institute

You can see more formal announcements from us here and from Toyota Research Institute here, but we are very pleased to announce our new relationship with TRI. TRI is the R&D arm of Toyota. TRI has contracted with us to help develop and grow ROS and Gazebo. In addition, TRI has made a $1 million donation to OSRF.

The CEO of TRI, Gill Pratt, is very familiar with us and our work, including our contributions to the DARPA Robotics Challenge, for which he was the program manager.

As Gill says in our release:

I’ve witnessed first-hand the value of the Open Source Robotics Foundation. Of the twenty-three teams that competed in the DARPA Robotics Challenge eighteen used ROS and fourteen used Gazebo. Through this charitable contribution, TRI will support efforts to grow the capabilities of ROS and Gazebo, not only for TRI, but also for the hundreds of thousands of members of the open source robotics community.

Part of today’s announcement also includes the news that we have created the Open Source Robotics Corporation, a for-profit subsidiary of OSRF. We will continue to create and distribute open source and free-of-charge applications for the robotics community, including ROS and Gazebo. If you have specific questions about our reorganization, please let us know.

HAPTIX: Simulation of prosthetic devices

Fundamentally, robotics is about helping people. Robots help us manufacture things, help us build things, and help make our lives easier and more convenient. As robotic systems increase in sophistication and capability, they’re starting to help people more directly, in elder care, rehabilitation centers, and hospitals. In the near future, robotics will become even more tightly integrated with humanity, to the point where cybernetics will be able to restore function to people with disabilities. In particular, amputee military personnel are the focus of one such program.

In 2014, DARPA announced its Hand Proprioception and Touch Interfaces (HAPTIX) program, which “seeks to create a prosthetic hand system that moves and provides sensation like a natural hand.”

According to Doug Weber, DARPA program manager of HAPTIX: “We believe that HAPTIX will create a sensory experience so rich and vibrant that the user will want to wear his or her prosthesis full-time and accept it as a natural extension of the body. If we can achieve that, DARPA is even closer to fulfilling its commitment to help restore full and natural functionality to wounded service members.”

Three different teams are involved in the HAPTIX project, and its success will depend on a carefully optimized mix of hardware, user interfaces, and control algorithms. OSRF is proud to be providing a customized version of the Gazebo simulator to the HAPTIX teams, allowing them to run tests on their software without being constrained by hardware availability: essentially, a kind of virtual playground for software engineers.

“The goal of HAPTIX is for OSRF to provide a realistic prosthetic simulation environment for biomechanical engineers to develop controllers for advanced prosthetics with high degrees of freedom,” explains John Hsu, co-founder and Chief Scientist at OSRF. The advanced prosthesis that DARPA is using in the HAPTIX program is DEKA’s “Luke” robotic arm, a 14 DoF cybernetic total arm replacement system. However, the arm is currently controlled by simple user interfaces designed for testing, and part of what HAPTIX hopes to deliver are interfaces that utilize control signals from muscles and nerves, while simultaneously delivering sensory feedback.

After nearly ten years of work and $40 million from DARPA, DEKA’s robotic arm is an amazing piece of hardware, but that’s just the beginning. “The hardware, in my opinion, needs to come before the software,” says Hsu. “They can be designed at the same time, but the hardware has a longer iteration cycle. Once you develop a nice hardware platform that’s stable, then you give it to the software team, and they take off, working really fast on the software while in the meantime trying not to break the hardware.”

This illustrates two reasons why having a good simulation environment is important: first, it lets you start working on the software before the hardware is fully complete, and second, it to some extent insulates software development from the hardware itself, meaning that you can have lots of engineers developing software in parallel, even if you only have one piece of hardware that may be fragile, expensive, and quite often inoperable for one reason or another.

For OSRF, creating and supporting a version of Gazebo for the HAPTIX program involves many different areas. Besides the customized simulation environment, OSRF has also provided teams with an OptiTrack motion capture device, NVIDIA stereo glasses and a 3D monitor, a 3D joystick, and the documentation required to get it all working together flawlessly. This custom version of Gazebo also includes support for a variety of teleoperation hardware, and for the first time, users can interact programmatically with the simulation using both Windows and MATLAB. HAPTIX developers can leverage these 3D sensors and teleoperation systems to translate the motions of physical arms and hands into virtual environments, allowing them to run common hand function tests in the real world and in simulation at the same time. This also lays the foundation for a framework that could provide amputees a powerful and affordable way to learn how to use their new prosthesis.

Once the HAPTIX teams receive their DEKA arms, OSRF’s job becomes even more important, according to Hsu, because they’ll get a chance to see how well the simulation is actually working and then refine it to bring it as close to reality as possible. “I’m really looking forward to the validation part,” Hsu says. “I think that’s one of the big missing pieces for many simulation platforms: good validation data. When we were working on Gazebo for the DARPA Robotics Challenge, we never had an ATLAS robot. Getting the DEKA hand to do validation is huge.”

Validation is the process of making sure that commands sent to the simulated DEKA arm result in the same movements as identical commands sent to the real DEKA arm. “We send commands to the real hand and the simulated hand to see if they behave differently,” explains Hsu. “If they do, we update our model to make them match.” The closer the simulation matches, the more useful it will be to the HAPTIX teams. The end goal is, of course, to get everything working on the real hardware, but an accurate and detailed simulator is critical to the development of effective software.

The first generation of the DEKA arm recently arrived at OSRF for validation testing, and the complete hardware is expected before the end of the year. OSRF has been steadily releasing a series of stable versions of the HAPTIX simulator, and as the fidelity of simulated position holding, force control and response, and other dynamics are verified on the arm over the next few months, OSRF will continue upgrading the simulation software to make sure that the HAPTIX teams have all of the tools that they need to progress as quickly and efficiently as possible.

By early 2017, Phase 1 of HAPTIX will be complete, and the software and hardware components that prove to be the most successful will continue into Phase 2, the end goal of which is a complete, functional HAPTIX system. DARPA is hoping that take-home trials of such a system will happen by 2019, and that soon after, any amputee who needs one will be able to benefit from a prosthetic hand that acts (and feels) just like the real thing.

ROS at the Intel Developer Forum

Next week is the Intel Developer Forum in San Francisco.

If you know anything about ROS and robots, then by now you know about the integration between ROS and Intel’s RealSense Camera.

Given this relationship, you can expect to see and hear a lot about ROS next week at IDF.

We encourage you to check out these sessions next week in San Francisco:

Michael Ferguson (Fetch Robotics): Accelerating Your Robotics Startup with ROS

Michael Ferguson spent a year as a software engineer at Willow Garage, helping rewrite the ROS calibration system, among other projects. In 2013, he co-founded Unbounded Robotics, and is currently the CTO of Fetch Robotics. At Fetch, Michael is one of the primary people responsible for making sure that Fetch’s robots reliably fetch things. Mike’s ROSCon talk is about how to effectively use ROS as an integral part of your robotics business, including best practices, potential issues to avoid, and how you should handle open source and intellectual property.

Because of how ROS works, much of your software development (commercial or otherwise) is dependent on many external packages. These packages are constantly being changed for the better — and sometimes for the worse — at unpredictable intervals that are completely out of your control. Using continuous integration, consisting of systems that can handle automated builds, testing, and deployment, can help you catch new problems as early as possible. Michael also shares that a useful way to avoid new problems is to not immediately switch over to new software as soon as they are available: instead, stick with long-term support releases, such as Ubuntu 14.04 and ROS Indigo.

While the foundation of ROS is built on open source, using ROS doesn’t mean that all of the software magic that you create for your robotics company has to be given away for free. ROS supports many different kinds of licenses, some of which your lawyers will be more happy with than others, but there are enough options with enough flexibility that it doesn’t have to be an issue. Using Fetch Robotics as an example, Mike discusses what components of ROS his company uses in their commercial products, including ROS Navigation and MoveIt. With these established packages as a base, Fetch was able to quickly put together operational demos, and then iterate on an operating platform by developing custom plugins optimized for their specific use cases.

When considering how to use ROS as part of your company, it’s important to look closely at the packages you decide to incorporate, to make sure that they have a friendly license, good documentation, recent updates, built-in tests, and a standardized interface. Keeping track of all of this will make your startup life easier in the long run. As long as you’re careful, relying on ROS can make your company more agile, more productive, and ready to make a whole bunch of money off of the future of robotics.
~~~~~~~~~~~~~~~~~~~~

Next up: Ryan Gariepy (Clearpath Robotics)

ROSCon 2016: Proposal deadline July 8th and venue information

With just over 3 months to go before ROSCon 2016, we have some important announcements:

* The deadline for submitting presentation proposals is July 8, 2016. If you want to present your work at ROSCon this year, make sure to submit your proposal before the deadline: http://roscon.ros.org/2016/#call-for-proposals.
* The conference will be held at the Conrad Seoul. Hotel rooms at the discounted conference rate are limited! Reserve your room today. http://roscon.ros.org/2016/#location. Also listed are some options for child care during the conference, which we hope will be helpful for attendees traveling with families.
* Registration will open in a couple of weeks: http://roscon.ros.org/2016/#important-dates.

We can’t put on ROSCon without the support of our generous sponsors, who now include Clearpath Robotics, Southwest Research Institute, GaiTech, and ARM!
http://roscon.ros.org/2016/#sponsors

We’d like to especially thank our Platinum and Gold Sponsors: Fetch Robotics, Clearpath Robotics, Intel, Southwest Research Institute, and Yujin Robot.