-
Notifications
You must be signed in to change notification settings - Fork 3
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
Parse URDF models from ergocub-software #26
Comments
Thanks for reporting the problem! The URDF to SDF conversion is not handled internally by If the conversion fails, we should understand what's the problem on the sdformat side. This is relevant because the same logic is called when the model is imported in a generic Gazebo simulation. In other words, if the conversion fails, likely the URDF model cannot be imported neither in Gazebo. Can you please call manually the following command and paste the produced error? gz sdf -p /path/to/ergocub.urdf |
For me with gz-sim7 and latest release of ergocub-software
prints just at the beginnining a warning:
While this may be something in ergocub-software, rod perhaps is getting confused by the warning? |
Thanks for your response @diegoferigo. Actually, the command does not fail with Warning [parser.cc:833] XML Attribute[name] in element[ray] not defined in SDF, ignoring. gz sdf -p /home/flferretti/mambaforge/envs/test101/share/ergoCub/robots/ergoCubGazeboV1_minContacts/model.urdf > ergocub.sdf |
The problem on the ergocub models should be fixed by icub-tech-iit/ergocub-software#164 . As a local modification, one can manually change |
The warning is not produced anymore by C.C. @diegoferigo |
With the most recent version of |
I was referring to most recent version of |
I've encountered an issue while trying to parse the URDF model using the
ergoCubGazeboV1_minContacts
model from theergocub-software
repository. Specifically, the problem arises whenrod
tries to convert the model from URDF to SDF format.Interestingly, removing the
<gazebo>
tags from the URDF resolves the problem. As a expected behaviour, I believe that if therod
tool doesn't recognize these tags, it should ideally ignore them and possibly log a warning message.Here's the traceback I'm encountering:
C.C. @diegoferigo @traversaro
The text was updated successfully, but these errors were encountered: