Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

MXNet model export to ONNX failed #18776

Open
xizi opened this issue Jul 23, 2020 · 5 comments
Open

MXNet model export to ONNX failed #18776

xizi opened this issue Jul 23, 2020 · 5 comments
Labels
Bug ONNX v1.x Targeting v1.x branch

Comments

@xizi
Copy link

xizi commented Jul 23, 2020

export rnn.GRU op failed, error message as follow:
AttributeError: No conversion function registered for op type _rnn_param_concat yet.

@szha szha added ONNX v1.x Targeting v1.x branch and removed needs triage labels Jul 23, 2020
@szha
Copy link
Member

szha commented Jul 23, 2020

Thanks for reporting. We are removing that op in the RNN layer in the 2.0. It will need to be registered in 1.x. That operator should be registered as simple concatenation for ONNX.

@xizi
Copy link
Author

xizi commented Jul 24, 2020

Thanks for reply. Can your provide some references show how to register _rnn_param_concat op as concatenation.

@szha
Copy link
Member

szha commented Jul 25, 2020

@xizi
Copy link
Author

xizi commented Jul 29, 2020

After installed mxnet2.0 build from source. export model error:
NotImplementedError: Only LSTM mode RNN conversion to ONNX is currently supported.

@szha
Copy link
Member

szha commented Jul 29, 2020

cc @josephevans
conversion of other RNN types will need to be added.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug ONNX v1.x Targeting v1.x branch
Projects
Development

No branches or pull requests

2 participants