-
Notifications
You must be signed in to change notification settings - Fork 25
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
Beam search validation #26
Comments
Thanks. Please check this issue for a reference. |
thank u for reply. I'm sorry it's too late.. It seems i haven't quite understood your system. |
This algorithm still follows the beam-search approach mentioned in the Speaker-Follower paper. I modified it to a greedy approach (Dijkstra algorithm) that only expands the state with the lowest score at each time step. It would empirically have a better estimation of the best path than the beam-search approach without losing speed. |
Okay I understood. If so, is it affected with the agent(listener) model's tokenizer? |
Hi, Is this any way to test your model as beam search?
I saw the code in train.py and agent.py ("beam_valid", "beam_search_test")
Could you please share any way to use it?
The text was updated successfully, but these errors were encountered: