You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mxnet.apache.org by GitBox <gi...@apache.org> on 2022/04/23 14:38:52 UTC

[GitHub] [incubator-mxnet] timprepscius commented on issue #20985: Is there onnx import support in 1.9.0

timprepscius commented on issue #20985:
URL: https://github.com/apache/incubator-mxnet/issues/20985#issuecomment-1107513672

   Ok.  Thanks for this response.
   
   Although, I understand my vote to be of basically no consequence - I would vote for MXNet to have an "approved" onnx importer.
   
   This is because you can not only verify MxNet's functioning, but also those of other platforms.  And you can have relative performance measurements.  (everyone runs the same model, who is faster, is anybody incorrect)
   
   For instance, MxNet used to have a bug in the CPU version, which affected some work I had with noise removal (I can find the mxnet issue if you'd like).  It was really hard to cope with because I assumed MxNet was correct.  I only found out MxNet wasn't correct because of the onnx importer.  As of now, I'm actually not sure if MxNet has fixed the bug, because I can no longer test.  And so, instead I'm using the ONNX runtime, which I could verify.
   
   Although I'm not sure of the overhead of the ONNX runtime, which I'm not so happy about.
   
   Anyhow, end babble, beep borp.
   


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@mxnet.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@mxnet.apache.org
For additional commands, e-mail: issues-help@mxnet.apache.org