The output of the course will be a short paper of the sort that could be sent to a conference. The paper should consist of a short description of the problem under study and the relevant CDS tools, followed by a preliminary set of results and a description of next steps to be pursued.
| Project |
Faculty sponsor
|
Team |
| Control of Electric Power Networks using Dynamic Incentive Mechanisms | John Ledyard Mani Chandy Richard Murray |
Steve Waydo |
| Insect Flight Dynamics and Control | Michael Dickinson | Sean Humbert Michael Reiser Domitilla Del Vecchio Mary Dunlop Antoine Trihoreau |
| Cell-Cell Communications and Signal Decay During Antagonistic Microbial Interactions | Jared Leadbetter | Vijay Gupta Tosin Otitoju Demetri Spanos Reiko Tanaka |
| Nonlinear Stability and Mixing in Geophysical Flows | Tapio Schneider | Shane Ross Jimmy Fung* Doug MacMartin Harish Bhat |
| Phase-Lock Loops for Coherent Signal Recovery | Hideo Mabuchi | Mike Armen Ramon van Handel Tamer Inanc |
|
Week
|
Date | Topic |
|
1
|
2 April* | Introduction and course overview (104 Watson) |
|
2
|
9 April* | First team meeting (104 Watson) |
|
3
|
16 April* | No class |
|
4
|
23 April* | No class |
|
5
|
30 April* | No class |
|
midterm
|
7 May | Project presentations; 10 min each (104 Watson) |
|
7
|
14 May* | No class |
|
8
|
21 May | No class |
|
9
|
28 May* | No class |
|
Final
|
6 June | Final projects reports due |
CDS 270 is a 6 unit course, offered either graded or pass/fail. Each team is expected to complete the following:
Project presentation: each team will make a short (10 min) presentation in week 6 of the class (midterms), describing the focus of their project. Comments on these presentations will be provided to the team for incorporation in the final report.
Final report: each team will prepare a paper describing their work during the term. This should build on the midterm report by including some preliminary results and/or case studies.
In order to complete the work for the term, each team should plan on meeting at least once per week. The first team meeting will be on Wednesday, 9 April, at 3:30 pm in 104 Watson (at which time a regular meeting time can be established by the team).