Skip to content
This repository has been archived by the owner on Jan 30, 2021. It is now read-only.

Beam search usefulness ? #3

Open
astariul opened this issue Jul 5, 2019 · 1 comment
Open

Beam search usefulness ? #3

astariul opened this issue Jul 5, 2019 · 1 comment

Comments

@astariul
Copy link

astariul commented Jul 5, 2019

In most text generating architecture, beam search provide a quality improvement by generating more natural text.

Is it useful to use beam search with XLNet ?


As far as I understand, since token are generated one by one, beam search is completely useless.
But what about generating tokens 2 by 2 ? Would it be useful to add beam search ?

Are you going to try it ?

@rusiaaman
Copy link
Owner

rusiaaman commented Jul 6, 2019

Beam search and greedy decoding causes degradation of text (it becomes repetitive) in open ended generation tasks. More discussion at https://arxiv.org/abs/1904.09751. I have observed that the same issues persist with XLNet.

Beam search is more helpful with translation and summarization where the generated text length is in the order of the context text length. The probability of degradation increases with length of the generated text for greedy (and beam search). This is still a research area so proper explanation is yet to be found.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants