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
CIFAR-10 tutorial train_quick issue - solver state filename #2907
Comments
I'm so new to caffe and I meet the same problem with you. I don't know whether you are correct. If you find the solution. Please do tell me. Thx! |
I also meet the problem. I edit the script train_quick.sh . |
I experienced the same problem and had to fix |
h5 represents HDF5 which is a data model, library, and file format for storing and managing data. More info you can find here https://www.hdfgroup.org/ |
Hi, I got the same problem but it doesn't work when I remove .h5. Do you have any ideas. Thx Resuming from examples/cifar10/cifar10_quick_iter_4000.solverstate.h5 |
I'm getting the same problem as everyone else. I've noticed that if I even try to build the simple demo code from the HDF5 website, I get the same error. I think the problem is on there end. |
Switched back to proto serialization in 8bc82c6. |
Hi,
I'm new to Caffe so I might be doing something very wrong, but I think I precisely followed the tutorial available here:
http://caffe.berkeleyvision.org/gathered/examples/cifar10.html
I have a clean master caffe installation on OS X 10.10.4.
The problem is that when running
train_quick.sh
at some point the training crashes as it expects to see the solver state (after 4k iters) file with.h5
extension (seems related to the recent commit: c9b333e):https://github.com/BVLC/caffe/blob/master/examples/cifar10/train_quick.sh#L11
Backtrace:
But apparently, the training procedure snapshots the state to a file without
.h5
extension. Quickly hacking thetrain_quick.sh
file to expect justexamples/cifar10/cifar10_quick_iter_4000.solverstate
resolved the issue.Correct me if I'm wrong, but it looks like there's some incompatibility between the training procedure and snapshot loading,
Cheers,
Marcin
The text was updated successfully, but these errors were encountered: