Bugfix stratify pretest sample #1004
Merged
Conversation
This file contains 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
added 2 commits
January 16, 2020 16:05
…alanced datasets pretest_* member variable are used to check dataset and pipeline compatibility. With highly imbalanced classification tasks the chance that a sample contains a single class arises. These changes ensure that at least one label for each class is included in the pretest dataset.
weixuanfu
suggested changes
Jan 17, 2020
|
Thank you for the PR. I merge this patch for a temp fix. |
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.
What does this PR do?
Fixes an edge case that arises when using tpot on dataset with extreme class imbalance where the pretest sample would cause an error to be thrown since the sample resulted in only one class being represented in the pretest_sample
Where should the reviewer start?
See the changes in the tpot base with the introduction of a init_pretest function and the corresponding implementation in the TPotClassifier
How should this PR be tested?
a unit test was added to verify that the pretest function works as intended
Any background context you want to provide?
see PR description
Questions: