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
Inconsistent collision checking when updating from hpp-fcl 2.2 to 2.3 #1902
Comments
Thanks @kingjin94 for raising this issue. |
Looking at your code, it seems that you are considering the meshes as BVHModelOBBRSS model in HPP-FCL, while your meshes are convex shapes. Isn't it? But what is sure is that you need to use Convex types by doing: bvh.buildConvexRepresentation(False)
convex = bvh.convex |
@lmontaut provided a fix to hpp-fcl humanoid-path-planner/hpp-fcl#387. |
The issue is solved via https://github.com/humanoid-path-planner/hpp-fcl/releases/tag/v2.3.1. |
Thanks to you and your team as well. Your response time and dedication is amazing! |
Thanks @kingjin94 for acknowledging our collective efforts to produce and maintain open-source toolboxes which might help the robotics community to move forward. |
Dear Pinocchio Team,
It seems that somewhere in the collision checking stack changes have occurred that significantly alter collision checking results. As I am not totally into the depths I can only provide the following example at the moment based on the pinocchio wrapper timor-python:
The
assembly.robot
object is a wrapper for pinocchio's RobotWrapper. The essential properties for pinocchio are (as needed for pin.computeCollisions):The self-collision pairs can be visualized as such: assembly.robot.visualize_self_collisions(); here same color = two parts of the robot in collision. From this robot it seems all new collisions are between meshes and cylinders that lie on neighboring links (if that helps).
Are you aware of any recent changes in pinocchio / hpp-fcl that might result in such different behaviors? Do you have any ideas how to debug this further?
The text was updated successfully, but these errors were encountered: