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

private setToIKSolverFrame() breaks workflow #2574

Closed
bsaund opened this issue Mar 31, 2021 · 3 comments
Closed

private setToIKSolverFrame() breaks workflow #2574

bsaund opened this issue Mar 31, 2021 · 3 comments

Comments

@bsaund
Copy link

bsaund commented Mar 31, 2021

#2461 makes setToIKSolverFrame() private. A public setToIKSolverFrame() is necessary (afaik) to effectively use other parts of the moveit API.
For example, my code uses the kinematics solver to get multiple IK solutions for a robot arm with redundant DOFs.

const kinematics::KinematicsBaseConstPtr &solver = jmg->getSolverInstance();
auto kinematic_state = std::make_shared<robot_state::RobotState>(model_);

kinematic_state->setToIKSolverFrame(solverTrobot, solver);

Eigen::Affine3d pose_in_solver_frame = solverTrobot * ee_target_pose_in_robot_frame;
... (conversion to target_poses) ...
solver->getPositionIK(target_poses, ...)

Link to my code
Moveit docs

It is necessary to transform the target pose(s) in the robot frame into the solver frame. With setToIKSolverFrame now private, I have to duplicate the setToIKSolverFrame() in my own code.

@rhaschke @AndyZe (were on the PR mentioned above)

Some possible resolutions are:

  1. Make setToIKSolverFrame() public again
  2. Duplicate setToIKSolverFrame() logic in my own code
  3. Find a different pathway to get multiple IK solutions from a pose in robot (not solver) frame.

I appreciate any time and comments w.r.t. this issue, thanks!

@welcome
Copy link

welcome bot commented Mar 31, 2021

Thanks for reporting an issue. Because we're a volunteer community, providing a pull request with suggested changes is always welcomed.

@rhaschke
Copy link
Contributor

Sorry. Obviously, we didn't expect this function to be used externally. @AndyZe can you make those functions public again, please?

@v4hn
Copy link
Contributor

v4hn commented Jul 9, 2021

Fixed by #2580

@v4hn v4hn closed this as completed Jul 9, 2021
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

Successfully merging a pull request may close this issue.

3 participants