-
Notifications
You must be signed in to change notification settings - Fork 516
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
last waypoint from STOMP solution doesn't always match goal #2554
Comments
@patrickKXMD could you test if #2625 fixes this issue for you? |
Hi @henningkayser But the stomp planner always failed to plan in allowed time (which is 10 seconds) for my case on the latest main branch and I'm still investigating... |
@henningkayser look like it's not fixed, sometimes the goal and last waypoint is not identical |
This issue is being labeled as stale because it has been open 45 days with no activity. It will be automatically closed after another 45 days without follow-ups. |
I too have the same problem, both starting and goal states can differ greatly from those specified in the MotionPlanRequest, even when planning trivial paths without collisions. |
Description
this is a really annoying problem, the last waypoint from STOMP solution doesn't always match the
goal_state
I added four lines here for debug
https://github.com/ros-planning/moveit2/blob/c2292a7054904c25851b6af78abb6aca8a5852ae/moveit_planners/stomp/src/stomp_moveit_planning_context.cpp#L68C1-L71C4
and here is the output
sometimes they are identical which is good.
sometimes they are different
I don't know why this happen but it's really annoying
Your environment
Steps to reproduce
Using STOMP planner and plan for some specific joint values
Expected behaviour
The last waypoint should be identical with the goal_state
Backtrace or Console output
Use gist.github.com to copy-paste the console output or segfault backtrace using gdb.
The text was updated successfully, but these errors were encountered: