Skip to content
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 version of trust region #269

Merged
merged 5 commits into from
Aug 13, 2016
Merged

Use Optim version of trust region #269

merged 5 commits into from
Aug 13, 2016

Conversation

rgiordan
Copy link
Contributor

In addition to removing the Celeste trust region code, I move most of the derivative tests back into the main test suite, leaving out only three very slow tests to be run with a custom flag.

@rgiordan
Copy link
Contributor Author

This is failing because Optim.jl hasn't tagged a version with the trust region code yet.

@jeff-regier , do you have a preferred method to get a particular commit for Travis? I'm going to try checking out master on Optim in travis, but I'm open to other ways of doing it.

@jeff-regier
Copy link
Owner

Hey Ryan, I think the best way forward is to ask them to tag it. Any other
solution I can think of is really a hack, with drawbacks. You contributed
some good code to their package, so they should tag a release with it for
you.

On Thu, Aug 11, 2016, 8:27 PM Ryan [email protected] wrote:

This is failing because Optim.jl hasn't tagged a version with the trust
region code yet.

@jeff-regier https://github.com/jeff-regier , do you have a preferred
method to get a particular commit for Travis? I'm going to try checking out
master on Optim in travis, but I'm open to other ways of doing it.


You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
#269 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIieC0ZJqxO8oKqm_AlfvIesTrfYUw2Zks5qe-gFgaJpZM4JivAH
.

@rgiordan
Copy link
Contributor Author

rgiordan commented Aug 12, 2016

How about that, the problem literally solved itself overnight. :) Thought it seems it hasn't been pushed to METADATA yet.

@rgiordan
Copy link
Contributor Author

Waiting on JuliaLang/METADATA.jl#5947.

@pkofod
Copy link

pkofod commented Aug 13, 2016

Hey Ryan, I think the best way forward is to ask them to tag it. Any other solution I can think of is really a hack, with drawbacks. You contributed some good code to their package, so they should tag a release with it for you.

Don't worry, I'm doing what I can to get it live ;) NelderMead deprecation handling is holding the merge back, but that should be fixed.

@rgiordan
Copy link
Contributor Author

@pkofod no problem!

@pkofod
Copy link

pkofod commented Aug 13, 2016

By the way, this is the new PR JuliaLang/METADATA.jl#5957

I'm very happy to see you using OptimizationOptions by the way. I think keywords in optimize will go at some point, so :)

@rgiordan rgiordan merged commit ad02634 into master Aug 13, 2016
@rgiordan rgiordan deleted the upgrade_optim branch September 2, 2016 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants