Skip to content

Conversation

@ChrisRackauckas
Copy link
Member

Much of the complexity in the issues with the Optim.jl wrapper is simply because it doesn't treat Optim well. It makes things always complete, instead of simplifying the call. This simplifies the call, so the less you use the less machinery is required. In particular:

Much of the complexity in the issues with the Optim.jl wrapper is simply because it doesn't treat Optim well. It makes things always complete, instead of simplifying the call. This simplifies the call, so the less you use the less machinery is required. In particular:

* TwiceDifferentiable is only made and used if the optimizer needs to use Hessians. This fixes #859, fixes #893
* Only uses constraints and bounds when the user sets them. Fixes #863 and fixes #558
@ChrisRackauckas ChrisRackauckas merged commit cbc8e97 into master May 6, 2025
25 of 26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants