Difference between revisions of "User:Mihirrege/GSOC 2013 Application - Interface for creating tagged corpora"

From Apertium
Jump to navigation Jump to search
(Blanked the page)
 
(74 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Name ==
 
 
Mihir Rege
 
 
== Contact information ==
 
 
E-mail: [mailto:mihirrege@gmail.com mihirrege@gmail.com]<br />
 
 
== Why are you interested in machine translation? ==
 
 
 
 
== Why are you interested in the Apertium project? ==
 
 
 
 
== Why Google and Apertium should sponsor it? ==
 
 
 
== How and who it will benefit in society? ==
 
 
== Which of the published tasks are you interested in? What do you plan to do? ==
 
There are currently three major interfaces:<br/>
 
a) Manual disambiguator<br/>
 
b) .prob evaluator<br/>
 
c) .tsx file editor<br/>
 
I have put up all the mockups together at http://imgur.com/a/4uk4q#r5Ur8jT and have also put links in separate sections. <br/>
 
<br/>
 
a) Manual disambiguator<br/>
 
Mockup: http://i.imgur.com/r5Ur8jT.png<br/>
 
Functions:<br/>
 
Jump to next ambiguous lexical unit or adjacent lexical-unit using the keyboard or mouse.<br/>
 
A quick-view bound to a key, to hide the tags and show the raw text<br/>
 
If the .tsx file is provided, information like the coarse tags, forbid, enforce rules applicable can also be displayed.<br/>
 
Show statistics of disambiguation<br/>
 
Compile and apply constraint grammar rules to the buffer<br/>
 
List the applied constraint grammar rules<br/>
 
Train and test the tagger (a prompt will ask the part of the corpus to be used as testing data).<br/>
 
Train the tagger and export the .prob file<br/>
 
Save progress ( this will save the corpus and also create a project description file which will keep track of the morphological analyser, .tsx files used, so that it is easier to resume tagging)<br/>
 
The interface will be keyboard centric, though it will be equally functional with a mouse.<br/>
 
Default keymaps will be provided and the bindings can be changed to suit the user<br/>
 
For example<br/>
 
[P] - <previous-ambiguous><br/>
 
[N] - <next-ambiguous><br/>
 
[F] - <forward-word><br/>
 
[B] - <back-word><br/>
 
[1], [2],[3],[4] for choosing the correct lexical form.<br/>
 
Evaluating the tagger<br/>
 
Functions<br/>
 
The trained tagger can be evaluated immediately by having an option of setting aside x% of the corpus as testing data.<br/>
 
Else, it can be evaluated using the .prob evaluator using an unrelated corpus.<br/>
 
Loading the corpus<br/>
 
The available options are:<br/>
 
Load a raw-text file, morphological analyser and .tsx file (optional)<br/>
 
Continue on an existing project<br/>
 
Pull a wiki-dump and use it as the corpus [ http://i.imgur.com/F9OXMs4.png ]<br/>
 
<br/>
 
b) .prob evaluator<br/>
 
Mockup: http://i.imgur.com/fIo6rV9.png<br/>
 
Functions<br/>
 
Input the .prob file , the manually disambiguated corpus along with morphologically analysed corpus or the morphological analyser for the language.<br/>
 
Evaluate the .prob file and display statistics about tagger accuracy<br/>
 
Generate a log file, which will basically be the diff between the provided tagged corpus and the corpus disambiguated by the tagger, making it easier to frame new sentences to add to the corpus, so as to give more context to the tagger<br/>
 
c) .tsx file editor<br/>
 
Mockup:<br/>
 
TSX Viewer<br/>
 
http://i.imgur.com/pVdsIem.png<br/>
 
Templates<br/>
 
http://i.imgur.com/hFGIQHR.png<br/>
 
Functions:<br/>
 
Add new tags<br/>
 
categories<br/>
 
multi-categories<br/>
 
forbid<br/>
 
enforce<br/>
 
prefer<br/>
 
Templates for adding new tags<br/>
 
Change the order of the tags (as more specific categories must be defined before more general ones) within the same parent tag. The nodes in the xml viewer can also be made draggable within the same parent node to make it easier to change the order<br/>
 
Search within tags for faster navigation.<br/>
 
Validate the tagger definition<br/>
 
Editor features like syntax highlighting , auto-indentation and tag completion for manual editing in the Node Contents textview for complex in-place editing.<br/>
 
<br/>
 
 
== Work plan ==
 
 
=== Coding challenge ===
 
 
 
=== Community Bonding Period ===
 
 
=== Week Plan ===
 
{| class="wikitable" border="1"
 
|-
 
!Week
 
!Plan
 
|-
 
|Week 01
 
|
 
|-
 
|Week 02
 
|
 
|-
 
|Week 03
 
|
 
|-
 
|Week 04
 
|
 
|-
 
| '''Deliverable #1'''
 
|
 
|-
 
|Week 05
 
|
 
|-
 
|Week 06
 
|
 
|-
 
|Week 07
 
|
 
|-
 
|Week 08
 
|
 
|-
 
|'''Deliverable #2'''
 
|
 
|-
 
|Week 09
 
|
 
|-
 
|Week 10
 
|
 
|-
 
|Week 11
 
|
 
|-
 
|Week 12
 
|
 
|-
 
|'''Deliverable #3'''
 
|
 
|}
 
 
== List your skills and give evidence of your qualifications ==
 
 
 
 
== My non-Summer-of-Code plans for the Summer ==
 
 
 
 
[[Category:GSoC_2013_Student_proposals|Mihirrege]]
 

Latest revision as of 20:43, 19 November 2013