Difference: CLMASurvivalGuide (13 vs. 14)

Revision 142015-01-29 - olzama

Line: 1 to 1

CLMS Survival Guide

Line: 25 to 25
  • Read the glossary at the back of the book. Explanations of all those mysterious linguistics terms!
  • Read the book before coming to lecture.
  • Xerox the entire appendix A of the textbook and cut out each type and lexical entry. Paste them onto a gigantic piece of craft paper in a tree hierarchy so you can visualize the inheritance. I wish I had done this prior to just before the final exam.
  • Get a copy of Linguistic Fundamentals for NLP: 100 Essentials from Morphology and Syntax (Bender 2013) and look up concepts that are new for you there. The book explains important things in relatively simple terms, and it is easier to read about them there first, then try to understand the HPSG analysis of these things. Sections #90 and #91 (raising and control) may be particularly helpful.

Ling 570

  • This class often lets you choose which programming language you want to use, as long as your code can be run on patas. Java, Perl, Lisp, Python, C# (Mono), C, C++, and others (?) are all installed and available for you to use so choose the one that you're most comfortable with.
  • Work in groups to write fairly detailed pseudocode before you start individual programming. When you work alone, even if you plan to thing everything through first, the temptation to just get to the coding is sometimes too big -- and you can pay for it dearly in some of the more involved assignments. when you work in a team, you will keep each other from rushing to implement things (not to mention from procrastination and surfing the web!) and this will make the harder assignments a lot less painful. This also applies to 572.

Ling 571

Ling 572

Line: 40 to 42
  • To get the most out of this challenging class, use a little time during Christmas break to install your linux machine, read the Copestake text, and play with the LKB before the first class meeting. You won't be sorry.
  • Contact gslayden at u if you want to use Windows for this class and be an early adopter of the 'agree' grammar engineering environment.
  • Apply the 10 minute rule!
  • Set a very serious deadline for when you will finish implementing, each week. Make yourself stop after you spent the hours that you allocated on the implementation. Allocate at least almost the same number of hours for the writeup. While working on the writeup, you will find bugs in your implementation and will need time to fix them or at least understand them well in order to be able to explain them clearly in the writeup. Remember (and remind yourself often): you do not need to implement everything 100% in this class to get 100% for the assignment. If you don't follow this rule, the number of hours you spend on this class can get unreasonable -- but it doesn't have to be this way!
  -- EmilyBender - 05 Dec 2007 \ No newline at end of file
This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback
Privacy Statement Terms & Conditions