You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 13, 2017. It is now read-only.
I have a robot trajectory of which I know that it is collision-free. Now I want to check whether it is still collision-free in combination with an attached object. Currently I see the following options:
perform full collision checking
perform collision checking limited to the joint model group that includes the link with the attached object
I could not find a method for restricting collision checking to a specific link or attached body. One workaround would be to modify the allowed collision matrix, so that all collision checks not including the attached body are skipped. Another workaround would be to define a group that contains only the link with the attached body and limit collision checking to that group. I like none of these workarounds because they require changing something I don't want to change (ACM respectively SRDF).
Is there any option I did not see?
If not, then I propose to include something like a link_name or attached_body_name in the collision_detection::CollisionRequest structure and use a method similar to CollisionData::enableGroup to restrict the active components to the desired link or attached body. Any thoughts on this?
Hello,
I have a robot trajectory of which I know that it is collision-free. Now I want to check whether it is still collision-free in combination with an attached object. Currently I see the following options:
I could not find a method for restricting collision checking to a specific link or attached body. One workaround would be to modify the allowed collision matrix, so that all collision checks not including the attached body are skipped. Another workaround would be to define a group that contains only the link with the attached body and limit collision checking to that group. I like none of these workarounds because they require changing something I don't want to change (ACM respectively SRDF).
Is there any option I did not see?
If not, then I propose to include something like a link_name or attached_body_name in the collision_detection::CollisionRequest structure and use a method similar to CollisionData::enableGroup to restrict the active components to the desired link or attached body. Any thoughts on this?
@isucan @davetcoleman Any thoughts on this?
The text was updated successfully, but these errors were encountered: