New Balancing PipeOps based on smotefamily
#824
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
advieser
changed the title
smotefamily
mb706
reviewed
Sep 17, 2024
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.
Implements two new pipeops based on
smotefamily:PipeOpADAS: ADASYN algorithm for balancing data. New instances are created based on difficulty for learning.PipeOpBLSmote: Borderline-SMOTE algorithm for balancing data. New instances are created only for data ponts near the decision regions.Both PipeOps only work for classification tasks with numeric features that have no missing values and accept target columns with multiple classes (although only the class with the least instances is upsampled).
Both pipeops use the implementation from #815 for handling unsupported column types (so that has to be checked first).
Currently,
PipeOpBLSmoteprints[1] "Borderline-SMOTE done"after training. I'd think that we'd want to suppress this somehow, ideally?Both
smotefamily::BLSMOTEandsmotefamily::ADAScontain bugs as of right now, which should be fixed on the side ofsmotefamily. This includes a bug where tasks with one feature cannot be handled (due to subsetting of thedata.framereducing the data to a vector on whichnrow()is called which is then used in an if-statement).Partially addresses #790