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
I encountered an issue where the outputs of a model optimized using ONNX Runtime (opt_level=0/1/2/99) are inconsistent with the original unoptimized model. This inconsistency occurs specifically for the output v4_0, and the error is intermittent (flaky test), not occurring every time the model is run.
The following error message is seen when comparing the results of the optimized model with the original model:
AssertionError:
Not equal to tolerance rtol=0.001, atol=0.001
Mismatched elements: 2 / 22 (9.09%)
Max absolute difference: 1841117444
Max relative difference: 4.60279361e+08
x: array([[-1841117440],
[ 32646],
[ 3],...
y: array([[4],
[3],
[3],...
I suspect this could be related to precision loss or non-deterministic operations introduced during the optimization process. Could the team assist in analyzing the root cause of this discrepancy?
Describe the issue
I encountered an issue where the outputs of a model optimized using ONNX Runtime (opt_level=0/1/2/99) are inconsistent with the original unoptimized model. This inconsistency occurs specifically for the output
v4_0,
and the error is intermittent (flaky test), not occurring every time the model is run.The following error message is seen when comparing the results of the optimized model with the original model:
I suspect this could be related to precision loss or non-deterministic operations introduced during the optimization process. Could the team assist in analyzing the root cause of this discrepancy?
To reproduce
Urgency
No response
Platform
Linux
OS Version
Ubuntu 20.04
ONNX Runtime Installation
Built from Source
ONNX Runtime Version or Commit ID
5c1b7cc
ONNX Runtime API
Python
Architecture
X64
Execution Provider
CUDA
Execution Provider Library Version
No response
The text was updated successfully, but these errors were encountered: