-
Notifications
You must be signed in to change notification settings - Fork 11
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
CUDA out of memory / cannot disable CUDA #61
Comments
Like so often (with this module), the problem runs deeper. Even if you:
Thus, IMO there's no way to run the dewarper without GPU, or with a CUDA-enabled GPU with "only" 4GB RAM. |
Thanks for trying and detailling how it fails. I will refactor the tool to at least properly integrate pix2pixHD repo as a submodule, installed with the tool and take a look at the parameter handling.
I have no access to GPU at all, so I cannot test (unless I the cpu variant working) but at least these glaring shortcomings can be fixed. |
fixed by #89 |
On a CUDA-enabled system with more than 3GB of GPU memory currently free, I get this from
dewarp
:Frankly, this does not make any sense to me.
However, I thought, at least I should be able to disable GPU computation. The only parameter that can influence Pytorch setup in dewarp is
gpu_id
, which would need to be set to'cpu'
. But the tool JSON requires this to be a number!The text was updated successfully, but these errors were encountered: