Skip to content
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

Finetuning can't find 'train', aborts #19

Closed
jlause opened this issue Feb 13, 2019 · 5 comments
Closed

Finetuning can't find 'train', aborts #19

jlause opened this issue Feb 13, 2019 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@jlause
Copy link

jlause commented Feb 13, 2019

Dear all,

I moved to GPU for finetuning, using the following setup:

Server: CUDA 10.0, cuDNN 7, Ubuntu 18, running within a docker container into which I ssh
Client: Ubuntu 16

I use the binaries provided at https://lmb.informatik.uni-freiburg.de/resources/opensource/unet/caffe_unet_package_18.04_gpu_cuda10_cudnn7.tar.gz

Segmentation and Detection work fine with this setup. However, finetuning does not even start, aborting with the following error:
image
The log output:
image
I use the following settings:
image

Thanks in advance for any hint what I might be doing wrong. If you need more details to reproduce, let me know!
Cheers, Jan.

@ThorstenFalk ThorstenFalk added the bug Something isn't working label Feb 13, 2019
@ThorstenFalk ThorstenFalk self-assigned this Feb 13, 2019
@ThorstenFalk
Copy link
Collaborator

Interesting, this is a bug in the caffe binary check, I did not expect that the empty string as command would pass... I'll fix it asap

ThorstenFalk added a commit that referenced this issue Feb 13, 2019
Empty strings in the preferences for caffeBinary and caffe_unetBinary
now lead to initialization with the plain binary name without path.
@ThorstenFalk
Copy link
Collaborator

Please try the latest version. It should reset your caffeBinary path to "caffe" and will present the dialog for entering the full path if caffe is not in your PATH envrionent.

@jlause
Copy link
Author

jlause commented Feb 13, 2019

Ok great, thanks a lot for the fast reply and fix!

Sorry for the naive question: Do I have to build from source then or will you also update the pre-build binaries on https://lmb.informatik.uni-freiburg.de/resources/opensource/unet/ ?

@ThorstenFalk
Copy link
Collaborator

The bug is only plugin-related, simply get the latest version using Help->Update.

@jlause
Copy link
Author

jlause commented Feb 15, 2019

great, fixed it for me, thanks for the fast support!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants