You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Gazebo uses the +x forward convention for all rendering sensors. This was done to keep the same behavior as Gazebo Classic. However, this is at odds with the convention in ROS, which is +z forward. Users run into this issue (e.g. #29) and the current workaround is to set a static transform in ROS to create a separate optical frame. There's an old PR in gazebosim/ros_gz#257 to add a dedicated publisher, but I think it would be best if Gazebo itself provided a way to set the convention used.
Implementation suggestion
We could do one of the following:
Add an SDFormat tag to all rendering sensors that sets whether the +z convention should be used.
Add an SDFormat under <sensor> that sets whether the +z convention should be used. This would be easier since we'd only modify one SDFormat description file, but it would affect all sensors
One of the two options above, but the tag would allow setting a custom transformation matrix.
The text was updated successfully, but these errors were encountered:
Desired behavior
Currently, Gazebo uses the +x forward convention for all rendering sensors. This was done to keep the same behavior as Gazebo Classic. However, this is at odds with the convention in ROS, which is
+z
forward. Users run into this issue (e.g. #29) and the current workaround is to set a static transform in ROS to create a separate optical frame. There's an old PR in gazebosim/ros_gz#257 to add a dedicated publisher, but I think it would be best if Gazebo itself provided a way to set the convention used.Implementation suggestion
We could do one of the following:
+z
convention should be used.<sensor>
that sets whether the+z
convention should be used. This would be easier since we'd only modify one SDFormat description file, but it would affect all sensorsThe text was updated successfully, but these errors were encountered: