Open Azyka opened 1 year ago
This issue has been automatically marked as stale due to inactivity and will be closed in 7 days if no further activity occurs. If further support is needed, please provide an update and/or more details.
@Azyka this might be fixed after https://github.com/pytorch/pytorch/pull/96320 if you set torch.onnx.export(..., keep_initializers_as_inputs=True
Try it out and let us know how it goes
@Azyka this might be fixed after pytorch/pytorch#96320 if you set
torch.onnx.export(..., keep_initializers_as_inputs=True
Try it out and let us know how it goes
@thiagocrepaldi I tried the keep_initializers_as_inputs=True
with the latest torch version, and the error still exists.
=========================
onnxruntime_enable_opt triggers assertion
Not equal to tolerance rtol=1e-07, atol=0
Mismatched elements: 1 / 1 (100%)
x: array(True)
y: array(False)
=========================
=========================
onnxruntime_disable_opt does not trigger assertion
=========================
This issue has been automatically marked as stale due to inactivity and will be closed in 30 days if no further activity occurs. If further support is needed, please provide an update and/or more details.
Describe the issue
ONNX opset version: 14 When 2 duplicate nodes(which have the same inputs and outputs) of torch.Tensor.to are defined, the model produce wrong results after ort optimization.
To reproduce
Model code:
Output:
Model0 produces array(True) after optimization, which is supposed to be array(False).
Urgency
This is an incorrect functionality implementation. It may cause severe bugs for those systems on the top of ORT.
Platform
Linux
OS Version
Ubuntu 22.04.3 LTS (x86_64)
ONNX Runtime Installation
Released Package
ONNX Runtime Version or Commit ID
1.15.1
ONNX Runtime API
Python
Architecture
X64
Execution Provider
Default CPU
Execution Provider Library Version
No response