-
Notifications
You must be signed in to change notification settings - Fork 18.7k
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
Finetune using whole images instead of bounding boxes #631
Comments
Hi, |
Make your new leveldb of input images and labels. Change the leveldb source Le jeudi 10 juillet 2014, caffecuda [email protected] a écrit :
Evan Shelhamer |
@shelhamer Thanks for the response. That's basically what I did, only that I didn't start from scratch and adapted the prototxt files in "pascal-finetuning/". The question is whether to keep these fields:
If they are kept I get: libprotobuf ERROR google/protobuf/text_format.cc:172] Error parsing text-format caffe.NetParameter: 13:17: Message type "caffe.DataParameter" has no field named "fg_threshold". if they are removed, I get: F0710 14:42:51.490083 9965 data_layer.cpp:254] Check failed: prefetch_rng_ PS with an old version of Caffe (downloaded in April) keeping these fields worked. |
Look at examples/imagenet instead. If you're not doing windowed finetuning, Le jeudi 10 juillet 2014, caffecuda [email protected] a écrit :
|
@shelhamer The only difference between my prototxt and those in examples/imagenet/imagenet is they use different leveldbs (plus of course different fc8 layers): where imagenet10 is my toy problem with 10 imagenet classes. While training works on examples/imagenet, on my finetuning toy problem it produces this error: I0710 15:56:32.887979 18611 finetune_net.cpp:27] Loading from caffe_reference_imagenet_model |
@Mezn Hi, would you mind sharing your prototxt files for finetuning using whole images instead of windows? Many thanks. |
Finetune prototxt for a binary classification task, the only layer that has to be modified is the last fully connected one (outputs changed from 1000 to 2 and name changed.) Training: To finetune you have to call finetune_net.bin solver.prototxt. Best regards, Chris |
@Mezn @shelhamer The problem was caused by the fact that I have "mirror: true" in the val.prototxt file. Comparing with Chris' version helped identify the problem, thanks! The pascal finetune example has |
I don't exactly know what blobs_lr does, for my experiments both worked (in terms of precision I could not see a difference, but this could be caused by the fact that I only considered very small examples yet). However a more sophisticated explanation would be very helpful! I am glad that I was able to help :) Best regards, |
@Mezn hello, if i call finetune_net.bin solver.prototxt in the terminal, it gives error I'm not sure about the usage of finetune_net.bin, is there some information that might help? Thank you! |
You are using it right, however I don't know why it crashes without any output in your case, that never happened to me. Maybe there is something wrong with the google logging library (wildshot). Did the MNIST example network training work for you? (http://caffe.berkeleyvision.org/gathered/examples/mnist.html) Good luck & best regards, |
You need to set Sergio 2014-07-13 7:45 GMT-07:00 mezN [email protected]:
|
Thank you! It's a downstream problem. GLOG_logtostderr=1 will allow code 2014-07-13 22:45 GMT+08:00 mezN [email protected]:
|
Hello,
With an old version of Caffe (master released downloaded in April) it's possible to finetune by specifying leveldb as sources instead of window_file_.txt. With the new version however I'm getting this error:
libprotobuf ERROR google/protobuf/text_format.cc:172] Error parsing text-format caffe.NetParameter: 13:17: Message type "caffe.DataParameter" has no field named "fg_threshold".
F0706 22:01:11.571449 4524 upgrade_proto.cpp:571] Check failed: ReadProtoFromTextFile(param_file, param) Failed to parse NetParameter file: pascal_finetune_train.prototxt
I have changed "WINDOW_DATA" to "DATA" and "window_data_param" to "data_param" etc. Thanks!
The text was updated successfully, but these errors were encountered: