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.
As raised by @OlivierBinette in #2202, sklearn models can run correctly when supplied with additional columns (on top of the feature columns), while _DummyModel must receive exactly the feature columns. This may lead to confusion when implementing custom checks, as users may expect context.model.predict(dataset.data) to work.
Describe the solution you'd like
In these cases, the _DummyModel should raise an error explaining it expects to receive exactly the feature columns, and no more.
ItayGabbay
changed the title
[FEAT] Better error message when passing illegal columns to _DummyModel
[DEE-6] [FEAT] Better error message when passing illegal columns to _DummyModel
Jan 11, 2023
Is your feature request related to a problem? Please describe.
As raised by @OlivierBinette in #2202, sklearn models can run correctly when supplied with additional columns (on top of the feature columns), while _DummyModel must receive exactly the feature columns. This may lead to confusion when implementing custom checks, as users may expect
context.model.predict(dataset.data)
to work.Describe the solution you'd like
In these cases, the _DummyModel should raise an error explaining it expects to receive exactly the feature columns, and no more.
DEE-6
The text was updated successfully, but these errors were encountered: