User:Darthxaher/Application2010 - Revision history

Darthxaher: /* List your skills and give evidence of your qualifications */

2010-04-10T01:16:16Z

List your skills and give evidence of your qualifications

Darthxaher: /* Official Coding Period */

2010-04-08T17:00:02Z

Official Coding Period

Darthxaher: /* Community Bonding Period */

2010-04-08T16:57:24Z

Community Bonding Period

Darthxaher: /* Work Plan */

2010-04-08T16:46:33Z

Work Plan

Darthxaher: /* Work Plan */

2010-04-08T16:32:25Z

Work Plan

Darthxaher: /* List any non-Summer-of-Code plans you have for the Summer */

2010-04-07T13:02:26Z

List any non-Summer-of-Code plans you have for the Summer

Darthxaher: /* List any non-Summer-of-Code plans you have for the Summer */

2010-04-07T06:36:40Z

List any non-Summer-of-Code plans you have for the Summer

Darthxaher: /* List your skills and give evidence of your qualifications */

2010-04-07T06:34:52Z

List your skills and give evidence of your qualifications

Darthxaher: /* Development Note */

2010-04-07T06:33:32Z

Development Note

Darthxaher: /* Work Plan */

2010-04-07T06:12:39Z

Work Plan

@@ Line 172: / Line 172: @@
 The project was followed up by a successful paper submission at [http://xixona.dlsi.ua.es/freerbmt09/ freeRBMT09] by me and my mentor Francis Tyers. The paper can be accessed from [http://www.mt-archive.info/FreeRBMT-2009-Faridee.pdf here]. I also tried to remain active in Apertium's community after summer of code. Several of the maintenance enhancements were carried out long after the project was officially over.
-Right now I’m in my final year of my undergraduate in Computer Science and Engineering in Bangladesh University of Engineering and Technology. I have attended both theoretical and practical courses in Algorithm, Automata Theory and Compiler. I took a compiler design course and as a part of term project successfully created a compiler that could run a subset of Pascal. So I believe that I have both the basic theoretical and practical knowledge for this project.
+Right now I’m in my final year of my undergraduate in Computer Science and Engineering in Bangladesh University of Engineering and Technology. I have attended both theoretical and practical courses in Algorithm, Automata Theory and Compiler. I took a compiler design course and as a part of term project successfully created a compiler that could run a subset of Pascal. I also attended basic OS course, where I had to go through Linux's source code implement a custom system call. implement some new features in 'Nachos' and solve some classic concurrency problem using POSIX thread. So I believe that I have both the basic theoretical and practical knowledge for this project.
 I have been an open source advocate in my country from my college years. I have been working with [http://www.ankur.org.bd/wiki/People Ankur], a not-profit organization since then. With them I have conducted numerous open source camps. I participated in creating and beta testing of several products from Ankur, notably Firefox spell-checking dictionary and off-line add-on CD for several localized Ubuntu versions.

@@ Line 105: / Line 105: @@
 Modify the VM so that now it can run t2x and t3x pseudo assembly files and produce desired output.
+'''Deliverable:''' A functional compiler and VM that can handle t1x, t2x, t3x files.
 ==== Week 7: June 7 - June 13 ====

@@ Line 74: / Line 74: @@
 ==== Week 1: April 27 - May 2 ====
-* Reviewing of the code structure of Apertium and Lt-toolbox that involves the lexical transfer and structural transfer module. Also come up with some set of test cases (at first, small t1x files and accompanying input) with increasing order of complexity (include t2x and t3x) for a preferred language pair. These test cases will be the the basis of how we'll keep adding more and more complex instructions in the python prototype.
+* Reviewing of the code structure of Apertium and Lt-toolbox that involves the lexical transfer and structural transfer module. Also come up with some set of test cases (at first, small t1x files and accompanying input) with increasing order of complexity (include t2x and t3x) for a preferred language pair. These test cases will be the the basis of how we'll keep adding more and more complex instructions in the python prototype. Previous works from Jacob Nordfalk will be an excellent place to start.
 '''Deliverable:''' Set of test cases

@@ Line 92: / Line 92: @@
 ==== Week 4: May 17 - May 23  ====
-Start coding on the python prototype VM. It will be able to run the instructions from pseudo-assembly text file and produce the desired structurally translated output.
+Start coding on the python prototype VM. It will be able to run the instructions from 't1x' pseudo-assembly text file and produce the desired structurally translated output.
 '''Deliverable:''' A very very simple and working prototype.
@@ Line 100: / Line 100: @@
 ==== Week 5: May 24 - May 30 ====
+Start working in t2x and t3x to pseudo-assembly compiler. This will involve adding more instructions to our instruction set.
-Keep adding more and more instructions to the prototype. Keep testing against more complex inputs.
 ==== Week 6: May 31 - June 6 ====
+Modify the VM so that now it can run t2x and t3x pseudo assembly files and produce desired output.
-Start working on t2x and t3x files
 ==== Week 7: June 7 - June 13 ====
-By this time the interpreted VM would be in a workable state. So now is the time to start code for the 'txx' to 'bytecode' compiler
+By this time the interpreted VM would be in a workable state. So now we add 'txx' to 'byte-code' generation mode to our compiler.
 '''Deliverable:''' The python implementation of the byte-code compile
@@ Line 114: / Line 114: @@
 ==== Week 8: June 14 - June 20 ====
-Start porting the text mode VM to byte-code mode VM, fix any remaining issues in the byte-code compiler.
+Start adding byte-code aware mode to our VM, fix any remaining issues in the 'txx' to 'byte-code' compiler. Test this new module.
 ==== Week 9: June 21 - June 27 ====
-Finish working on the byte-code mode VM
+Finish working on the byte-code mode VM, also explore the possibilities of JIT optimization for the VM.
 '''Deliverable:''' Fully working python prototype

@@ Line 49: / Line 49: @@
 I have been keeping in touch with mentors Sergio Ortiz Rojas, Francis Tyers and Jimmy O'Regan regarding the details and plan for this project. So far I've noted the following things will need to be done:
-* Separate the lexical transfer module from the structural transfer module without breaking the existing system
+* Separate the lexical transfer module from the structural transfer module without breaking the existing system. This part is necessary because the VM will take word pairs [source language, target language] as input, so we need something that can feed the VM that data. '''''(Note: I have been notified by mentor Ortiz Rojas that he will take care of this part)'''''
 * Define the instruction-set and data structure for the pseudo assembly
@@ Line 80: / Line 80: @@
 ==== Week 2: May 3 - May 9  ====
+Define a very minimal set of instructions and data structure for the prototype VM, try to come up with a simple as possible schematics for the python implementation.
-* Write a patch for 'apertium-transfer' tool that separates the lexical transfer module form the structural transfer module without breaking backward compatibility. This part is necessary because the VM will take word pairs [source language, target language] as input, so we need something that can feed the VM that data.
-'''Deliverable:''' A usable patch for the above mentioned purpose
+'''Deliverable:''' A minimal instruction set and data structure + schematics for the python VM
 ==== Week 3: May 10 - May 16  ====
+Start preliminary work on 't1x' to 'pseudo-assembly text' compiler.
-Define a very minimal set of instructions and data structure for the prototype VM, try to come up with a simple as possible schematics for the python implementation.
-'''Deliverable:''' A minimal instruction set and data structure + schematics for the python VM
+'''Deliverable:''' A minimal compiler that can compile from 't1x' to 'pseudo-assembly' text
 ==== Week 4: May 17 - May 23  ====
-Start coding on the python prototype VM. It will be able to run the instructions from text file and produce the desired structurally translated output.
+Start coding on the python prototype VM. It will be able to run the instructions from pseudo-assembly text file and produce the desired structurally translated output.
 '''Deliverable:''' A very very simple and working prototype.

@@ Line 184: / Line 184: @@
 ==  List any non-Summer-of-Code plans you have for the Summer ==
-Right now, as I write this application, I'm attending my first semester final exams at university. My exams will be over in April 14 and my next semester does not start until the end of July. So after this exam is over, I will be able to fully concentrate on my work of the project. My class schedules will overlap at the ending phase of the project, but normally there is not much pressure at the beginning of the semester. Keeping all these in mind, I plan to finish the project up as soon as possible while I can give it full attention and at the later stage do bug fixing and enhancements. And if need arises, I could always do extra work in the weekend to minimize the effect of overlapping.
+Right now, as I write this application, I'm attending my first semester final exams at university. My exams will be over in April 14 and my next semester does not start until July. So after this exam is over, I will be able to fully concentrate on my work of the project. My class schedules will overlap at the ending phase of the project, but normally there is not much pressure at the beginning of the semester. Keeping all these in mind, I plan to finish the project up as soon as possible while I can give it full attention and at the later stage do bug fixing and enhancements. And if need arises, I could always do extra work in the weekend to minimize the effect of overlapping.
 == Conclusion ==

@@ Line 166: / Line 166: @@
 == List your skills and give evidence of your qualifications ==
-As I've already mentioned, I successfully completed my Google Summer of Code project titled '''''Conversion of Anubadok: Creating an English Bengali Language Pair'''''<ref>http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2009/apertium/t124021625239</ref> under Apertium last year. It was a really ambitious project given the fact that there was little linguistic data available for Bengali other than another open source machine translation project called Anubadok. The project had three stages, building a Bengali morphological analyser/generator, creating a English to Bengali bilingual dictionary and  the creating a transfer system. Building the morphological analyser/generator proved to be tougher than we originally comprehended as Apertium needs more information for each lexical category than what was tagged in Anubadok's dataset. Therefore by the end of the project we had a morphological analyser with 68% coverage of the most used 20 thousand words. The [http://wiki.apertium.org/wiki/Google_Summer_of_Code/Report_2009#Conversion_of_Anubadok_.28darthxaher.29 post GSoC report] discussed the outcome in further details.
+As I've already mentioned, I successfully completed my Google Summer of Code project titled '''''[http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2009/apertium/t124021625239 Conversion of Anubadok: Creating an English Bengali Language Pair]''''' under Apertium last year. It was a really ambitious project given the fact that there was little linguistic data available for Bengali other than another open source machine translation project called Anubadok. The project had three stages, building a Bengali morphological analyser/generator, creating a English to Bengali bilingual dictionary and  the creating a transfer system. Building the morphological analyser/generator proved to be tougher than we originally comprehended as Apertium needs more information for each lexical category than what was tagged in Anubadok's dataset. Therefore by the end of the project we had a morphological analyser with 68% coverage of the most used 20 thousand words. The [http://wiki.apertium.org/wiki/Google_Summer_of_Code/Report_2009#Conversion_of_Anubadok_.28darthxaher.29 post GSoC report] discussed the outcome in further details.
 The project was followed up by a successful paper submission at [http://xixona.dlsi.ua.es/freerbmt09/ freeRBMT09] by me and my mentor Francis Tyers. The paper can be accessed from [http://www.mt-archive.info/FreeRBMT-2009-Faridee.pdf here]. I also tried to remain active in Apertium's community after summer of code. Several of the maintenance enhancements were carried out long after the project was officially over.

@@ Line 164: / Line 164: @@
 From my previous GSoC experience I have realized that a lot of unexpected problems arise during the course of the project which are not part of the original plan. In those cases I'll try to modify the project plan to fit our needs but try to maintain the deadlines as much as possible.
-waa== List your skills and give evidence of your qualifications ==
+== List your skills and give evidence of your qualifications ==
 As I've already mentioned, I successfully completed my Google Summer of Code project titled '''''Conversion of Anubadok: Creating an English Bengali Language Pair'''''<ref>http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2009/apertium/t124021625239</ref> under Apertium last year. It was a really ambitious project given the fact that there was little linguistic data available for Bengali other than another open source machine translation project called Anubadok. The project had three stages, building a Bengali morphological analyser/generator, creating a English to Bengali bilingual dictionary and  the creating a transfer system. Building the morphological analyser/generator proved to be tougher than we originally comprehended as Apertium needs more information for each lexical category than what was tagged in Anubadok's dataset. Therefore by the end of the project we had a morphological analyser with 68% coverage of the most used 20 thousand words. The [http://wiki.apertium.org/wiki/Google_Summer_of_Code/Report_2009#Conversion_of_Anubadok_.28darthxaher.29 post GSoC report] discussed the outcome in further details.

@@ Line 46: / Line 46: @@
 == Work Plan ==
-<u>'''NOTE: just a draft, a lot fix needed, comments are always welcome'''
-</u>
 I have been keeping in touch with mentors Sergio Ortiz Rojas, Francis Tyers and Jimmy O'Regan regarding the details and plan for this project. So far I've noted the following things will need to be done: