-
Notifications
You must be signed in to change notification settings - Fork 30
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
dataloader num_workers=0 #7
Comments
As described in our paper, we utilize the straight-throught trick. Therefore, we only need to apply the image opeartion with maximum probability. |
so this means we cannot set num worker > 0 ? have to confirm single process reader? |
Hi, I tried num workers > 0, and got this error:
I think it is because the getitem function of AugmentDataset uses the parameters of Network in model_search.py including magnitudes, weights, probilities, which are cuda tensors. |
This code do not support num_workers > 0, since the data loader need to sample the policy according to the parameters "magnitudes, probabilities", which are different in every iteration. |
Whats the point of DADA being faster if it can only operate with num_workers = 1. It would still be slower than Fast or Faster AutoAugment with num_workers = 12. Its not like most people use single CPU processor cores. |
Would it not be possible to set num_workers to a higher value and sample each batch based on magnitude/probabilities? within iteration, it would be the same |
hi, it seems that in DADA, dataloader num_workers have to be 0 in order to avioding mislocation between gradient and actual augment parameters.
But if num worker ==0, the speed advantages of DADA cannot be shown if comparsion with PBA. So do you have some trick to deal with this issue?
The text was updated successfully, but these errors were encountered: