Matt Post
Matt Post
This sounds like a very user-friendly simplification to me.
Is it still true that macros only work with FTS?
Thanks for this, will review soon!
A man page might be good. I like the approach of writing an extensive README and converting that to a man page somehow, or having `bibsearch help` pull it in...
Another idea is to borrow a concept from bash shell and use the reverse of a word as the closing concept: so bash's if/if and case/esac become start/trats or begin/nigeb.
I second this request. The bottom line is that **scores produced with different reference tokenizations are not comparable**. To discourage (even inadvertent) cheating, the user should never touch the reference....
Yes, there are slides like that at WMT every year :) BLEU correlates with human judgment only at coarse levels, and it seems to be getting worse when people try...
Sacrebleu supports STDIN for the system output, but not for the ref (and doesn’t use the source). So the COMET-style use would be ``` $ cat system.txt | comet -s...
(Note that, via @ozancaglayan, sacrebleu also supports tab-delimited system output on STDIN, and will then do significance testing among them, e.g., ``` $ paste system1.txt system2.txt | sacrebleu -t wmt20...
Hmm, good question. What’s your timeline for the release? > On Oct 19, 2021, at 15:30, Ricardo Rei ***@***.***> wrote: > > > Thanks, Matt! These are nice features...