-
-
Notifications
You must be signed in to change notification settings - Fork 26.5k
FIX Adjust tags in RFE to allow nans by default #21807
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Can we bring this back to life? It's somewhat niche, but came up again organically with a |
|
@thomasjpfan wanna give this an update? happy to review. |
This reverts commit dbfce87.
|
This one is a little tricker. Consider the following two pipelines: pipe1 = make_pipeline(
SimpleImputer(),
StandardScaler(),
LogisticRegression(),
)
pipe2 = make_pipeline(
StandardScaler(),
LogisticRegression(),
)In both cases, the pipeline's first step accepts nans, but an imputer imputes the output and a scalar passes through the nans. This means |
adrinjalali
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I think it's okay to delay the errors / warnings to the step which actually has to deal with it anyway.
ogrisel
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's also test for RFECV but otherwise, LGTM.
Co-authored-by: Olivier Grisel <[email protected]>
Co-authored-by: Olivier Grisel <[email protected]>
Reference Issues/PRs
Fixes #21743
What does this implement/fix? Explain your changes.
This PR adjusts
RFEto allow nans by default and only changesallow_nanif the underlying estimator has tags.Any other comments?
I agree with #21743 (comment) for meta-estimators in general. I think meta-estimators should default to
allow_nan=True, unless proven otherwise.