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
For most Vector parameters, the values they accept are (atomic) vectors of values in their feasible set. An exception of note is the "discretevector", which uses lists of its feasible values. This is obviously necessary when the discrete values are complicated types. Often enough, however, the possible values of a "discretevector" are all just character(1), in which case it would be very useful if one could use character vectors as values of these discretevector parameters.
I suggest a use.atomic flag (or similar) for makeDiscreteVector[Learner]Param, which
requires all feasible values to be character (or possibly all numeric, all integer etc.).
uses character vectors (or possibly other types) as values instead of lists.
I don't know ParamHelpers internals enough to know what changes 2. would require, one obvious place is constraintsOkParam.
The text was updated successfully, but these errors were encountered:
For most
Vector
parameters, the values they accept are (atomic) vectors of values in their feasible set. An exception of note is the"discretevector"
, which uses lists of its feasible values. This is obviously necessary when the discrete values are complicated types. Often enough, however, the possible values of a"discretevector"
are all justcharacter(1)
, in which case it would be very useful if one could use character vectors as values of thesediscretevector
parameters.I suggest a
use.atomic
flag (or similar) formakeDiscreteVector[Learner]Param
, whichcharacter
vectors (or possibly other types) as values instead of lists.I don't know ParamHelpers internals enough to know what changes 2. would require, one obvious place is
constraintsOkParam
.The text was updated successfully, but these errors were encountered: