Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
[ros2] gazebo_ros_api_plugin split #779
See the table below for a proposal of a split based on what kind of entity (model / link / joint / etc) an API targets.
I also considered a split which takes into account whether an API provides access to ground truth that wouldn't be available in the real world, or whether it allows altering simulation with a god's hand, i.e. in a way a robot wouldn't be able to in the real world. But after marking the API below with these 2 characteristics (to the best of my knowledge), it became clear to me that they really go hand-in-hand, and maybe the most useful approach would make each API disable-able within their plugins.
Another question I have is whether the new plugins should be in
A couple ideas I have for the port:
Otherwise this splitting looks good to me! It makes sense to me to just put all the plugins (including the sensors, etc) into
I can find more use cases for diving them into
I have no experience with both so can not comment anything against the removal.