-
Notifications
You must be signed in to change notification settings - Fork 41
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
Introduce mutating functions for Problem member functions #53
Merged
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
…nguish modifying and non-modifying memberfunctions.
Codecov Report
@@ Coverage Diff @@
## master #53 +/- ##
==========================================
+ Coverage 99.28% 99.66% +0.37%
==========================================
Files 41 45 +4
Lines 1968 2360 +392
==========================================
+ Hits 1954 2352 +398
+ Misses 14 8 -6
Continue to review full report at Codecov.
|
# Conflicts: # Project.toml # src/plans/gradient_plan.jl # src/plans/hessian_plan.jl # src/plans/stepsize.jl # src/solvers/gradient_descent.jl # test/solvers/test_trust_regions.jl
…opt.jl into mutating-evalutations
* use grad instead of ∇ to denote the gradient * use gradient within options (instead of ∇) to denote the current gradient * use gradient!! within probems (instead of ∇) to denote the gradient function gradF * use ˚\operatorname{grad}` within math formular (instead of ∇) to denote the gradient * use `grad_` (instead of `∇`) to prefix gradient functions * introduce a notation page in the documentation. * adapt Newton (still with allocation always) to new scheme).
# Conflicts: # src/solvers/quasi_Newton.jl
…, finish documentation overhaul.
This PR is finished, we just need JuliaManifolds/Manifolds.jl#334 to be merged. |
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.
This is a major rework of the inner structure of
Manopt.jl
to support mutating problem functions, most prominentlygradient!(X,x)
.gradient!!
function and encapsulate all of this inget_gradient
/get_gradient!
Circle
/PositiveNumbers
since thengradient!!
never mutates.get_gradient!
should be introducedhessian
tohessian!!
ApproximateHessian
to act as a normal hessian (mutating or allocating) functionsubgradient
tosubgradient!!
proxes
toproximal_maps!!
∇
tostochastic_gradient!!
PrimalDualProbem
to!!
.M
as their first parameter.This then solves #52.
The problem parameter might even later be used to indicate whether the gradient/hessian is Riemannian or Euclidean, though their conversions have to first be more established.
Maybe a small benchmark of the two new methods (providing either a allocation or a mutating gradient) would be nice, too.