CSE 221
Welcome to the CSE 221 web page. This is the graduate
Operating System class.
Office hours: Thu 2pm-3pm. As it says on the handout, you can drop
by at other times sans appointments, and I'll accommodate you if I'm
not busy; to be sure, make an appointment.
This web page contains virtual handouts / announcements.
Papers
For our OSSurvey98 conference, you, as members of the program
committee, should pick up copies of the submissions from outside of my
office door -- they should be ready by late afternoon Thursday (May
28). The papers should be evaluated using the following method (this
is taken from a real conference's program committee review
instructions and revised slightly, since survey papers will not
necessarily contain new research -- though if there are new research
ideas, that's even better):
Papers will be evaluated in two parts: a set of numeric scores and a
written commentary. Scores will be on a 1 to 7 scale (with 4 as an
"average" in all cases 1 is bad, 7 is best). Do not
assign a zero score. Also, please use integer values.
Scoring will be in four categories:
Import -- is the work (both its area and results) important to the OS
community? Low scores might be given for evaluations of marketing
literature and papers on inappropriate or dead topics. High scores
are for papers that nearly all attendees will want to read and
understand carefully.
Novelty -- are the observations novel? Low scores should be given for
papers that re-hash known observations about works in the topic area.
High scores are for papers that open new fields or demonstrate new
ways to attack a problem.
Quality -- are the observations / criticisms sound? A low score might
go to a paper whose observations are incorrect or whose critiques are
biased or not well supported in your opinion. High scores are for
papers with enough justification to convince you that the opinions are
correct and viable.
Overall -- should we accept this paper or not? This is by far the
most important number. It need not be an average of the
other numbers, but it should reflect them. This number can also
reflect issues in addition to those described above (e.g., poor
presentation or lack of knowledge of related work).
You should write up your reviews for Monday (Jun 1) so that the
numeric scores and the public comments are on one sheet of paper and
the private comments are on another. You should bring to class two
copies of the numeric and public reviews -- I will get one copy (along
with the private comments) and the authors will get the other copy.
There are a total of 6 papers -- so get started on these early! They
are:
Note that the conference evaluation criteria emphasizes novelty and
importance to the OS community; when I grade these, these will be
important, but not given as much emphasis -- I will pay more attention
to the quality of the reasoning and the soundness of the observations
/ criticisms, so having selected what's currently ``hot'' (or what's
not) wouldn't be so important.
On Wednesday (Jun 3), the groups with the top two papers will give an
oral presentation for the entire class. I'll arrange to have an
overhead projector available, so you can use slides. Each group will
have about 1/2 hour total, so you should plan on 20-25 minutes for the
presentation and 5-10 minutes for questions and answers from the
audience.
Amusing: Operating
System Sucks-Rules-O-Meter.
[
CSE home |
bsy's home page |
webster i/f |
yahoo |
hotbot |
lycos |
altavista |
pgp key svr |
spam |
commerce
]
bsy+www@cse.ucsd.edu, last updated Tue Sep 22 08:44:02 PDT 1998.
email bsy
