mcourse1993 opened a new issue #20394:
URL: https://github.com/apache/incubator-mxnet/issues/20394


   ## Description
   (A clear and concise description of what the bug is.)
   I tried to convert my mxnet model into onnx and by using the recent release 
version of mxnet and its library, I didn't change my mxnet version, 
1.7.0.post2, I added and reformed my former files in the mx2onnx folder based 
on files provided 
here(https://github.com/apache/incubator-mxnet/tree/v1.9.x/python/mxnet/onnx/mx2onnx)
 but I encountered this error
   ### Error Message
   (Paste the complete error message. Please also include stack trace by 
setting environment variable `DMLC_LOG_STACK_TRACE_DEPTH=100` before running 
your script.)
   index_lookup = kwargs["index_lookup"]
   KeyError: 'index_lookup'
   ## To Reproduce
   (If you developed your own code, please provide a short script that 
reproduces the error. For existing examples, please provide link.)
   
   ### Steps to reproduce
   (Paste the commands you ran that produced the error.)
   
   1. I provided the model below.
   2. 
https://drive.google.com/file/d/13_fmDpkD7IyZAP5HWbwAdmAsonFQ34vm/view?usp=sharing
   2.
   
   ## What have you tried to solve it?
   
   1.
   2.
   
   ## Environment
   
   ***We recommend using our script for collecting the diagnostic information 
with the following command***
   `curl --retry 10 -s 
https://raw.githubusercontent.com/apache/incubator-mxnet/master/tools/diagnose.py
 | python3`
   
   <details>
   <summary>Environment Information</summary>
   
   ```
   # Paste the diagnose.py command output here
   ```
   
   </details>
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to