-
Notifications
You must be signed in to change notification settings - Fork 5
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
detectron2 vs CUDA dependency #7
Comments
CUDA version 11.2 (default for Debian stable) is also unsupported. |
OCR-D CUDA docker images use CUDA version 11.3. |
That's due to the changes I introduced since I wrote this. They support all CUDA versions.
Yes, so it seems. I have two options now: add that case to the CPU fallbacks, or run with the Pytorch for that platform and introduce a fallback source build for Detectron2. I tend towards the latter, as it would also cover other platforms. |
I just had a failing build on Debian stable with Python 3.7 and CUDA version 11.4. What about building from source as a fallback as you already suggested above? |
If it worked for you, that's sheer luck I'm afraid. I get:
Facebook Research has obviously failed to set up the package in a way that either EDIT: just found this issue describing the problem I am at a loss what we should do going forward TBH. |
It seems the latest versions we can get any
detectron2
for are:detectron==0.6
[Python 3.6-3.9]detectron==0.6
[Python 3.6-3.9]detectron==0.5
[Python 3.6-3.8]detectron==0.6
[Python 3.6-3.9]detectron==0.6
[Python 3.6-3.9]detectron==0.2.1
[Python 3.6-3.8]What a mess! So as with Tensorflow, older CUDA versions quickly tend to not get supported. It's not as bad regarding Python version ranges, but CUDA 10.0 – which still is OCR-D's main target platform for CUDA builds – is out.
The text was updated successfully, but these errors were encountered: