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

ikfast: document success rate of IKFast generated plugins #99

Closed
gavanderhoorn opened this issue May 22, 2014 · 4 comments
Closed

ikfast: document success rate of IKFast generated plugins #99

gavanderhoorn opened this issue May 22, 2014 · 4 comments

Comments

@gavanderhoorn
Copy link
Member

As part of the plugin generation process, openrave runs a number of IK tests, which ultimately results in output like:

openravepy.databases.inversekinematics: testik, \
  success rate: 0.930000, \
  wrong solutions: 0.000000, \
  no solutions: 0.070000, \
  missing solution: 0.470000

Additional output is a list of exactly which tests failed (trial nr, joint angles, etc).

This is important data, as it provides an indication of the 'quality' of a provided IK plugin, and should probably be included with a *_moveit_plugins pkg documentation.

@gavanderhoorn gavanderhoorn self-assigned this May 22, 2014
@gavanderhoorn gavanderhoorn added this to the Untargeted milestone Jul 21, 2014
@gavanderhoorn
Copy link
Member Author

Also related to #112.

@simonschmeisser
Copy link
Contributor

Can you give some info on how to use this test? I just created a new ikfast plugin for an lrmate200ic and it completely doesn't work (ikfast gives 0 solutions, even before checking validity). The one provided was somewhat running, but did not give very useful results. kdl works just fine

@gavanderhoorn
Copy link
Member Author

gavanderhoorn commented Sep 2, 2016

I'll see if I can find my notes, but I'm more interested in / worried about:

The one provided was somewhat running, but did not give very useful results

You mean that fanuc_lrmate200ic_moveit_plugins didn't work for you?

If so, could you please report that in a new issue?

@gavanderhoorn
Copy link
Member Author

As we're migrating to OPW kinematics (#245), this issue is no longer relevant.

Closing.

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

No branches or pull requests

2 participants