-
Notifications
You must be signed in to change notification settings - Fork 322
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
Support the FATROP NLP solver in Moco #3787
Comments
Leaving some thoughts here as I table development on this feature for now. These thoughts are based on the state of #3906 at commit 93d0060.
|
A quick comparison between Ipopt and FATROP with the same solver settings. Running a 1-DOF "sliding mass" problem that travels one meter and starts and ends at rest:
The shared solver settings:
Ipopt output
FATROP output
SummaryWith the current implementation of Moco and the above solver settings, FATROP takes more solver time (2.05 s) compared to Ipopt (1.24 s). Notably, FATROP requires more iterations, more function evalulations in every category, and loses the most time in computing the Hessian. This is likely because Moco still relies on finite-differencing, which may be negating the benefits of FATROP. |
Add support for the FATROP solver via the recently added support through CasADi's nlpsol.
Requires:
The text was updated successfully, but these errors were encountered: