[BUG] Tensor for argument #2 'mat1' is on CPU, but expected it to be on GPU (while checking arguments for addmm)
See original GitHub issueSimilar to #453, but training NBEATS() with a val_series, I am getting:
RuntimeError: Tensor for argument #2 'mat1' is on CPU, but expected it to be on GPU (while checking arguments for addmm)
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Tensor for argument #2 'mat1' is on CPU, but expected it to be ...
It seems some of my variables should be defined in another way to be able to be executed on GPU. My questions: How...
Read more >Debugging Runtime Error: Tensor for argument #2 'mat1' is on ...
Debugging Runtime Error: Tensor for argument #2 'mat1' is on CPU, but expected it to be on GPU (while checking arguments for addmm)....
Read more >Tensor for argument #2 'mat1' is on CPU, but expected it to be ...
RuntimeError : Tensor for argument #2 'mat1' is on CPU, but expected it to be on GPU (while checking arguments for addmm) #90....
Read more >Tensor for argument #2 'mat1' is on CPU, but expected it to be ...
Tensor for argument #2 'mat1' is on CPU, but expected it to be on GPU (while checking arguments for addmm). 需要将模型和输入数据都移动到 ...
Read more >runtimeerror: expected all tensors to be on the same device ...
Expected all tensors to be on the same device, but found at least two devices, cpu and cuda:0! (when checking argument for argument...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hm, no, that’s not it… But I’ll try to do a fresh install of darts tomorrow. Hopefully, that’ll fix it!
Great 👍