| Class: | Monday, Wednesday, 9:00-10:15am, Science Center 204 |
|---|---|
| Lab A (Hope): | Tuesday 1:05-2:35pm, Martin 113 |
| Lab B (Hope): | Tuesday 2:45-4:15pm, Martin 113 |
| Lab C (Soni): | Tuesday 2:45-4:15pm, Martin 313 |
| Communication: | Ed Discussion Platform Important announcements will be posted here You can ask questions and answer other students' questions here |
||||
|---|---|---|---|---|---|
| Instructor: | Gabriel Hope | ||||
| Email: | ghope1@swarthmore.edu | ||||
| Office: | Martin 236 | ||||
| Office Hours: |
|
||||
| Co-Instructor: | Ameet Soni | ||||
| Email: | asoni1 at swarthmore dot edu | ||||
| Office: | Martin 232 | ||||
| Office Hours: |
|
Artificial Intelligence (AI) is the branch of computer science that is concerned with the automation of intelligent behavior. "Intelligent behavior" encompasses a wide range of abilities, and as a result AI has become a very broad field.
In recent years, the term "AI" has become associated very strongly with large-language models used for text generation (e.g. ChatGPT, Gemini, Claude, etc.). While we will discuss these models, the course will not be entirely centered on them. Our understanding of "AI" will be that AI is a field of study which has existed for many decades, and includes search, game playing, reasoning, planning, natural language processing, computer vision, modeling human performance (cognitive science), machine learning, and robotics. This course will focus on a subset of these topics, specifically search and machine learning, while also drawing connections to cognitive science.
In search, we will see familiar techniques such as depth-first and breadth-first, as well as new techniques such as A*, minimax, and simulated annealing applied to AI problems. In machine learning, which is concerned with programs that define their behavior in terms of previous examples, we will explore reinforcement learning and neural networks, including the popular sub-field of deep learning, of which LLMs are a sub-sub-field. The first half of the semester will focus on search, and the second half of the semester will focus on machine learning.
| Weight | Coursework |
|---|---|
| 10% | Class Participation |
| 45% | Exams |
| 25% | Labs |
| 20% | Final Project |
Staying engaged with the course material throughout the semester is critical for your learning and for your grade.
We will use physical iClickers for reading quizzes, questions, feedback, and peer discussion. Bring your registered clicker to each class meeting. If you forget it, you may use the phone app, but your phone should be away when it is not needed.
See the Swarthmore Computer Science iClicker instructions for compatible devices, purchasing, and registration. Course-specific details will be posted on Ed.
Up to three unexcused absences are allowed without penalty. If you have a medical or other emergency, contact the instructor as soon as possible.
In-class quizzes are intended only to ensure that you are keeping up with the reading and should not require additional preparation.
Rather than using a single textbook, we will be using materials from a variety of sources. Many of the materials will be available online. You only need to purchase the first text listed below by Melanie Mitchell, which is required.
Our class meetings will be a combination of lecture and discussion. To be ready to participate in the discussion will require some preparation on your part. Most of this will consist of careful reading and reflection on the assigned reading through the use of reading questions.
You should check the class schedule and complete each assigned reading before the class meeting where it appears. You will get the most out of the reading if you approach it as follows:
To help focus your efforts and give us a basis for discussion, you will be provided with a short list of reading questions to consider for each week's reading. Reflecting on your responses to the questions will help give you a deeper understanding of the most important concepts surrounding each topic. Be ready to discuss your answers in class!
Lab release and due dates will be posted on the course schedule and course platforms. Generally, labs will be due the following Monday at 11:59 PM, with the exception of Lab 1. Even if you do not fully complete a lab, you should submit what you have done to receive partial credit.
You will work with a partner on all labs after Lab 1. You must reselect a partner for each lab, so you may continue with the same person or choose a different partner the following week.
Complete the Lab Partner Selection Form. Only one student from each partnership needs to submit the form. You can change partners by resubmitting it; your latest submission will be used. If you do not submit the form, the instructor will assign you a partner.
Deadline: Lab partners cannot be changed after noon on the day the lab is released. The instructor may occasionally override requested partnerships.
You have three late days that you may use on any lab, for any reason. If you are using a late day, you must contact me by email or private message on Ed to let me know.
Your late days will be counted at the granularity of full days and will be tracked on a per-student (NOT per-partnership) basis. That is, if you turn in an assignment five minutes after the deadline, it counts as using one day. For partnered labs, using a late day counts towards the late days for each partner. In the rare cases in which only one partner has unused late days, that partner's late days may be used, barring a consistent pattern of abuse.
If you feel that you need an extension on an assignment or that you are unable to attend class for two or more meetings due to a medical condition or other extenuating circumstance, please let me know as soon as possible.
The general ethos of this policy is that actions which shortcut or avoid the learning process are forbidden, while actions which promote learning are encouraged.
For example: studying lecture materials or discussing readings together provides an additional avenue for learning and is encouraged. Using a classmate’s solution, however, is prohibited because it avoids the process of doing the work; since doing the work is how much of the learning takes place, avoiding the work inherently means avoiding the learning as well. Note that this applies to generative AI tools (e.g. ChatGPT, GitHub Copilot, etc.) just the same way it does to any other resource.
If you have any questions about what is or is not permissible, please contact your instructor.
Academic honesty is required in all of your work. Under no circumstances may you hand in work done with (or by) someone else under your own name. Your code should never be shared with anyone; you may not examine or use code belonging to someone else, nor may you let anyone else look at or make a copy of your code. The only exception to this policy is that you may freely share code with your lab partner.
You should not obtain solutions from students who previously took the course or copy code that can be found online. You may not share solutions after the due date of the assignment.
Failure to abide by these rules constitutes academic dishonesty and will lead to a hearing of the College Judiciary Committee. According to the Faculty Handbook: "Because plagiarism is considered to be so serious a transgression, it is the opinion of the faculty that for the first offense, failure in the course and, as appropriate, suspension for a semester or deprivation of the degree in that year is suitable; for a second offense, the penalty should normally be expulsion."
Discussing ideas and approaches to problems with others on a general level is fine (in fact, we encourage you to discuss general strategies with each other), but you should never read any other student's code or let another student read your code. All code you submit must be your own with the following permissible exceptions: code distributed in class and code given in the readings. Regardless of the source, you should always include comments that indicate on which parts of the assignment you received help, and what your sources were. You may not share your solutions even after the due date of the assignment.
Any code, text, or content not created exclusively by you and used without attribution is plagiarism. This is true regardless of whether the original source was a scholarly text, another student, an online platform (e.g. StackOverflow), or a generative model (e.g. ChatGPT). Using resources such as these may be appropriate under some circumstances, and not under others, but regardless you must always properly acknowledge and cite the source of the information. When in doubt, add a statement of attribution! In addition, when using any type of generative AI, you must also describe how it was used, e.g. by giving the prompt.
In this course we will be learning the fundamental tools for building large language models and chat AIs, such as ChatGPT. Therefore I encourage you to experiment with ChatGPT and its competitors during this course, but only for learning about concepts.
The use of generative AI tools (e.g. ChatGPT, GitHub Copilot, etc.) for lab assignments without permission is considered to be unauthorized collaboration with an outside source and is a violation of our academic integrity policy. You may not share any assignment materials with large language models including assignment questions, support code and your own answers. This includes AI-assisted coding tools such as GitHub Copilot and Google Gemini in Colab. Please disable these tools when working on class lab assignments. As stated above, failure to do so will be considered a violation of the academic integrity policy.
Be cautious when using generative AI tools for learning purposes. AI models are not an authoritative source of information, and they can produce incorrect or misleading information. You should always first seek primary sources (e.g. textbooks, scholarly articles, or other authoritative sources) as your starting point, and use generative AI tools only as a supplement to your learning. If you do use generative AI tools for learning purposes, you must always properly attribute the source of the information and describe how it was used.
You may not use generative AI to respond to reading questions or questions on Ed.
You may use AI-assisted coding tools in the final project for debugging and for coding non-core parts of your project (e.g. for setting up the development environment, reading and writing files and interacting with libraries). If you feel these tools would be appropriate in a given context, please contact the instructor to ask. Note that even if permission is granted, these sources must be properly attributed.
Here are some examples of what this might look like:
If you believe you need accommodations for a disability or a chronic medical condition, please visit the Student Disability Services website for details about the accommodations process. Since accommodations require early planning and are not retroactive, contact Student Disability Services as soon as possible. You are also welcome to contact me privately to discuss your academic needs. However, all disability-related accommodations must be arranged, in advance, through Student Disability Services.
| WEEK | DAY | TOPICS | READINGS | LAB | EXTRAS |
| 1 | Aug 31 | Guide to lab assignments | Optional: Quick, Draw! AI game | ||
Sep 02 |
| ||||
| 2 | Sep 07 | No class on Labor Day | Lab 2: Informed search | ||
Sep 09 |
| Optional: Google Maps is unreasonably fast. Let me explain | |||
| 3 | Sep 14 | Local Search [S26] |
| Lab 3: Local search | Optional: Simulated annealing demo |
Sep 16 | Game Search [S26] | ||||
| 4 | Sep 21 | Minimax and Alpha-Beta Pruning [S26] |
| Lab 4: Game play with Minimax | Optional: Minimax and alpha-beta visualizer |
Sep 23 | Monte Carlo Tree Search [S26] |
| Optional: AlphaGo Movie | ||
| 5 | Sep 28 | MCTS implementation [S26] | Lab 5: MCTS | Optional: Monte Carlo Tree Search (Computerphile) | |
Sep 30 | Problems with symbolic AI [S26] |
| Optional: ELIZA rule-based chatbot demo | ||
| 6 | Oct 05 | Exam 1 Review Exam 1 in lab (Oct 06) | Exam 1 in lab | ||
Oct 07 | Intro to Neural Networks [S26] |
| |||
Oct 12 | Fall Break | ||||
Oct 14 | |||||
| 7 | Oct 19 | Multi-layer Neural Networks [S26] |
| Lab 6: Neural Networks | Optional: TensorFlow neural network playground |
Oct 21 | Applying ML to categorization tasks [S26] |
| |||
| 8 | Oct 26 | Deep learning and Convolution networks [S26] |
| Lab 7: Convolutional Networks | Optional: Teachable Machine |
Oct 28 | Introduction to Reinforcement Learning [S26] |
| |||
| 9 | Nov 02 | Approximate Q-learning [S26] |
| Lab 8: Reinforcement Learning | Optional: Q-learning Snake visualizer |
Nov 04 | Evolutionary Computation [S26] |
| |||
| 10 | Nov 09 |
| Lab 9: Genetic Algorithms | Optional: Genetic Cars 2 | |
Nov 11 | Evaluating ML [S26] |
| |||
| 11 | Nov 16 | Optional: Interactive LLM tokenization demo | |||
Nov 18 | Large Language Models | Optional: How LLMs work and that's why they don't | |||
| 12 | Nov 23 | In-class review [S26] | Exam 2 in lab | ||
Nov 25 | Thanksgiving Break | ||||
| 13 | Nov 30 | Transformers [S26] | Optional: Transformer Explainer | ||
Dec 02 | Philosophy of AI [S26] |
| Optional: Moral Machine Optional: AI and our future | ||
| 14 | Dec 07 | Last CS 63 lecture meeting |
| ||
Dec 14 | Final project poster session (exact date and time to be announced) | ||||