2024 May 2,
Carleton College, Spring 2024, Dr. Joshua R. Davis, , CMC 324, x4095
This course ponders fundamental questions of computer science: What can computers do, and how much time and space do they require to do it? To address these questions, the course proceeds in three stages:
Along the way, we encounter some fascinating connections to philosophy, mathematics, and linguistics. Your work is a mixture of writing proofs, executing algorithms by hand, and Python programming. For example, you learn how to determine whether a programming problem is solvable by regular expressions, and solve it with them if it is.
The official prerequisites for this course are a data structures course (CS 200 or CS 201) and a proof course (CS 202 or Math 236). If you don't know Python, then study it on your own, using the links below or other tutorials. Talk to me if you are concerned about your background.
The College's accreditation says that a 6-credit course is 150 hours of work. That's about 15 hours per week or 5 hours per class meeting. Those 5 hours break down into about 1 hour for class itself and 4 hours for homework, reading, studying, etc. If you find yourself spending less time and struggling, then talk to me. If you find yourself spending much more time, then talk to me.
Our class meets in Leighton 305 during period 5A (MonWed 1:50-3:00, Fri 2:20-3:20). You are expected to attend every class meeting, take notes on paper or a tablet, participate in discussion and group work, and ask and answer questions. You can make up for a deficiency in class participation by talking with me in office hours.
Laptops, phones, photos, and recordings are prohibited (except by special arrangement). Why? This course's material can't be typed easily on a keyboard. Using a laptop or phone measurably distracts the students around you. Photographing a chalkboard is not as educational as taking notes. I want our class to be a safe space, where students do not feel that they're on stage.
It is important that our course be welcoming to all students, regardless of their identities, backgrounds, and experiences. We all sometimes say and do things that make life worse for others, and we should all strive not to. Please let me know if the class feels hostile to you, because of something that I or someone else has done.
Although class meetings may seem like the core of the course, homework assignments are actually where you learn the material. As far as your grade is concerned, homework serves primarily as the first step in studying for exams.
On homework, you are encouraged to figure out the problems with other students. However, you should always write/type your solutions individually, in your own words. You may not copy someone else's work or allow them to copy yours. Presenting someone else's work as your own is a violation of Carleton's Academic Integrity standards.
Writing is not just for English and history majors. Communication skills are essential to every academic discipline, and they are highly prized by employers. In this course, your written work is evaluated both for correctness and for presentation. Compose your solutions as if the intended audience is your fellow students. By doing so, you show enough detail that the reader can ascertain whether you yourself understand the material.
Homework is usually due two class meetings after it was assigned. This schedule tries to keep you on track, so that work doesn't pile up. But we all have bad weeks, where we can't get everything done, right? If you need to submit an assignment late, then write "LATE" at the top of the front page and submit it as soon as you can. If the grader hasn't graded the assignment yet, then they can grade your paper with the others for full credit. If the grader has graded the assignment already, then you might not get credit. There are limitations to how much delay and complication a grader can handle.
When handing in an assignment, please staple your pages into a single packet, in the correct order. Is there a stapler in the classroom? Often not, so staple ahead of time. Is a paper clip just as good? Sorry, no.
Depending on time constraints in any given week, perhaps not all of your homework is graded. In order to ensure full credit, do all of the assigned problems.
We have three exams. Exam A is given in class about one third of the way through the course. Exam B is a take-home exam given about two thirds of the way through the course. It is cumulative but focused on recent material. Exam C is scheduled for the official final exam period: Saturday June 1, 3:30-6:00. It is cumulative but focused on recent material. Self-scheduling is not permitted for Exam C.
For better or worse, we are required to measure your learning using grades. Your numerical grade is based on the responsibilities above: participation 5%, homework 15%, Exam A 25%, Exam B 25%, Exam C 30%.
Numerical grades are converted to letter grades only at the end of the term. Grades are not curved, so students are not in competition with each other. Grades are also not based on predetermined percentages (90%, 80%, 70%, etc.) or explicit specifications, because CS 254 problems are difficult to tune so precisely. (I could accidentally write a difficult exam and wreck everyone's percentages.) Rather, I assign grades by comparing the students to the course goals. For example:
Talk to me, if you are concerned about your grade.
I want all of my students to work hard and learn a lot. I try to give them all of the resources that they need. For starters, let's list some basic documents:
Here are the exams from this term, with quartiles (75th, 50th, and 25th percentiles) listed.
Here are the exams from when I taught the course in fall 2022, with quartiles (75th, 50th, and 25th percentiles) listed. Our exams might cover slightly different material, but these old exams are still good sources of practice problems.
Here the exams from my winter 2020 version of this course. There are four of them, because that's how I did things that term. Every term is a bit different.
Remember that I encourage you to solve problems with classmates (even if the work that you submit must be your own). Olin 310 is staffed with lab assistants during the afternoons and evenings. They can help with Python and maybe even a little CS 254 if you're lucky. The tutors in the Math Skills Center on the second floor of CMC might also be able to help you with logic or what little math we use.
I hold several office hours per week. See below for the schedule. No appointment is needed; just drop in! If you cannot attend office hours, then consult my weekly schedule and e-mail me, listing several times at which we could meet. Our course prefect, Lily (e-mail haasl), also holds prefecting sessions. Again, just drop in or e-mail for a special appointment.
Josh When? | Where? | Lily When? | Where? |
---|---|---|---|
Mon 8:30-9:40 AM (1A) | CMC 324 | Mon 8:00-9:00 PM | Olin 306 |
Wed 11:10-12:20 (3A) | CMC 324 | ||
Thu 9:30-10:30 AM | CMC 324 | ||
Thu 2:00-3:00 PM | CMC 324 | Thu 5:00-6:00 PM | Olin 306 |
Fri 9:40-10:40 PM (2A) | CMC 324 |
If a health condition or other personal matter affects your participation in class, homework, exams, etc., then please let me know as soon as possible. Depending on the situation, we might want to confer with Accessibility Resources, Assistive Technology, Student Health and Counseling, or Sexual Misconduct Prevention and Response. When you ask me to help, I do my best to help. :)
To help you decode the schedule, here is an example. Wednesday March 27 is Day 02 of the course. On that day, we discuss deterministic finite automata. You have homework called "Day 02". Attempt it immediately, but hand it in at the start of class on Day 04. Read Section 1.1 to get another treatment of the material.
Date | Day | Topic | Assignment | Due | Reading | Notes |
---|---|---|---|---|---|---|
M 3/25 | 01 | introduction | Day 01 | 03 | 0.1-0.4 | sum.py, collatz.py |
W 3/27 | 02 | deterministic finite automata | Day 02 | 04 | 1.1 | |
F 3/29 | 03 | nondeterministic finite automata | Day 03 | 05 | 1.2 | DFA vs. NFA Details |
M 4/01 | 04 | regular expressions | Day 04 | 06 | 1.3 | Python Regular Expressions |
W 4/03 | 05 | pumping lemma | Day 05 | 07 | 1.4 | |
F 4/05 | 06 | pumping lemma | Day 06 | 08 | Radiolab: Amnesia | |
M 4/08 | 07 | pushdown automata | Day 07 | 09 | 2.2 | |
W 4/10 | 08 | context-free grammars | Day 08 | 10 | 2.1 | |
F 4/12 | 09 | pumping lemma | Day 09 | 12 | 2.3 | |
M 4/15 | 10 | pumping lemma | Day 10 | 13 | Wikipedia: Alan Turing | |
W 4/17 | 11 | Exam A | ||||
F 4/19 | 12 | Turing machines | Day 12 | 14 | 3.1 | |
M 4/22 | 13 | variants of Turing machines | Day 13 | 15 | 3.2 | |
W 4/24 | 14 | nondeterministic Turing machines | Day 14 | 16 | 3.3 | |
F 4/26 | 15 | decidable examples | Day 15 | 17 | 4.1 | |
M 4/29 | Midterm Break | |||||
W 5/01 | 16 | undecidable examples | Day 16 | 18 | 4.2 | |
F 5/03 | 17 | undecidable, unrecognizable examples | Day 17 | 19 | 5.1 | Paradoxes |
M 5/06 | 18 | unrecognizable examples, Rice's theorem | 20 | |||
W 5/08 | 19 | time complexity | 22 | 7.1 | ||
F 5/10 | 20 | catching up | Exam B? | 21 | ||
M 5/13 | 21 | time complexity | 23 | 7.2 | ||
W 5/15 | 22 | deterministic polynomial time | 24 | 7.3 | ||
F 5/17 | 23 | nondeterministic polynomial time | 25 | 7.3 | ||
M 5/20 | 24 | mapping reducibility | 26 | 7.4 | ||
W 5/22 | 25 | NP-completeness | 7.4 | |||
F 5/24 | 26 | NPSPACE = PSPACE | 28 | 8.1-8.2 | ||
M 5/27 | 27 | glimpses, review | none | 8.3 | ||
W 5/29 | 28 | conclusion | none | |||
S 6/01 | Exam C 3:30PM-6:00PM |