Debugging self-collision? #223
-
What would be an efficient way to debug self-collision? I've set up my spheres in isaac sim (a bit slow and painful 😬 ), but now I'm seeing self-collision issues when trying to collision check. I know I need to probably tweak the yml, but without being able to visualize the self-collisions I fear this will take forever. Are there existing gui tools for helping fix issues like this? Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
One way to check is by setting the robot at a configuration that you know is collision free and then use this class's self collision check: curobo/src/curobo/wrap/model/robot_world.py Line 231 in d6e600c Here is how to create an instance of RobotWorld: Then remove link from collision_link_names one by one until you find the link that's causing the problem. |
Beta Was this translation helpful? Give feedback.
In case others find this useful, this is what I came up with -- I realized by setting
state.robot_spheres.requires_grad = True
the CC kernel will fill outrollout.robot_self_collision_constraint._sparse_sphere_idx
, which I can then use to see which sphere have collision. Here's the full script I'm using: