ENH: add option in OneVsRest classifier to handle undefined predictions #31448
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ns according to the user's preferences
…elevant assertion error
772e33f to
f340aba
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reference Issues/PRs
Fixes #31224. See also #31228 that made a bug fix related to the same area.
What does this implement/fix? Explain your changes.
This gives the user control over how undefined predictions are handled in OneVsRest classifiers. There are a new parameter that can take 4 different options. See the docstring for what they are and what they enable.
Any other comments?
I wasn't so sure what to do with the case where OneVsRest is used with a binary target. Any input would be appreciated.