-
Notifications
You must be signed in to change notification settings - Fork 250
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
RuntimeError: expected scalar type Long but found Int #71
Comments
I have encountered this problem, how to solve it |
oh me too |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
D:\anaconda3\envs\pytorch114\lib\site-packages\torch\optim\lr_scheduler.py:134: UserWarning: Detected call of
lr_scheduler.step()
before `optimizer.stFile "train.py", line 202, in
train_model()
File "train.py", line 137, in train_model
loss = criterion(outputs, labels)
File "D:\anaconda3\envs\pytorch114\lib\site-packages\torch\nn\modules\module.py", line 889, in _call_impl
result = self.forward(*input, **kwargs)
File "D:\anaconda3\envs\pytorch114\lib\site-packages\torch\nn\modules\loss.py", line 1048, in forward
ignore_index=self.ignore_index, reduction=self.reduction)
File "D:\anaconda3\envs\pytorch114\lib\site-packages\torch\nn\functional.py", line 2690, in cross_entropy
return nll_loss(log_softmax(input, 1), target, weight, None, ignore_index, None, reduction)
File "D:\anaconda3\envs\pytorch114\lib\site-packages\torch\nn\functional.py", line 2385, in nll_loss
ret = torch._C._nn.nll_loss(input, target, weight, _Reduction.get_enum(reduction), ignore_index)
RuntimeError: expected scalar type Long but found Int
The text was updated successfully, but these errors were encountered: