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

Non initialized pose header in motion planning request might create an issue #268

Open
ChamzasKonstantinos opened this issue Nov 1, 2021 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@ChamzasKonstantinos
Copy link
Collaborator

We need to make sure the header frame and stamp are set correctly in the poses set inside the goalConstraints.

For example it was observed that the following code needs to used in order to have the correct goal sampler.

auto setGoal = [this, &request](RobotPose &eef_pose) {
            geometry_msgs::PoseStamped poseMsg;
            poseMsg.header.frame_id = robot->getModelConst()->getModelFrame();
            poseMsg.header.stamp = ros::Time::now();
            poseMsg.pose = TF::poseEigenToMsg(eef_pose);
            request.clearGoals();
            request.getRequest().goal_constraints.push_back(
                kinematic_constraints::constructGoalConstraints(
                    robot->getSolverTipFrames(group)[0], poseMsg,
                    {1e-3, 1e-3, 1e-3}, {1e-2, 1e-2, constants::pi}));
            return true;
        }; 
@ChamzasKonstantinos ChamzasKonstantinos added the bug Something isn't working label Nov 1, 2021
@ChamzasKonstantinos
Copy link
Collaborator Author

@LeeYiyuan Maybe you should be aware of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants