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
Currently there is the possibility of declaring default ranges for model hyper-parameters, for use one day in hyper-parameter optimization. However, the one-parameter range objects NominalRange and NumericRange, and their constructors, are defined in MLJBase and not MLJModelInterface. Since the idea is that implementing the MLJ model API should not require having MLJBase as a dependency, we should:
Migrate the types/constructors to MLJModelInterface; or
Move both types/constructors and methods (iterator, sampler, and so forth) to a stand-alone package for possible use outside MLJ.
Thoughts anyone?
The text was updated successfully, but these errors were encountered:
ablaom
changed the title
Migrate one-dimensional range types and constructors to MLJModelInterface
Emigration of one-dimensional range types
Jun 7, 2021
At present the first argument can have type Model for automatic inference of the type of the hyper-parameter. But the method is now also overloaded to accept the type itself. So, in the port, we do the latter and leave the former overloading for MLJBase.
Currently there is the possibility of declaring default ranges for model hyper-parameters, for use one day in hyper-parameter optimization. However, the one-parameter range objects
NominalRange
andNumericRange
, and their constructors, are defined in MLJBase and not MLJModelInterface. Since the idea is that implementing the MLJ model API should not require having MLJBase as a dependency, we should:iterator
,sampler
, and so forth) to a stand-alone package for possible use outside MLJ.Thoughts anyone?
The text was updated successfully, but these errors were encountered: