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

Remove gradient storage #48

Merged
merged 7 commits into from
May 21, 2017
Merged

Remove gradient storage #48

merged 7 commits into from
May 21, 2017

Conversation

anriseth
Copy link
Collaborator

Fixes #47

I also updated the README and the tests (can't enable them until Optim 1.0 is tagged)

@codecov
Copy link

codecov bot commented May 20, 2017

Codecov Report

Merging #48 into master will decrease coverage by 3.1%.
The diff coverage is 24.59%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #48      +/-   ##
==========================================
- Coverage   48.63%   45.52%   -3.11%     
==========================================
  Files           8        8              
  Lines         584      615      +31     
==========================================
- Hits          284      280       -4     
- Misses        300      335      +35
Impacted Files Coverage Δ
src/api.jl 0% <ø> (ø) ⬆️
src/basic.jl 100% <100%> (ø) ⬆️
src/backtracking.jl 75% <100%> (ø) ⬆️
src/morethuente.jl 53.71% <100%> (-0.27%) ⬇️
src/deprecate.jl 27.08% <2.77%> (-72.92%) ⬇️
src/hagerzhang.jl 32.53% <33.33%> (-0.48%) ⬇️
src/strongwolfe.jl 75.67% <80%> (+0.35%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5eebe50...7436f53. Read the comment docs.

@@ -84,7 +82,6 @@ function _hagerzhang!{T}(df,
x::Array{T},
s::Array,
xtmp::Array,
g::Array,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you keep a signature with a warning and g_scratch, and make sure that copy!(g_scratch, d.g at the end of this method, like

function _hagerzhang!(df, x, s, xtmp, g, lsr, c, mayterminate, ...)
    warn("you no longer have to provide a "g" input")
    _hagerzhang!(df, x, s, xtmp, lsr, c, mayterminate, ...)
    copy!(g, d.g)
end

then this doesn't have to be a breaking change... don't know if it's worth the trouble though.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea! I'll try to do this.

@anriseth
Copy link
Collaborator Author

This can be merged, if nobody objects.

Then we can tag a new minor

@pkofod
Copy link
Member

pkofod commented May 21, 2017

I'll merge after the tests run (can't be sure the conflict resolution worked flawlessly)

@pkofod pkofod merged commit 35d523d into master May 21, 2017
@anriseth anriseth deleted the anriseth/nolsgradient branch October 11, 2017 08:14
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.

2 participants