User:Arghya1998 - Revision history

Arghya1998: Blanked the page

2018-03-27T09:19:37Z

Blanked the page

Show changes

Arghya1998 at 09:05, 27 March 2018

2018-03-27T09:05:43Z

Arghya1998: /* Coding Challenge */

2018-03-27T08:22:04Z

Coding Challenge

Arghya1998: /* Detailed project plan and workflow */

2018-03-27T08:14:54Z

Detailed project plan and workflow

Arghya1998: /* Detailed project plan and workflow */

2018-03-26T08:53:41Z

Detailed project plan and workflow

Arghya1998: /* Coding Challenge */

2018-03-23T10:08:10Z

Coding Challenge

Arghya1998: /* About me: Education and Experience */

2018-03-23T10:01:48Z

About me: Education and Experience

Arghya1998 at 18:37, 19 March 2018

2018-03-19T18:37:09Z

Arghya1998: /* GSoC Proposal : Python API/library for Apertium */

2018-03-19T18:33:06Z

GSoC Proposal : Python API/library for Apertium

Arghya1998: /* Why is it that I am interested in Apertium? */

2018-03-19T06:01:06Z

Why is it that I am interested in Apertium?

@@ Line 1: / Line 1: @@
+== <center>GSoC Proposal :  Python API/library for Apertium </center> ==
-<span style="font-family:Courier;background-color:#b3ffb3;">
-== <center> GSoC Proposal :  Python API/library for Apertium </center> ==
 == Basic Details ==

@@ Line 278: / Line 278: @@
 * Transducer model python importable
+         <center>[[File:Codingchallenge1.png]]</center>
-         import transducer
 * The library has
+        <center>[[File:Codingchallenge2.png]]</center>
-        transducer.Transducer
-        transducer.Alphabet
-        transducer.Compression
-* Transducers can be built using
+* Transducers can be built using:
+<center>[[File:Code.png]]</center>
-        t = Transducer()
-        t.insertSingleTransduction()
-* t.show() returns the transducer in tuple format
+* t.show() returns the transducer in tuple format:
+<center>[[File:Showout.png]]</center>
 [https://github.com/arghyatiger/transducer-wrapper Repo]

@@ Line 74: / Line 74: @@
 a.) The modules would be python importable, the pythonic usage would be as follows:
-           from apertium.lttoolbox import transducer
+           <center>[[File:pic4.png]]</center>
 b.) The modules would be nested so as to keep a proper code structure
-           apertium.lttoolbox.transducer
+           <center>[[File:Pic.png]]</center>
 c.) The internal usage of the functions would be as follows:
+           <center>[[File:Internalusage.png ]]</center>
-           import apertium.transducer.internal
-           t = apertium.transducer.internal.Transducer().insertSingleTransduction()
-d.) Specialized input functions have to be written for the wrapper as Python may not support a lot of input types
+d.) Specialized IO functions have to be written for the wrapper as Python may not support a lot of input types, For example
+           <center>[[File:func.png]]</center>
-           Example: Consider Alphabet::includeSymbol(wstring const &s)
-           Logical usage of this in python would be alphabet.includeSymbol(L'<n>'), but this gives a Syntax error as - L isn't a valid string prefix in Python.
+Logical usage of this in python would be:
+           <center>[[File:Pic3.png]]</center>
-           So functions have to be written to process the input taken in python and pass appropriate arguments to the C++ functions
+But this gives a Syntax error as - L isn't a valid string prefix in Python. in python. So we can accept a normal string ( str ) instead and pass the appropriate string along with the prefix to the core function
+           <center>[[File:Iofix.png]]</center>
 '''2. Tool to be used: '''
@@ Line 114: / Line 115: @@
 |}
+<center>[[File:Timeline.png]]</center>
 Week-Wise Goals:

@@ Line 80: / Line 80: @@
            import apertium.transducer.internal
            t = apertium.transducer.internal.Transducer().insertSingleTransduction()
+d.) Specialized input functions have to be written for the wrapper as Python may not support a lot of input types
+           Example: Consider Alphabet::includeSymbol(wstring const &s)
+           Logical usage of this in python would be alphabet.includeSymbol(L'<n>'), but this gives a Syntax error as - L isn't a valid string prefix in Python.
+           So functions have to be written to process the input taken in python and pass appropriate arguments to the C++ functions
 '''2. Tool to be used: '''
@@ Line 267: / Line 272: @@
 |}
 (***)The tasks are similar to the tasks of the referenced week
 == Coding Challenge ==

@@ Line 271: / Line 271: @@
 == Coding Challenge ==
-.)Make the Transducer model python importable
+* Transducer model python importable
+         import transducer
+* The library has
+        transducer.Transducer
+        transducer.Alphabet
+        transducer.Compression
+* Transducers can be built using
+        t = Transducer()
+        t.insertSingleTransduction()
+* t.show() returns the transducer in tuple format
+[https://github.com/arghyatiger/transducer-wrapper Repo]
 == About me: Education and Experience ==

@@ Line 277: / Line 277: @@
 == About me: Education and Experience ==
-I am a sophomore at IIIT-Hyderabad, India, pursuing my Dual-Degree in Computer Science and Computational Linguistics. I&rsquo;ve worked with C++ and Python closely in a lot of projects and I take keen interest in machine learning as well.I usually love building fun applications. The details of my work experience can be found [[here]].
+I am a sophomore at IIIT-Hyderabad, India, pursuing my Dual-Degree in Computer Science and Computational Linguistics. I&rsquo;ve worked with C++ and Python closely in a lot of projects and I take keen interest in machine learning as well.I usually love building fun applications. The details of my work experience can be found [https://researchweb.iiit.ac.in/~arghya.b/cv here].
 == Non-Summer Of Code Plans ==

@@ Line 113: / Line 113: @@
 {| class="wikitable" style="background-color:#b3ffb3;"
+! PHASE AND BRIEF DESCRIPTION
-! Phase And Brief Description
+! DURATION
-! Duration
+! TASK EXPLANATION
-! Task Explanation
+! DELIVERABLE OF THE WEEK
-! Deliverable for the week
 |-style="background-color:#ccffcc;"
 | COMMUNITY BONDING PERIOD
@@ Line 181: / Line 181: @@
 * END:June 17th
 |
-* Ref Week 1
+* Ref Week 1(***)
 |
 * First version of the apertium module that is python importable
@@ Line 266: / Line 266: @@
 * Final Release of the wrapper.
 |}
+(***)The tasks are similar to the tasks of the referenced week
 == Coding Challenge ==

@@ Line 48: / Line 48: @@
 == Why is it that I am interested in Apertium? ==
-Being a student, with primary academic focus on Computational Linguistics, Apertium happens to be one of the important tools that I use for my university assignments.The Apertium projects provide a nice blend of linguistic and coding tasks and that makes the projects interesting to me. Belonging to the intersect of people who understand both linguistics and computers these projects really are the most relvant to my domain. Also as a part of the long-term goal of contributing to the community, I think contributions to Apertium would make a significant impact on the Computational Linguistics community all around the globe and that further motivates me to work for Apertium.
+Being a student, with primary academic focus on Computational Linguistics, Apertium happens to be one of the important tools that I use for my university assignments like building transducers for small restricted grammar and building morphological generators.The Apertium projects provide a nice blend of linguistic and coding tasks and that makes the projects interesting to me. Belonging to the intersect of people who understand both linguistics and computers these projects really are the most relvant to my domain. Also as a part of the long-term goal of contributing to the community, I think contributions to Apertium would make a significant impact on the Computational Linguistics community all around the globe and that further motivates me to work for Apertium.
 == Which of the published tasks am I interested in? ==