-
Notifications
You must be signed in to change notification settings - Fork 10
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
About ge-spmm's pytorch-custom #10
Comments
It should work together with cudatoolkit v10.1. Try this inside your Python environment |
I don't have anaconda, I only have python3.8 under ubuntu, all the previous operations ran through and only this sentence is a problem. Can I have any other options? |
Testing the successful installation, why did this happen when running the gcn_custom_2layer.py file?Please ask for help. |
Hi @GugaGugaGuga, the error occurs because cusparse in cuda11 and cuda10 have different APIs, so what matters is CUDA Toolkit version. Can you try |
Yes,the output is 10.1. I know |
Sorry, the
when the shared library is jit-compiled. In my case it is through Note that you may need to clean the compilation cache and run again to see this logging, in your case you need to delete your folder |
Listening to your answer, I was deleted folder /tmp/torch_extensions/spmm, and is still the case. |
I cannot reproduce the error... Is your LD_LIBRARY_PATH including your /usr/local/cuda-10.1/lib64 ? |
Yes |
Since I cannot reproduce the environment problem, I suggest you use a docker image that I test fine. This is the easiest way. The image pytorch/pytorch:1.4-cuda10.1-cudnn7-devel will work for this repo. |
Do I need to download cudnn, and if so, what version? |
The code does not depend on cudnn, only cusparse, which comes together with cuda toolkit (we need version <= 10.1). Again I suggest using docker to solve environment problem, and pytorch/pytorch:1.4-cuda10.1-cudnn7-devel image should work. |
When I run
"python3.8 gcn_custom_2layer.py --n-hidden=32"
, the following situation occurred:Please help me how to run through next.
The text was updated successfully, but these errors were encountered: