The below is a DRAFT, and is subject to change.
Please note that this course:
- is primarily “on-demand” online inasmuch as lectures can be watched at a student’s preferred time, but
- it DOES expect weekly section attendance from students live in an online classroom.
Section timing will be determined based on students’ preferences, but has historically been on Tuesday, Wednesday, or Thursday evenings (Eastern time, United States).
Syllabus
Instructor
Head Teaching Fellow
Doug Lloyd
lloyd@cs50.harvard.edu
Description
This course explores the concepts and algorithms at the foundation of modern artificial intelligence, diving into the ideas that give rise to technologies like game-playing engines, handwriting recognition, and machine translation. Through hands-on projects, students gain exposure to the theory behind graph search algorithms, classification, optimization, reinforcement learning, and other topics in artificial intelligence and machine learning as they incorporate them into their own Python programs. By course’s end, students emerge with experience in libraries for machine learning as well as knowledge of artificial intelligence principles that enable them to design intelligent systems of their own.
Prerequsisites
CSCI E-50 (or CS50x) or at least one year of experience with Python.
Expectations
You are expected to
- watch all lectures,
- attend seven sections,
- implement seven projects,
- submit seven quizzes, and
- submit one test.
Grades
Final grades are determined using the following weights:
| Projects | 65% |
| Quizzes | 10% |
| Section attendance | 10% |
| Test | 15% |
Scores are normalized across teaching fellows at term’s end, so mid-semester comparisons among students of scores are not reliable indicators of standing.
Projects will be graded on the basis of correctness, design, and style, with each project’s overall score computed as 3 × correctness + 2 × design + 1 × style. (Project 0 only is graded only along the axis of Correctness).
- Correctness refers to the extent to which your code is consistent with the project’s specifications and free of bugs.
- Design refers to the extent to which your code is written well (i.e., efficiently, elegantly, and logically).
- Style refers to the extent to which your code is readable (i.e., clear, consistent, commented, indented, with variables aptly named). This includes, but is not limited to, adherence to Python’s style guide, which you can verify using
pycodestyle.
Lectures
Note: lecture topics are subject to change. Lectures are watched on-demand and will typically be posted by noon Eastern Time on their release dates.
| date | lecture | topics | |
|---|---|---|---|
| Lecture 0 | 1/24 | Search | graph search, heuristic search, adversarial search, alpha-beta pruning |
| Lecture 1 | 2/7 | Knowledge | knowledge representation, propositional logic, inference, resolution, first-order logic |
| Lecture 2 | 2/21 | Uncertainty | probability, random variables, probabilistic inference, Bayesian Networks, Markov Models |
| Lecture 3 | 3/7 | Optimization | local search, hill climbing, constraint satisfaction, backtracking search |
| Lecture 4 | 3/21 | Learning | classification, regression, super vector machines, reinforcement learning, clustering |
| Lecture 5 | 4/4 | Neural Networks | feed-forward networks, backpropagation, convolutional networks, recurrent networks |
| Lecture 6 | 4/18 | Language | context-free grammar, n-gram models, Naive Bayes, tf-idf, word2vec |
Sections
Lectures are supplemented by sections led by the teaching fellows. A schedule will be posted on the course’s website. Sections are an opportunity to discuss the course’s material, ask questions, and explore related material. Students are required to attend at least one section per week, unless granted an exception in writing from either the instructors or head teaching fellow before the start of the term.
While recordings of one section per week will be made available within 72 hours, watching those recordings after the fact does not satisfy this requirement.
Office Hours
Office hours are opportunities for guidance and feedback from the staff on projects as well as for discussion of the course’s material more generally. A schedule will be posted on the course’s website.
Projects
| released | due | |
|---|---|---|
| Project 0 | Mon 1/24 | 2022-02-06T23:59:00-05:00 |
| Project 1 | Mon 2/7 | 2022-02-20T23:59:00-05:00 |
| Project 2 | Mon 2/21 | 2022-03-06T23:59:00-05:00 |
| Project 3 | Mon 3/7 | 2022-03-20T23:59:00-04:00 |
| Project 4 | Mon 3/21 | 2022-04-03T23:59:00-04:00 |
| Project 5 | Mon 4/4 | 2022-04-17T23:59:00-04:00 |
| Project 6 | Mon 4/18 | 2022-05-01T23:59:00-04:00 |
Quizzes
Quizzes are short assignments associated with each lecture that allow you to apply each week’s concepts. Each quiz is open-book: you may use any and all non-human resources during a quiz, but the only humans to whom you may turn for help or from whom you may receive help are the course’s heads.
| released | due | |
|---|---|---|
| Quiz 0 | Mon 1/24 | 2022-01-30T23:59:00-05:00 |
| Quiz 1 | Mon 2/7 | 2022-02-13T23:59:00-05:00 |
| Quiz 2 | Mon 2/21 | 2022-02-27T23:59:00-05:00 |
| Quiz 3 | Mon 3/7 | 2022-03-13T23:59:00-04:00 |
| Quiz 4 | Mon 3/21 | 2022-03-27T11:59:00-04:00 |
| Quiz 5 | Mon 4/4 | 2022-04-10T23:59:00-04:00 |
| Quiz 6 | Mon 4/18 | 2022-04-24T23:59:00-04:00 |
Test
The test is opportunity to synthesize concepts across weeks and solve new problems based on lessons learned. The test is open-book: you may use any and all non-human resources during the test, but the only humans to whom you may turn for help or from whom you may receive help are the course’s heads.
| released | due |
|---|---|
| Wed 5/4 | 2022-05-09T23:59:00-04:00 |
Lateness Policy
For each minute that an assignment is turned in late, the course will impose a 0.1% deduction on your grade for the project. (Therefore, once an assignment is 16 hours and 40 minutes late it will earn no credit at all.) Late work will not be accepted for the test.
Extension Policy
Once during the term you may grant yourself a 3-day (72-hour) extension. That extension cannot be apportioned among multiple projects, to the quizzes, or be applied to the test. To grant yourself this extension, submit this form before the project’s deadline. No other action or confirmation from the course heads is required. If you try to submit the form multiple times, subsequent submissions will be automatically ignored.
The course otherwise does not allow for extensions of any kind on its projects. Exceptions to this policy will be considered only in situations of documented medical or family emergency. Extensions that are only requested after a project’s deadline, even via the above form, will not be considered at all. The only individuals authorized to grant extensions are the instructor and the head teaching fellow.
If you receive an extension under the terms of this policy, it may not also be combined with the late policy above. After 72 hours from the original deadline, the work will not be accepted at all.
Accessibility
The Accessibility Services Office (ASO) is available to support all students who require accommodations due to disabling conditions; all such accommodations must be approved and coordinated by the ASO. If you require accommodations, please contact the ASO at 617-998-9640, or by email at accessibility@extension.harvard.edu.
Academic Honesty
This course’s philosophy on academic honesty is best stated as “be reasonable.” The course recognizes that interactions with classmates and others can facilitate mastery of the course’s material. However, there remains a line between enlisting the help of another and submitting the work of another. This policy characterizes both sides of that line.
The essence of all work that you submit to this course must be your own. Collaboration on assigned projects is not permitted except to the extent that you may ask classmates and others for help so long as that help does not reduce to another doing your work for you. Generally speaking, when asking for help, you may show your code to others, but you may not view theirs, so long as you and they respect this policy’s other constraints. Collaboration on the course’s final project is permitted to the extent prescribed by its specification.
Below are rules of thumb that (inexhaustively) characterize acts that the course considers reasonable and not reasonable. If in doubt as to whether some act is reasonable, do not commit it until you solicit and receive approval in writing from the course’s heads. Acts considered not reasonable by the course are handled harshly. If the course refers some matter for disciplinary action and the outcome is punitive, the course reserves the right to impose local sanctions on top of that outcome that may include an unsatisfactory or failing grade for work submitted or for the course itself. The course ordinarily recommends exclusion (i.e., required withdrawal) from the course itself.
Regret clause. If you commit some act that is not reasonable but bring it to the attention of the course’s heads within 72 hours, the course may impose local sanctions that may include an unsatisfactory or failing grade for work submitted, but the course will not refer the matter for further disciplinary action except in cases of repeated acts.
Reasonable
- Communicating with classmates about projects in English (or some other spoken language).
- Discussing the course’s material with others in order to understand it better.
- Helping a classmate identify a bug in his or her code at office hours, elsewhere, or even online, as by viewing, compiling, or running his or her code, even on your own computer.
- Incorporating a few lines of code that you find online or elsewhere into your own code, provided that those lines are not themselves solutions to projects and that you cite the lines’ origins.
- Sending or showing code that you’ve written to someone, possibly a classmate, so that he or she might help you identify and fix a bug.
- Sharing a few lines of your own code online so that others might help you identify and fix a bug.
- Turning to the web or elsewhere for instruction beyond the course’s own, for references, and for solutions to technical difficulties, but not for outright solutions to projects.
- Whiteboarding solutions to projects with others using diagrams or pseudocode but not actual code.
- Working with (and even paying) a tutor to help you with the course, provided the tutor does not do your work for you.
Not Reasonable
- Accessing a solution to some project prior to (re-)submitting your own.
- Asking a classmate to see his or her solution to a project before (re-)submitting your own.
- Decompiling, deobfuscating, or disassembling the staff’s solutions to projects.
- Failing to cite (as with comments) the origins of code or techniques that you discover outside of the course’s own lessons and integrate into your own work, even while respecting this policy’s other constraints.
- Giving or showing to a classmate a solution to a project when it is he or she, and not you, who is struggling to solve it.
- Paying or offering to pay an individual for work that you may submit as (part of) your own.
- Searching for or soliciting outright solutions to projects online or elsewhere.
- Splitting an assigned project’s workload with another individual and combining your work.
- Submitting (after possibly modifying) the work of another individual beyond the few lines allowed herein.
- Submitting the same or similar work to this course that you have submitted or will submit to another.
- Submitting work to this course that you intend to use outside of the course (e.g., for a job) without prior approval from the course’s heads.
- Using AI-based software that suggests or completes lines of code.
- Viewing another’s solution to a project and basing your own solution on it.
Acknowledgement and Authorization
Harvard plans to record audio, photos, and video of Computer Science 50 (CS50) lectures, sections, office hours, seminars, and other events and activities related to CS50 (the “Recordings”), with the aims of making the content of the course more widely available and contributing to public understanding of innovative learning (the “Projects”). As part of the Projects, the Recordings, or edited versions of them, may be made available to other Harvard students, to students at other educational institutions, and to the broader public via edX, the Internet, television, theatrical distribution, digital media, or other means. One of the ways it is expected that the Recordings, or edited versions of them, will be made publicly available is under a Creative Commons Attribution-NonCommercial-ShareAlike (CC BY-NC-SA) license. Another example is that Harvard may make and disseminate montages of “memories” from the class with images from the Recordings. The Recordings also may be used to make other derivative works in the future. Students may elect not to appear in photos and video used in the Projects and may still participate fully in CS50.
To attend CS50, you will need to sign online an Acknowledgement and Authorization in the following form:
I understand and agree that, if I do not wish any photos or video of me to be used as part of the Projects:
- If I am participating in CS50 in a classroom or other course location, I should sit in the designated “no-film” zone of the classroom or location, and should not walk in the field of view of the cameras.
- If I am participating in CS50 online, I should turn off my own camera and should not display a photo of myself. In addition, if I do not wish my real name to be displayed when I speak and my voice is recorded, I should select a pseudonymous user name in Zoom (or other online service). If I select a pseudonymous user name, I will inform the instructor, so the instructor knows who I am.
I understand that I am free not to be included in the Projects’ photos and video in this way, and that this will not affect my grade or my ability to participate in course activities.
Unless I exclude myself from the Projects’ photos and video as described above and take any other steps outlined by the instructor to avoid being filmed, I authorize Harvard and its designees to make and use Recordings of my participation in CS50 and activities related to CS50. I understand and agree that the Recordings may include my image, name, and voice. I also understand and agree that, even if I opt out of the Projects’ photos and video and choose a pseudonymous user name, my voice will be recorded if I am participating online, and may be picked up by microphones outside the “no-film” zone if I am in a CS50 classroom or other location, and my spoken name also may be included in the Recordings. If the class is online, I may participate instead via chat messages, which will not be included in the Recordings.
I understand and agree that Harvard and its designees will have the irrevocable, worldwide right to make, edit, modify, copy, publish, transmit, distribute, sell, publicly display, publicly perform, and otherwise use and make available the Recordings and any other works that may be derived from those Recordings, in any manner or medium now known or later invented, in connection with the Projects, and to authorize others to do so as well. I hereby transfer to Harvard any rights, including copyrights, I may have in the Recordings that Harvard makes. I will remain free to use and disseminate any ideas, remarks, or other material that I may contribute to course discussions.
I acknowledge and agree that I will not be entitled to any payment, now or in the future, in connection with the Recordings or any works derived from them. This Acknowledgment and Authorization is a binding agreement, and is signed as a document under seal governed by the laws of the Commonwealth of Massachusetts.
Unless you exclude yourself as described in the Acknowledgment and Authorization, you are agreeing, by attending CS50, that your participation in CS50 and related activities may be recorded and used by Harvard in connection with the Projects without further obligation or liability to you, even if you do not sign any authorization.
If you have any questions about the above, contact recordings@cs50.harvard.edu.