-
Notifications
You must be signed in to change notification settings - Fork 96
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
URDF parser fails if two consecutive fixed joints are present in the model. #105
Comments
Original comment by Silvio Traversaro (Bitbucket: traversaro).
|
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters). This happens because ReduceFixedJoints() in parser_urdf.cc recurses to the children of the tree and adds them up gradually until it gets back to the top. The inertial lumping is using code copied from ODE. Specifically, dMassAdd doesn't check for division by zero if both masses are zero, which is causing the I'll see if I can replace the ODE inertial code with the |
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters). I've started work in d696f97 (branch |
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters). |
Original comment by Silvio Traversaro (Bitbucket: traversaro). Hi @scpeters , |
Original comment by Antoine Hoarau (Bitbucket: ahoarau). Also affected with this bug ... Any news ? |
@scpeters I wonder if the test failures you mentioned is related to the recent fix in ign-math |
Original report (archived issue) by Silvio Traversaro (Bitbucket: traversaro).
The original report had attachments: singleFixed.urdf, doubleFixed.urdf
If two consecutive fixed joints are present in a URDF model, and both joints have a massless child, the conversion to SDF is broken. In particular the COM of the resulting link is reset to zero (observed in Linux) or set to NaN (observed on OS X).
To reproduce the issue, call the
gz sdf -p
program in the attached urdf files:Working model, with a single fixed joint:
Broken model, with two fixed joints (note the COM pose):
The text was updated successfully, but these errors were encountered: