-
Notifications
You must be signed in to change notification settings - Fork 162
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
the input of decoder is an one-hot vector #62
Comments
I think this is used in generating the string for where clause . It uses a pointer network in which at each time step a particular token of question is pointed out The one hot vector would have same length as that of question with 1 corresponding to the position of current token .. the process is repeated until end tokens index gets 1 This what I have understood. Correct me if I am wrong |
@bestbzw you can look on paper related to pointer network |
@JACOBIN-SCTCS I found that the Pointer-Generator-Network (Get To The Point: Summarization with Pointer-Generator Networks) uses dense vectors as the inputs of decoder, so I guess pointer network also uses dense vectors. |
Ok thank you for your info |
hi
Why the input of the decoder is an one-hot vector? We usually use dense vectors(through embedding lookup function) as the input in seq2seq models.
The text was updated successfully, but these errors were encountered: