-
-
Notifications
You must be signed in to change notification settings - Fork 25.9k
Handling out-of-bounds in IsotonicRegression (clean PR #3147) #3199
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
Handling out-of-bounds in IsotonicRegression (clean PR #3147) #3199
Conversation
nice ! +1 for merge |
bounds_error=False) | ||
|
||
# Clip out-of-bounds values if requested. | ||
if self.out_of_bounds == "clip": |
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.
This is alright, but seems a little strange to not be handled as an elif in the clause above, seeing as it's mutually exclusive from raise
and nan
. In this context, I think it's fine to reuse the name T
for the clipped data.
Mostly looks fine, but I think you should structure that |
LGTM 👍 |
Handling out-of-bounds in IsotonicRegression (clean PR #3147)
Here's a clean, follow-up PR based on the other Isotonic merges today and conversation from PR #3147.
out_of_bounds
Argument behavior
Let me know if you want to see L296-310 differently. I'd like to clean up
fit
vs.fit_transform
and some of the matrix/vector notation mismatch in the module anyway.(My interpretation is also that there is no need for
f
to be created anew on each call totransform
.)