Closed rushter closed 3 years ago
That's strange the only significant change to the translation pipeline since then has been multiple hypotheses but in this case I don't think that would change the way CTranslate2 is called. We may have changed some of the CTranslate2 parameters since then but I'm not sure.
Overall though I don't have any reason to believe that translations have gotten worse.
This is the parameter that changes the behavior: https://github.com/rushter/argos-translate/blob/03dcbcf53960c9248e699d212e16c2023de90def/argostranslate/translate.py#L396
Using beam_size=2
and num_hypotheses=1
gives the old bahaviour.
That makes sense, beam_size would change the output sometimes. I think this should generally improve translations though, just not in this specific case.
Actually maybe the issue is that when num_hypotheses is 1 it reduces beam_size which could make translations worse.
I set a min beam size of 4. Hopefully this improves translations some, speed didn't change noticeably.
I've noticed different output from LibreTranslate and the latest version of argos-translate for Chinese language. LibreTranslate uses
argostranslate==1.1.4
.I've tested this problem locally and got the same results. It looks like a regression to me. Both versions are using the same model.
Original sentence (in English, translated using GoogleTranslate):
argostranslate==1.3.0
LibreTranslate (
argostranslate==1.1.4
):