Overview
CSCI101 is an introduction to languages and the theory of computation. The course investigates models of computation such as finite-state automata and Turing machines, formal languages such as context free grammars, and computability. Connections to applications such as lexical analysis and parsing will be explored. Along the way there will be proof-writing and coding.
The prerequisite for the class is CSCI054. CSCI062 is a co-requisite. You should not be taking (will not receive credit for) this class if you have already taken CSCI081. Send me (Prof. Chen) an email if you have questions about these requirements.
Resources
The professor for this class is Professor Chen. Please stop by my office hours (Tues 1:30-3pm and Thurs 10-11:30am) if you want to talk about the class, about theory more generally, or anything else. I'll also be available for occasional small group lunches/dinners (see sign-up sheet on my office door) if you'd just like to chat sometime. I'm also happy to meet with you at other times by appointment (in person or on zoom): send me an email with some times that are good for you and a sense of what you want to talk about.
The mentors/TAs for the class are: Rory Beals, Arsh Chhabra, Cameron Hatler, Richard Kim, and Vivian Song. In general the mentor hours will be on the 1st or 2nd floor of Edmunds at times TBD. Please expect occasional changes and cancellations; these will be posted on Slack.
We'll be using Canvas for distributing course materials. We'll be using Slack for announcements and informal discussion. We'll be using Gradescope for submitting and returning assignments. Let me know if you run into issues accessing any of these.
The textbook for the class is:
In addition, since you'll be writing code in Haskell, it's recommended that you have access to something such as the following:
You are encouraged to look for and to use other resources to learn more about the ideas and concepts (you may not, however, look directly for answers to individual questions on the weekly problem sets!). Some others that people have found useful are:
If you find anything particularly helpful you are encouraged to share it with the class on Slack!If you need accommodations please contact the Disability Coordinator on your home campus. The process for Pomona students is available here.
More generally, life happens to all of us and I know there may be times when staying on top of the workload in this class is going to feel like too much on top of everything else that you're managing. If that happens, please come talk to me so that I'm aware and so that we can work together to try to figure out a plan. Please keep in touch! (Note: I encourage you to come chat with me even if there isn't anything in particular that you feel you need to discuss!)
Logistics
The basic flow each week will be as follows:
The lectures will be in Edmunds 114.
You will be assigned to a small group of approximately 5-6 students the first week of classes. Your group will work together for the entire semester; your first task will be to find an hour when all of you can meet either Thursday or Friday. The plan is for each group to have an assigned TA who will attend the meetings to answer questions, talk through concepts, etc. Each week there will be a low-stakes assignment to work on during your group meeting; this should be turned in by 10pm Friday evening on Gradescope. There may occasionally be anonymous surveys for you to give feedback on how your group is doing, but please feel free to bring up concerns with me at any time.
In addition, there will be a weekly problem set. The assignments will mostly be done and submitted in pairs and will also be submitted on Gradescope. The pairs will be by assignment for the first few weeks and then at your discretion after that. Problems on the assignment will ask you to apply concepts in new ways. You may discuss the problems with anyone else currently taking cs101 (or with the TAs or myself), but each pair must write up their own solution without referring to any written/typed/etc materials that may have been generated during such discussion. In addition, you must acknowledge who you worked with and what their contribution was. Unless stated otherwise, problem sets are due by 10pm on the due date.
Finally there will be a written, in-class checkpoint approximately every 5 weeks. There will also be a take-home final exam that will need to be completed no later than noon on Monday 12/9.
The breakdown of grades will be as follows:
Schedule
This is a high-level outline of the planned schedule. Note that the calendar is subject to change. For the readings "ACC" refers to the book "Automata, Computability, and Complexity" by Elaine Rich.
Unless stated otherwise, all deadlines are at 10pm on the given date.
Week | Day | Date | Topic | Reading | Due |
---|---|---|---|---|---|
1 | M | 8/26 | (review) sets, logic, function, relations, proofs; small groups | ACC: Ap A | intro survey due noon on 8/25 |
W | 8/28 | basic definitions, languages, FSM, regular languages | ACC: Ch 5.1 | ||
F | 8/30 | week01-group | |||
Su | 9/1 | week01-ps | |||
2 | M | 9/2 | *** no class - Labor Day *** | ||
W | 9/4 | constructing FSM, closure properties of regular languages | ACC: Ch 5.1-3 | ||
F | 9/6 | week02-group | |||
Su | 9/8 | week02-ps (written, coding) | |||
3 | M | 9/9 | NDFSM | ACC: Ch 5.4 | |
W | 9/11 | Myhill-Nerode, minimization | ACC: Ch 5.7 | ||
F | 9/13 | week03-group | |||
Su | 9/15 | week03-ps | |||
4 | M | 9/16 | non-regular languages and the pumping lemma | ACC: Ch 8 | |
W | 9/18 | regular grammars, expressions | ACC: Ch 6, 7 | ||
F | 9/20 | week04-group | |||
Su | 9/22 | week04-ps | |||
5 | M | 9/23 | Haskell data types, modelling DFSM, lexers | ||
W | 9/25 | review | |||
F | 9/27 | week05-group | |||
6 | M | 9/30 | *** checkpoint 1 in class *** | ||
W | 10/2 | CFGs | ACC: Ch 11.1-8 | ||
F | 10/4 | week06-group | |||
Su | 10/6 | week06-ps (written, coding) | |||
7 | M | 10/7 | pushdown automata | ACC: Ch 12.1-3 | |
W | 10/9 | CFGs, CFLs, PDAs; ambiguity and parse trees | ACC: Ch 11.6-7, 12.3-6 | ||
F | 10/11 | week07-group | |||
8 | M | 10/14 | *** no class - Fall break *** | ||
W | 10/16 | non-CFLs, pumping lemma for CFLs | ACC: Ch 13.1-4 | ||
F | 10/18 | week08-group | |||
Su | 10/20 | week08-ps | |||
9 | M | 10/21 | closure for CFLs, algorithms for CFLs | ACC: Ch 14 | |
W | 10/23 | recap on regular and CF languages, lexers and parsers, LL(k) grammars | parsing handout | ||
F | 10/25 | week09-group | |||
Su | 10/27 | week09-ps (written, coding) | |||
10 | M | 10/28 | parsers: recognizing LL(1) grammars | parsing handout | |
W | 10/30 | parsing big picture, review | |||
F | 11/1 | week10-group | |||
11 | M | 11/4 | *** checkpoint 2 in class *** | ||
W | 11/6 | Turing machines, Turing machines variations | ACC: Ch 17.1-3 | ||
F | 11/8 | week11-group | |||
Su | 11/10 | week11-ps (written, coding) | |||
12 | M | 11/11 | TM variations, universal Turing machines | ACC: Ch 17.3, 17.6-7 | |
W | 11/13 | UTM, halting problem | ACC: Ch 17.6-7, 19 | ||
F | 11/15 | week12-group | |||
Su | 11/17 | week12-ps | |||
13 | M | 11/18 | halting problem, proving undecidability with reductions (HALT, ACCEPT) | ACC: Ch 19, 21 | |
W | 11/20 | more reductions | ACC: Ch 21 | ||
F | 11/22 | week13-group | |||
Su | 11/24 | week13-ps | |||
14 | M | 11/25 | more reductions, D vs SD vs not SD, Rice's theorem, Church-Turing | ACC: Ch 21.1-7, 18 | |
W | 11/27 | *** no class - Thanksgiving *** | |||
15 | M | 12/2 | semantics, PCF, type-checkers | type-checker handout | |
W | 12/4 | wrap-up | week15-ps |