-
Notifications
You must be signed in to change notification settings - Fork 87
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
CUDA/CPU transfer error #2
Comments
Hi @rotobash thanks for submitting an issue. I have reproduced the error - it is due to Also, perhaps a better API design would be to allow users to explicitly set a device to use, rather than automatically using GPU if available. I'm working on it and will open a PR soon :) |
Hi again @rotobashm, the fix has been merged and the updated package is published as Let me know whether the issue gets solved, so I can close this :) |
Hi @MisaOgura, so sorry for the delay I hadn't had a chance to look at this till now. This seems to solve the cuda transfer issue for the one model I tried, I'll try some other models when I get a chance and let you know if I run into any issues. Thanks for the fix! |
Brilliant @rotobash - I would love to see |
Hi, I was interested in visualizing a CNN I created. I was following the example provided but when I try to use my model instead of a pretrained model from torchvision I get:
I looked through the source code a bit and saw that
Backprop
moves the network to cuda (if available) regardless if I move it there myself or not. Is this possibly a bug? I've had a bit of trouble with CUDA in the past so it might be a problem on my end.Thanks for your time, if there's any other information I can provide please let me know. Cheers.
The text was updated successfully, but these errors were encountered: