The course will center around three basic entities:
readings, assignments, and a final project.
For most every class, you will have to read one or more papers (as assigned), which we will then discuss in class. You will also have to think and write a little bit about each paper. During the first half of the semester, you will also have to perform a few mini-assignments, just to get warmed up for the project. Then, finally, you will work on your projects, which is the real key to the class: a mini-research project on the topic of your choice. Though we will provide some suggestions, you are encouraged to come up with a topic of your own (after all, that is what research is all about). More details will be available below in the weeks to come.
|01/21||Holiday: No class||01/23||
||02/27||No class: FAST||02/29||No class: FAST|
||03/28||No Class (Visit Day)|
|04/28||No Class||04/30||Rethink the Sync||05/02||Bugs Rx|
|05/05||Review (Exam at night)||05/07||How to...||05/09||Last class|
PapersYou will have three basic responsibilities for the readings covered in the course:
1 - Read the assigned papers (as in the schedule) before class. This is a must!
2 - Form a discussion group. You should have about four people in your group, and discuss each paper sometime before class meets. When you have formed a group, please send me email with a list of group members.
3 - Answer the question posed for each paper. Your individual write-up should consist of a short-essay answer to the question(s) posed. The write-up should not exceed half of a page in length. The list of questions to answer is available here. Turn in your write up via email to me (remzi@cs) before 10am on the day of the class where we discuss the paper, with the class and date in the subject line (e.g., 736 Reading 9/12). Late write-ups will automatically receive a null score. Write-ups should be in plain text and not some fancy encoding, for the professor's viewing pleasure. Write-ups not in plain text will be returned to the sender ungraded (but unharmed).
The reading load will be heavy, so
make sure not to fall behind.
The final project is the main focus of the course. You are expected to perform work which could eventually be suitable for publication in a major operating systems conference; indeed, each year one or two projects end up becoming published works in some major OS conference! In general, people should work in groups of size one or two -- I will not allow groups larger than that. I will provide some suggestions for you to pick from, although you are encouraged to think of a project on your own, which I can then help to refine. Project write-ups will be similar in format to a conference submission, and all will be entered into a class-wide mini-conference. The best papers will receive some kind of recognition. More details are forthcoming.
Here are links to some previous class projects:
Midterm Exam: Wednesday, 03/12 at 7:15pm in 1263 CS.
Final Exam: Monday, 05/05 at 7:15pm in 1325 CS.
Assignment #0: Digital PictureAssignment #2: Project Proposal Meeting (by Tuesday, April 1)
Assignment #1: Reading Group
Complaints about file systems, youtube, flickr, and del.icio.us to