Syllabus
Course Description
Climate variability and change pose threats to lives and livelihoods. These climate risks can be managed through the design and operation of infrastructure systems, as well as through disaster response and recovery. Decisions about how to develop and choose risk management strategies are often based on pure vibes, but occasionally rigorous quantitative analyses that make use of scientific information can inform them (we will focus on these cases). These analyses involve integrating knowledge from multiple disciplines to balance competing goals (objectives) under uncertainty.
In this course, you will learn climate science, uncertainty quantification, and decision analysis methods to support climate risk management. You will be assigned readings for every class that cover both methods and applications, and will work collaboratively to implement key concepts through programming problem sets. Active class participation is required. Methods covered include scenario analysis, exploratory modeling, cost-benefit analysis, single- and multi-objective policy search, reinforcement learning, deep uncertainty, robust decision making, and equitable decision making.
Course Information
Prerequisites & Preparation
The following prerequisites are required:
- An introductory course in probability and statistics, such as CEVE 313, is strictly required.
In addition, the following prerequisites are encouraged.
- Some exposure to Python, Julia, Matlab, R, or another programming language
- Additional coursework in applied statistics
- Linear algebra (you should be comfortable with matrix notation and basic operations)
- Optimization (you should be comfortable writing down optimization problems)
If you are unsure whether your background gives you an adequate preparation for this course, please contact the instructor!
If your programming, mathematics, or statistics skills are a little rusty, don’t worry! We will review concepts and build skills over the course of the semester.
Course Objectives
After completing this course, you will be able to:
- Evaluate and describe the strengths and weaknesses of different approaches to modeling the impact of weather and climate hazards on critical systems.
- Apply and critique methods for cost-benefit analysis, optimization, policy search, and stochastic control to climate adaptation problems.
- Describe multiple frameworks for decision making under deep uncertainty.
- Decision analytical frameworks well suited to a particular problem and justify the choice.
Required Materials
No textbook is required for this course. All materials will be posted as open source on the course website or on Canvas.
You will regularly be assigned scientific papers to read. Where those are available through the Rice library, you will be expected to access them yourself. You are encouraged, though not required, to use Zotero (Rice students have free storage). See Fondren Library’s Resources for resources.
You will need a working laptop for this class. If you do not have access to a working laptop, or if you lose access during the semester, please email the instructor.
A Community of Learning
Rice’s core values are responsibility, integrity, community, and excellence. Our goal is to create a learning community aligned with these core values.
Core Expectations
Course success involves a dual responsibility on the part of the instructor and the student.
As the instructor, my responsibility is to provide you with a structure and opportunity to learn. To this end, I commit to:
- provide organized and focused lectures, in-class activities, and assignments;
- encourage students to regularly evaluate and provide feedback on the course;
- manage the classroom atmosphere to promote learning;
- schedule sufficient out-of-class contact opportunities, such as office hours;
- allow adequate time for assignment completion;
- make lecture materials, class policies, activities, and assignments accessible to students.
Students are responsible for their own learning in the course and should commit to:
- attending all lectures;
- doing all required preparatory work before class;
- actively participating in online and in-class discussions;
- beginning assignments and other work early; and
- attending office hours as needed.
Please stay home if you’re feeling sick! This is beneficial for both for your own recovery and the health and safety of your classmates. We will also make any necessary arrangements for you to stay on top of the class material and if whatever is going on will negatively impact your grade, for example by causing you to be unable to submit an assignment on time.
Diversity, Equity, and Inclusion
Rice is committed to building and maintaining an equitable and inclusive campus community. Diversity can refer to multiple ways that we identify ourselves, including but not limited to race, color, national origin, language, sex, disability, age, sexual orientation, gender identity, religion, creed, ancestry, belief, veteran status, or genetic information. Each of these diverse identities, along with many others not mentioned here, shape the perspectives our students, faculty, and staff bring to our campus. We, at Rice, will work to promote diversity, equity and inclusion not only because diversity fuels excellence and innovation, but because we want to pursue justice. We acknowledge our imperfections while we also fully commit to the work, inside and outside of our classrooms, of building and sustaining a campus community that increasingly embraces these core values.
Each of us is responsible for creating a safer, more inclusive environment.
Accommodation for Students with Disabilities
If you have a documented disability or other condition that may affect academic performance you should: 1) make sure this documentation is on file with the Disability Resource Center (Allen Center, Room 111 / adarice@rice.edu / x5841) to determine the accommodations you need; and 2) talk with me to discuss your accommodation needs.
Accommodation for Scheduling Conflicts
If any of our class meetings conflict with your religious events, student athletics, or other non-negotiable scheduling conflict, please let me know ASAP so that we can make arrangements for you.
Mask Policies
Masks are welcome but not required in the classroom. However, if a colleague (student, faculty, or staff) requests that others wear a mask, you are strongly encouraged to make them feel safe. Please do not ask someone making such a request to disclose their underlying medical condition. If for some reason you need your instructor or classmates to wear a mask, please let me know and I will communicate this to the class without disclosing your identity.
These policies may change over the course of the semester as the situation evolves.
Getting Help
You can ask questions through Canvas Discussions and Office Hours. We will make an effort to respond to all Canvas discussion questions within 24 hours, though this won’t always be possible (travel, weekends, etc.). Please do not use email for questions about course content or labs, since other students may have related questions. You should use email for questions about personal matters, such as scheduling conflicts, accommodations, etc.
Academic Integrity
This class is designed to encourage collaboration, and students are encouraged to discuss their work with other students. Engineering as a profession relies upon the honesty and integrity of its practitioners (see e.g. the American Society for Civil Engineers’ Code of Ethics). All work submitted must represent the students’ own work and understanding, whether individually or as a group (depending on the particulars of the assignment).
If you are ever unclear about academic integrity, please ask! Additionally, always err on the side of providing more information.)
Rice Honor Code
More specifically, all students will be held to the standards of the Rice Honor Code, a code that you pledged to honor when you matriculated at this institution. If you are unfamiliar with the details of this code and how it is administered, you should consult the Honor System Handbook at honor.rice.edu/honor-system-handbook/. This handbook outlines the University’s expectations for the integrity of your academic work, the procedures for resolving alleged violations of those expectations, and the rights and responsibilities of students and faculty members throughout the process.
AI/ML Resource Policy
Large language models (LLMs), like GPT, are powerful tools for generating text that can be used for coding and doing data analysis. This is at once empowering (LLMs are powerful and can save you time) and risky (LLMs can make mistakes that are hard to detect).
Our general view is that LLMs are powerful tools that you will encounter and use when you leave this classroom, so it’s important to learn how to use them responsibly and effectively. You are generally permitted to use LLMs in this course, but ultimately, you are responsible for guaranteeing, understanding, and interpreting your results. In particular:
- One of the best applications of LLMs is to write code. This can help accelerate your workflow, especially when you are learning new syntax. However, LLMs can make bad decisions about how to structure your code, can introduce bugs, and can mislead you about what your code is doing. You are responsible for understanding and debugging your code, and for ensuring that it does what you intend it to do.
- LLMs should not be used to generate text that you submit as your own work. If you are assigned a writing assignment, the point is to stimulate your thought process, and you short-cut this if you ask a LLM to generate the response for you. This leads to shallow thinking! However, you may use tools including LLMs (but also Grammarly, spell-check, etc.) to help you edit your writing. This can sometimes be a fine line; it’s always better to ask if you’re not sure, and to disclose your use of these tools in your submission
The resources page has links to helpful ideas about LLMs and how to use them.
Policy on Web Posting of Course Materials
Uploading course materials to web sites is not an authorized use of the course material. Both the poster and the user are in violation of the university policy, which is actionable.
Grading
Your final grade will be calculated as follow:
Category | Points (421) | Points (521) |
---|---|---|
Reading quizzes | 10 | 10 |
Labs | 10 | 10 |
Tests | 40 | 30 |
Project | 30 | 30 |
Reading Discussion | 0 | 10 |
Reading Notes | 10 | 10 |
Reading Quizzes
The purpose of assigning readings is to enhance class discussions. Students who are prepared for class enhance the learning experience for everyone and enable a collaborative group discussion. At the start of classes for which reading was assigned, expect a very short (5 minute) quiz covering basic concepts from the reading. You should be able to get all points on these readings if you have done the reading, even if you found key concepts challenging or confusing.
Your lowest two reading quizzes will be dropped.
Labs
On Fridays we will use class time for hands-on programming exercises (“labs”) to give you guided practice applying the concepts and methods from class. These labs will be announced on the course website ahead of time so anyone who is able can bring a laptop to class. These labs can be done in groups; if you cannot bring a laptop to class for whatever reason, you will be able to (and are encouraged to) work with other students, though you must turn in your own assignment for grading. All labs will cover either a set of programming tools or a case study.
Your lowest two labs will be dropped.
Tests
In-class written exams will be given for each module of the course. Tests are designed to be straightforward and will cover key ideas from reading, as well as key terms and concepts from lecture and code interpretation related to labs.
Project
We will build a case study related to house elevation over the course of the semester through weekly labs. Answers will be posted for each lab, so mistakes made in one lab do not pass to the next.
For a final project, you will be asked to incorporate additional concept(s) from the course into the case study. For example, you might improve the representation of additional sources of uncertainty, use a more sophisticated optimization algorithm, or change the objectives of the optimization problem.
Students enrolled in the 421 section (i.e., undergraduates) may work in small groups. Students enrolled in the 521 section (i.e., graduate students) must work individually.
Reading Discussion
All students enrolled in the 521 section (i.e., graduate students) will present one of the papers assigned to the class and lead a discussion.
- This discussion should take 30-50 minutes.
- You should sign up for a time by the second week of class.
- You should meet with your instructor at least one week before your presentation to discuss the reading and your discussion plan.
You will be graded on the quality of your presentation, the depth of your understanding of the reading, and your ability to lead a discussion.
Students enrolled in the 421 section may choose to present a paper alone or in a group. If you choose to present a paper, you will be graded on the same scale as the 521 students.
Reading Notes
All students will act as “note-taker” for an in-class reading discussion. The note-taker will be responsible for taking notes on the discussion (following up from the recording as necessary), then adding them to the course website (through a Pull Request; guidance will be provided). These notes should summarize, rather than transcribe, the discussion, and identify key insights, questions, disagreements, and points of confusion.
You should sign up for a time by the second week of class. Groups may be permitted depending on enrollment.
Late Work Policy
Late projects will be subjected to a 10% penalty per day. Specifically, your grade will be multiplied \(0.9^d\) where \(d\) is the number of days late. Late labs will not be accepted so that solutions can be posted promptly.
As described above, your lowest two labs and reading quizzes will be dropped. This is intended to accommodate events like minor illnesses, travel to a conference, and other circumstances that may cause you to miss a lab or quiz. If a major circumstance arises (e.g., a death in the family, a serious illness, etc.) that causes you to miss an extended period of time, please contact the instructor to discuss accommodations.
Preliminary Schedule
The following schedule outlines our planned topics and readings for the semester. In general, we will use Mondays for lecture, Wednesdays for group discussion centered on readings, and Fridays for computational labs.
This schedule is subject to change. Updated versions will be posted on the Schedule page of the course website.
Not all readings listed here will be assigned in full. Some may be assigned as optional reading and others may be assigned as excerpts.
Week | Course Dates | Topic | Reading | Exam / Project |
---|---|---|---|---|
Module 1: | Introduction | |||
1 | 1/8, 1/10, 1/12 | Introduction to climate risk management | Frank (2022), Loucks (2017) Ch. 1 | |
2 | 1/17, 1/19 | Science of climate hazard | Seneviratne et al. (2021), Lall et al. (2018) | |
3 | 1/22, 1/24, 1/26 | Vulnerability, exposure, and impacts | Wing et al. (2020), Bonnafous et al. (2017) | |
4 | 1/29, 1/31, 2/2 | Systems | Reed et al. (2022), | Exam 1 |
Module 2: | Decision Analysis | |||
5 | 2/5, 2/7, 2/8 | Cost-benefit analysis | Arrow et al. (2013) | |
6 | 2/12, 2/14, 2/16 | Scenario analysis | Bankes (1993) | Final Project: Proposal |
7 | 2/19, 2/21, 2/23 | Policy search and optimization | Berchum et al. (2019), Schwetschenau et al. (2023) | |
8 | 2/26, 2/28, 3/1 | Multiobjective policy search | Zarekarizi et al. (2020) | |
9 | 3/4, 3/6, 3/8 | Sequential decision problems | Herman et al. (2020), Quinn et al. (2017), Fletcher et al. (2019), Sutton & Barto (2018) | |
10 | 3/18, 3/20, 3/22 | Robustness | Herman et al. (2015), McPhail et al. (2019) | Revised Project Proposal; Exam 2 |
Module 3: | Thinking Critically | |||
11 | 3/25, 3/27, 3/29 | Deep uncertainty | Schneider (2002), Lempert & Schlesinger (2000), Oreskes et al. (1994) | |
12 | 4/1, 4/3, 4/5 | Equity and justice | Pollack et al. (2024), Fletcher et al. (2022) | |
13 | 4/10, 4/12 | Financial and systemic risks | Thomson et al. (2023), Condon (2021) | |
14 | 4/15, 4/17, 4/19 | Reflections | Keller et al. (2021), Gilligan & Vandenbergh (2020) | Draft Project Writeup; Exam 3 |
Final Projects | ||||
TBD | during final exam slot | Project presentations | ||
4/30 | Final write-up |