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 API document of convolution #667

Closed
NianzuMa opened this issue Jan 2, 2016 · 2 comments
Closed

Question about the API document of convolution #667

NianzuMa opened this issue Jan 2, 2016 · 2 comments

Comments

@NianzuMa
Copy link

NianzuMa commented Jan 2, 2016

In issue 196, the problem of definition of different padding is mentioned.
https://www.tensorflow.org/versions/master/api_docs/python/nn.html#convolution

I think the document of convolution is still quite confusing right now.
What does the different dimension of strides = [1, 1, 1, 1] mean?
Why the definition of "VALID" and "SAME" padding is quite different from the Stanford cs131n tutorial.

I think most of the people learn CNN according to the tutorials online. Is it possible to modify the document according to the tutorial? Thank you very much.

@NianzuMa NianzuMa changed the title Question about padding type definition Question about the part of convolution document Jan 2, 2016
@NianzuMa NianzuMa changed the title Question about the part of convolution document Question about document about convolution Jan 2, 2016
@NianzuMa NianzuMa changed the title Question about document about convolution Question about the API document of convolution Jan 2, 2016
@cesarsalgado
Copy link
Contributor

The strides = [1, 2, 2, 1] are the strides for each of the dimension of the input tensor [batch, in_height, in_width, in_channels]. For the tf.nn.conv2d function the dimension 0 and 3 must have strides equal to 1. Based on what @Yangqing said in #196 I think the padding scheme is non-intuitive due to legacy reasons.

@girving
Copy link
Contributor

girving commented Mar 8, 2016

Closing due to lack of activity.

@girving girving closed this as completed Mar 8, 2016
darkbuck pushed a commit to darkbuck/tensorflow that referenced this issue Jan 23, 2020
…pstream-doc-whlpkg

tensorflow-rocm compatibility doc
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

3 participants