ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
0

ros2 and ignition roadmap

asked 2020-05-07 10:10:34 -0500

johnconn gravatar image

What's the roadmap look like for ros2 x ignition? I see that ignition can be built from source for ros2, I also see that the demos directory of the repo is a TODO. Is all the functionality I love in Gazebo with ros2 in ignition as well?

edit retag flag offensive close merge delete

1 Answer

Sort by » oldest newest most voted
1

answered 2020-05-07 10:36:02 -0500

updated 2020-05-08 10:53:36 -0500

What's the roadmap look like for ros2 x ignition?

  • Dashing: You can compile ros_ign from source, for either Blueprint or Citadel.
  • Eloquent: ros_ign may compile from source but we're not testing it currently.
  • Foxy: We'll release ros_ignwith Citadel support into http://packages.ros.org shortly after Foxy's release

Is all the functionality I love in Gazebo with ros2 in ignition as well?

Ignition and Gazebo have a different set of features, see the feature comparison.

I also see that the demos directory of the repo is a TODO

Here are the Dashing demos.

Update

will ignition and ROS2 have 1:1 mappings of versions?

As it's always been the case for several external dependencies, including Gazebo, the official version of Ignition for each ROS 2 distro will be defined in REP-2000 starting from Foxy (Ignition Citadel 🔥🏰).

We've also always supported non-official Gazebo-ROS combinations through http://packages.osrfoundation.org/ , as documented on Which combination of ROS/Gazebo versions to use. We plan on keeping doing the same for Ignition.

I’m not used to having the simulators be named vs version numbers.

For what it's worth, like ROS, we're choosing names alphabetically, so it should be easy to know version's relative ages.

wondering if we should really be numbering both ignition and ROS2 versions alongside a name

Ignition is not a monolithic application like Gazebo, it's a collection of libraries. Each Ignition library has its own numbered version following semantic versioning. The named releases are just collections of major versions of each library that are guaranteed to work together. The same version of a library can be in multiple collections (i.e. ign-math6 is used on both Blueprint and Citadel), but one collection can't have more than one version of each library. We think that, the same way as ROS distros, naming each collection makes it easier to talk about versions for various packages that are guaranteed to work together.

This is documented on Ignition Releases and Ignition Citadel libraries.

edit flag offensive delete link more

Comments

Followup: will ignition and ROS2 have 1:1 mappings of versions? I’m not used to having the simulators be named vs version numbers. Its totally fair to have names and gets me wondering if we should really be numbering both ignition and ROS2 versions alongside a name.

stevemacenski gravatar image stevemacenski  ( 2020-05-08 01:54:00 -0500 )edit

Updated answer addressing your questions.

chapulina gravatar image chapulina  ( 2020-05-08 10:53:58 -0500 )edit

Question Tools

2 followers

Stats

Asked: 2020-05-07 10:10:34 -0500

Seen: 404 times

Last updated: May 08 '20