From Apertium
Revision as of 02:32, 1 June 2019 by Firespeaker (talk | contribs) (→‎Translation accuracy)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Apertium language modules and translation pairs are subject to the following types of evaluation:

  • Morphology coverage / regression testing
  • Size of system
    • Number of stems in lexc, monodix, bidix
    • Number of disambiguation rules
    • Number of lexical selection rules
    • Number of transfer rules
  • Naïve coverage
    • Monolingual naïve coverage
    • Trimmed naïve coverage (i.e., using a trimmed dictionary)
  • Accuracy of analyser
    • Precision/Recall/F-score
  • Accuracy of translation
    • Overall accuracy (over parallel corpora): WER/PER/BLEU
    • Regression tests (pairs of phrases or sentences)
  • Cleanliness of translation output
    • Testvoc

Morphology coverage[edit]

The tools we have for this are aq-morftest from Apertium quality and

Two complaints: they don't support directionality restrictions on tests, and they don't return error codes.

Naïve coverage[edit]

In theory, aq-covtest does this, but mostly people write their own scripts.

A good generalised script that supports hfst and lttoolbox binaries and arbitrary corpora would be good. It should also (optionally) output hitparades (e.g., frequency lists of unknown forms in the corpus).

Translation accuracy[edit]

Translation cleanliness[edit]

There are several ways to test translation cleanliness that are good for different purposes:

  • morphology expansion testvoc ("standard testvoc")
  • prefixed morphology expansion testvoc ("testvoc lite")
  • corpus testvoc