Skip to content
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

Surprising interpretation of "group" in CollisionRequest #3570

Open
simonschmeisser opened this issue Feb 13, 2024 · 1 comment
Open

Surprising interpretation of "group" in CollisionRequest #3570

simonschmeisser opened this issue Feb 13, 2024 · 1 comment

Comments

@simonschmeisser
Copy link
Contributor

We are working on a feature where we wanted to check collisions between the end-effector and some piece in a editor for grasps. However there were often no collisions at all.

Turns out that while one can define a JointModelGroup via a list of links in SRDF, the collision checking will only consider child links of any active joint:

https://github.com/ros-planning/moveit/blob/6863b711dde4b03e952ffdaf3fef3e8745a5a099/moveit_core/collision_detection_fcl/src/collision_common.cpp#L941

So for a magnetic gripper or a suction gripper this will do no collision checks at all.

Should this rather check the union of getUpdatedLinkModelSet and getLinkModels? The first one to keep the current and expected behavior of including the gripper/end-effector when checking the robot, the second to include also non-actuated links?

@rhaschke
Copy link
Contributor

Are you sure that getUpdatedLinkModelsSet() doesn't include fixed joints, but only active ones?
I couldn't find a hint for that in code. Did you use the correct group?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants