Getting Started

  • Welcome & Overview
  • Logistics & Format
  • Team Participation
  • Prerequisites
  • Setup & Day 0 Checklist

Week 1 — Agentic Cowork Tools

  • Week 1 Overview
  • Week 1 Schedule
  • Week 1 Resources

Week 2 — Agentic Systems

  • Week 2 Overview
  • Week 2 Schedule
  • Week 2 Resources

Week 3 — Deep Learning

  • Week 3 Overview
  • Week 3 Schedule
  • Week 3 Resources

Week 4 — Foundation Models in Research

  • Week 4 Overview
  • Week 4 Schedule
  • Week 4 Resources
ESDS Advanced/Getting Started/Team Participation
OverviewESDS CourseAll Programs

Up next

Prerequisites

What you need before each week — from "no prerequisites" for the first two days to scientific programming experience for foundation models.

On this page

    Team Participation

    Team participation is optional. Working on a team project is a great way to get hands-on practice with everything the course teaches — but not every participant needs to join a team or work on a team project. You can take the full course, attend every session, and still get a lot out of the course without a team project.
    That being said, projects are a great way to get hands on experience with guidance from the instructors.

    How teams work

    Teams build a real NOAA/NCICS tool or product during the course, folding in what each week teaches — agentic cowork tools for research and reporting, agentic systems to automate part of the work, and (in the winter weeks) deep learning and foundation models where they add capability.

    During Weeks 1 and 2, every day includes a team project time and office hours session from 1:00 to 2:00 PM ET. This hour is for:

    • Teams working together on their projects.
    • Getting questions answered — office hours with instructors on hand.
    • Mentoring and practice — applying the morning's material with guidance.

    The session is open to everyone, whether or not you're on a team.

    Using team time for your own work

    Some participants will use team time to accelerate existing projects at NCICS and NOAA — bringing their own work to the course and using the tools, the time, and the instructors to move it forward. This is one of the best ways to participate: you don't need a formal team or a new project to make the most of the hour.

    What makes a good team project

    If you do join a team, strong projects tend to:

    • Solve a real problem, not a toy example.
    • Keep a human in the loop where scientific quality matters.
    • Validate results rather than trusting agent or model output blindly.
    • Produce something a non-technical stakeholder can actually use.

    Not sure whether a team is right for you? Ask on the course Slack channels or bring it to any office-hours session — the instructors will help you figure out the best way to participate.