Climate Resiliency and Digital Sovereignty Learning Lab

This repository supports lessons, hackathons, lunch-and-learns, and train-the-trainer events built around a climate-resiliency analysis for Pine Ridge Reservation and the White River watershed. The code is a tool for asking community-grounded questions; producing more code is not the goal.

The canonical end-to-end reference is climate_resiliency_notebook.ipynb. It remains preserved as the full workflow. Most learners should use one of the purpose-built track notebooks below instead.

Choose your pathway

Pathway	Start here if...	Your goal
Guided Explorer	You have never coded, or have only watched someone use a notebook	Run prepared cells, change a few marked values, interpret one result, and complete the reflections
Data Investigator	You use spreadsheets or have tried Python	Change dates, gauges, weights, or chart choices and explain how the result changes
Technical Extender	You are comfortable debugging Python	Validate methods, replace data sources, generalize the geography, or add uncertainty and provenance

Not sure? Choose Guided Explorer. Moving slowly and explaining one defensible finding is success!

Open the notebook for your pathway:

• tracks/01_guided_explorer.ipynb — prepared drought snapshot, one chart, interpretation, limitation, and review check
• tracks/02_data_investigator.ipynb — gauge comparison, missingness audit, time-window sensitivity, and weight sensitivity
• tracks/03_technical_extender.ipynb — low-flow validation, tests, estimator comparison, and provenance design

Start here

1. Install Miniconda or Anaconda if your instructor has not provided a prepared computer.
2. From this repository, run conda env create -f environment.yml.
3. Activate it with conda activate ed-py.
4. Run python scripts/check_environment.py.
5. Open onboarding/00_readiness_check.ipynb and complete its short orientation.
6. Read guides/data_governance.md before using or sharing results.
7. Open the notebook for your selected pathway in tracks/ and run cells in order. Use climate_resiliency_notebook.ipynb for the full reference workflow.

If the environment already exists, update it with conda env update -f environment.yml --prune.

Time and equipment

• Full experience: about 10 hours across two days
• Short routes: 90 minutes or half a day; see guides/instructor_guide.md
• Equipment: one internet-connected computer per team, a modern browser, and about 3 GB of free disk space
• Recommended team size: 3–5 people
• Live data sources: U.S. Census Bureau, USGS, NOAA, and basemap services

Internet is part of the full workflow, but it should not determine whether a workshop succeeds. Instructors should run python scripts/prepare_workshop_data.py before an event. See data/README.md for the fallback policy.

While using the main notebook

• Run cells from top to bottom; later cells depend on earlier ones.
• Change only values identified by CUSTOMIZE HERE unless you are using an extension challenge.
• Treat saved outputs as drafts until the team has checked their provenance, assumptions, and sharing permissions.
• Use the cell-by-cell map in guides/beginner_cell_guide.md if code is new to you.
• If something fails, stop and use guides/troubleshooting.md; do not repeatedly rerun a failing download.

Expected outputs are written to outputs/figures/ and outputs/report/. See outputs/README.md before committing or publishing them.

Team roles

• Navigator: keeps the team on the selected route
• Driver: operates the notebook
• Data steward: tracks provenance, governance, and sharing questions
• Interpreter: explains plots and numbers in plain language
• Recorder/storyteller: captures reflections and findings

Rotate roles during the event. Coding experience should not determine whose knowledge counts.

Important scientific scope

This is a teaching workflow, not an operational assessment. Several values—such as health-score scaling, component weights, and the low-flow threshold—are illustrative choices that require local validation before decision-making. See guides/instructor_guide.md for specific teaching cautions.

Public availability is not the same as ethical permission. The analysis concerns Oglala Lakota lands and waters and should be reviewed under the Nation's own governance, protocols, and priorities before public release. Frameworks mentioned in the notebook are educational references, not evidence of local adoption or endorsement.

Repository map

guides/       learner, instructor, governance, accessibility, and troubleshooting support
onboarding/   five-minute readiness notebook
tracks/       three runnable notebooks tailored to different coding-comfort levels
challenges/   optional investigator and technical extensions
data/         source manifest and instructor-prepared fallback data
scripts/      environment check and workshop-data preparation
outputs/      generated figures and reports

Facilitation and support

• Learners: start with guides/learner_quickstart.md.
• Instructors and mentors: start with guides/instructor_guide.md.
• Errors: consult guides/troubleshooting.md and include the failed cell number when asking for help.
• Terms: consult guides/glossary.md.

License and citation

Code and original instructional text are provided under the license in LICENSE. Source datasets retain their own terms, citations, and governance considerations. Cite this repository using CITATION.cff and cite each source dataset separately.