Kazakh and Tatar/Work plan

From Apertium
< Kazakh and Tatar
Revision as of 20:54, 5 June 2012 by Ilnar.salimzyan (talk | contribs) (Undo revision 34472 by Ilnar.salimzyan (Talk))
Jump to navigation Jump to search

This is a workplan for development efforts for Kazakh and Tatar translator in Google Summer of Code 2012.

  • Trimmed coverage means the coverage of both of the morphological analysers after being trimmed according to the bilingual dictionary of the pair, that is, only containing stems which are also in the bilingual dictionary.
  • Testvoc for a category means that the category is testvoc clean, in both translation directions.
  • Evaluation is taking words and performing an evaluation for post-edition word error rate (WER). The output for those words should be clean.
Week Dates Trimmed coverage Testvoc Evaluation Notes
0 23/04—21/05 45% <postadv> <ij> 500 words Preliminary evaluation. Translate the story total coverage and without diagnostics (in both directions). Get a baseline WER. Work on disambiguation, the morphological ambiguities in the story should be resolved.
1 21/05—27/05 50% <num> <post> - Basic numerals, and postpositions should be clean.
2 28/05—03/06 53% <cnjcoo> <cnjadv> <cnjsub> -
3 04/06—10/06 59% <adv> <abbr> 200 words Work on disambiguation.
4 11/06—17/06 63% <prn> <det> -
5 18/06—24/06 68% <adj> <adj><advl> - Adjectives with attributive and adverbial function should be clean. Numerals + affixes should have their phonology solved.
6 25/06—01/07 70% <n> <num><subst> <np> <adj><subst> 500 words Midterm evaluation. Work on disambiguation.
7 02/07—08/07 73% - -
8 09/07—15/07 75% - -
9 16/07—22/07 77% - 200 words Work on disambiguation.
10 23/07—29/07 80% <v> -
11 30/07—05/08 80% - - Work on disambiguation.
12 06/08—12/08 80% all categories clean 500 words Final evaluation. Tidying up, releasing