15-712 is a PhD course in operating systems. The goals are:
Please note: This course is open to SCS Ph.D. students. Other students may be admitted by the permission of the instructor; please attend the first few sessions to see if you're interested. There will be a hard limit for the total number of students to ensure sufficient "face-time" for project meetings.
This course assumes a basic familiarity with operating sytems concepts. The course will consist of a reading/lecture/discussion component and a project component. The class will cover approximately 40 research papers. Some of these papers will introduce students to the basic principles on which modern operating systems and distributed systems are based. Others will cover more recent work to explore the state of the art and observe the evolution of these systems over time.
Students are expected to read papers before the class and participate in the discussion during the class.
| Name | Office | Tel | Office Hours | |
|---|---|---|---|---|
| David Andersen | dga AT cs DOT cmu DOT edu | GHC 9109 | - | By Appointment |
| Name | Office | Tel | Office Hours | |
|---|---|---|---|---|
| Ziyue Qiu | ziyueqiu@andrew.cmu.edu | GHC 5007 | - | By Appointment |
Emi Perdan eperdan@cs.cmu.edu
Students are encouraged to talk to each other, to the course staff, or to anyone else about any of the assignments. Assistance must be limited to discussion of the problem and sketching general approaches to a solution. Each student must write out his or her own solutions to the homework.
Students MUST write paper summaries on their own. No AI or autocomplete use is permitted. Violating this policy will result in failing the course. The paper summaries are an integral part of working through the material: By writing your thoughts down after you read it, you exercise te neural pathways that remember information about the paper. The summaries are part of the learning process.
You are allowed to use AI as part of your research project - but you must write up your paper on your own. Writing the paper is where you make sure you really understand what's going on. It's part of the thinking process, it's not just mechanical. You need to do this yourself. You're welcome to use AI assistance after you draft it to fix spelling and grammar and even get feedback, but please don't let the LLM override your voice and way of communicating. LLMs are much better coders than they are writers.
You are responsible for the correctness of your results, AI or not. Research relies on us being careful scientists. You need to be certain your results actually say what you're presenting them as. You need to be certain your code is implementing what you believe it is. If you've used AI to generate substantial chunks of code, you are responsible for verifying that it did what you think it does, whether that's through manual inspection, very extensive testing, or even formal verification. You are the final line of research responsibility, AI or not.