Skip to content

Rollout system trajectories with benchmarked solvers themselves #5

Description

@stephane-caron

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

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions