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
I reviewed the implementations of optimisers, most of them use @. to update the internal states. It seems that these optimisers (Momentum, Nesterov, RMSProp etc) do not work with TrackedReal object. I wonder if this is done intentionally in order to force people using array-like parameters instead of real number.
The text was updated successfully, but these errors were encountered:
The optimisers are just heavily designed for Tracker-style usage (where we have mutable reference types like arrays everywhere); ideally optimisers would just work with whatever you give them, including scalars. This is going to happen gradually with #637.
I reviewed the implementations of optimisers, most of them use
@.
to update the internal states. It seems that these optimisers (Momentum, Nesterov, RMSProp etc) do not work withTrackedReal
object. I wonder if this is done intentionally in order to force people using array-like parameters instead of real number.The text was updated successfully, but these errors were encountered: