Natural Language Processing Systems and Applications
N.B.: If you are a student enrolled in this course, please refer to the course page on Canvas. This page is purely for archival purposes.
Days | Time (P.M.) | Classroom |
---|---|---|
Tuesdays and Thursdays | 1:30-3:20 | RAI 116 |
Instructor | Teaching Assistant | |
Name | Ryan Georgi | David Inman |
Office | GUG 418-D | GUG 407 |
Contact | Use Canvas Inbox | |
Office Hours | Thu 12:30–2:00 or by Appt. | TBA |
Course description
This course examines building coherent systems to handle practical applications. Particular topics vary. This quarter we will focus on automatic summarization.
Course Resources
Textbook There is no required textbook for this course. However, you may find the following reference texts useful.
- Speech and Language Processing: An Introduction to Natural Language Processing, Computational Linguistics, and Speech Recognition, 2nd edition, by Daniel Jurafsky and James Martin.
- Foundations of Statistical Natural Language Processing, Chris Manning and Hinrich Schutze.
Some good survey texts in this area are:
- Advances in Automatic Text Summarization. (1999) Mani, I. and Maybury, M. T.,. MIT Press.
- Automatic Summarization (2001) I. Mani. John Benjamins.
- Automatic Summarization (2011), A. Nenkova and K. McKeown. NOW.
A number of published research articles will also provide background for the course. The articles are linked from the syllabus below, and the full citations are found in the reading list.
Historical proceedings from Summarization shared tasks are also available.
Prerequisites:
- LING 570, 571, 572
- CSE 373 (Data Structures) or equivalent
- Math 394 (Probability), MIT EdX 6.041, or equivalent
- Formal grammars, languages, and automata
- Programming in one or more of Java, Python, C/C++, or Perl
- Linux/Unix commands
Grading
- 60%: Deliverable Code
- 20%: Project Reports
- 10%: Project Presentations
- 10%: Class/Group Participation & Peer Evaluation
NOTE: While participation is set at 10%, this accounts only for the overhead of working in a team. Groupmates are still individually responsible for completing their portion of the group’s project and will receive grades individually.
Code Repository Posting Policy
During the course of the class, you are required to have a private code repository. Due to the nature of the project being potentially CV-worthy, you may make your repository public after the quarter is over, provided that you follow the following public code posting policy.
Course Policies
Additional detailed information on grading, collaboration, incompletes, etc.
Tentative schedule, subject to change without notice.