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
MAINT change default value for min/max of IterativeImputer #16493
Conversation
Dropping support for |
IterativeImputer is still experimental. In addition, |
@DarshanGowda0 You need to resolve the conflict |
IterativeImputer is still experimental. In addition, None was the default
and it was defaulting on either -inf or +inf which we are replacing it by.
I think that we should be fine with both combined reasons. WDYT?
+1
|
Yes, definitely, I missed that it was still experimental. |
I solved the conflicts. |
Please add an entry to the change log at doc/whats_new/v0.23.rst under the section |
@@ -602,9 +602,9 @@ def fit_transform(self, X, y=None): | |||
self.n_iter_ = 0 | |||
return super()._concatenate_indicator(Xt, X_indicator) | |||
|
|||
self._min_value = IterativeImputer._validate_limit( | |||
self._min_value = self._validate_limit( |
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.
For reviewer: I made this change just for style because I find this weird.
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
Reference Issues/PRs
Fixes #16490
What does this implement/fix? Explain your changes.
Changed the default value of max and min to
np.inf
and-np.inf
respectively.