Use Optim.jl directly for Optim solvers #129
Open
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.
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.