User:Irene/workplan - Revision history

Irene: /* Workplan */

2017-08-17T18:45:33Z

Workplan

Irene: /* Workplan */

2017-08-03T01:56:44Z

Workplan

Irene: /* Workplan */

2017-08-01T17:54:09Z

Workplan

Irene: /* Workplan */

2017-07-05T04:48:40Z

Workplan

Irene: /* Workplan */

2017-06-29T18:54:26Z

Workplan

Irene: /* Workplan */

2017-06-27T05:44:29Z

Workplan

Irene: /* Workplan */

2017-06-23T02:02:21Z

Workplan

Irene: /* Workplan */

2017-06-22T02:19:22Z

Workplan

Irene: /* Workplan */

2017-06-21T03:50:03Z

Workplan

Irene at 17:00, 20 June 2017

2017-06-20T17:00:16Z

@@ Line 77: / Line 77: @@
 | 11 || 8/7 - 8/13  || (cont. support for individual language pairs)
+||
+testing and refining for beta testing languages: kaz/kir, deu, eng, fao-nor
 |-
 | 12 || 8/14 - 8/20 || (cont. support for individual language pairs)
+||
+support for +thing, lsx-comp appends <j/> to the end of every entry, before <e/>, causes issues with paradigm, remove feature. <br/>
 |-
+/17:
 | 13 || 8/21 - 8/27 || (cont. support for individual language pairs)
 |-

@@ Line 71: / Line 71: @@
 | 10 || 7/31 - 8/6 || superblanks, integration, fstp
 ||
-/31: worked on superblanks, used fstp object
+/31: worked on superblanks, used fstp object <br />
-/1: improvements
+/1: improvements <br />
+/2: insert superblanks between the # in e.g. 'take# out' and between words in counterexamples by amending 'in' and 'out' strings, fixed error where ^ was not printing at the end of reordering a sep. multiword, updated dictionary to improve success rate <br />
 |-

@@ Line 57: / Line 57: @@
 |-
-| 7 || 7/10 - 7/16 ||
+| 7 || 7/10 - 7/16 || xml format, working compiler and processor
 |-
-| 8 || 7/17 - 7/23 ||
+| 8 || 7/17 - 7/23 || improving dictionary, compiler, and processor
 |-
@@ Line 69: / Line 69: @@
 |-
-| 10 || 7/31 - 8/6 || support for individual language pairs
+| 10 || 7/31 - 8/6 || superblanks, integration, fstp
+||
+/31: worked on superblanks, used fstp object
+/1: improvements
 |-

@@ Line 28: / Line 28: @@
 /24: migrated to source forge. added testing set.
 ||
 |-
 | || ||
-||
+|
 |-
@@ Line 36: / Line 37: @@
 |-
-| 5 || 6/26 - 7/2 || finite-state acceptor for 'take out'
+| 5 || 6/26 - 7/2 || hard-coded finite-state acceptor for 'take out'
 ||
-/26: trying to make the program backtrack when it gets to <ANY_CHAR> or <ANY_TAG>
+/26: trying to make the program backtrack when it gets to <ANY_CHAR> or <ANY_TAG> <br />
-/27: debugging & supporting any number of tags
+/27: debugging & supporting any number of tags <br />
-/28: successfully reads and prints ^take<vblex><pres><tag1><tag2><tag3><tag4>$ ^the<det><tag1><tag2><tag3><tag4>$ ^thing<n><sg><tag><Tag>$ ^out<adv>$
+/28: successfully reads and prints ^take<vblex><pres><tag1><tag2><tag3><tag4>$ ^the<det><tag1><tag2><tag3><tag4>$ ^thing<n><sg><tag><Tag>$ ^out<adv>$ <br />
-/29: working on being selective about what middle words are accepted
+/29: working on being selective about what middle words are accepted <br />
+/1: python prototype for acceptor is pretty much working, just needs to be able to read from corpuses that don't put every sentence on a new line, and to assign numbers to states in a more elegant fashion. <br />
-/30:
 |-
-| 6 || 7/3 - 7/9 || finite-state transducer for 'take out'
+| 6 || 7/3 - 7/9 || hard-coded finite-state transducer for 'take out'
+||
+/3: tried to convert the python script to c++ code. trying to use lttoolbox's FST class. <br />
+/4: still trying to convert to c++ and use lttoolbox <br />
+/5:
+/6:
+/7:
+/8:
+/9:
 |-
@@ Line 54: / Line 63: @@
 |-
-!'''Second evaluation''' !! 7/24 - 7/28 !! XML representation, finite-state implementation
+!'''Second evaluation''' !! 7/24 - 7/28 !! finite-state implementation
 |-

@@ Line 24: / Line 24: @@
 /19: Still trying to get FST example to compile on my computer. Worked on the reordering module for English in c++ <br />
 /20: Spent a lot of time trying to fix hashing errors with the c++ prototype, and then gave up with c++. Switched everything to python because I've been spending too much time working out c++ API. Wrote documentation. Still trying to get [https://github.com/unittest-cpp/unittest-cpp unittest++] and the fst example to compile. <br />
+/21: Separated the prototype (now scripted in python) into organized files.
-/21: Separated the prototype (now scripted in python) into organized files. The reordering module for English and Spanish are under control (there is still some tedious work to with them, which I was not able to get to today). I was I think I am feeling much more confident in being able to get the prototype working by the evaluation deadline this week. I had listed a bunch of languages in my original proposal, except I couldn't find data on separable verbs except for German (. I feel a little out-of-place for fiddling with languages that I am not familiar with. However, I am not confident at all that any of this will even be of use (other than the basic idea) when we try to integrate it into Apertium because most of my code will probably be replaced with existing Lttoolbox functions.
 /23: video meeting.
+/24: migrated to source forge. added testing set.
 ||
 |-
@@ Line 38: / Line 39: @@
 ||
 /26: trying to make the program backtrack when it gets to <ANY_CHAR> or <ANY_TAG>
+/27: debugging & supporting any number of tags
+/28: successfully reads and prints ^take<vblex><pres><tag1><tag2><tag3><tag4>$ ^the<det><tag1><tag2><tag3><tag4>$ ^thing<n><sg><tag><Tag>$ ^out<adv>$
+/29: working on being selective about what middle words are accepted
+/30:
 |-

@@ Line 1: / Line 1: @@
 == Workplan ==
-[https://github.com/irene-tang/separable-words on github]
 {|class=wikitable
@@ Line 21: / Line 20: @@
 /21: work on reordering module for Celtic language (welsh) <br />
 /22: work on reordering module for <br />
-/23: work on reordering module for  && prototype should be finished <br />
+/23: work on reordering module for  & prototype should be finished <br />
 ||
 /19: Still trying to get FST example to compile on my computer. Worked on the reordering module for English in c++ <br />
 /20: Spent a lot of time trying to fix hashing errors with the c++ prototype, and then gave up with c++. Switched everything to python because I've been spending too much time working out c++ API. Wrote documentation. Still trying to get [https://github.com/unittest-cpp/unittest-cpp unittest++] and the fst example to compile. <br />
-/21: Separated the prototype (now scripted in python) into organized files. The reordering module for English and Spanish are under control (there is still some tedious work to with them, which I was not able to get to today). I was I think I am feeling much more confident in being able to get the prototype working by the evaluation deadline this week. I had listed a bunch of languages in my original proposal, except I couldn't find data on separable verbs except for German (. I feel a little out-of-place for fiddling with languages that I am not familiar with. However, I am not confident at all that any of this will even be of use (other than the basic idea) when we try to integrate it into Apertium because most of my code will probably be replaced with existing Lttoolbox functions. :(
+/21: Separated the prototype (now scripted in python) into organized files. The reordering module for English and Spanish are under control (there is still some tedious work to with them, which I was not able to get to today). I was I think I am feeling much more confident in being able to get the prototype working by the evaluation deadline this week. I had listed a bunch of languages in my original proposal, except I couldn't find data on separable verbs except for German (. I feel a little out-of-place for fiddling with languages that I am not familiar with. However, I am not confident at all that any of this will even be of use (other than the basic idea) when we try to integrate it into Apertium because most of my code will probably be replaced with existing Lttoolbox functions.
+/23: video meeting.
-/22: I think I accomplished very little today...Wrote a small handful of tests (python's unittest is great). Slightly enhanced the module: put deliminators (commas, periods) in the right place when transferring to output file; combined the multiword (e.g. 'take<>#out' rather than 'take<> out<>'. I'm really losing motivation to continue enhancing the module because I know none of the prototype script (whether it's in python or c) will be of much actual use. I'm looking forward to next week, after the first deadline is over, so I will be able to spend more time understanding Lttoolbox API. I found it frustrating on days when I did not accomplish very many useful lines of code at the end of the day, but I tried to keep in mind that a significant portion of any programming project is to read and modify existing code.
 ||
 |-
@@ Line 36: / Line 35: @@
 |-
-| 5 || 6/26 - 7/2 ||
+| 5 || 6/26 - 7/2 || finite-state acceptor for 'take out'
+||
+/26: trying to make the program backtrack when it gets to <ANY_CHAR> or <ANY_TAG>
 |-
-| 6 || 7/3 - 7/9 ||
+| 6 || 7/3 - 7/9 || finite-state transducer for 'take out'
 |-

@@ Line 19: / Line 19: @@
 /19: separate out the language-dependent functions in the c++ prototype, work on reordering module for Romance languages (Spanish, Portuguese) <br />
 /20: work on reordering module for Germanic language (Swedish) <br />
-/21l: work on reordering module for Celtic language (welsh) <br />
+/21: work on reordering module for Celtic language (welsh) <br />
-/22: work on more modules? <br />
+/22: work on reordering module for <br />
-/23: prototype should be finished
+/23: work on reordering module for  && prototype should be finished <br />
 ||
 /19: Still trying to get FST example to compile on my computer. Worked on the reordering module for English in c++ <br />
 /20: Spent a lot of time trying to fix hashing errors with the c++ prototype, and then gave up with c++. Switched everything to python because I've been spending too much time working out c++ API. Wrote documentation. Still trying to get [https://github.com/unittest-cpp/unittest-cpp unittest++] and the fst example to compile. <br />
+/21: Separated the prototype (now scripted in python) into organized files. The reordering module for English, Spanish, and Portuguese are under control (there is still some tedious work to with them, which I was not able to get to today). I was I think I am feeling much more confident in being able to get the prototype working by the evaluation deadline this week, for all of the languages that I wrote in my original proposal. I do feel out-of-place for fiddling with languages that I am not familiar with. However, I am not confident at all that any of this will even be of use (other than the basic idea) when we try to integrate it into Apertium because most of my code will probably be replaced with existing Lttoolbox functions. :(
 ||
 |-

@@ Line 4: / Line 4: @@
 {|class=wikitable
 |-
-! Week !! Dates !! Goals/Progress !! Bugs !! Evaluation
+! Week !! Dates !! Goals !! Progress/Notes !! Evaluation
 |-
@@ Line 13: / Line 13: @@
 |-
-| 3 || 6/12 - 6/18 || [[Irene/proposal#workplan | preparing data]], prototype script set up, read specifications of Lttoolbox API || ||
+| 3 || 6/12 - 6/18 || preparing data, prototype script set up, read specifications of Lttoolbox API || ||
 |-
+| 4 || 6/19 - 6/25 ||
-| 4 || 6/19 - 6/25 ||  6/19 goal: separate out the language-dependent functions in the c++ prototype, work on reordering module for Romance languages (Spanish, Portuguese) <br />
-/20 goal: work on reordering module for Germanic language (Swedish) <br />
+/19: separate out the language-dependent functions in the c++ prototype, work on reordering module for Romance languages (Spanish, Portuguese) <br />
-/21 goal: work on reordering module for Celtic language (welsh) <br />
+/20: work on reordering module for Germanic language (Swedish) <br />
-/22 goal: work on more modules? <br />
+/21l: work on reordering module for Celtic language (welsh) <br />
+/22: work on more modules? <br />
-/23 goal: prototype should be finished
+/23: prototype should be finished
-|| 6/19: get fst example to compile on my computer
+||
-/20: fix hashing on c++ prototype, trying to get unittest++ and fst example to compile
+/19: Still trying to get FST example to compile on my computer. Worked on the reordering module for English in c++ <br />
+/20: Spent a lot of time trying to fix hashing errors with the c++ prototype, and then gave up with c++. Switched everything to python because I've been spending too much time working out c++ API. Wrote documentation. Still trying to get [https://github.com/unittest-cpp/unittest-cpp unittest++] and the fst example to compile. <br />
 ||
 |-
 | || ||
 ||
-|-
+|-
 ! '''First evaluation''' !! 6/26 - 6/30 !! testing framework set up + prototype system in Python !! !!
 |-