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
Read from STDIN #30
Comments
I'll investigate this. It seems like a good feature. Do you have support for this in If so I can start by looking into |
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
which is different from what I proposed. But it gives me another idea, which would be to add support for sacrebleu-style builtin test sets, e.g.,
You could accomplish this by just using sacrebleu as a library. It’s pretty easy:
|
(Note that, via @ozancaglayan, sacrebleu also supports tab-delimited system output on STDIN, and will then do significance testing among them, e.g.,
Just something else to consider in terms of CLI). |
Thanks, Matt! These are nice features indeed! Do you want to submit a PR 😁 ? If not I can still try to allocate some time to do them before the new release |
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 indeed! Do you want to submit a PR 😁 ?
If not I can still try to allocate some time to do them before the new release
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
We were planning the release for the end of November beginning of December |
🚀 Feature
It would be really nice if COMET could read input from STDIN, e.g.,
Motivation
This is consistent with standard UNIX usage. It is also slightly less cumbersome, and allows comet to be used in settings without writing files to disk.
The text was updated successfully, but these errors were encountered: