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

Improvement / workaround: MoveIt! collision checking in-between trajectory keyframes #2

Open
JenniferBuehler opened this issue Mar 25, 2016 · 0 comments

Comments

@JenniferBuehler
Copy link
Owner

The MoveIt! motion planner only does collision checking at key frames (which is certainly intended due to performance reasons). If there is a collision in-between key frames, it is not detected. Therefore, in some instances, the arm may still collide with objects.

The probably easiest way to fix this is to check each trajectory by refining it to key-frames at very small intervals, then do the collision checking again, and only accept the trajectory if there are no collisions. If there are collisions, re-compute a new trajectory.

Until this fix is done, a way to detect such a "faulty" trajectory is to enable the display of the trajectory path in RViz and visually check for possible collisions. If one is found, then abort execution and try again.

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

1 participant