Difference between revisions of "User:Naan Dhaan/User friendly lexical training"
Naan Dhaan (talk | contribs) m (week 6) |
Naan Dhaan (talk | contribs) |
||
Line 48: | Line 48: | ||
* some minor fixes like formatting string with f"" and fixes in apertium-lex-tools |
* some minor fixes like formatting string with f"" and fixes in apertium-lex-tools |
||
| |
| |
||
|- |
|||
| July 13-19 |
|||
| |
|||
* added Github actions for training and checking config |
|||
* incorporated changes of apertium-lex-tools(60a6ae9) |
|||
| |
|||
* lexical_selection.py takes config file as an optional input |
|||
* Github actions |
|||
* no need to run Makefile in apertium-lex-tools/scripts to generate process-tagger-output and path of apertium-lex-tools is not required in config file. Installing apertium-lex-tools installs everything in the std paths |
|||
|} |
|} |
Revision as of 04:34, 22 July 2021
The lexical selection module selects the right sentence in the context, based on lexical selection rules, from the multiple(ambiguous) sentences output by the transfer module. These rules can be written manually or inferred automatically by training on a corpus. But, the training process is a bit tedious with various tools like irstlm, fast-align, moses, etc, and various scripts like extract-sentences, extract-freq-lexicon, process-tagger-output, etc, involved, which require a lot of manual configs.
The goal of this project is to make this as simple and automated as possible with little involvement of the user. In a nutshell, there should be a single config file and the user does the entire training using a driver script. Finally, design regression tests on the driver script so that it works in the face of updates to the third-party tools. Also, train on different corpora and add lexical selection rules to the languages which have few to no lexical selection rules, thereby improving the quality of translation
Work Plan
Time Period | Details | Deliverable |
---|---|---|
Community Bonding Period
May 17-31 |
|
driver script can validate if the required tools are setup |
Community Bonding Period
June 1-7 |
reading apertium documentation |
|
June 8-14 |
|
driver script can now, clean corpus, tag it and generate alignments |
June 15-21 | full driver script complete(requires testing (: ) | driver script can now generate rules |
June 22-28 | bug fixes | |
June 29 - July 5 | some more bug fixes | |
July 6-12 |
|
|
July 13-19 |
|
|