Skip to content
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

[ENH] Custom Mixing of Oversamplers and Undersamplers #925

Closed
BradKML opened this issue Sep 11, 2022 · 1 comment
Closed

[ENH] Custom Mixing of Oversamplers and Undersamplers #925

BradKML opened this issue Sep 11, 2022 · 1 comment

Comments

@BradKML
Copy link

BradKML commented Sep 11, 2022

Is your feature request related to a problem? Please describe

Currently we are doing research on comparing classifiers' effectiveness on highly imbalanced data:
SVC(kernel="linear", C=0.025), SVC(gamma=2, C=1), GaussianProcessClassifier(1.0 * RBF(1.0)), GaussianNB(), QuadraticDiscriminantAnalysis().
Applied against the following Oversamplers:
SMOTE(), SMOTEN(), ADASYN(), KMeansSMOTE(), SVMSMOTE()

Problem: The credit card fraud dataset has a 1-to-1000 difference https://www.geeksforgeeks.org/ml-credit-card-fraud-detection/

Describe the solution you'd like

Being able to input an oversampler and an undersampler as input for creating SMOTEENN/SMOTETomek-like data. Currently through understanding other tutorials of binary classifiers, that:

  1. If the majority and the minority forms an N-to-1 ratio, then the Oversampler should take a float that is less than 1/N
  2. Afterwards the minority sampler defaults to having sampling_strategy=0.5

Currently I use float(5*sum(y)/y.size) to expand the size of the minority class to be five times its size.

Describe alternatives you've considered

I do not understand why SMOTEENN or SMOTETomek can be combined to a single algorithm without a clear way of having a generic pipeline.

Additional context

https://machinelearningmastery.com/combine-oversampling-and-undersampling-for-imbalanced-classification/

@hayesall
Copy link
Member

hayesall commented Nov 6, 2022

See #328 and #787

@hayesall hayesall closed this as completed Nov 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants