It is not possible to add new URDF robots in different path of models
See original GitHub issueI am giving my robotic class using this amazing tool in python library, but I found a problem. In an exercise, I want that student use a specific urdf, but It is not possible to view the mesh because Mesh.filename use an absolute path àbspath
to the models of the toolbox.
I know that this is the only error, because I change to the specific path and works, but I do not find which could be the best solution in the architecture of your code
Issue Analytics
- State:
- Created 3 years ago
- Comments:22 (11 by maintainers)
Top Results From Across the Web
URDF robot model not loading correctly in Gazebo
I tried to change the robot model from mp_400 to other from the same package (e.g. mpo_700, in the launcher file) but then...
Read more >[ROS2 Q&A] 231 - How to load URDF files from Github
Your browser can't play this video. Learn more. Switch camera.
Read more >Spawn a URDF model in Gazebo with ROS2 - YouTube
Step by step, learn how to spawn a URDF robot model into a Gazebo world using ROS2 and the differences with respect to...
Read more >Tutorial: Using a URDF in Gazebo
URDF can only specify the kinematic and dynamic properties of a single robot in isolation. URDF can not specify the pose of the...
Read more >importrobot - MathWorks
Specify the URDF character vector. This character vector is a minimalist description for creating a valid robot model. URDFtext = '<?xml version="1.0" ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Ok, so default to current folder, then fallback to the distribution. We are thinking about putting the models in a separate package, they make the RTB package very large and don’t change much. This won’t affect operation from user perspective.
I’ve worked out a solution. No more need for
chdir
. My modified version: https://github.com/kxxt/swift/ I’ll open a pull request soon.