-
Notifications
You must be signed in to change notification settings - Fork 21
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
using move_group for ik solver #11
Comments
@isucan are there any other nodes that wrap the IK solver functionality without launch a move_group capability? thanks! |
Nope, there are not. |
I think the right solution here is to reimplement pr2_kinematics on top of MoveIt, as per: PR2/pr2_kinematics#2 . |
So you mean reimplement a node that wrap's MoveIt!'s IK solver functionality without requiring to launch all of MoveIt!? One suggestion I offered to @k-okada is just launch move_group with only one capability:
|
As a compatibility layer so that nodes developed against the old API continue to work, yes. (I believe that node used to do what you're looking for, and reviving it would be a great service to the PR2 community) |
Actually I don't work with the PR2, @k-okada was just asking me because I know MoveIt! (so not volunteering) |
pr2_kinematics has now been re-implemented ontop of MoveIt.PR2/pr2_kinematics@de17caa. pr2_apps has been re-written to use MoveIt as the backend. #12 discusses changes and testing and #13 is the one that is planning to be merged. |
+1 to doing this! |
We can use moveit_msgs/msg/{PositionIKRequest.msg,KinematicSolverInfo.msg} instaed of msg from arm_navigation
@aginika
The text was updated successfully, but these errors were encountered: