Search results

• Talk:Task ideas for Google Code-in
  |title=Increase test coverage of [[begiak]], our IRC bot, by at least 10% |mentors=sushain, Unhammer, wei2912, Josh, xavivars, shardulc
  397 KB (52,731 words) - 11:22, 10 December 2019
• Task ideas for Google Code-in
  |title=expand coverage of Kyrgyz to English structural transfer |mentors=JNW, sevilay, Unhammer, marcriera, padth4i, Oguz, popcorndude
  32 KB (4,862 words) - 06:23, 5 December 2019
• Talk:Ideas for Google Summer of Code
  * '''Mentors''':<br>[[User:Unhammer|Unhammer]], [[User:Francis Tyers|Francis Tyers]], [[User:Mlforcada|Mikel Forcada]] ...te-of-the-art in terms of translation quality. This will involve improving coverage to 95-98% on a range of corpora and decreasing [[word error rate]] by 30-50
  71 KB (10,374 words) - 21:14, 18 January 2021
• Task ideas for Google Code-in (2013)
  ...imzyan]] [[User:Xavivars]] [[User:Bech]] [[User:Jimregan|Jimregan]] [[User:Unhammer]] [[User:Fsanchez]] [[User:Nikant]] [[User:Fulup|Fulup]] [[User:Japerez]] [ ...rule|Read more]]... || [[User:Mlforcada]] [[User:ilnar.salimzyan]] [[User:Unhammer]] [[User:Nikant]] [[User:Fulup|Fulup]] [[User:Juanpabl]]
  68 KB (10,323 words) - 15:37, 25 October 2014
• Ideas for Google Summer of Code
  * Unhammer's [[User:Unhammer/wishlist|wishlist]] ...lation pair to releasable quality. This would entail obtaining good naïve coverage and a clean [[testvoc]].
  23 KB (3,198 words) - 09:15, 4 March 2024
• Ideas for Google Code-In (2011)
  ...alyser || While the current bn-en morphological analyser has a pretty good coverage, it should have been higher. Part of the reason is that a lot of verbs have ...pair HOWTO]] into Nynorsk. ||align=center| 5&ndash;8 || [[User:Unhammer|Unhammer]]
  187 KB (21,006 words) - 22:14, 12 November 2012
• PMC proposals/Move Apertium to Github
  ...tatus checks can be anything from code linting, unit/integration tests and coverage tools (i.e. continuous integration). These tools have to be configured at a ...realise most people don't care. --[[User:Unhammer|unhammer]] ([[User talk:Unhammer|talk]]) 12:44, 9 February 2018 (CET)
  22 KB (3,325 words) - 14:06, 12 March 2018
• Apertium-quality/Quickstart
  ...olkit portion of the project consists of tools such as regression testing, coverage testing, vocabulary testing and statistics storage, while the framework is Author: Kevin Brubeck Unhammer <unhammer@fsfe.org>
  12 KB (1,931 words) - 17:06, 24 October 2018
• Germanic languages
  Once a transducer has ~80% coverage on a range of medium-large corpora we can say it is "working". Over 90% and !rowspan=2| coverage
  32 KB (3,684 words) - 06:16, 28 December 2018
• User:Sushain/GermanicLanguages
  Once a transducer has ~80% coverage on a range of medium-large corpora we can say it is "working". Over 90% and !rowspan=2| coverage
  26 KB (3,036 words) - 07:04, 14 December 2014
• Kazakh and Tatar/Diary
  I'll need help to set up coverage-measuring scripts and to learn how I can testvoc only certain POS's. Tomorrow I am going to translate this additional Tatar ones (to boost up the coverage - they seem to be quite frequent!) and work on transfer rules if they are n
  8 KB (1,205 words) - 21:50, 19 July 2012
• Maltese and Hebrew/Final report
  ...esults; within about 2 weeks (and during my exams period) we got to a ~80% coverage of the Maltese corpora. This way we easily got good enough coverage of nouns, verbs, adjectives, etc.
  7 KB (1,063 words) - 11:13, 26 August 2011
• Translation quality statistics
  ...an=2| 0.6.1 || nno → nob ||rowspan=2 {{yes}} || - || - || - ||rowspan=2| Unhammer and Trosterud, 2009<br/> (two reference translations; as of [https://github == Coverage and Dictionary size ==
  9 KB (1,233 words) - 09:10, 21 November 2021
• Google Summer of Code/Report 2009
  ==Norwegian Nynorsk and Bokmål (Unhammer)== ...ing the most frequency used missing words. Right now we have a roughly 68% coverage of the 20K most freq used words. At first I was strictly focused on creatin
  12 KB (1,886 words) - 12:20, 20 June 2019
• Semitic languages
  Once a transducer has ~80% coverage on a range of medium-large corpora we can say it is "working". Over 90% and !rowspan=2| coverage
  20 KB (2,336 words) - 18:10, 14 April 2015
• User:Sushain/SemeticLanguages
  Once a transducer has ~80% coverage on a range of medium-large corpora we can say it is "working". Over 90% and !rowspan=2| coverage
  19 KB (2,259 words) - 07:52, 3 January 2014
• Курсы машинного перевода для языков России/Session 8
  ...translator is very high, and compares with commercial systems -- over 95% coverage (around 5 unknown words out of 100 words), and between 3-7% word-error rate ...ken up again in 2009 during the Google Summer of Code competition by Kevin Unhammer, a masters' student in computational linguistics at the University of Berge
  12 KB (1,679 words) - 12:00, 31 January 2012
• Helsinki Apertium Workshop/Session 8
  ...translator is very high, and compares with commercial systems -- over 95% coverage (around 5 unknown words out of 100 words), and between 3-7% word-error rate ...ken up again in 2009 during the Google Summer of Code competition by Kevin Unhammer, a masters' student in computational linguistics at the University of Berge
  12 KB (1,683 words) - 08:42, 10 May 2013
• Tartu Apertium Course/Session 8
  ...translator is very high, and compares with commercial systems -- over 95% coverage (around 5 unknown words out of 100 words), and between 3-7% word-error rate ...ken up again in 2009 during the Google Summer of Code competition by Kevin Unhammer, a masters' student in computational linguistics at the University of Berge
  12 KB (1,683 words) - 11:00, 30 October 2015
• User:Francis Tyers
  ...., the idea is to model as much of the language as possible, the wider the coverage the better. An Apertium MT system on the other hand is a closed system. The <Unhammer> *silent scream*
  12 KB (1,835 words) - 00:06, 1 July 2020

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)