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

question about the input size #9

Open
ShadowLau opened this issue Dec 31, 2016 · 4 comments
Open

question about the input size #9

ShadowLau opened this issue Dec 31, 2016 · 4 comments

Comments

@ShadowLau
Copy link

@HyeonseobNam
Thanks for your generous to make your excellent work open.
Recently, when i read your paper, i am confused with your network architecture. In your paper, you said that the input size is "107 = 75 (receptive) + 216 (stride)". Can you explain me how to get the "75" and "216"?
Thank you very much again.

@hyseob
Copy link
Owner

hyseob commented Jan 2, 2017

@ShadowLau
As written in the paper, we designed the input size to produce 3x3 feature maps at conv3.
Our network converts a 75x75 input to 1x1 at conv3; the stride of conv3 w.r.t the input is 16 (=2x2x2x2x1), so a (75+16k)x(75+16k) input produces (1+k)x(1+k) at conv3.

@ShadowLau
Copy link
Author

@HyeonseobNam
Thank you.
I can understand 107x107 to 3x3 step by step (layer by layer). I just can not understand why stride is 16. Maybe you mean "x2 pool" equals to "stride 2"?

@hyseob
Copy link
Owner

hyseob commented Jan 2, 2017

@ShadowLau
Right :) Pooling sizes equal to pooling strides in our network.

@ShadowLau
Copy link
Author

@HyeonseobNam
Get it :) Thank you very much!

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

2 participants