| Announcements |
Paper Guidelines: Detailed guidelines
on the paper submission can be found here. Here's a summary: Due 1/10 by
noon as a PDF to cs266-reviews@eecs. Paper length no more than 10
pages (not including bibliography), at least 10 point font, single
spaced. Focus on readability and clearly laying out what you did for
the project and what your results were. Several suggestiongs on how to
do that are given in the guidelines, but I will also try and get
written feedback to all of you.
Also in your email include the
abstract in ascii text for the final projects webpage.
Lecture presentations: I'd like to
put up all the lecture presentations from class. If you have not sent
me yours, please do so asap (ppt/pdf or txt). Do not worry about
editting - they will be kept behind the password section.
Evaluations: If you did not get a
chance to fill out a evaluation form, or would like to say more, you
can find the form here. You can drop it
off in my mailbox in the second floor lounge. These evals are very
helpful in improving the course, and I appreciate your input.
The goal of the update is to report your progress so far on achieving
your milestones, to bring up issues/problems that you are
experiencing, as well as to inform your classmates what you are upto.
So this update will have three parts:(1) Send me an email update in
(ascii text to cs266-reviews@eecs). You should recieve an email
with the format (2) In class be ready to give a 2 minute
description of what you are doing and how its going (3) Set a time
to meet with me.
Submit a (<) 3-page proposal on your class project. Your proposal
should contain (1) A succinct description of the problem/project you
are investigating and its significance (2) A description of
background/related work (3) A plan of execution along with a list of 2
week milestones (4) A short bibliography (5) One sentence about where
you'd eventually like to go with this project.
In setting a plan and milestones, keep a couple of points in
mind. First you should feel free to set milestones that come with the
caveat "if all goes well upto this point". Second, make sure that you
build in evaluation points into your milestones - how will you
evaluate success at intermediate steps? Also for joint person
projects, give some indication (and thought) as to who will be doing
which parts.
Submit your proposal (preferably pdf) via email to cs266-reviews@eecs.