You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I was trying out the manifold functionality in Optim.jl. It's nifty. However, I noticed that in order to use it, you need to not only define the methods retract! and project_tangent! but also need to subtype the abstract Manifold type.
Is it really necessary to subtype the Manifold type if you need to define those methods anyway? Why not drop that requirement altogether, similar to the way that ProximalOperators.jl only requires you to define prox! and grad!?
The text was updated successfully, but these errors were encountered:
That is possible, yes. Abstract types can be useful for fallbacks, but that's probably not too relevant as you say, as you have to define the manifold specific methods anyway.
I think the plan is to transition to Manifolds.jl: JuliaManifolds/Manifolds.jl#35 . There is more than these two functions that can be useful for manifold optimization.
Which manifold did you have in mind? Besides Optim transitioning to support also the manifolds as Mateusz mentioned, you might also want to check https://github.com/JuliaManifolds/Manopt.jl (disclaimer – a package I develop).
Hi, I was trying out the manifold functionality in Optim.jl. It's nifty. However, I noticed that in order to use it, you need to not only define the methods
retract!
andproject_tangent!
but also need to subtype the abstractManifold
type.Is it really necessary to subtype the
Manifold
type if you need to define those methods anyway? Why not drop that requirement altogether, similar to the way that ProximalOperators.jl only requires you to defineprox!
andgrad!
?The text was updated successfully, but these errors were encountered: