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.

Sign up for GitHub

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

Jump to bottom

Why use the 'tf.layer.conv1d' for query, key transformation instead of fully connected layer? #36

Open
LEEYOONHYUNG opened this issue Sep 4, 2019 · 0 comments
Open

Why use the 'tf.layer.conv1d' for query, key transformation instead of fully connected layer? #36

LEEYOONHYUNG opened this issue Sep 4, 2019 · 0 comments

Comments

@LEEYOONHYUNG
Copy link

Considering that the query and key have a timestep of 1 from the perspective of 1d convolution, I think that it is totally same with using the fully connected layer.

Is there any reason for using the tf.layer.conv1d for query, key transformation instead of fully connected layer?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@LEEYOONHYUNG