Ubiquitous increases in flood magnitude in the Columbia River basin under climate change
Bibliographic record
Abstract
The USA and Canada have entered negotiations to modernize the Columbia River Treaty, signed in 1961. Key priorities are balancing flood risk and hydropower production, and improving aquatic ecosystem function while incorporating projected effects of climate change. In support of the US effort, Chegwidden et al. (2017) developed a large-ensemble dataset of past and future daily streamflows at 396 sites throughout the Columbia River basin (CRB) and selected other watersheds in western Washington and Oregon, using state-of-the art climate and hydrologic models. In this study, we use that dataset to present new analyses of the effects of future climate change on flooding using water year maximum daily streamflows. For each simulation, flood statistics are estimated from generalized extreme value distributions fit to simulated water year maximum daily streamflows for 50-year windows of the past (1950–1999) and future (2050–2099) periods. Our results contrast with previous findings: we find that the vast majority of locations in the CRB are estimated to experience an increase in future streamflow magnitudes. The near ubiquity of increases is all the more remarkable in that our approach explores a larger set of methodological variation than previous studies; however, like previous studies, our modeling system was not calibrated to minimize error in maximum daily streamflow and may be affected by unquantifiable errors. We show that on the Columbia and Willamette rivers increases in streamflow magnitudes are smallest downstream and grow larger moving upstream. For the Snake River, however, the pattern is reversed, with increases in streamflow magnitudes growing larger moving downstream to the confluence with the Salmon River tributary and then abruptly dropping. We decompose the variation in results attributable to variability in climate and hydrologic factors across the ensemble, finding that climate contributes more variation in larger basins, while hydrology contributes more in smaller basins. Equally important for practical applications like flood control rule curves, the seasonal timing of flooding shifts dramatically on some rivers (e.g., on the Snake, 20th-century floods occur exclusively in late spring, but by the end of the 21st century some floods occur as early as December) and not at all on others (e.g., the Willamette River).
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".