Fix AutoMLSearch to only threshold pipelines when problem is binary classification#1622
Merged
Fix AutoMLSearch to only threshold pipelines when problem is binary classification#1622
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1622 +/- ##
=========================================
+ Coverage 100.0% 100.0% +0.1%
=========================================
Files 240 240
Lines 18160 18177 +17
=========================================
+ Hits 18152 18169 +17
Misses 8 8
Continue to review full report at Codecov.
|
bchen1116
requested review from
ParthivNaresh,
angela97lin,
dsherry and
jeremyliweishih
dsherry
reviewed
Dec 29, 2020
dsherry
approved these changes
Dec 30, 2020
Contributor
dsherry
left a comment
dsherry
left a comment
There was a problem hiding this comment.
LGTM! Please wait until after the Dec release to merge.
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
fix #1573