-
Notifications
You must be signed in to change notification settings - Fork 65
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
Comments
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? |
@Levi-Armstrong Yep that was the problem, solved this by using move_group execute() method. |
At the very least a warning should be printed when an empty robot state is encountered. |
This was referenced Aug 26, 2021
This was referenced Oct 4, 2021
This has likely been fixed by ros-industrial/stomp_ros#26 ? |
26 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
The text was updated successfully, but these errors were encountered: