-
Notifications
You must be signed in to change notification settings - Fork 24
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
Thank for your work! Please comment,when training ,report another error. #2
Comments
Thank you for reporting! Could you please provide the full error trace? Thank you. (It is always ideal to have the CUDA_LAUNCH_BLOCKING=1 flag when running, so any low-CUDA errors shall be triggered) |
Thank you for you reply! The complete error appears below. |
@matyasbohacek Hi have you resolved this error ? I am also getting the same error |
I'm having the same problem, is there a solution for it? |
Hey, I have found a solution! Go to
That -1 is the cause of our problems, because while working with WLASL100, labels go from 0 to 99 and, as a result, when we call the class Taking that into account, the following fix worked for me:
Hope this helps! :D |
RuntimeError: CUDA error: device-side assert triggered.
` for i, data in enumerate(dataloader):
inputs, labels = data
# inputs, labels = Variable(inputs), Variable(labels)-1
inputs = inputs.squeeze(0).to(device)
labels = labels.to(device, dtype=torch.long)
The text was updated successfully, but these errors were encountered: