Paper presentation schedule
| date | 2pm section | 3pm section
|
| Wed. Feb 9 | Keith Brown | Allen Chein
|
| Wed. Feb 23 | Justin Gullotta | Ritesh Pradhan
|
| Sharad Chandra | Greg Holden
|
| Wed. Mar 8 | Dan Malone | Melaku Ayele
|
| Noohul Bosheer | Tim Richter
|
| Wed Mar 29 | Daniela Hauck | Greg Krudysz
|
| Nikmohd Alias | Matt Manger
|
| Wed Apr 12 | Chris Cerniglia | Xianfeng Zhao
|
| | Eugene Mulone | Kyle Baldassari
|
Presentation guidelines
-
Give a short overview of the paper (5-15 minutes). Introductory
material and related work should be brief. Focus on what they actually did in
the paper, how they did it, and what their results were.
-
At some point, I am likely to jump in to focus the discussion; I view
my role in these classes as something of a "co-moderator". I may simply be
trying to focus an an aspect of the paper(s) that students didn't understand
(based upon the classes' reading reports).
-
I'd like this to be more of a discussion --- going through the paper to
develop a better understanding of it. Few people get everything from a first
reading.
-
Assume that everyone has read the paper, but perhaps not as thoroughly
as you have. This means you probably won't need to go into much detail in
motivations, but you might for the technical details.
-
Have a few topics for discussion. These topics might be technical
details that merit more explanation, interesting issues raised by the paper,
relevant issues not addressed by the paper, or points regarding the motivation
or application of the work.
whuang@cs.rpi.edu
Last updates: March 6; February 22, 2000