IpoptOptimizer now stores solver specific options and the callbacks are faster #1021
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Move Ipopt-specific options from
solve()toIpoptOptimizerstruct fields.Options are now set via the struct constructor or additional_options dict,
while common interface args (
reltol,maxiters,maxtime,verbose) remainin
solve().BREAKING CHANGES:
IpoptOptimizer()constructor instead ofsolve().u(current state),z_L, z_U(for lower/upper bounds) andg, lambda(for constraints), so if the historical values for these are needed, these values must be copied!Co-authored-by: Claude claude@anthropic.com
Checklist
contributor guidelines, in particular the SciML Style Guide and
COLPRAC.
Additional context
Add any other context about the problem here.