-
Notifications
You must be signed in to change notification settings - Fork 117
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
Points for sampler #7
Comments
I think you're right. I also found this issue when running the code. I think it only effects "Resample" and can be fixed by adding a line after the "ImbalancedDatasetSampler" is created to make sure the dataloader use the created sampler. |
Thank you for the quick response! |
You should probably wait for the author's response before closing the issue though I think you're right about the question. And it's also better to keep the issue opened before the code is updated. |
@AlanChou Thank you for the another reply! |
The same question for me. I found it rejected to change the sampler of train_loader after initialization(because the sampler affects shuffle, etc.), so I wonder if I should:
|
Thanks for sharing your great job.
I have a question about the point for sampler in your code.
train_sampler is first declared at L167 in cifar_train.py then, train_loader gets the sampler in L169-171.
This seems to be fine in itself. But in the middle of training(train+validation) there is a part which seems to be for sampler in L186-L208. I understand this part is need for LDAM and DRW, but I think this new train_sampler object does not affect train_loader.
How's your opinion?
Thnks!
LDAM-DRW/cifar_train.py
Lines 186 to 208 in 3193f05
The text was updated successfully, but these errors were encountered: