Skip to content
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

Rollout system trajectories with benchmarked solvers themselves #5

Open
stephane-caron opened this issue Dec 14, 2023 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@stephane-caron
Copy link
Member

stephane-caron commented Dec 14, 2023

Current context

MPC problems are generated statically using a reference solver (e.g. quadprog for LIPMWALK problems, ProxQP for WHLIPBAL problems), saved to data/ and then run with benchmark solvers.

Describe the solution you'd like

This comparison is not fair in the context of MPC: in MPC, when a solver fails to find a solution, the integrator moves on with the previous one, often leading to "failure in series" (loss of recursive feasibility). The benchmark would be more realistic (more relevant to roboticists) if we used solver solutions to rollout trajectories.

See also

@stephane-caron stephane-caron added the enhancement New feature or request label Dec 14, 2023
@stephane-caron stephane-caron changed the title Rollout MPC problems with solver itself Rollout MPC problems with benchmarked solvers themselves Dec 14, 2023
@stephane-caron stephane-caron changed the title Rollout MPC problems with benchmarked solvers themselves Rollout system trajectories with benchmarked solvers themselves Dec 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant