-
Notifications
You must be signed in to change notification settings - Fork 39
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
error converting StreamPETR to onnx #63
Comments
Hi @rod409, could you please provide the versions of the packages you are using? Like torch, onnx, onnxruntime etc |
Here are package versions I have
|
I also tried to upgrade to pytorch 1.10. I got different errors related to dimensions. torch 1.10 output
Here are the packages in this environment:
|
Can you try torch 1.12? |
Thanks I got it to work with 1.12. |
Hello, @rod409! I have met this problem too. Could you please show me the versions of the packages you are using in Torch 1.12? Thanks! |
it is almost the same as before just with updated torch packages.
|
I'm very surprised that the python packages in my conda env are exactly the same as those you list, but I still can't run it. |
I have created a new conda env and config it according to StreamPETR/docs/setup.md with torch 1.9,and then updated to torch1.12.1+cu116. I have succeeded after reinstall numpy by conda install. I think the problem may be that the version of mmcv-full、numpy and numba match. @rod409 `s version reference is very useful. Thank you so much, @rod409 ! |
Follow the steps to convert StreamPETR to onnx, I get two error. The first I can get past.
The errors occur when converting the head of the model
CUBLAS_WORKSPACE_CONFIG=:4096:8 python tools/pth2onnx.py projects/configs/test_speed/stream_petr_r50_704_bs2_seq_428q_nui_speed_test.py --section pts_head_memory
I got past this first one by setting the opset to 11 in the pth2onnx.py file. After doing so I run into this error
Are there additional steps or requirements in the setup? I'm not sure what is causing a type issue here.
The text was updated successfully, but these errors were encountered: