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
(OEP = Optim Enhancement Proposal) Rather than keeping track of f_calls and g_calls in the algorithm, it seems much cleaner to have DifferentiableFunction store these quantities, and every time you call value(d, x) and gradient!(g, d, x) the counters get updated. That way there is no chance you're not keeping track of each evaluation (e.g., #219).
The text was updated successfully, but these errors were encountered:
I'd throw my time after this asap (as in asap, not open source work asap), but (and correct me if I'm mistaken) I've seen @johnmyleswhite oppose something similar earlier. Any opinions? If I remember correctly, you said you wanted to go in the opposite direction API wise. Care to elaborate? Or correct me?
(OEP = Optim Enhancement Proposal) Rather than keeping track of
f_calls
andg_calls
in the algorithm, it seems much cleaner to haveDifferentiableFunction
store these quantities, and every time you callvalue(d, x)
andgradient!(g, d, x)
the counters get updated. That way there is no chance you're not keeping track of each evaluation (e.g., #219).The text was updated successfully, but these errors were encountered: