-
Notifications
You must be signed in to change notification settings - Fork 25
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 does not 'train' ,aborts #85
Comments
I also had a question regarding the tile shape (px) settings. As I am using a caffe framework on CPU I am little confused about the x and y entries for the tile shape (px). I have a CPU of Intel(R) Core(TM) 17-10700CPU @2.90 GHz and a GPU 0- Intel(R) UHD Graphics 630. |
The finetuning problem stems from using the caffe_unet binary which does not support training, for this the regular caffe binary is used. Check your IJPrefs.txt and correct the caffe binary entry to point to caffe, not caffe_unet. |
Well CPU upper limits are defined by the available amount of RAM, but I would not go too large, it becomes awfully slow. |
If you don't need the systemwide installed caffe, I would recommend to deinstall it, then the caffe binary shipped with caffe_unet should be automatically found and used. Otherwise you can edit ~/.imagej/IJPrefs.txt (maybe it is in .config) and just explicitly replace the unet.caffe_binary by /home/kumar/u-net/bin/caffe. If you really don't find it, try |
Or put /home/kumar/u-net/bin at the beginning of your PATH environment variable, then your system caffe is only found if explicitly called using /usr/bin/caffe. |
I installed the backed server on an Ubuntu 18.04 Virtual machine ( Oracle VM) and i have tried following the instructions in the video for segmentation, finetuning and detection but unfortunately finetuning doesn't work and aborts after showing an error.
I use the binaries provided at https://lmb.informatik.uni-freiburg.de/resources/opensource/unet/caffe_unet_package_18.04_cpu.tar.gz
Finetuning does not even start, aborting with the following
The log output :
I used the following settings:
The text was updated successfully, but these errors were encountered: