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
Is your feature request related to a problem? Please describe.
Currently, the oneHotEncoding function allows you to encode a variable into a list-like object. However, if used on a multi class target variable that is stored as a string (4 classes in my case), the nodeClassification function is unable to predict using the resulting list-like object. Forcing you to resort manually encoding the variable via CASE statements.
Describe the solution you would like
Allow for nodeClassification to use a one hot encoded list-like object as a target variable.
The text was updated successfully, but these errors were encountered:
@seankrobinson - we've added this feature request to our backlog for improving our ML pipelines. We'll reach out if we have questions about API, behavior, etc :)
Is your feature request related to a problem? Please describe.
Currently, the
oneHotEncoding
function allows you to encode a variable into a list-like object. However, if used on a multi class target variable that is stored as a string (4 classes in my case), thenodeClassification
function is unable to predict using the resulting list-like object. Forcing you to resort manually encoding the variable viaCASE
statements.Describe the solution you would like
Allow for
nodeClassification
to use a one hot encoded list-like object as a target variable.The text was updated successfully, but these errors were encountered: