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
By default Optimistix doesn't expose the search attribute of concrete solvers but NeMoS users might want to flexibly switch between linesearches and constant learning rates depending on whether stepsize is passed as a solver argument.
A solution to this would be to create short redefinitions of the required solvers with the search as an argument to __init__, and in the adapter dealing with stepsize with something like:
if"stepsize"insolver_init_kwargs:
assert"search"notinsolver_init_kwargs, "Specify either search or stepsize"solver_init_kwargs["search"] =optx.LearningRate(
solver_init_kwargs.pop("stepsize")
)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
By default Optimistix doesn't expose the search attribute of concrete solvers but NeMoS users might want to flexibly switch between linesearches and constant learning rates depending on whether
stepsizeis passed as a solver argument.A solution to this would be to create short redefinitions of the required solvers with the
searchas an argument to__init__, and in the adapter dealing withstepsizewith something like:and
Beta Was this translation helpful? Give feedback.
All reactions