Collision shapes of CustomRobot
💬 Open
Hi Jacobi team,
When loading a CustomRobot from a URDF, I'm wondering what is happening regarding collision shapes.
- I am not sure if the collisions shapes described in the URDF are actually loaded or not. (Playing a bit with the Robot object, I have the impression they are, but they might be messed up because of point 2 below.)
- Reading the documentation, I have the impression that a single collision shape is expected per link.
- I am not sure if the collision shape can be a primitive shape or if it needs to be specified as a mesh.
Could you please give more some more explanations on this topic and/or maybe extending the related documentation?
Thank you very much
Hi Alban! CustomRobot currently requires a specificified collision mesh per link, and our URDF parser currently loads in a single collision mesh per link only. We currently don't have too much in depth documentation on this feature as it is in a beta preview state, but you can find our basic documentation on it here. I imagine this is probably what you were already looking at.
Is there specific functionality that you would expect CustomRobot to be able to perform? Can I ask aobut what kind of URDFs you intend to use with this feature?
0 6 months ago Reply
Hi Jonathan,
Right now I am considering a simple single arm URDF. But:
If I understand correctly, to use the CustomRobot class, I would need to modify our URDF to point to a single mesh per link that would encompass the current multiple collision shapes. Is that correct?
Also, could this mesh be non-convex?
Thanks,
0 6 months ago Reply
@Alban Laflaquiere: Yes, as of now you would need to modify the URDF to point to a single mesh per link. That mesh would encompass the current multiple collision shapes. If the mesh is non-convex we do generate a convex hull for the mesh, however if you require more precision in your convex representation, you can also upload a representative convex mesh instead
0 6 months ago Reply
6 months ago