masahi edited a comment on issue #8140:
URL: https://github.com/apache/tvm/issues/8140#issuecomment-857175926
The reproduction I got locally was due to a tie in scores. The top 2 scores
have identical scores but the order is swapped between TF / TVM:
```
Mismatched elements: 8 / 256 (3.12%)
Max absolute difference: 1.8291236
Max relative difference: 21.120028
x: array([[[ 0.613913, -0.086606, 0.650708, 0.433798],
[ 0.398791, 1.742517, 1.710477, 0.569614],
[ 0.736459, 0.409182, 0.026915, -0.968162],...
y: array([[[ 0.398791, 1.742517, 1.710477, 0.569614],
[ 0.613913, -0.086606, 0.650708, 0.433798],
[ 0.736459, 0.409182, 0.026915, -0.968162],...
```
@trevor-m I wouldn't call it a bug, since neither TF or ONNX specifies what
the order should be when there is a tie. In particular, TVM uses stable sort,
while it seems TF uses unstable sort for NMS. I confirmed this based on
comparing input and output box coordinates.
Probably we should change the test code to make sure there would be no ties
in scores.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
