szha edited a comment on issue #17676: [RFC] MXNet 2.0 API Deprecation URL: https://github.com/apache/incubator-mxnet/issues/17676#issuecomment-593574187 From: @samskalicky TensorRT support is currently using ONNX to convert from NNVM: https://github.com/apache/incubator-mxnet/blob/746cbc55fd666bb4529e88d247fed8e0907270f9/src/operator/subgraph/tensorrt/tensorrt.cc#L313-L318<https://github.com/apache/incubator-mxnet/blob/746cbc55fd666bb4529e88d247fed8e0907270f9/src/operator/subgraph/tensorrt/nnvm_to_onnx-inl.h> Although I would like to see TensorRT support moved away from ONNX with a native integration using the Accelerator API compile support: https://github.com/apache/incubator-mxnet/pull/17623. But the migration from ONNX to AccAPI is still in discussion and the compile support PR is not merged yet (shameless plug: please review! :-D) Sam On Feb 28, 2020, at 9:06 PM, JackieWu <[email protected]<mailto:[email protected]>> wrote: I think we should keep ONNX APIs, since it is able to export many basic models, although it is not perfect. Users will train their models in MXNet 2.0, and export ONNX model, then use the ONNX model in their deployment frameworks. (http://onnx.ai/supported-tools). It is useful to attract users to use MXNet 2.0 to train their models with ONNX. -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-mxnet/issues/17676#issuecomment-592878029
---------------------------------------------------------------- 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] With regards, Apache Git Services
