-
Notifications
You must be signed in to change notification settings - Fork 164
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
Support batch normalization #63
Comments
thanks, are there models in caffe format with batchnorm available? should be quick to add, just need a test. resnets won't work. |
@szagoruyko You're saying that you cannot use resnets for this test, or you're saying resnets won't work till you get this test working? |
@JoshPowell resnets have non-sequential structure which loadcaffe doesn't support now |
@JoshPowell you might want to give [caffegraph](https://github.com/nhynes/caffegraph) a try. It's not yet as fully featured as loadcaffe (it's missing a few modules), but it will load your resnet just fine. |
Hi, could loadcaffe load models in caffe format with batch normalization,now? |
@wuhuo714 no |
@szagoruyko Will batchnorm be available soon? |
@wuhuo714 don't have time unfortunately |
@szagoruyko Thanks a lot,anyway! |
Hi,@szagoruyko,if my caffemodel has batchnorm layers which loadcaffe can not recognize, can the following layers like Relu get its correponding weights?It has confused me a lot. |
@wuhuo714 no, it will ignore layers it can't recognize |
Although the layers it can't recognize are ignored, will the weights of these unrecognizable layers be used in the following layers it recoginze? |
@wuhuo714 weights of unrecognized layers will not be loaded at all |
@szagoruyko ok, it's very kind of you to answer my doubts! |
Hi @szagoruyko, |
Batch Normalization was added to Caffe in October 2015. (See BVLC/caffe#3229 and BVLC/caffe#3299). The caffe.proto file in this repo is from April 2015, so it doesn't know about Batch Normalization and can't load newer model definition files.
The text was updated successfully, but these errors were encountered: