You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Regarding #17 and #44, we should introduce an option to interpret the kinematic constraints as "soft" ones. Then, we don't want to get within the kinematic constraints as fast as possible, but to avoid overshooting the limits.
This requires to disable the braking trajectory and to add the UDUD profiles in step 1. I'm not yet sure how to guarantee a solution in this case.
The text was updated successfully, but these errors were encountered:
Hello Pantor,
I am integrating your library in a project and I am facing the same behaviour of overshooting when changing max_velocity on the fly.
I would ask if there are any update on this topic and if there are also some workaround at the moment?
I tried to set the min_velocity parameter equal to zero which can avoid backward movement but I cannot set it to higher value (to decrease more the overshoot) since it may be in conflict with target_velocity. Any suggestion?
Regarding #17 and #44, we should introduce an option to interpret the kinematic constraints as "soft" ones. Then, we don't want to get within the kinematic constraints as fast as possible, but to avoid overshooting the limits.
This requires to disable the braking trajectory and to add the
UDUD
profiles in step 1. I'm not yet sure how to guarantee a solution in this case.The text was updated successfully, but these errors were encountered: