The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
What's the roadmap look like for ros2 x ignition?
ros_ign may compile from source but we're not testing it currently.ros_ign with Citadel support into http://packages.ros.org shortly after Foxy's releaseIs 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
Before making the Foxy release we'd like to port the demos as well. Contributions most welcome š
| | 2 | No.2 Revision |
What's the roadmap look like for ros2 x ignition?
ros_ign may compile from source but we're not testing it currently.ros_ign with Citadel support into http://packages.ros.org shortly after Foxy's releaseIs 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
Before making Here are the Foxy release we'd like to port the demos as well. Contributions most welcome šDashing demos.
| | 3 | No.3 Revision |
What's the roadmap look like for ros2 x ignition?
ros_ign may compile from source but we're not testing it currently.ros_ign with Citadel support into http://packages.ros.org shortly after Foxy's releaseIs 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.
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.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.