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.

Sign up for GitHub

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

Jump to bottom

Improve the iLQR stopping conditions #5

Open

bamos opened this issue Oct 15, 2018 · 0 comments

Member

bamos commented Oct 15, 2018 •

edited

Loading

Current: Fixed number of iters or a threshold on the full action step norm
It would also be nice to stop based on the absolute or relative change in cost if the user doesn't care about hitting a fixed point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment