SCHOOL OF ENGINEERING AND APPLIED SCIENCES
HARVARD UNIVERSITY

CS 266: Biologically-inspired Distributed and Multi-agent Systems

Prof. Radhika Nagpal
Fall 2007


Course Description   Assignments and Guidelines   Schedule and Reading List   Paper Reviews   Project Milestones and Suggestions   Fall06   Staff  

Assignments

This course will involve reading research papers, leading and participating in class discussions, and a final project.

More details on each of these aspects will be presented at the first class. The final grade will take into account each of these aspects.

Guidelines for Paper Reviews, In-class Discussions and Lecture Presentations

This course will involve reading research papers, leading and participating in class discussions. This is a key learning (and grading) tool in this course. Here are some guidelines on what we expect and how to make it productive.

Paper Reading, Reviews, and Participation

For each class, there will be 2 assigned research papers. Often one might be more important to read in depth than the other -- I will mark that paper with an asterix. That is also the paper that you need to review. In class we will not review the paper, so if you have not read it then it will put you at a significant disadvantage. Also under that topic there are several additional papers that you may read if you want to follow up on more threads.

In reading the paper there are several aspects to pay attention to --- what was the key idea, what would it require to be implemented in the real-world, what other problems could it be applied to. Also how well was it evaluated, what would be an optimal solution to compare it to, and can it be mathematically analyzed. We will also read several papers on models in biology with the goal of identifying abstract principles that lead to robustness and adaptability. A key thing to keep in mind while reading these papers is that many of them are "firsts" on a completely new idea and therefore less fully evaluated than one might expect for a more developed topic.

For the paper review, you should submit a review of the asterixed paper. Reviews are due MIDNIGHT the day before class and are posted on a discussio forum that all of us can read. Your review should consist of the following:

  1. Short para on any of the following points: What do you feel the main contribution of this paper is? What did you find interesting aout this work? What's the essential principle that the paper exploits?
  2. One major strength of the paper (one sentence)
  3. One weakness of this paper (one sentence)
  4. One question or future work direction you think should be followed OR a reply to a previous question posted on the discussion forum.

The point of the reviews is not to regurgitate the paper but to identify what *you think* is the key concept to learn from the paper and what your opinion is of the strength/weakness of the idea and or paper. It is also to identify some of the issues to think about before coming into class.

In-class participation is key. The lead presenter will give a short presentation on other literature - e.g. work that was done afterwards, or additional areas. They will also have a list of specific discussion topics and problems for participation. It is essential that you speak up and contribute meaningfully to the discussion both by raising questions and proposing answers. We will do everything possible to encourage a comfortable discussion environment.

Lecture Presentations

The goal of the lecture presenter is to educate the rest of the class through a meaningful discussion of the paper topic (as opposed to just the paper). This means that the lecture presenter has to do a more indepth study of the paper topic and previous/future work as well as come up with some interesting problems to discuss in class. Here are some guidelines on how to go about this.

Preparation

Lecture Format

  • Give a short discussion of the paper (~5 mins), with your opinion on the main contributions of this paper. The goal is not to review the paper or restate the major results of the paper, most everyone should have read the paper well enough for that. Instead the goal is to provide a more high-level treatment: What (in your opinion) is the real contribution this paper? What's the main principle exploited or what's the take-away lesson that you think you could apply elsewhere, What did you really like about the paper and where did you think it fell short.

    Occasionally we will read a long paper or a paper with a significant amount of technical material/depth (e.g. the AntNet paper). In those cases it is ok to violate the above. You can spend time to go through the mathematics, or experimental data, or some interesting part of the paper in more detail. The goal is for everyone to understand the technique reasonably well - if that is hard, then we should spend time on it in class.

  • Give a short presentation on related work (~15 minutes). This is very valuable to the class, since many objections and ideas and questions relate to what has been done before and what has been done since. Also many times there are related areas that are interesting. And there are now lots of movies online and those can add a very visual understanding for some of the topics. Finally, you can (and should) use your personal interest to guide which part of the future/past work you want to focus on -- a long survey is much harder to retain than a good story about one direction.

  • Pick a short list of questions you want to discuss, and a format to discuss them in . For example, you can choose one topic to do as a big group, and one question/problem to do by breaking into smaller groups. This is especially good for discussing issues that the whole class might have wondered about, or essembling a list of properties of a system. The smaller groups format works very well for fairly open-ended problems -- problem solving, alternative algorithms, extensions, type of questions . Basically you break the class into groups, and allocate some time. Then we could get back together after some fixed amount of time and each group could summarize their "findings". I will also bring some questions to the class, and so I may derail the class direction during this section. Therefore front load the topics you want to discuss most and dont get too upset that some may never be reached.

  • Finally, don't worry too much about the paper reviews, its your presentation. You pick a few questions for discussion (<=4 total) - I will bring a few too. The more "deep/general" the questions are the better. For example, if there are two papers, then one can spend a good amount of the discussion time constrasting them and learning alot just from that.