Course Plan

Below is a rough course schedule for the semester, including plans for lecture content, labs, homeworks, and projects. This is not a contract: it is a plan, and it may change substantially as the semester unfolds. We will update this schedule as necessary.

Note that all lecture videos are posted on the bCourses “Lectures” playlist for the course (this link is accessible only to Berkeley personnel).

Lecture slides¶

Not all lectures will have slides associated with them, but for those that do, you can find them all in this shared google folder. Links to individual weeks are provided below. See the Lectures tab on the left for links to the individual lecture notes.

• August 27: Logistics, conceptual overview of open science and open source. Lec 01 - Design and Teaching of Collaborative and Reproducible Data Science with Environmental Applications.

• September 3: Intro to Git, GitHub, with companion Git Visuals slides.

• September 10: Jupyter in action.

• September 17: Data Visualization - Guest Lecture by Sam Pottinger from Berkeley DSE. Slides: Lec 04 - DataViz - Sam Pottinger.pdf.

• Lec 06 - Binder Intro.

• Lec 07 - Climate Data - C. Gentemann [Guest].

• Lec 09 - Documentation and Publishing.

• Lec 09 Extra - Hub MyST Previews.

• Lec 10 - Data.

• Lec 12 - Tying it all together.

• Lec 13a - CO2 and Climate.pptx.

Lab Content¶

All the labs for the course can be found in the navigation bar on the left. Useful information about how to setup the labs in your JupyterHub sesssion can be found in the introduction page.

• August 29: Lab 00 - Intro Python and setup.

• September 5: Lab 01 - GitHub Classroom, Unix

• September 12: Lab 02 - Git, GitHub, Jupyter ...

What does a generic week look like?¶

Below shows a table of what a usual week will look like in this course, including assignment deadlines and course happenings. Note that this will generally be the structure for each week, but there may be some exceptions. When there are exceptions, announcements will be made well in-advance. Note: HW will generally be due biweekly, with peer code reviews due one week after the corresponding HW was due. So, for example, on Thursdays, either a HW or code review will be due, depending on whether a HW or code review was due last week.