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

start using opti.solve() instead of solve_NLPSOL #142

Open

dgupta7 opened this issue Jul 29, 2024 · 0 comments

Labels

Milestone

Collaborator

dgupta7 commented Jul 29, 2024

With casadi 3.6.5, we should be able to use opti.solve() instead of solve_NLPSOL through the setting detect_simple_bounds = true

This will make the code cleaner and extraction of variables can also be changed to be more cleaner (instead of unpacking the w_opt).

dgupta7 added the enhancement label

Lars-DHondt-KUL added this to the low priority milestone

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