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 including 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. 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 (Mon 9-10am, Wednesday 1:30-3pm) if you want to talk about the class, about theory more generally, or anything else. I'm 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, Sophy Figaroa, Cameron Hatler, Franklin Paas, and Lawrence Stampino-Strain. In general the mentor hours will be on the 1st or 2nd floor of Edmunds at times TBD. Please get in the habit of checking Slack for occasional changes and cancellations!
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 reading/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. That said, there may be differences between how other resources cover topics and how we cover them in this class. I'll point out some of these along the way but, ultimately, it is your responsibility to make sure that you know/understand things as they are taught in CSCI 101 this semester (which will follow the official textbook above). With that said, some other resources 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 working.
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 on Gradescope by 10pm on the due date. You are allowed to submit an assignment up to 24 hours after the due date with no penalty; any additional extension will require documentation of circumstances that could not have been anticipated. When assignments are returned on Gradescope you will have 7 days to request a regrade.
Finally there will be three written, in-class checkpoints with one approximately every 5 weeks.
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 | W | 1/22 | (cs54 review) sets, logic, functions, relations, proofs; Haskell datatypes; groups | ACC: Ap A | intro survey due noon on Tuesday 1/21 | |
F | 1/24 | week01-group | ||||
Su | 1/26 | week01-ps-coding | ||||
2 | M | 1/27 | basic definitions, languages, FSM, regular languages | ACC: 5.1 | ||
W | 1/29 | constructing FSM, closure properties of regular languages | ACC: Ch 5.1-3 | |||
F | 1/31 | week02-group | ||||
Su | 2/2 | week02-ps | ||||
3 | M | 2/3 | NDFSM | ACC: Ch 5.4 | ||
W | 2/5 | Myhill-Nerode, minimization | ACC: Ch 5.7 | |||
F | 2/7 | week03-group | ||||
Su | 2/9 | week03-ps | ||||
4 | M | 2/10 | non-regular languages, pumping lemma | ACC: Ch 8 | ||
W | 2/12 | regular grammars, expressions | ACC: Ch 6, 7 | |||
F | 2/14 | week04-group | ||||
Su | 2/16 | week04-ps | ||||
5 | M | 2/17 | Haskell data types, modelling DFSM, lexers | |||
W | 2/19 | review | ||||
F | 2/16 | week05-group | ||||
6 | M | 2/24 | *** checkpoint 1 in class *** | |||
W | 2/26 | CFGs | ACC: Ch 11.1-8 | |||
F | 2/28 | week06-group | ||||
Su | 3/2 | week06-ps, week06-ps-coding | ||||
7 | M | 3/3 | pushdown automata | ACC: Ch 12.1-3 | ||
W | 3/5 | CFGs, CFLs, PDAs; ambiguity and parse trees | ACC: Ch 11.6-7, 12.3-6 | |||
F | 3/7 | week07-group | ||||
Su | 3/9 | week07-ps | ||||
8 | M | 3/10 | non-CFLs, pumping lemma for CFLs | 13.1-4 | ||
W | 3/12 | closure for CFLs, algorithms for CFLs | ACC: Ch 14 | |||
F | 3/14 | week08-group | ||||
9 | M | 3/17 | *** no class - Spring break *** | |||
W | 3/19 | *** no class - Spring break *** | ||||
S | 3/23 | week08-ps | ||||
10 | M | 3/24 | parsers: big picture, LL(k) grammars, LL(1) grammars | parsing handout | ||
W | 3/26 | parsers: LL(1) grammars, recognizers vs. parsers, AST | parsing handout | |||
F | 3/28 | week10-group | ||||
Su | 3/30 | week10-ps, week10-ps-coding | ||||
11 | M | 3/31 | review | |||
W | 4/2 | *** checkpoint 2 in class *** | ||||
F | 4/4 | week11-group | ||||
S | 4/6 | week11-ps-coding | ||||
12 | M | 4/7 | Turing machines | ACC: Ch 17.1-2 | ||
W | 4/9 | Turing machine variations | ACC: Ch 17.3 | |||
F | 4/11 | week12-group | ||||
Su | 4/13 | week12-ps, week12-ps-coding | ||||
13 | M | 4/14 | Universal Turing Machines, halting problem | ACC: 17.6-7, 19 | ||
W | 4/16 | halting problem | ACC: Ch 19 | |||
F | 4/18 | week13-group | ||||
Su | 4/20 | week13-ps | ||||
14 | M | 4/21 | reductions | ACC: Ch 21 | ||
W | 4/23 | more reductions | ACC: Ch 21 | |||
F | 4/25 | week14-group | ||||
Su | 4/27 | week14-ps | ||||
15 | M | 4/28 | more reductions, D vs SD vs not SD, Rice's theorem, Church-Turing | ACC: Ch 21.1-7, 18 | ||
W | 4/30 | semantics, PCF, type-checkers | type-checker handout | |||
F | 5/2 | week15-groups | ||||
Su | 5/4 | week15-ps | ||||
16 | M | 5/5 | wrap-up, review | |||
W | 5/7 | *** checkpoint 3 in class *** |