Open walmsley opened 6 years ago
If this issue remains unaddressed, people who only need to serve their model with multiple beam search candidates as output can just use the code pasted above.
I do not quite follow this. You can pick up the first beam search result from multiple beams once you need only one translation.
Working with serving multiple beam search outputs, and bumped into an issue. I've actually solved the issue, but need to figure out how to submit the change without breaking for other people.
The code at: https://github.com/tensorflow/tensor2tensor/blob/master/tensor2tensor/serving/serving_utils.py#L119
assumes that beam search returns only a single candidate; but I've needed to modify it to the following to handle multiple outputs:
The question is: how to design this to gracefully handle the multi-beam-output case while also not changing the output for single-output cases?