Fix LevenbergMarquardt trace constructor to match Optim v0.5. #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Does this work with any earlier versions of Optim? If not, then best to set a lower bound of |
|
Good point, changed. |
|
Changes Unknown when pulling bdc7f27 on pkofod:master into * on madsjulia:master*. |
|
Changes Unknown when pulling bdc7f27 on pkofod:master into * on madsjulia:master*. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ref: https://gist.github.com/anonymous/4609c24a5c7b8bb8222012c9564958c6 and JuliaLang/METADATA.jl#5341
The way traces are initiated has changed a bit in Optim. I didn't notice you were accessing
OptimizationTracedirectly, so currentlyMads.jltests will fail incontamination.jlwith Optim v0.5, because a trace cannot be initiated.