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
int64withbool - Full list here
- Replacing instances of
- Updating component behaviour
CatBoostRegressor-Target value "False" cannot be parsed as floatinfitLightGBMClassifierandXGBoostClassifier- Possibly an issue withLabelEncoderinpredictOversampler-SMOTENCreturned instead ofSMOTEdue to difference in expected categorical columnsClassImbalanceDataCheck- Reverse mapping required to return the original values instead ofTrue/Falsein data check details/messageTargetLeakageDataCheck- Issue when calculating dependence when features or target are inferred as boolean instead of intpartial_dependence- Inconsistent logical types when attemptingpred = prediction_method(X_eval)TimeSeriesPipelineBase- Attempting to use the old schema when reinitializingycan lead to anincomaptible dtypeerror in_drop_time_indexClassificationPipeline- Mapping issue inLabelEncoderthat results in incorrect mapping when_encode_targetsis called. The keys in the mapping dict can't be found so post mapping all values are converted toNaN