-
Notifications
You must be signed in to change notification settings - Fork 0
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
should include 5 different expriment for each learner #8
Comments
I think in the Testing Phase2, you should SMOTE both training and tuning. On Sun, Nov 29, 2015 at 2:04 PM, Wei Fu notifications@github.com wrote:
Regards, Vivek Nair |
I can do that, but somehow, it seems overffiting. use testing data as training data again... I don't know, I will try that when the whole framework works. |
@timm Phase1 would be exactly as described by @WeiFoo. In Phase2, he seems to be only using the training data where as in the baseline approach he is using both training data as well as tuning data(assuming that traning_data + tuning_data = baseline_training_data). It seems to be as this approach gives the baseline approach an undue advantage of having more data to train on (assuming that there are some classes missing from the training_data in the SMOTEing phase) |
traning_data + tuning_data = baseline_training_data this is right! for baseline experiment, baseline trainning data is used for training. @vivekaxl You suggest use A+B, the same baselin_tranining_data for phase 2, here, my concern is, the parameters got from tuning is not based on B as part of training data during tuning, B actually was tuning testing data. If inlucding B for phase 2, do the parameters for SMOTE work well? it seems not fair for SMOTE, because you give some extra data that never used as training data. How could we expect the tuned SMOTE work well? my point is, for baseline and tuning experiment, I used the same amount of data to build learner before prediciton, but in different ways:
Yes, here, we're trying to make a balance and don't give any advantage to each part. |
go. do. |
The text was updated successfully, but these errors were encountered: