Closed blooop closed 6 months ago
We found an issue in the joint space planner that's causing this. We have a fix coming soon (ETA: end of this week). Currently verifying to make sure it doesn't break other things.
Thanks!
This is now fixed in latest commit on main. Can you verify and close?
Yes, it works. thanks for the quick fix!
I noticed that when I was doing plan_single_js() plans that often the robot would get quite close but not fully reach the desired joint state.
I found a workaround of executing the plan, and then performing another plan with the same goal position. The second plan would get the robot to the desired goal state.
This is a minimal example that reproduces the bug and the workaround based off this demo: https://curobo.org/get_started/2a_python_examples.html#motion-generation
output: