Mixe/Transducer

From LING073
Revision as of 14:28, 10 April 2022 by Eresend1 (talk | contribs) (Notes)

Jump to: navigation, search

GitHub repository (internal Swarthmore access may be required to view).

Notes

Dunno why, but most of the adjectives aren't passing. something to do with the saltillos? More generally, sometimes a morphtest fails even though the form is correctly analyzed when I do echo form | apertium -d . mto-morph

The form of a noun can change when other morphology is added, likely for phonological reasons. I'm not sure the best way to deal with this, especially since I can't predict when such alternations take place (at least, I haven't figured out the pattern as of yet).

The way we've implemented verb morphology seems to work in general, but there's probably a better, cleaner way to approach it. Many verbs in Totontepec have stems that alternate depending on morphological environment. The issue isn't that there are alternations, but that there are so many of them, and they don't seem to follow a clear pattern across all verbs. The current solution is to have multi-columned verb stem LEXICONs and about 40 verb patterns. Not only does this look confusing and cluttered, but it makes troubleshooting verb analysis and generation more tedious.

Currently, we have 82 morphTests, 47 of which pass.

Tests that don't pass (as of 4-10 at 1pm):

  • most of the inflected transitive verbs
  • nouns and verbs with phonological alternations. We're not sure how to predict when such alternations will occur, so we're not sure of the best way to deal with them.
  • complex verbs. We currently have seven morphTests for verbs that include non-obligatory morphology. We haven't added those morphotactics to the transducer yet, mostly because there are about 20 possible morpheme spots per verb, so there are many additional morphemes to implement.

From the top unknown words in our corpus, we determined the analyses of the following:

  • dü <pro><perf>
  • tseꞌe <disc><asrt>
  • maas <adj>

By adding these, however, our coverage only went from 0.4

Evaluation

First time running coverage-hfst: Coverage at 0.41%,