-
Notifications
You must be signed in to change notification settings - Fork 178
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
Checking target vel/accel do not exceed limits #74
Comments
Are you expecting users to clip the target velocity and acceleration before inputting to Ruckig? That is easy enough, I guess. These checks make the Ruckig smoothing almost worthless, I would say, other than jerk. |
Yes, Ruckig expects target velocities and accelerations within the given limits, otherwise a
Ruckig calculates a time-optimal and exact trajectory to a target waypoint. In fact Ruckig guarantees (e.g. for numerical exactness) that the error of the final position and final velocity to be within 1e-8, and for the final acceleration to be within 1e-10. When a target waypoint is not achievable (e.g. if the waypoints are outside of the limits, but also if a jerk limit is too low to reach the target velocity within the acceleration limit), an error is returned. The method |
We had some questions about these lines (and similar) in ruckig.hpp:
This does not make sense to us. Isn't the the purpose of Ruckig to take a target waypoint (position,velocity,acceleration) that is not necessarily achievable? And Ruckig will calculate the best possible solution?
@nbbrooks
The text was updated successfully, but these errors were encountered: