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

STOMP failes to plan with using the the move_group move() method. #53

Open
Levi-Armstrong opened this issue Aug 31, 2017 · 4 comments
Open
Assignees

Comments

@Levi-Armstrong
Copy link
Contributor

It looks like the moveit move_group move method does not populate the robot start state in the planning request. Therefore STOMP check if it is populated and if not it exits and prints a warning where OMPL will plan fine. Not sure if this is really a STOMP issue or a moveit issue. Maybe if the start state is not provided it should get the current state of the robot?

@janisa9
Copy link

janisa9 commented Apr 12, 2018

Hi!

Is this issue solved? Recently ran into this problem and I don't know in which part is this issue.. Yesterday added comment in #37. Can you take a look?

@janisa9
Copy link

janisa9 commented Apr 13, 2018

@Levi-Armstrong Yep that was the problem, solved this by using move_group execute() method.

@jrgnicho
Copy link
Contributor

jrgnicho commented Jul 5, 2018

At the very least a warning should be printed when an empty robot state is encountered.

@simonschmeisser
Copy link
Contributor

This has likely been fixed by ros-industrial/stomp_ros#26 ?

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

No branches or pull requests

5 participants