-
Notifications
You must be signed in to change notification settings - Fork 25
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
Initial IK seed #46
Initial IK seed #46
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a reasonable addition. Would you mind adding this seed_state
parameter to the unit test config file as an example for others as well?
Also, please run the |
Thanks for the feedback, I tried to implement the changes in the last commit. |
I worked in your suggestions. Sorry for taking to so long. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good; thanks for the updates
This small PR adds an option to specify the initial IK seed.
It was helpful for my use case to be able to specify this, as I am using a high DoF robot and a difficult to reach workpiece.
Maybe it is helpful for others too. If you don't want to add this feature, it is also fine for me.
As long a this parameter is not defined, previous behavior of using the zero pose is used.
For the demo study, one can for example add the following to the
optimization
part of the config yaml (although it does not provide an advantage in this simple case).