-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SDFormat in the ROS ecosystem #91
Comments
The CTU-CRAS-Norlab models in SubT use a fully automated pipeline to "render" various outputs (URDF for rviz, SDF for G classic or for new G) from a single Xacro source. The pipeline is probably not easy to understand for newcomers, though... See e.g. https://github.com/osrf/subt/tree/master/submitted_models/ctu_cras_norlab_marv_sensor_config_1 . |
I can confirm that SDF works with both RViz and I wrap the SDF using Finding this, I think interoperability between URDF and SDF in both Gazebo and ROS is a good idea, allowing flexibility in workflow. |
Users in the community need guidance on how best to use URDF with SDFormat, especially when using URDF with tools in the ROS ecosystem together with Gazebo. This issue is meant to capture some of the questions/requests raised by members of the community and as a place for discussion on how to address them. There is also an ongoing effort to improve the interoperability of SDFormat with tools in the ROS ecosystem. Since there's likely to be overlap between the work there and some of the discussion here, this issue will hopefully serve as a central place for all discussions regarding SDFormat in the ROS ecosystem.
Here's an initial list of questions to address/discuss:
model://
topackage://
?cc @srmainwaring @quarkytale @bperseghetti
The text was updated successfully, but these errors were encountered: