Applications for Winter Quarter 2018 are closed. We will not be offering this class in Spring Quarter.
The sustainable development goals (SDGs) encompass many important aspects of human and ecosystem well-being that are traditionally difficult to measure. This project-based course will focus on ways to use inexpensive, unconventional data streams to measure outcomes relevant to SDGs, including poverty, hunger, health, governance, and economic activity. Students will apply machine learning techniques to various projects outlined at the beginning of the quarter. The main learning goals are to gain experience conducting and communicating original research. Prior knowledge of machine learning techniques, such as from CS 221, CS 229, CS 231N, STATS 202, or STATS 216 is required. Open to both undergraduate and graduate students. Enrollment limited to 24.
Note for co-term and masters students in CS: This class counts toward part (c) of the AI specialization.
Time and Location
- Tuesdays, 1:30pm - 4:20pm
- Location: Shriram 108
TA Office Hours
Professor Office Hours
- Stefano: Fridays, 11am-12pm, Gates 228
- David: Wednesday, 11:30-12:30pm, Y2E2 367
- Marshall: Tuesdays, 12:00-1:20pm Y2E2 365
You may choose to take the class for 3, 4, or 5 units. There is no difference in workload or expectations.
By the end of the quarter, students will be able to:
- Identify various sources of geospatial data, their pros and cons, and connect data sources to sustainable development goals
- Develop ML applications in the cloud (scripting, batching, etc)
- Demonstrate improved skills in building ML models (avoiding overfitting, model development and selection, combining multiple data sources, modeling spatio-temporal dependence, etc.)
- Effectively communicate their problem and results in both oral and written form
The class will consist of three main parts: the first week will be background info, the next seven will focus on team development of their projects with regular presentations, and the last two weeks will focus on wrapping up and communicating results. Guidelines for each presentation will be given later.
|2||Group presentations. Summary of:
||Literature review and slides for presentation|
||Slides for presentation|
|4||Group presentations. Show results from some baseline models such as regression.
||Slides for presentation|
|5||Group presentations.||Slides for presentation|
|6||Group presentations.||Slides for presentation|
|7||Group presentations.||Slides for presentation|
|8||Group presentations.||Slides for presentation. Draft of final paper.|
|9||Peer feedback session.||Written review of another team's paper.|
|10||Final presentations.||Slides for presentation. Final paper.|
We encourage engagement during class - meaning listening closely to your peers and providing useful suggestions. To achieve this, we will have the following rules:
- No open laptops during class
- All slides must be submitted on a common google slide deck by 1pm on the day of class. The TAs will send out a link to the slides for each week.
- Talks are limited to 12 minutes, with 5 minutes for questions/discussion after.
- Groups will be randomly assigned each week to the “1st half” or “2nd half” sessions. Three groups will present in 1st half, then we will have a 15 minute break, then three groups will present in 2nd half. You only need to attend the half that your group is in. You can use the rest of class time to work on your project outside of class.
- TAs will also circulate guidelines for presentations, such as not to show raw code, not to show more than 2 significant digits, not to spend a lot of time on parts you don’t want feedback on, etc.
- After each class, TAs will send out a quick survey where you vote for the best presentation among the others in your session, and give a reason why you think it was best.
Weekly Group Presentations (week 2-8): 6 pts each
Participation in weekly surveys: 5 pts Individual peer-review report of another team’s paper: 8 pts
Final presentation, paper (to be written in the form of a short conference paper), and code repository: 45 pts
Instructions and Rubrics:
Students will not be graded on whether they can successfully achieve their desired accuracies in predicting outcomes, given that most projects will be risky and not guaranteed to work. Students will be graded on devoting sufficient time to the project, clearly explaining progress and challenges, correctly applying techniques, and clearly writing up results. Successful projects will have the reward of paid trips to conferences (if the paper is accepted).
Length of weekly presentations will be determined by the number of projects. All students are expected to attend all sessions, and to give full attention and feedback to their classmates or instructors (no open laptops except for presenters).
Students will work in groups of 3 people. We expect that each member of the team contribute in both technical and non-technical components. At the end of quarter, we will solicit feedback on your teammates and reserve the right to give individuals in the group higher or lower grades than the group average.
Earth System Science
Email: mburke [at] stanford.edu
Email: ermon [at] cs.stanford.edu
Earth System Science
Email: dlobell [at] stanford.edu