-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
请问模型如何转换成onnx? #36
Comments
嗯,应该就是标准的转换流程吧。 |
按照标准流程走我导出失败了,代码如下:
输出信息如下: [WARNING 2022-02-14 11:07:35,808 _showwarnmsg:109] C:\Anaconda3\lib\site-packages\torch\nn\functional.py:3679: UserWarning: The default behavior for interpolate/upsample with float scale_factor changed in 1.6.0 to align with other frameworks/libraries, and now uses scale_factor directly, instead of relying on the computed output size. If you wish to restore the old behavior, please set recompute_scale_factor=True. See the documentation of nn.Upsample for details. [WARNING 2022-02-14 11:07:35,824 _showwarnmsg:109] K:\cnocr\cnstd-master\model\dbnet.py:243: TracerWarning: Converting a tensor to a NumPy array might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs! [WARNING 2022-02-14 11:07:35,874 _showwarnmsg:109] K:\cnocr\cnstd-master\model\dbnet.py:250: TracerWarning: torch.from_numpy results are registered as constants in the trace. You can safely ignore this warning if you use this function to create tensors out of constant variables that would be the same every time you call this function. In any other case, this might cause the trace to be incorrect. graph(): onnx大小只有1k,应该是有问题的。 |
No description provided.
The text was updated successfully, but these errors were encountered: