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.
|
Week
|
Date | Topic |
|
1
|
3 April | Introduction and course overview |
|
2
|
10 April | First team meeting (104 Watson) |
|
3
|
17 April | No class |
|
4
|
24 April | Project presentations (1/2); 10 min each |
|
5
|
1 May | Project presentations (2/2); 10 min each |
|
midterm
|
7 May | No class; Project overview due 7 May |
|
7
|
15 May | No class |
|
8
|
22 May | Project presentations (1/2); 15 min each |
|
9
|
29 May | Project presentations (2/2); 15 min each |
|
Final
|
7 June | Final projects reports due |
This course is graded pass/fail. Each team is expected to complete the following:
Project presentation #1: each team will make a short (10 min) presentation in week 4 or 5 of the class, describing the focus of their project. Comments on these presentations will be provided to the team for incorporation in the midterm report.
Midterm report: each team will prepare a short report describing the problem they are studying, the background information from the application domain and the relevant CDS tools.
Project presentation #2: each team will make a short (15 min) presentation in week 8 or 9 of the term, describing their preliminary results. Comments on these presentations will be provided to the team for incorporation in their 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, 10 April, at 3:30 pm in 104 Watson (at which time a regular meeting time can be established by the team).
| Project |
Faculty sponsor
|
Team |
| Wireless Communications and Control |
Babak Hassibi
|
Timothy Chung (timothyc@its) Abhishek Tiwari (atiwari@its) Masoud Sharif (masoud@systems) Lun Li (lun@cds) Amir Farajidana (amirf@its) Vijay Gupta (gupta@its) Yindi Jing (yindi@its) |
| Building robust software |
Jason Hickey
|
Eric Klavins (klavins@cs) |
| Nonlinear behavior in congestion control protocols |
Steven Low
|
Ao Tang (aotang@its) Hyojeong (Dawn) Choe (hjchoe@cs) Lars Cremean (lars@its) Feng-Li Lian (fengli@its) Melvin Flores (melvin@its) |
| Application of controls to circuits |
Ali Hajimiri
|
Aristotelis Asimakopoulos (aristo@cds) J. Sean Humbert (jshumber@cds) Abbas Komijani (komijani@its) Hossein Hashemi (hashemi@its) |
| Modeling microbial ecosystems (Newman) |
Dianne Newman
|
Dave van Gogh (dvangogh@cds) Adam Hayes (athayes@its) Yongqin Jiao (jyq@gps) Davin Malasarn (biodomey@its) Tracy Teal (tracyt@its) |
|
Micromechanical parametric amplifiers (Roukes) |
Michael Roukes
|
Jimmy Fung (fung@its) Lijun Chen (chen@cds) Shwetank Kumar (shwetank@its) X. M. Henry Huang (xmhenryhuang@its)
|
|
Real-time control of atomic motion in an optical cavity |
Jeff Kimble
|
Theresa Lynn (theresa@its) Kevin Birnbaum (birnbaum@its) Domitilla Del Vecchio (ddomitilla@cds) Martha Gallivan (martha@cds) Dong Eui Chang (dchang@cds) |