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

This keras implementation has different order of bn and activation #14

Open
pgr2015 opened this issue Sep 25, 2019 · 0 comments
Open

This keras implementation has different order of bn and activation #14

pgr2015 opened this issue Sep 25, 2019 · 0 comments

Comments

@pgr2015
Copy link

pgr2015 commented Sep 25, 2019

Hi, thank you for your work. One thing I want to point out here is that you have some tiny difference compared with original implementaion, which may lead to more latency.
Your implementation here is conv + activation + bn as shown below:

y = Conv2D(32, 3, strides=2, padding='same', activation='relu', name='conv1_1_3x3_s2')(y)
y = BatchNormalization(name='conv1_1_3x3_s2_bn')(y)

But the original caffe implementaion is conv + bn + activation, which normally won't have much differnce, but this kind of order make it possible to merge bn into conv, thus leads to smaller latency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant