You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying out the training model creation on the MNIST-12 from here, when I set the loss to artifacts.LossType.CrossEntropyLoss,
it does something strange.
Even though the output label is of shape (1,10), it creates an input node called "labels" with shape of size (1)
Surely the labels shape should also be of size (1,10) ?
When using artifacts.LossType.MSELoss is creates an input node called "target" of shape (1,10) which is correct.
Is this a bug?
Edit:
I just realised that perhaps the label is not of the form (0,0,0,1,0,0,0,0,0,0) but just the index 4, in this case. Is this correct?
OK, I think I get it. you can delete this post.
To reproduce
AS above
Urgency
No response
ONNX Runtime Installation
Released Package
ONNX Runtime Version or Commit ID
1.15.1
PyTorch Version
1.13.1
Execution Provider
CUDA
Execution Provider Library Version
1.13.1
The text was updated successfully, but these errors were encountered:
Describe the issue
Trying out the training model creation on the MNIST-12 from here, when I set the loss to artifacts.LossType.CrossEntropyLoss,
it does something strange.
Even though the output label is of shape (1,10), it creates an input node called "labels" with shape of size (1)
Surely the labels shape should also be of size (1,10) ?
When using artifacts.LossType.MSELoss is creates an input node called "target" of shape (1,10) which is correct.
Is this a bug?
Edit:
I just realised that perhaps the label is not of the form (0,0,0,1,0,0,0,0,0,0) but just the index 4, in this case. Is this correct?
OK, I think I get it. you can delete this post.
To reproduce
AS above
Urgency
No response
ONNX Runtime Installation
Released Package
ONNX Runtime Version or Commit ID
1.15.1
PyTorch Version
1.13.1
Execution Provider
CUDA
Execution Provider Library Version
1.13.1
The text was updated successfully, but these errors were encountered: