-
Notifications
You must be signed in to change notification settings - Fork 17
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
ocrd_all - Release v2023-06-14 - issue with GPU #375
Comments
that's before the recent fixes in #362 and OCR-D/core#1041 Please use the most recent version. Also, IMO the report should go to ocrd_all repo, not here. (There's a test-cuda target there, too.) |
Sorry, for using wrong repo ... |
ok, I guess you did use the current version after all. From the title of the issue it sounded like an older checkout. (Current tip is d8cdeec. The most recent tag is
That's not the correct procedure after an update, though. You first have to make sure your submodules are up to date. Doing Can you check with
Yes, that's the best way to do it. The version identifier recipe in ocrd_detectron2 picks whatever matches first, unless using this override. Alas, at the moment we cannot guarantee that ocrd_kraken and ocrd_typegroups_classifier (which also depend on Pytorch) do not overwrite with their version. Best way to check is
Sounds like an issue with your checkout. It could be the ownership problem alluded to above, or some previous failure. Strange though that despite git's complaint, it does not exit with error and does in fact recurse...
That variable is only relevant at install time – it has no effect on the test itself.
ok, so apparently somewhere in your environment you have an dynamic linker override variable Could you please check where that variable is coming from? (I.e. bashrc or profile or venv..., and who installed that, e.g. CUDA installer script, or manual) |
Many thanks @bertsky for your detailed comments. I will follow your advice and come back with another feedback ... |
and
Concerning
Yes, it is set in
Well, of course I could change this, but I have no idea, where the 11.8 version was installed to - see:
For both folders
A
--> So, please tell me, where I can find the version 11.8 Anyway, I will do re-install now, following your @bertsky advises from above. |
Hmm, not good ...
Then, I just have called
--> it looks like there simply no exists the
-> any recommendation? |
Have a look at the
So all you need to do AFAICS (while using ocrd_all) is to suppress your
There have been merges with additional improvements, but no new release yet (which I guess is normal dev cycle, so I'm surprised you're surprised...).
That was I had suspected. Only strange that the So please (There's no need to re-do
Looks like follow-up errors. To be on the safe side, |
Looks like I made it :-) |
Splendid. So to recap:
BTW, to be on the safe side, consider running |
Concerning "recap":
Concerning
Should I create another issue for this? (or re-open this one?) |
yes, that's sufficient (for that task). In general,
Yes, please do. (This is new.) https://github.com/qurator-spk/sbb_binarization/ would be best fit IMO. Please also explain what version of the model you have installed (e.g. |
@bertsky :
--> should I try with |
Looks like you instrumented the code... |
yes, you are right. |
Hi,
I just have installed the
ocrd_all
Release v2023-06-14, and it looks like I have an issue with GPU/CUDA.Hint: I use
Ubuntu 22.04.1
In detail:
I have downloaded latest version with:
Then I have made:
I have created a new VENV like this:
(Remark: Python 3.8 was already available using "deadsnakes" repo)
Next I have done the "main make" like this:
--> I have used this "CUDA_VERSION" parameter, as on my system somehow CUDA-Version 11.6 is the default, and I have seen, that CUDA-Version 11.8 was installed with
sudo make deps-cuda
.This has run successfully with one remark:
Somewhere in between I have seen this error message:
--> Nevertheless this make has run through successfully.
(but maybe I have overlooked more "hidden" errors like this).
If I now do
make test-cuda
(in this VENV) I get this error:(I get the same error without using parameter "CUDA_VERSION")
At least:
My standard test workflow works find (but does not use the GPU).
The text was updated successfully, but these errors were encountered: