Midterm overview - Revision history

Jwashin1: /* The assignment */

2026-03-16T00:47:10Z

‎The assignment

Jwashin1: /* The assignment */

2026-03-16T00:46:15Z

‎The assignment

Jwashin1 at 15:52, 5 March 2026

2026-03-05T15:52:14Z

Jwashin1: /* Measuring precision and recall */

2025-03-06T16:30:15Z

‎Measuring precision and recall

Jwashin1 at 16:29, 6 March 2025

2025-03-06T16:29:25Z

Jwashin1: /* Midterm Overview */

2023-03-21T13:27:14Z

‎Midterm Overview

Jwashin1: /* The assignment */ this year's date

2023-03-21T13:26:12Z

‎The assignment: this year's date

Jwashin1: /* Midterm Overview */

2023-03-19T16:55:31Z

‎Midterm Overview

Jwashin1: /* Midterm Overview */

2023-03-19T15:12:51Z

‎Midterm Overview

Jwashin1: /* The assignment */

2022-03-01T05:14:28Z

‎The assignment

@@ Line 107: / Line 107: @@
 <s>You may create a visual aid to support your presentation.  I recommend creating a single page, either on the wiki or a PDF slide/"poster" with five sections that you can step through quickly.</s>  This year, please add '''one''' slide to the [https://docs.google.com/presentation/d/1TAR5_Eh0vGFnriz7VsCZhUUjRcMFBqqarOIhJuMHV1U/edit shared deck] (let me know if you have trouble accessing it).
-Each point can be covered very briefly—you only have about 5 minutes!
+Each point can be covered very briefly—you only have about 5-10 minutes total!
 The point of this assignment is for the class to get a picture of what their fellow students' work is like.  Everyone's working on different languages, so this should give some sense of the diversity of problems encountered.  On the other hand, everyone's struggled with one thing or another, so there will be some familiarity in others' overviews.
 [[Category:Assignments]]

@@ Line 77: / Line 77: @@
 == The assignment ==
-This assignment is due in class on Thursday of the 8th week (this semester, '''11:20 on Thursday, March 20th, 2025''').
+This assignment is due in class on Tuesday of the 8th week (this semester, '''9:55 on Tuesday, March 17th, 2026''').
 This assignment has two parts:
@@ Line 93: / Line 93: @@
 === Midterm Overview ===
-For your midterm overview, you will need to speak for '''about 5 minutes''' and outline the following:
+For your midterm overview, you will need to speak for '''about 5 to 10 minutes''' and outline the following:
 * What language you worked on and '''some quick facts''' about it (where it's spoken, the size of the community that uses it, any prominent languages it might be related to),
 * General morphological (lots of prefixes? suffixes? reduplication?) and phonological/orthographic (lots of phonological changes? accent markings? syllabic orthography?) properties of the language,

@@ Line 105: / Line 105: @@
 ** Alternatively, feel free to share a problem that's caused you lots of grief and/or that you still haven't solved.
-<s>You may create a visual aid to support your presentation.  I recommend creating a single page, either on the wiki or a PDF slide/"poster" with five sections that you can step through quickly.</s>  This year, please add '''one''' slide to the [https://docs.google.com/presentation/d/1Brb_ZWVe8Qih8SqKdk9vxDbk2z3eUj4Q6lu2yzrKa14/edit shared deck] (let me know if you have trouble accessing it).
+<s>You may create a visual aid to support your presentation.  I recommend creating a single page, either on the wiki or a PDF slide/"poster" with five sections that you can step through quickly.</s>  This year, please add '''one''' slide to the [https://docs.google.com/presentation/d/1TAR5_Eh0vGFnriz7VsCZhUUjRcMFBqqarOIhJuMHV1U/edit shared deck] (let me know if you have trouble accessing it).
 Each point can be covered very briefly—you only have about 5 minutes!

@@ Line 70: / Line 70: @@
 In the example above of hand annotation, the precision is 90% (there are 9 true positives and 1 false positive), meaning that 90% of the returned analyses were correct.  Recall is lower, at 75% (there are 9 true positives and 3 false negatives), meaning that only 75% of the correct analyses were returned.
-There is a script called <code>precisionRecall</code> that can be used to calculate from files like those above.  You can run <code>precisionRecall referencecorpus.txt annotatedcorpus.txt</code>.
+There is a script called <code>precisionRecall</code> that can be used to calculate from files like those above.  You can run it like this:
 If you have trouble with the script on the lab computers or want to use it on your own computer, you can get it from the [[Using the tools on your own system#Misc tools|tools repo]].  On your own system, you can clone and then update the repo (<code>git pull</code>) and run <code>sudo make</code> to ensure that you have this script installed.
 == The assignment ==

@@ Line 70: / Line 70: @@
 In the example above of hand annotation, the precision is 90% (there are 9 true positives and 1 false positive), meaning that 90% of the returned analyses were correct.  Recall is lower, at 75% (there are 9 true positives and 3 false negatives), meaning that only 75% of the correct analyses were returned.
-There is a script in the [[Using the tools on your own system#Misc tools|tools repo]] called <code>precisionRecall</code>.  You can update the repo (<code>git pull</code>) and run <code>sudo make</code> to ensure that you have this script installed on your system.  You can then run <code>precisionRecall referencecorpus.txt annotatedcorpus.txt</code>.
+There is a script called <code>precisionRecall</code> that can be used to calculate from files like those above.  You can run <code>precisionRecall referencecorpus.txt annotatedcorpus.txt</code>.
@@ Line 76: / Line 78: @@
 == The assignment ==
-This assignment is due in class on Thursday of the 8th week (this semester, '''9:55 on Thursday, March 23rd, 2023''').
+This assignment is due in class on Thursday of the 8th week (this semester, '''11:20 on Thursday, March 20th, 2025''').
 This assignment has two parts:
@@ Line 104: / Line 106: @@
 ** Alternatively, feel free to share a problem that's caused you lots of grief and/or that you still haven't solved.
-<s>You may create a visual aid to support your presentation.  I recommend creating a single page, either on the wiki or a PDF slide/"poster" with five sections that you can step through quickly.</s>  This year, please add a slide to the [https://docs.google.com/presentation/d/19EMa81OY1Megc-WTdRvffVF8NFljIwnV0a4mmQHC3-c/edit shared deck] (let me know if you have trouble accessing it).
+<s>You may create a visual aid to support your presentation.  I recommend creating a single page, either on the wiki or a PDF slide/"poster" with five sections that you can step through quickly.</s>  This year, please add '''one''' slide to the [https://docs.google.com/presentation/d/1Brb_ZWVe8Qih8SqKdk9vxDbk2z3eUj4Q6lu2yzrKa14/edit shared deck] (let me know if you have trouble accessing it).
 Each point can be covered very briefly—you only have about 5 minutes!

@@ Line 93: / Line 93: @@
 === Midterm Overview ===
 For your midterm overview, you will need to speak for '''about 5 minutes''' and outline the following:
-* What language you worked on and some quick facts about it (where it's spoken, the size of the community that uses it, any prominent languages it might be related to),
+* What language you worked on and '''some quick facts''' about it (where it's spoken, the size of the community that uses it, any prominent languages it might be related to),
 * General morphological (lots of prefixes? suffixes? reduplication?) and phonological/orthographic (lots of phonological changes? accent markings? syllabic orthography?) properties of the language,
 * Some evaluation metrics:
-** What sort of coverage you're currently getting on your corpus (as a percentage of forms analysing, and as number of tokens being analysed out of total), and what did the most to increase that number in the last couple couple weeks,
+** What sort of '''coverage''' you're currently getting on your corpus (as a percentage of forms analysing, and as number of tokens being analysed out of total), and what did the most to increase that number in the last couple couple weeks,
-** The accuracy of your transducer (precision and recall, as you measured above),
+** The '''accuracy''' of your transducer (precision and recall, as you measured above),
-** The mean ambiguity over your corpus with and without disambiguation.
+** The mean '''ambiguity''' over your corpus with and without disambiguation.
-* A couple aspects of the course that you've found the most challenging (finding resources? understanding what constitutes normative orthography? understanding the grammar? learning to work with lexd or twol? implementing prefixes/infixes? dealing with too many characters in the orthography? not being able to find ambiguous forms?),
+* A couple aspects of the course that you've found the most '''challenging''' (finding resources? understanding what constitutes normative orthography? understanding the grammar? learning to work with lexd or twol? implementing prefixes/infixes? dealing with too many characters in the orthography? not being able to find ambiguous forms?),
 * Discuss some specific aspect(s) of the orthography/grammar that was/were particularly challenging to understand or deal with (one of the following):
 ** You can briefly outline a grammar point (what the alternation is) and what you had to do to implement it computationally.
 ** Alternatively, feel free to share a problem that's caused you lots of grief and/or that you still haven't solved.
-You may create a visual aid to support your presentation.  I recommend creating a single page, either on the wiki or a PDF slide/"poster" with five sections that you can step through quickly.
+<s>You may create a visual aid to support your presentation.  I recommend creating a single page, either on the wiki or a PDF slide/"poster" with five sections that you can step through quickly.</s>  This year, please add a slide to the shared deck.
 Each point can be covered very briefly—you only have about 5 minutes!

@@ Line 76: / Line 76: @@
 == The assignment ==
-This assignment is due in class on Thursday of the 7th week (this semester, '''8:30 on Thursday, March 7th, 2019''').
+This assignment is due in class on Thursday of the 8th week (this semester, '''9:55 on Thursday, March 17th, 2022''').
 This assignment has two parts: