evalml
evalml copied to clipboard
Update EvalML to be compatible with the new Woodwork `Boolean` inference
Woodwork updated their Boolean inference in this PR, with an additional update in this one.
This issue covers two main areas of change:
- Updating tests to be compatible
- Replacing instances of
y.ww.init()
withww.init_series(y)
- Replacing expected
int64
withbool
- Full list here
- Replacing instances of
- Updating component behaviour
-
CatBoostRegressor
-Target value "False" cannot be parsed as float
infit
-
LightGBMClassifier
andXGBoostClassifier
- Possibly an issue withLabelEncoder
inpredict
-
Oversampler
-SMOTENC
returned instead ofSMOTE
due to difference in expected categorical columns -
ClassImbalanceDataCheck
- Reverse mapping required to return the original values instead ofTrue/False
in data check details/message -
TargetLeakageDataCheck
- Issue when calculating dependence when features or target are inferred as boolean instead of int -
partial_dependence
- Inconsistent logical types when attemptingpred = prediction_method(X_eval)
-
TimeSeriesPipelineBase
- Attempting to use the old schema when reinitializingy
can lead to anincomaptible dtype
error in_drop_time_index
-
ClassificationPipeline
- Mapping issue inLabelEncoder
that results in incorrect mapping when_encode_targets
is called. The keys in the mapping dict can't be found so post mapping all values are converted toNaN
-