-
Notifications
You must be signed in to change notification settings - Fork 36
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
Invalid inertia values #30
Comments
To reproduce this issue you can simply use ros2 launch tiago_description robot_state_publisher.launch.py to publish the robot_description, and this kind of snippet with gazebo fortress running to spawn based on the published robot_description:
|
Specifically, it seems following check is failing: |
Hello @EGAlberts! Thank you for reporting the bug. Most of our team are currently on vacation. We will take a look into it when our team is back. Best Regards, |
Thanks for replying, in the mean time I used meshlab and imported the .stl of Tiago's shoulder. This gave me new inertia values which do make sense. https://www.hamzamerzic.info/mesh_cleaner/ is a website which allows you to do this process without actually installing meshlab yourself and just upload the relevant mesh file. See the relevant commit: EGAlberts@d95a395 . You may consider recreating this process yourself to confirm our work, and possibly having those be the inertia values. To give more details about the error with the current values, it finds that the triangle equality (some moments are smaller when summed than bigger ones) is not satisfied. |
In the process of migrating from Gazebo classic to Gazebo fortress, I am publishing the robot_description described contained within this package. In doing so, I get three errors:
By zero-ing out the inertia values (see EGAlberts@a4a7fd6) of these three links I am able to make Tiago spawn.
One of these lives in this repo, specifically arm_1_link. I shall open a separate issue in the pal_gripper repository.
Can you please verify the inertia values are valid? Or determine if the parsing/validation by the new version of Gazebo warrants changes?
The text was updated successfully, but these errors were encountered: