-
Notifications
You must be signed in to change notification settings - Fork 6
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
Use Optim.jl directly for Optim solvers #129
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportBase: 93.00% // Head: 78.26% // Decreases project coverage by
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more Additional details and impacted files@@ Coverage Diff @@
## main #129 +/- ##
===========================================
- Coverage 93.00% 78.26% -14.74%
===========================================
Files 13 15 +2
Lines 572 635 +63
===========================================
- Hits 532 497 -35
- Misses 40 138 +98
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
With LogDensityProblems, we have the ability to simultaneously compute the log density, its gradient, and even its Hessian. Optim.jl supports this kind of interface that shares work; however, Optimization.jl does not.
This PR changes the internals of Pathfinder to use Optim.jl whenever a LogDensityProblem and an Optim.jl optimizer are provided. In the best case, this halves the amount of work performed by Pathfinder. Since the optimization solution stored in
PathfinderResult
can now be one of two types, this change is marked as breaking.