Implement coverage penalty in fast beam search #1277
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per discussion on #1268 .
All the slow/fast scores are matching. There's also some better validation of the coverage params. This fixes #994 since the scores don't line up unless that's fixed. That makes the slow code appreciably faster, but still not as fast as the fast code.
Scores on 694c8fc (master)
Slow baseline
Slow summary cov
Slow summary cov stepwise
Slow length avg penalty
Slow length wu penalty
Fast baseline
Fast length avg penalty
Fast length wu penalty
"Evidence" of #994 fix
(Note the gold score changes too. This doesn't fix that!)
Batch size 1 (baseline) 7999890
Batch size default
Batch size default after fix a03250e
03b3539 (this)
Slow baseline
Slow summary cov
Slow summary cov stepwise
Slow length avg penalty
Slow length wu penalty
Fast baseline
Fast length avg penalty
Fast length wu penalty
Fast summary cov
Fast summary cov stepwise