December 13, 2018
Special Collection on Open Source Robotics

@fmrico wrote:

Dear ROS community,

Some members of the ROS community are publishing a special issue of the International Journal of Advanced Robotic Systems (IJARS, IF: 0.952) entitled “Open Source Robotics”. I hope this is of special interest to many people of our community.

Special Collection on Open Source Robotics

Focus:
Currently we are living a revolution in Robotics that is closely related to the use of Open Source Software and Hardware. The creation of communities around areas of interest in Robotics provides a development model that promotes the diffusion and standardization of technologies. The establishment of such standards provides an effective and convenient method to disseminate implementations of algorithms and models, which otherwise could not be carried out, which allow the reproduction and comparison of results, advancing technology and science in Robotics. This philosophy of free knowledge is emerging from academic environments to be adopted by the industry, as a way to optimize their development and business models. The emergence of community makers, 3D printing, the emergence of Open Source standards such as ROS or YARP, or initiatives such as ROS Industrial are a revolution in the way we approach the development of robotic technology.

Novel theoretical approaches or practical applications of all aspects involving open source robotics are welcomed. Contributions shall contribute to the understanding of the value of an open source approach.

Topics:

  • Open Source middleware and frameworks for Robotics
  • Open Source in education
  • Open Source projects
  • Open Standards for Robotics
  • Description of Open Source Industrial approaches
  • Open Hardware
  • Development models based on Open Source

Guest editors:

  • Dr. Francisco Martín Rico - Rey Juan Carlos University, Spain (francisco.rico@urjc.es)
  • Dr. Carlos Hernandez Corbato - TU Delft Robotics Institute, Netherlands (c.h.corbato@tudelft.nl)
  • MSc. Gijs van der Hoorn - TU Delft Robotics Institute, Netherlands (G.A.vanderHoorn@tudelft.nl)
  • MSc. Ir. Sam Pfeiffer - University of Technology, Sydney, Australia (sammypfeiffer@gmail.com)
  • Dr. Juan González Gómez - Rey Juan Carlos University, Spain (juan.gonzalez.gomez@urjc.es)

Submission deadline: February 28, 2019

Links:

Best,
Francisco

Posts: 4

Participants: 2

Read full topic

by @fmrico Francisco Martín Rico on December 13, 2018 07:00 AM

December 12, 2018
New Packages for Kinetic 2018-12-12

@tfoote wrote:

We’re happy to announce 35 new packages and 81 updated packages for Kinetic Kame. Full details are below.

Thank you to everyone who has helped make these packages available. Your efforts are greatly appreciated.

Package Updates for kinetic

Added Packages [35]:

  • ros-kinetic-costmap-queue: 0.2.2-0
  • ros-kinetic-dataspeed-ulc: 0.0.3-0
  • ros-kinetic-dataspeed-ulc-can: 0.0.3-0
  • ros-kinetic-dataspeed-ulc-msgs: 0.0.3-0
  • ros-kinetic-dlux-global-planner: 0.2.2-0
  • ros-kinetic-dlux-plugins: 0.2.2-0
  • ros-kinetic-dockeros: 1.0.2-0
  • ros-kinetic-dwb-critics: 0.2.2-0
  • ros-kinetic-dwb-local-planner: 0.2.2-0
  • ros-kinetic-dwb-msgs: 0.2.2-0
  • ros-kinetic-dwb-plugins: 0.2.2-0
  • ros-kinetic-global-planner-tests: 0.2.2-0
  • ros-kinetic-locomotor: 0.2.2-0
  • ros-kinetic-locomotor-msgs: 0.2.2-0
  • ros-kinetic-locomove-base: 0.2.2-0
  • ros-kinetic-nav-2d-msgs: 0.2.2-0
  • ros-kinetic-nav-2d-utils: 0.2.2-0
  • ros-kinetic-nav-core-adapter: 0.2.2-0
  • ros-kinetic-nav-core2: 0.2.2-0
  • ros-kinetic-nav-grid: 0.2.2-0
  • ros-kinetic-nav-grid-iterators: 0.2.2-0
  • ros-kinetic-nav-grid-pub-sub: 0.2.2-0
  • ros-kinetic-pilz-robot-programming: 0.3.0-0
  • ros-kinetic-robot-navigation: 0.2.2-0
  • ros-kinetic-uuv-assistants: 0.6.2-0
  • ros-kinetic-uuv-auv-control-allocator: 0.6.2-0
  • ros-kinetic-uuv-control-msgs: 0.6.2-0
  • ros-kinetic-uuv-cpc-sensor: 0.3.0-0
  • ros-kinetic-uuv-gazebo: 0.6.2-0
  • ros-kinetic-uuv-gazebo-ros-plugins-msgs: 0.6.2-0
  • ros-kinetic-uuv-plume-msgs: 0.3.0-0
  • ros-kinetic-uuv-plume-simulator: 0.3.0-0
  • ros-kinetic-uuv-sensor-plugins-ros-msgs: 0.6.1-0
  • ros-kinetic-uuv-sensor-ros-plugins-msgs: 0.6.2-0
  • ros-kinetic-uuv-world-ros-plugins-msgs: 0.6.2-0

Updated Packages [81]:

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 Rössler
  • Alexander Tiderko
  • AutonomouStuff Software Development Team
  • AutonomouStuff Software Team
  • David V. Lu!!
  • Ioan Sucan
  • Isaac I. Y. Saito
  • Jack Kilian
  • Josh Whitley
  • Kevin Hallenbeck
  • Konstantin Schauwecker
  • Kris Kozak
  • Krzysztof Żurad
  • Marc Alban
  • Michael Ferguson
  • Michele Colledanchise
  • Micho Radovnikovich
  • Musa Morena Marcusso Manhaes
  • P. J. Reed
  • Pilz GmbH and Co. KG
  • Ralf Kaestner
  • Wolfgang Merkt
  • ct2034

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on December 12, 2018 09:40 PM

New Packages for Indigo 2018-12-12

@tfoote wrote:

We’re happy to announce 32 new packages and 58 updated packages for Indigo Igloo. Full details are below.

Thank you to everyone who has helped make these packages available. Your efforts are greatly appreciated.

Package Updates for indigo

Added Packages [32]:

  • ros-indigo-behaviortree-cpp: 2.4.1-0
  • ros-indigo-costmap-queue: 0.2.2-0
  • ros-indigo-dataspeed-ulc: 0.0.3-0
  • ros-indigo-dataspeed-ulc-can: 0.0.3-0
  • ros-indigo-dataspeed-ulc-msgs: 0.0.3-0
  • ros-indigo-dlux-global-planner: 0.2.2-0
  • ros-indigo-dlux-plugins: 0.2.2-0
  • ros-indigo-dwb-critics: 0.2.2-0
  • ros-indigo-dwb-local-planner: 0.2.2-0
  • ros-indigo-dwb-msgs: 0.2.2-0
  • ros-indigo-dwb-plugins: 0.2.2-0
  • ros-indigo-flexbe-behavior-engine: 1.1.0-0
  • ros-indigo-flexbe-core: 1.1.0-0
  • ros-indigo-flexbe-input: 1.1.0-0
  • ros-indigo-flexbe-mirror: 1.1.0-0
  • ros-indigo-flexbe-msgs: 1.1.0-0
  • ros-indigo-flexbe-onboard: 1.1.0-0
  • ros-indigo-flexbe-states: 1.1.0-0
  • ros-indigo-flexbe-testing: 1.1.0-0
  • ros-indigo-flexbe-widget: 1.1.0-0
  • ros-indigo-global-planner-tests: 0.2.2-0
  • ros-indigo-locomotor: 0.2.2-0
  • ros-indigo-locomotor-msgs: 0.2.2-0
  • ros-indigo-locomove-base: 0.2.2-0
  • ros-indigo-nav-2d-msgs: 0.2.2-0
  • ros-indigo-nav-2d-utils: 0.2.2-0
  • ros-indigo-nav-core-adapter: 0.2.2-0
  • ros-indigo-nav-core2: 0.2.2-0
  • ros-indigo-nav-grid: 0.2.2-0
  • ros-indigo-nav-grid-iterators: 0.2.2-0
  • ros-indigo-nav-grid-pub-sub: 0.2.2-0
  • ros-indigo-robot-navigation: 0.2.2-0

Updated Packages [58]:

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
  • AutonomouStuff Software Development Team
  • AutonomouStuff Software Team
  • David V. Lu!!
  • Isaac I. Y. Saito
  • Josh Whitley
  • Kevin Hallenbeck
  • Kris Kozak
  • Marc Alban
  • Michael Ferguson
  • Michele Colledanchise
  • Micho Radovnikovich
  • P. J. Reed
  • Philipp Schillinger

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on December 12, 2018 09:39 PM

Regarding Migration of Launch File from ROS1 -> ROS2

@SR9591 wrote:

Hi,

Currently, I am migrating launch XML to python (ROS1 -> ROS2). I can handle <node> with python generated API but I am not understanding, How can I replace <group>, <test>, <rosparam> and other parameter from xml.launch to python file.

Please guide me to migrate launch file.

Thanks.

Posts: 1

Participants: 1

Read full topic

by @SR9591 Gabbar on December 12, 2018 04:32 AM

December 10, 2018
ROS Crystal Clemmys t-shirts available until Dec 31st

@nuclearsandwich wrote:

ROS Crystal Clemmys t-shirts available until Dec 31st

With each release of ROS we have a tradition of having a mascot and making t-shirts. ROS Crystal Clemmys is coming out soon! To let you show your excitement for ROS and support this tradition, we have setup a Teespring Campaign which should cover both the US and EU, and can ship worldwide.

ROS Crystal Clemmys campaign on Teespring

The campaign will run through 31 December 2018 be sure to order yours before you ring in the New Year!
Rush shipping does not appear to be available for all different shirts which means you may not be able to get yours before the Christmas holiday, even with rush shipping.

Since this is the first public announcement, here’s the full graphic for Crystal Clemmys.

Thanks to everyone who is working hard to get Crystal release-ready. You can help us out! Check out the call for testing here: ROS 2 Crystal Clemmys call for testing and package releases

Posts: 5

Participants: 4

Read full topic

by @nuclearsandwich Steven! Ragnarök on December 10, 2018 11:00 PM

Observations from the first RIA Robotic Grinding and Finishing Conference hosted by 3M

A recent conference brought together end-users, solution providers, OEMs and researchers to discuss the latest in robotic applications around grinding and surface finishing (https://www.robotics.org/robotic-grinding-and-finishing-conference). It was an eye opening event and the first of its kind to focus on automation for these types of processes. While there are many conferences on automation, the topics of surface grinding and finishing are rarely at the top of the topic areas. This event also underscored how there are few specialists in this area.

Day 1

The first panel of note discussed whether to automate these operations and how to understand if there was benefit in attacking what is typically considered manual work. There were a number of assumptions that went into the approach, but we learned quickly there was a lot of interest as this was an audience that has historically struggled with legacy approaches and hardware in automating such operations and processes.

 Charles Gales of Weldon Solutions Presents on Automating of Complimentary Processes as a means to introduce surface finishing to your operations.

Charles Gales of Weldon Solutions Presents on Automating of Complimentary Processes as a means to introduce surface finishing to your operations.

The sessions’ two main points were: automate as you can, such as complimentary processes (capture more work with that automation investment), understand your process and burden, and be cognizant of the fact of how you do it a certain way manually today doesn’t mean that will be the most optimal way to execute your process robotically.

Force control was the next panel that gained a lot of attention. Obviously, force/torque sensing in a number of areas has become an area of active robotic interest in traditional automation applications and of course applicable in surface processing. There were introductory conversations about the types of force control, such as the pros and cons of passive versus active. A number of compelling applications leveraging active force control were featured. ATI, PushCorp and FerRobotics all offer approaches to meet a wide array of client needs and applications.

 ATI, PushCorp, and Fer Robotics participate on a panel discussing force control in surface finishing and grinding applications.

ATI, PushCorp, and Fer Robotics participate on a panel discussing force control in surface finishing and grinding applications.

Near the end of the day was an additional panel around DIY Integration, which was incredibly eye opening and generated a lot of conversation. The panelists – Brandon Berth, from Kohler, Matt Morrison, from Marshalltown, and Scott Harms, from MetalQuest – shared interesting stories about making progress on their automation journey through trial and error and developing their own in-house skills to manage deployments. These were stories that relied on a commitment and a process; starting small, developing the skills and gradually moving to more complex applications.

Day 2

The second day started off with Kuka presenting on enabling small and medium enterprises to take on grinding application development. The key tool they demonstrated was the ability in their simulation ecosystem to empirically model the sanding process and highlight the path and planned surface contact and subsequent material removal. This provided a very compelling visual assessment for the grinding process as it is being developed in their off-line environment.

The next two presentations were very interesting as they showcased two competent integrators in the space. What was evident, even though their core expertise varied, was that they relied heavily on the teach pendant and skilled online programmers to really bring the process over the finish line. Much like the prior presentations, or the presentations by the DIY’ers, here again we were relying on skilled technicians and industrial robot programmers to complete the implementation of the automation. The level of variation management is limited due to the nature of the deployments. Also, for some of these applications, it may not be realistic to enable too much flexibility as the broad array of complex surface finishing applications was impressive.

I had the opportunity to talk about ROS-Industrial and the work that has been going on in surface finishing using perception and advanced path planning and process planning techniques. This space has talked about path planners (Trajopt!) and applications (Robotic Blending, A5 and undergrads using these tools), so I won’t get into those details here, but two thing are evident. There is a need to change how we approach these processes if we want to truly attack these types of applications. We can’t rely on skilled robot techs to have a teach pendant in-hand. Not every company can grow that expertise in-house over years. Even if they do, how do they scale beyond their core facilities?

 Panel on advances in surface finishing moderated by Jay Douglass of the ARM Institute

Panel on advances in surface finishing moderated by Jay Douglass of the ARM Institute

I was asked about the capabilities in the blending and A5 videos and how ready they are to go into anyone’s plant. That is a great question, and I would be asking that, too, if I was in that seat, as I did when I was on the industry side. We are working on that, hence we were there with the ARM Institute and all the interest in the surface finishing topic calls, and continued development of A5, and an additional milestone upcoming for Robotic Blending. That is why there is a ROS-I Consortium and a ROSIN initiative in the EU. We will continue to make the modules more robust and build out application examples that can be leveraged and molded into end-user capability. In the meantime we hope to entice integrator and solution providers to embrace a ROS-based software approach along with our OEM partners. If we work together we can build out reusable components that meet this need, in this greatly underserved area. The exciting part is there is a lot we can do, and it doesn’t have to that far away! It was great to see 3M, our hosts, showcase a ROS-based demonstration and do their part to introduce the concepts and how they could lend a hand in solution development. We are excited to have 3M as such an engaged partner and hope together we can keep growing the open-source tool revolution! #GoROS

by Matthew Robinson on December 10, 2018 10:35 PM

Robot_navigation stack released

@DLu wrote:

tl;dr: Check out https://github.com/locusrobotics/robot_navigation

Greetings ROS-Users!
I’d like to announce the robot_navigation stack’s latest release. This includes everything I talked about in my ROSCon2018 Talk [slides]. This includes

  • The new nav_core2 interfaces
  • The DWB Local Planner (introduced last year)
  • The Dlux Global Planner
  • Locomotor - the path planning coordination engine to replace move_base
  • Backwards compatible adapters for nav_core interfaces

The overall goal of the stack is to create a new revision of the “classic” navigation stack but with cleaner interfaces to make it easier for developers to create custom 2.5D navigation algorithms that fit their individual contexts.

Additional things that I’m proud of:

In the near future (for some definition of near), we’ll be releasing new refactored packages implementing the layered costmap and map server, at which point we’ll be able to explore converting the whole stack to ROS2.

Source is available here: https://github.com/locusrobotics/robot_navigation
Binaries will be available for Indigo, Kinetic, Lunar and Melodic with the next syncs.
The main documentation is in Github READMEs, but you can also check out the wiki and Code API

Posts: 1

Participants: 1

Read full topic

by @DLu David!! on December 10, 2018 03:16 PM

December 07, 2018
New Release of ROS Qt Creator 4.8 RC on Xenial and Bionic

We are pleased to announce the release of the ROS Qt Creator Plug-in for Qt Creator 4.8 RC on Xenial and Bionic. The ROS Qt Creator Plug-in creates a centralized location for ROS tools to increase efficiency and simplify tasks.

 Picture obtained from  Qt Blog

Picture obtained from Qt Blog

Highlights:

  • Qt Creator 4.8 introduces several new rich features and improvements to existing capabilities.
    • Generic Programming Language Support (Python Support!)
      • To use this feature, you must enable the Language Support Plugin
    • C++
      • Compilation Database Projects!
      • Clang Format Based Indentation!
      • Cppcheck Diagnostics!
      • Simultaneously debugging one or more executables!
  • ROS Plug-in introducint a few new features and bug fixes
    • Upgraded to Qt Creator 4.8
    • Added catkin_test_results run step
    • Added ROS Settings Page to configure default settings
    • Bug Fixes
      • Issue #284 Package Wizard caused Qt Creator to crash if using when a ROS project is not loaded.
      • Issue #289 Clicking Help caused Qt Creator to crash
qt-creator-ros-settings-page.png

by Levi Armstrong on December 07, 2018 01:50 AM

December 04, 2018
Call for TIAGo loan for the 1st SciRoc Challenge

PAL Robotics is opening a Call for loan of 6 TIAGo Steel and 4 TIAGo Iron robots to teams who want to participate in the 1st ERL SciRoc Challenge. As SciRoc Platinum Sponsors, we offer the possibility of loaning a TIAGo to make it easier for teams to participate in this new and challenging robotics competition.

Breaking news! Teams showing outstanding expertise and innovative developments will have the chance to receive one of the TIAGo Steel and one of the TIAGo Iron robots for free. The application deadline is on Thursday 20th December at 20:00 CET.

Find the full TIAGo loan conditions and application procedure here.

The SciRoc Challenge: robots assisting in Smart Cities

The first SciRoc Challenge merges tasks that robots have to accomplish in the different ERL Leagues: Consumer, Professional, and Emergency. These selected tasks are integrated into a Smart Shopping Mall, where service robots like TIAGo help customers and create an innovative shopping experience. In fact, it is highly recommendable for SciRoc participating teams to take part in an ERL Consumer Tournament as a previous training. The 1st SciRoc Challenge will take place in Milton Keynes (UK) from September 16th to September 22nd, 2019.

Read more about the SciRoc Challenge here!

TIAGo-IRON-STEEL-SCIROC-CHALLENGE-robotics-competition-robocup

TIAGo Iron and TIAGo Steel, the two robotic platforms for loaning to participate at the SciRoc Challenge.

TIAGo for robotics competitions

TIAGo has proven its robustness and reliability in several international competitions – see the RoboCup@Home, the ERL-SR, the WRS, and the MMH. Its modularity and expansion opportunities are two features that teams highly value in competitions.

Besides the onboard sensors and equipment, teams can hack TIAGo by connecting devices to expand its capabilities even more, from extra microphones to AI-devices or extra cameras. This way, teams could adjust TIAGo’s skills to their specific needs and goals. TIAGo is 100% ROS based: remember that it has a public simulation model online along with a comprehensive set of tutorials that you can try even if you don’t have the robot.

The main difference between TIAGo Iron and Steel models is whether it has the 7-DoF arm. TIAGo Iron provides navigation, perception and Human-Robot Interaction skills. The Steel model adds to that list the grasping and manipulation skills in different heights – it is even able to reach the floor.

Steps to participate

Teams can apply to both types, TIAGo Steel and Iron, but can eventually receive only one. The first step to apply is to accomplish with a set of requirements, and email tiago@pal-robotics.com including the following documentation:

  • Contact details for the team leader. University teams must also supply contact details for an academic supervisor.
  • A one-page executive summary of the application.
  • The team’s motivations behind their application.
  • One-page CVs of the team members.
  • A detailed description of the team’s specialisms and expertise, as well as past research and other achievements (limited to two pages).
  • Videos of past achievements (with real robots or simulators).
  • List of target episodes of the SciRoc challenge (the more episodes the more potential value the application will have).
  • Detailed descriptions of how the teams plan to use the TIAGo to fulfill the tasks in each selected episode.
  • Teams might be requested further documentation in case of need.

By January 10th, the awarded teams will be announced, and then the following steps will take place. Find here the full details on the application procedure.

We strongly encourage teams to participate and apply for having a TIAGo to compete! Participating in robotics tournaments like the SciRoc Challenge or ERL triggers knowledge, reinforces collaboration between teams and enhances the whole robotics field. Good luck to all candidates!

The post Call for TIAGo loan for the 1st SciRoc Challenge appeared first on PAL Robotics Blog.

by Judith Viladomat on December 04, 2018 10:21 AM

December 03, 2018
Announcing PhysX SDK 4.0, an Open-Source Physics Engine

@lentinjoseph wrote:

Posts: 3

Participants: 3

Read full topic

by @lentinjoseph Lentin Joseph on December 03, 2018 08:16 PM

November 30, 2018
"Open robotics meets the open road." - DECODED Show S3E01

@lentinjoseph wrote:

We learn about robotics in the factory with BMW and SwRI, curators of ROS-Industrial an open-source robotics project. Our journey starts in San Antonio Texas where we meet with Matt Robinson from SwRI and look at robots in the research laboratory. Then open-source takes to the open road as we travel to Germany to look at how BMW is innovating in logistics using smart transport robots in their production facilities.

Featuring
Matt Robinson - PM for ROS-Industrial at SwRI


https://www.swri.org/

Martin Bauer - Feature Team Lead - ATS at BMWGroup
https://www.bmwgroup.com/

Posts: 1

Participants: 1

Read full topic

by @lentinjoseph Lentin Joseph on November 30, 2018 04:23 PM

A ROS-Industrial Collaboration with Microsoft and BMW

ROS-Industrial recently had the opportunity to collaborate with Microsoft, BMW and Open Robotics on an automation solution that was featured in Season 3 of the Decoded show on YouTube. This enabled the ROS-I Consortium to realize sustainable gains on the team’s vision for greater efficiency and visibility with respect to logistics and material management challenges in assembly plants.

Mobile Robot.png

BMW has set forth a vision where they break down the barriers between the historical automation paradigms and the challenges with interacting with the largely manual operations of their ever-increasing high-mix assembly operations. Historically, materials are delivered to the line for human operators to consume and exact quantities and status are lost at that point of consumption. The idea is to leverage intelligent autonomous operation to give better visibility to what is where, while leveraging cloud technologies to create a tighter loop and connection to the order delivery systems. The goal is to enable a leaner operational buffer within the workflow, reducing carried inventory and driving greater efficiency.

This is where Microsoft came into the picture, with their Azure solutions and client support team to do rapid development sprints to enable tighter coupling between their SAP work order environment to the “to-be deployed” autonomous robotic fleet.

BMW has built a home-grown start transport robot that runs on the same battery used in the i3 model car they produce. However, there needed to be coordination of these assets over the long term with a richer simulation environment as the platform’s capability increased. This is where the Microsoft team came to deliver.

Close Up.png

Originally, the Southwest Research Institute (SwRI) ROS-I team support was around navigation and evaluation of Gazebo in manufacturing environments supporting many mobile robots. It became clear as the Microsoft team got to work that Gazebo would not support spinning up multiple mobile robots in one instance. In fact, due to how Gazebo is structured, even a handful of robots brought Gazebo processing to a crawl. This led to the implementation of Argos, an open-source simulator that also has the capability to include physics as the scale BMW was interested in. A container strategy was developed and, in the end, the ROS-I team ended up learning quite a bit from the Microsoft team through the week-long development hack on SwRI’s campus. This development week really furthered the understanding of capability with regard to richer simulation capabilities, including the physics, which supports the ROS-I vision of tighter process performance and management of non-rigid bodies within the planning cycle.

As things got going in Germany, as the Decoded episode shows, the Microsoft team worked closely with BMW’s ROS and Manufacturing Execution System (MES) developers, tightly coupling the SAP functionality along with the fleet management and navigation tuning functionality that was required along with the Argos implementation. In the end, this led to a functional, if not sustainable, solution for the BMW team as they continued to refine the performance of the specific ROS-based robot, leveraging the Azure environment to assure SAP to simulation, to robot action within the Azure platform.

VPLogistics.png

We hope those who watch this Decoded episode agree this demonstrates that collaborations between for-profit entities such as Microsoft, and nonprofits – such as SwRI, Open Robotics and Fraunhofer IPA, as well as open-source projects such as ROS-I – can enable end-users such as BMW to create their own sustainable, high performing solutions. We believe the open-source contributions will enable others to leverage the development and hopefully expand the capability. This idea of a pre-competitive foundation that enables interoperability and flexibility without generating silos is key if we are to move the ball forward with respect to operational efficiency gains at the scale we need.

As we have seen in recent months, robotics development and IT are entering a new phase, where more teams and individuals can grasp their own destiny and ROS-Industrial is excited to be a part of that journey!

Thanks to Microsoft and BMW as well as the Decoded team for making this project possible.

by Matthew Robinson on November 30, 2018 12:44 AM

November 28, 2018
New Packages for Kinetic 2018-11-27

@tfoote wrote:

We’re happy to announce 20 new packages and 45 updated packages for Kinetic. Thank you to everyone who helped make this possible, including maintainers and contributors. Full details are below.

Package Updates for kinetic

Added Packages [20]:

Updated Packages [45]:

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:

  • AWS RoboMaker
  • AutonomouStuff Software Development Team
  • AutonomouStuff Software Team
  • Dave Coleman
  • Davide Faconti
  • Franka Emika GmbH
  • Jonathan Hechtbauer
  • Jorge Santos
  • Koji Terada
  • Konstantin Schauwecker
  • Marc Alban
  • Max Schwarz
  • Michele Colledanchise
  • Mike Lautman
  • Sebastian Pütz
  • Tokyo Opensource Robotics Kyokai (TORK) Developer Team
  • Tully Foote
  • Vincent Rabaud
  • Vladimir Ermakov
  • shi

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on November 28, 2018 12:40 AM

November 27, 2018
Number of ROS users?

@OpenR2 wrote:

I am putting together a presentation for our project. I know that I have a special interest subgroup that I am trying to bring ROS to that has 5000 members. Are there any numbers that can be shared on the number of folks using ROS in general that we could include in the presentation?

Posts: 7

Participants: 5

Read full topic

by @OpenR2 Robert Jackson on November 27, 2018 09:02 PM

JetBrains published guidelines on how to make ROS and CLion work together

@mch wrote:

https://www.jetbrains.com/help/clion/2018.3/ros-setup-tutorial.html

From my experience I can strongly recommend CLion (https://www.jetbrains.com/clion/download/#section=linux) as a developer dream IDE for C/C++/Python. It’s very convenient and boosts your productivity a lot.

Posts: 3

Participants: 3

Read full topic

by @mch on November 27, 2018 08:34 PM

ROS 2 D Name Brainstorming

@nuclearsandwich wrote:

ROS 2 Crystal Clemmys will be released soon. That means it’s time to start brainstorming the following ROS 2 release: D Turtle.

Existing ROS 2 names and codenames:

  • Ardent Apalone - ardent
  • Bouncy Bolson - bouncy
  • Crystal Clemmys - crystal

Existing ROS 1 names and codenames:

  • Boxturtle - boxturtle
  • C Turtle - cturtle
  • Diamondback - diamondback
  • Electric Emys - electric
  • Fuerte - fuerte
  • Groovy Galapagos - groovy
  • Hydro Medusa - hydro
  • Indigo Igloo - indigo
  • Jade Turtle - jade
  • Kinetic Kame - kinetic
  • Lunar Loggerhead - lunar
  • Melodic Morenia - melodic
  • Noetic Ninjemys - noetic

Here are some links to turtle species to get us started.
http://www.chelonia.org/byspecies.htm#D
https://en.wikipedia.org/wiki/Category:Turtle_genera
https://en.wikipedia.org/wiki/Category:Prehistoric_turtle_genera

Please share your suggestions and comments.

There are no rules to this process so be creative.

Posts: 37

Participants: 31

Read full topic

by @nuclearsandwich Steven! Ragnarök on November 27, 2018 04:03 PM

New packages for Lunar 2018-11-27

@clalancette wrote:

We’re happy to announce the next update for ROS Lunar. We have 2 new packages as well as 55 updated packages.

As always, thanks to all of the maintainers and contributors who help make these updates possible!

Full details are below.

Package Updates for lunar

Added Packages [2]:

  • ros-lunar-novatel-msgs: 1.1.0-0
  • ros-lunar-novatel-span-driver: 1.1.0-0

Updated Packages [55]:

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:

  • Davide Faconti
  • Ioan Sucan
  • Jorge Santos
  • Koji Terada
  • Konstantin Schauwecker
  • Kris Kozak
  • Marc Alban
  • Max Schwarz
  • Mike Purvis
  • P. J. Reed
  • Sebastian Pütz
  • Tully Foote
  • Vincent Rabaud
  • Vladimir Ermakov

Posts: 1

Participants: 1

Read full topic

by @clalancette Chris on November 27, 2018 02:15 PM

New packages for Melodic 2018-11-27

@clalancette wrote:

We’re happy to announce the next update for ROS Melodic. We have 18 new packages as well as 56 updated packages.

As always, thanks to all of the maintainers and contributors who help make these updates possible!

Full details are below.

Package Updates for melodic

Added Packages [18]:

Updated Packages [56]:

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:

  • Dave Coleman
  • Davide Faconti
  • Dirk Thomas
  • Ioan Sucan
  • Jorge Santos
  • Kei Okada
  • Koji Terada
  • Konstantin Schauwecker
  • Kris Kozak
  • Marc Alban
  • Max Schwarz
  • Mike Lautman
  • Mike Purvis
  • P. J. Reed
  • Robert Haschke
  • Ryohei Ueda
  • Sebastian Pütz
  • Tokyo Opensource Robotics Kyokai (TORK) Developer Team
  • Tully Foote
  • Vincent Rabaud
  • Vladimir Ermakov
  • YoheiKakiuchi

Posts: 1

Participants: 1

Read full topic

by @clalancette Chris on November 27, 2018 02:03 PM

Olin Robotics Lab Robotic Tractor

@ROS-A wrote:

Big thanks to Olin Robotics Lab and their work on a robotic tractor.
https://github.com/olinrobotics/tractor_sim Learn more about their project here: https://github.com/olinrobotics/gravl/wiki/Kubo:-Overview

ROS Agriculture community meeting is tomorrow night. Tuesday, Nov 20 from 6-7pm Pacific Time. Web meeting link: http://meet.ros-a.org/

If you are interested in using ROS in Agriculture join the Slack group. Sign up on the web page (http://rosagriculture.org/)

Matt

Posts: 1

Participants: 1

Read full topic

by @ROS-A ROS Agriculture on November 27, 2018 02:50 AM

New Packages for Indigo 2018-11-16

@tfoote wrote:

We’re happy to announce the availability of 28 updated packages for Indigo. Thank you to all the maintainers and contributors who have helped make these packages available!

The full list of packages updates is below.

Package Updates for indigo

Added Packages [0]:

Updated Packages [28]:

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:

  • AutonomouStuff Software Development Team
  • AutonomouStuff Software Team
  • Davide Faconti
  • Jorge Santos
  • Koji Terada
  • Marc Alban
  • Sebastian Pütz
  • Tokyo Opensource Robotics Kyokai (TORK) Developer Team
  • Tully Foote
  • Vincent Rabaud

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on November 27, 2018 01:01 AM

ROS Node for Speech Recognition with Mozilla DeepSpeech

@RichardKelley wrote:

Hi all,

My students and I wanted to use Mozilla’s DeepSpeech model on some of our robots, so we wrote a simple node to make the model available in ROS:

Functionality is fairly limited at the moment, but we’ve been happy with our testing so far and think that the system could be useful to others looking for a simple speech recognition solution that runs offline.

We’re currently planning the next iteration of this package, and would love to hear your thoughts if you try it out.

Thanks,
Richard

Posts: 2

Participants: 2

Read full topic

by @RichardKelley Richard Kelley on November 27, 2018 12:52 AM

November 26, 2018
Check out AWS RoboMaker

@coleray wrote:

Hello all,

I’m an engineer with Amazon and we’ve been working to launch a new service called AWS RoboMaker, announced at AWS re:Invent Midnight Madness last night.

The service helps you develop, simulate, test, and deploy ROS applications. I would love to hear your feedback about the service.



Thanks,
Ray

EDIT: Fixing youtube link, adding additional video

Posts: 18

Participants: 14

Read full topic

by @coleray Ray Cole on November 26, 2018 11:34 AM

November 20, 2018
TSC Meeting Notes 2018-11-15

@gerkey wrote:

ROS 2 TSC Meeting Minutes: November 15th, 2018

  • Attendees:
    • Allison
    • Doug
    • Filipe
    • Louise, Tully, Brian, Dirk
    • Dejan
    • Matt D
    • Matt H
    • Vincent
    • Karsten
    • Seonman
  • (45 mins) Update: (Brief!) Review of ongoing work for Crystal:
    • Milestones
      • 2 - Nov 21st
        • Major API changes that will effect others (like action generators)
      • 3 - Dec 4th
        • Major feature additions (One week for testing)
    • Jump to the Crystal ticket and iterate through the items:
    • Assuming checked off items are done
    • Launch – Dirk: likely getting in for Crystal. Dropped launch in containers.
    • Rosbag – Karsten: rosbag is there. Working on read-only ROS1 bag playback
    • Web Visualization – Dirk: scope change; now focused on web visualization like rviz in the web, which isn’t really ROS 2-specific. Remove this item from the roadmap.
    • Buildfarm improvements – Dirk: upgrading Jenkins to use latest LTS complete. Snapshotting support ongoing. Incremental CI ongoing. On track.
    • IDL – Dirk: Contention with Actions. High risk on getting this done.
    • Performance Testing – Louise: Basic ping pong test targeted for integration into Jenkins, but after that we’re putting this task on hold for now.
    • Actions – Dirk: Parsing of files implemented, rcl implementation in review. Client libraries are less complete than hoped.
    • Improve MISRA compliance – Dirk: Progress made but not everything will be merged prior to release.
    • Audit memory management – Dirk: Progress made but not everything will be merged prior to release.
    • Enhanced QoS settings – Dejan: liveliness and deadlines have huge APIs not clear how to expose those APIs. Too complicated to land before QoS. Will drop from Crystal.
    • CI /testing – Dejan: replacing legacy launch. It’s an extension package so not blocking on release milestones
    • Logging – Doug: rcl pull requests under review. Expect it can target Milestone 3.
    • Rqt – Doug: good progress. Mostly plugins can target Dec 4th
    • Security – Doug: progress in discourse thread. No one currently working on threat models. Expect a PR by the end of the week.
    • ROS 1 ROS 2 migration – Doug: as done as it will be. Capture current state to make it as complete
    • Navigation – Matt H.: in integration/debug phase now. Components all running. Debugging dependencies. Targeting Milestone 3. Have dependencies for message filters and geometry message filters. Carrying patches locally. Mostly testing in simulation. Gazebo_ros_pkg missing model states to get ground truth system test. Cartographer not building at the moment; there’s been a lot of changes on the upstream project.
    • OpenEmbedded – Seonman: Expect something meaningful early next year. Move off of Crystal target.
    • Windows support – Vincent: Not working on ROS2 at the moment. Focused on ROS 1.
    • TB3 – (Pyo unable to attend) Robot is working enough in simulation for testing navigation, from above. Teleop demonstrated.
    • Image pipeline – Matt H.: some progress on that PR in review for depth processing but stalled.
    • Librealsense – Matt H.: package externally built dependency – Follow up with Tully about getting it hosted
    • Cross-compilation improvements – Filipe: add these to the Crystal ticket:
      • Provide a toolchain file and instructions
      • Example build in Docker
      • Including Python packages
  • (20 mins) Discussion & decision: New TSC members to consider (Brian)
    • Interest to join from multiple orgs. We now have information from them regarding their backgrounds and intentions but before taking action we should use this opportunity to formalize the process for admitting new members.
      • Brian to write formalized process, likely as amendment to charter.
    • Interest in having an “observer seat” from an org.
      • With meeting notes published and good transparency, anyone can already observe. Likely just additional logistical cost to add someone to the meeting. We’ll decline this option.
  • (5 mins) Old business:
    • Update: Status on ROS trademark application (Brian)
      • No update: still planning to submit application in November
    • Update: Status on DCO process for ROS 2 repos (Dirk)
      • Tested on a dummy repo: https://github.com/osrf-test-dco
      • Only discovered limitation is that edits using the web UI are not possible since such commits are not signed off
      • Plan is to to enable the checks post-Crystal release in order to not introduce additional friction that late in the release cycle
  • Maybe have one more meeting before release.

Posts: 7

Participants: 7

Read full topic

by @gerkey gerkey on November 20, 2018 10:25 PM

Introducing BehaviorTrees.CPP (who needs Finite State Machines anymore?)

@facontidavide wrote:

Dear roboticists,

I would like to share with you our new libraries that can help you greate robot Behaviors.
Behavior Trees are similar to Hierarchical Finite State Machines, but they are more intuitive and maintainable.

BehaviorTree.CPP is a C++ library to develop reactive Behavior Trees.
It is embeddable in your own node and the creation of a Bt Executer requires only few lines of codes.
Trees can be loaded at run-time without recompiling your application, since their definition is stored in a user friendly and easy to read XML format.

Read introduction and tutorials here.

Additionally, you can start playing around with the preliminary release of Groot the graphical user-interface that allows you to create. edit, monitor and replay the execution of BehaviorTrees.

Both these tools are middleware independent by design, i.e. they do not depend on ROS.

On the other hand, it is trivial to use them together with ROS using Topic, Services and Actions.

We will soon release a ROS specific example.

Cheers

Davide Faconti

Acknowledgment

This software was created as part of the project MOOD2Be, and it is developed at Eurecat.

MOOD2Be is one of the six Integrated Technical Projects (ITPs) selected from the RobMoSys first open call . It received funding from the European Union’s Horizon 2020 Research and Innovation Programme under the RobMoSys project.

Posts: 8

Participants: 6

Read full topic

by @facontidavide Davide Faconti on November 20, 2018 03:06 PM

November 19, 2018
Notes from the ROS-Industrial Consortium-Americas Training Workshop at SwRI

The ROS-I Americas consortium hosted its third training event of 2018 at Southwest Research Institute on November 13-15. The three-day workshop was led by Dr. Josh Langsfeld, Joseph Schornak, and Michael Ripperger and attended by 16 participants hailing from diverse backgrounds across academia and industry.

The curriculum was split into Basic and Advanced tracks, and alternated between slide-driven lectures and hands-on coding exercises. On Day 1, students in the Basic class were introduced to core ROS concepts like nodes, messages, services, and parameters, while the Advanced class developed a Python-enabled perception pipeline and explored introspective debugging tools.

Dinner following the Day 1 session was hosted at La Gloria in San Antonio’s Pearl district, where attendees contended with six courses of tacos and tortas.

The two classes reunited on Day 2 to develop a perception-driven planning application for a simulated robotic workcell. On Day 3 students were free to independently pursue a variety of open-ended lab exercises, including developing a more advanced pick-and-place application and adapting their programs from previous exercises to run on an actual UR5 robot.

1fb2c62c-9083-43d9-a9f8-ef61694208b2-original.jpeg

The ROS-I initiative is currently working on a migration to Melodic that will include the training exercises and curriculum for an initial unveiling in early 2019. Also under consideration for early 2019 is an introductory ROS2 advanced topic.

Please reach out to us if you have any suggestions for improvements or additions to the lectures or exercise. We really enjoyed working with you and we hope to see you again!

by Joseph Schornak on November 19, 2018 11:12 PM


Powered by the awesome: Planet