Difference between revisions of "User:Khannatanmai"

From Apertium
Jump to navigation Jump to search
 
(197 intermediate revisions by 4 users not shown)
Line 1: Line 1:
'''Google Summer of Code 2019: Proposal [First Draft]'''

'''Anaphora Resolution'''

== Personal Details ==
== Personal Details ==

'''Name:''' Tanmai Khanna
'''Name:''' Tanmai Khanna


Line 15: Line 10:
'''LinkedIn:''' [http://linkedin.com/in/khannatanmai khannatanmai]
'''LinkedIn:''' [http://linkedin.com/in/khannatanmai khannatanmai]


'''Current Designation:''' Graduate Researcher in the LTRC Lab, IIIT Hyderabad (5th year student) and a Teaching Assistant for Linguistics courses
== About Me ==


'''Time Zone:''' GMT+5:30
'''Open Source Softwares I use:''' I have used Apertium in the past, Ubuntu, Firefox, VLC.


== About Me ==
'''Professional Interests:''' I’m currently studying NLP and I have a particular interest in Linguistics and NLP tools, specifically Machine Translation and its components.

'''Hobbies:''' I love Parliamentary Debating, Singing, and Reading.

'''What I want to get out of GSoC'''

I’ve studied about apertium and it’s amazing to me that I get an opportunity to work with them. NLP is what I want to do in life and working with a team to develop tools that actual people use will be invaluable experience that classes simply cannot match. Of course, the stipend is a big plus!

=== Why is it that I am interested in Apertium and Machine Translation? ===

Apertium is an Open Source Rule-based MT system. I have been part of the Machine Translation lab in my college and it interests me because it’s a complex problem and is often called NLP-Complete by my professors, i.e. it uses most of the tools NLP has to offer and hence if one learns to do good MT they learn most of Natural Language Processing.

Each part of Apertium's mission statement, especially the fact that they focus on Low Resource Languages, interests me and excites me to be working with them. While Neural Networks and Deep Learning is the fad these days, it only works for resource rich languages and that’s why I feel a tool which is rule based and open source really helps the community with language pairs that are resource poor and gives them free translations for their needs.

== Project Proposal ==
=== Which of the published tasks am I interested in? What do I plan to do? ===

Anaphora Resolution - Currently uses default male. I don’t plan to make a perfect anaphora resolution in 3 months, but I’m confident that I can make one which works significantly better than the default male and it can increase the fluency and intelligibility of output by a lot.

The Anaphora Resolution tool will be language agnostic and hence this project affects almost all language pairs in apertium and hence it affects almost everyone using the tool. Pronouns are present in a lot of languages and with gendered pronouns, singular, plural, etc., we need to find out what they refer to. Why is this important?

A sentence like “The group agreed to release his mission statement” is grammatically incoherent and an incorrect pronoun will more often than not confuse people in more complex sentences.

What puts people off Machine Translation is the lack of fluency, and I feel this is an important contribution to fluency and will definitely generate more fluent sentences leading to more trust in this tool.


'''Professional Interests:''' I’m currently doing research in Computational Linguistics and I have a particular interest in Linguistics and NLP tools, specifically Machine Translation and its components.
=== Work Plan ===


'''Hobbies:''' I enjoy playing the bass, singing, reading, and used to be super into Parliamentary Debating in uni.
* Understand the system, Get familiar with the files that I need to modify
* Formalise the problem, limit the scope of anaphora resolution (To Anaphora needed for MT)
* May include general anaphora (Need to decide on scope [for gisting])
* Annotation of anaphora for evaluation
* Flowchart of proposed system and Pseudocode
* Implement a scoring system for antecedent indicators [work for Target Language:English for now]
* Decide on a definite context window
* Implement basic anaphora outside the pipeline (python)
* Implement basic transfer rules to see if final system will work
* A basic prototype of final system ready
* Port the basic prototype to C++ (All further coding to be done in C++)
* TEST the system
* Document the outline
* Implement system to work out all possible antecedents
* Add ability to give antecedents a score
* TEST basic sentences with single antecedents, Test the pipeline
* '''Deliverable #1: Anaphora Resolution for single antecedents, with transfer rules [The full pipeline]'''
* Implement Antecedent Indicators:
* Implement Boosting Indicators
* Implement Impeding Indicators
* Implement tie breaking systems
* Implement fallback for anaphora (in case of too many antecedents or not past certainty threshold)
* Code to remember antecedents for a certain window
* TEST Scoring System
* Implement transfer rules to deal with new additions
* Evaluate current system and produce precision and recall
* Implement Expectation-Maximization Algorithm
* Use Monolingual corpus to get probabilities of anaphora
* Implement choosing anaphora with max probability:
* If Scoring System has a tie
* As an independent system
* Compare the effectiveness of the above two possibilities
* Test EM Algorithm and implemented system
* Evaluate if addition of EM gives us significant benefits
* '''Deliverable #2: Anaphora Resolution with antecedent scores, fallback mechanism, EM algorithm'''
* Document Antecedent Indicators, Scoring System, EM Algorithm, Fallback
* Insert into Apertium pipeline
* Implement code to accept input in chunks and process it
* Output with anaphora attached
* EXTENSIVELY TEST final system with multiple pairs, see what needs to be changed for pairs
* TEST for backwards compatibility and ensure it
* '''Project Completed'''


== Ideas ==
=== Additional Information ===
* Agreement: Different for different languages?
* Agreement rules in Arabic, however, are different. For instance, a set of non- human items (animals, plants, objects) is referred to by a singular feminine pronoun.
* Since Arabic is an agglutinative language, the pronouns may appear as suffixes of verbs, nouns (e.g., in the case of possessive pronouns) and preposi- tions.


'''Constructions in low resource MT:''' [[User:Khannatanmai/Constructions]]
* '''Antecedent Indicators:'''


== Google Summer of Code 2019 -- Anaphora Resolution ==
* Boosting Indicators[Scoring different for different languages]
* First NPs
* Indicating Verbs
* Lexical Reiteration
* Section Heading Preference
* Collocation Pattern Preference
* Immediate reference (if it is pronoun then its reference)
* Sequential Instructions


'''Proposal ''': [[User:Khannatanmai/GSoC2019Proposal]]
* Impeding Indicators
* Indefiniteness
* Prepositional NPs


'''Final Report''': [[User:Khannatanmai/GSoC2019Report]]
=== Reasons why Google and Apertium should sponsor it ===


== Google Summer of Code 2020 -- Markup handling with wordbound blanks ==
I feel that this project affects almost all language pairs in apertium and hence it affects almost everyone using Apertium. A decent anaphora resolution will give the output an important boost in it’s fluency and intelligibility, not just for one language, but all of them.
It’s a project which has promising future prospects - apart from the fact that language specific features can be added to improve it, we’ll be doing anaphora resolution even for languages which don’t need it to pick the correct pronoun. Doing this will enable Apertium to do gisting translation, which is an important tool and anaphora resolution is an essential cog in that wheel.


'''Proposal: Modifying the apertium stream format and eliminating dictionary trimming: [[User:Khannatanmai/GSoC2020Proposal_Trimming]]'''
=== A description of how and who it will benefit in society ===
It will definitely benefit most users of Apertium and hopefully will attract more people to the tool. I’m from India and for a lot of our languages we don’t have the data to create reliable Neural MT systems. Similarly, for all resource poor languages, Apertium provides an easy and reliable MT system for their needs. That’s how Apertium benefits society already.


Development of the stream extension: [[User:Khannatanmai/New_Apertium_stream_format]]
I feel that currently what repels people from Machine Translation is unintelligible outputs and too much post editing which makes it useless for them. While Apertium aims to make minimal errors, as of now it selects a default male pronoun and that leads to several unintelligible outputs. Fixing that and making the system more fluent and intelligible overall should definitely attract people to using Machine Translation and help them to reduce costs of time and money.


Eliminating Dictionary Trimming: [[User:Khannatanmai/Eliminating_Dictionary_Trimming]]
== Skills and Qualifications ==
I'm currently a third year student at IIIT Hyderabad where I'm studying Computational Linguistics. It is a dual degree where we study Computer Science, Linguistics, NLP, etc. right from the start. I've been interested in linguistics from the start and due to the rigorous programming courses, I'm also adept at several programming languages like Python, C++, etc.


'''Progress: [[User:Khannatanmai/GSoC2020Progress]]'''
Due to the focused nature of our course, I've worked in several projects, such as building Translation Memory, Detecting Homographic Puns, POS Taggers, Grammar and Spell Checkers, Named Entity Recognisers, Building Chatbots, etc. all of which required a working understanding of Natural Language Processing.


Documentation of features related to secondary tags: [[User:Khannatanmai/Secondary_tags_features]]
=== Coding Challenge ===
I successfully completed the coding challenge and proposed an alternate method to process the input as a chunk which resulted in a speedup of more than 2x.


Alternate stream modification proposal: [[User:Khannatanmai/Alternate_stream_modification]]
The repo can be found at: https://github.com/khannatanmai/apertium


Development of the updated stream extension: [[User:Khannatanmai/Secondary_info_apertium_stream_format]]
Files in Repo:
* Code to do basic anaphora resolution (last seen noun), input taken as a stream (byte by byte)
* Code to do basic anaphora resolution (last seen noun), input taken as a stream (as a chunk)
* Speed-Up Report


'''Development of wordbound blanks: [[User:Khannatanmai/Wordbound_blanks]]'''
== Non-Summer-Of-Code Plans ==


'''Documentation of wordbound blanks: [[Wordbound_blanks]]'''
I will have my college vacations during GSoC so will have no other commitments in that period and will be dedicated to GSoC full time, i.e. 40 hours a week.


'''Final Report: [[User:Khannatanmai/GSoC2020_Final_Report]]'''
I am planning to go on a short trip to London from 18 May to 25 May but I will have internet there and will be working a little less than normal but will catch up.

Latest revision as of 04:27, 9 September 2020

Personal Details[edit]

Name: Tanmai Khanna

E-mail address: khanna.tanmai@gmail.com , tanmai.khanna@research.iiit.ac.in

IRC: khannatanmai

GitHub: khannatanmai

LinkedIn: khannatanmai

Current Designation: Graduate Researcher in the LTRC Lab, IIIT Hyderabad (5th year student) and a Teaching Assistant for Linguistics courses

Time Zone: GMT+5:30

About Me[edit]

Professional Interests: I’m currently doing research in Computational Linguistics and I have a particular interest in Linguistics and NLP tools, specifically Machine Translation and its components.

Hobbies: I enjoy playing the bass, singing, reading, and used to be super into Parliamentary Debating in uni.

Ideas[edit]

Constructions in low resource MT: User:Khannatanmai/Constructions

Google Summer of Code 2019 -- Anaphora Resolution[edit]

Proposal : User:Khannatanmai/GSoC2019Proposal

Final Report: User:Khannatanmai/GSoC2019Report

Google Summer of Code 2020 -- Markup handling with wordbound blanks[edit]

Proposal: Modifying the apertium stream format and eliminating dictionary trimming: User:Khannatanmai/GSoC2020Proposal_Trimming

Development of the stream extension: User:Khannatanmai/New_Apertium_stream_format

Eliminating Dictionary Trimming: User:Khannatanmai/Eliminating_Dictionary_Trimming

Progress: User:Khannatanmai/GSoC2020Progress

Documentation of features related to secondary tags: User:Khannatanmai/Secondary_tags_features

Alternate stream modification proposal: User:Khannatanmai/Alternate_stream_modification

Development of the updated stream extension: User:Khannatanmai/Secondary_info_apertium_stream_format

Development of wordbound blanks: User:Khannatanmai/Wordbound_blanks

Documentation of wordbound blanks: Wordbound_blanks

Final Report: User:Khannatanmai/GSoC2020_Final_Report

Retrieved from "https://wiki.apertium.org/w/index.php?title=User:Khannatanmai&oldid=72940"