[Plans for solvers](@id planSection)
CurrentModule = Manopt
In order to start a solver, both a
Options are required.
Together they form a plan and these are stored in this folder. For
sub-problems there are maybe also only
Options, since they than refer to the
For most algorithms a certain set of options can either be generated beforehand of the function with keywords can be used. Generally the type
Decorators for Options
Options can be decorated using the following trait and function to initialize
In general decorators often perform actions so we introduce
as well as a helper for storing values using keys, i.e.
StoreOptionsAction getStorage hasStorage updateStorage!
[Debug Options](@id DebugOptions)
Modules = [Manopt] Pages = ["plans/debugOptions.jl"] Order = [:type, :function]
see [DebugSolver](@ref DebugSolver) for details on the decorated solver.
DebugActions can be found at the specific Options.
[Record Options](@id RecordOptions)
Modules = [Manopt] Pages = ["plans/recordOptions.jl"] Order = [:type, :function] Private = false
see [RecordSolver](@ref RecordSolver) for details on the decorated solver.
RecordActions can be found at the specific Options.
there's one internal helper that might be useful for you own actions, namely
[Stepsize and Linesearch](@id Stepsize)
The step size determination is implemented as a
Functor based on
in general there are
Modules = [Manopt] Pages = ["plans/stepsize.jl"] Order = [:type]
A problem usually contains its cost function and provides and implementation to access the cost
EvalOrder LinearEvalOrder RandomEvalOrder FixedRandomEvalOrder
Gradient based problem
Subgradient based problem
[Proximal Map(s) based problem](@id ProximalProblem)
Further planned problems