-
Notifications
You must be signed in to change notification settings - Fork 214
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
StepLength Extrapolation #294
Comments
Merged
Maybe to simplify this, it might be better to make step length extrapolation part of the line-search type. |
I'll try to deal with this tomorrow or Friday |
Awesome! |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Aside from
the step-length extrapolation (from step-length, gradient and function history) is maybe the most crucial aspect of the optimisation algorithms implemented in Optim.
I suggest to (minimally) refactor
Optim
to allow the user to choose how to perform this? E.g.cg.jl
usesalphatry
which is HZ's method,LBFGS
uses just the previous step. But I'd really like to play around or even try my own variants.CC: @pkofod @anriseth
(this should probably be done in parallel in
Optim
andLineSearches
)The text was updated successfully, but these errors were encountered: