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
Their readme clearly states that it handles cateogircals yet the input_scitype is marked as Continuous and it indeed seems that it does not in fact handle categoricals because it needs to be able to define a isless operation?
I think this has now been clarified at the above thread. The DecisionTree input_scitypes could be updated to Table(Continuous, OrderedFactor, Count) but with a comment in the doc-string that coercion of OrderedFactor columns to Count or Continuous may lead to better performance, without affecting outcomes.
To be clear, Multiclass is not strictly supported. If such data is coerced to one of the other ordered types, by choosing an ordering, then the outcome of training will depend on that choice.
Their readme clearly states that it handles cateogircals yet the
input_scitype
is marked as Continuous and it indeed seems that it does not in fact handle categoricals because it needs to be able to define aisless
operation?Opening an issue on DecisionTree as well for clarifications: https://github.com/bensadeghi/DecisionTree.jl/issues/92
The text was updated successfully, but these errors were encountered: