-
Notifications
You must be signed in to change notification settings - Fork 34
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
Install issue Ubuntu 18 #19
Comments
I managed to get it to work by manually downgrading to pip install tensorflow==2.3 Maybe this could be integrated into the dependency management of pip? |
The pyronn package need to be build against a specific Tensorflow version. The current packages in the pip repository are built against TF 2.3 with CUDA 10 . Currently, there are some problems with the bazel configuration preventing a version for Tensorflow 2.4 with Cuda 11 . I agree, that this should be inetragted in the dependency management, or at least the supported and working version combinations should be statet in this repository for clarification. |
@mareikethies While we are at it: Maybe the windows-binary can be made available via pip as well? I made my build available here: https://github.com/maxrohleder/win-pyronn |
Hi, I encountered the same problem... |
@cocoakang You would have to recompile the layers with your desired cuda version. In theory that's not a problem if you feel comfortable with the tf build pipeline. |
I've built a CUDA11 version against TF 2.5, it currently supports only py3.6 (I'm still working on newer versions), but the patches needed by CUDA 11 should be almost the same. |
When installing pyronn like so:
On my system:
cuda 10.1
andcudnn8.0.4
I tested the installation:
python -c "import tensorflow as tf;tf.config.list_physical_devices('GPU');import pyronn"
I get the following log/error:
First I had
cuda 11.1
installed, but then I got this error:, which made me assume, that cuda 10.1 is needed by the pyronn-layers.
I suspect, that the layers were built against a specific tf version. This thread suggests that the error code implies this. Which version were the layers build against? (Maybe I am missing something) Could this be taken care of by the setup wheel?
The text was updated successfully, but these errors were encountered: