Wildfire, extreme precipitation and debris flows, oh my! Channel response to compounding disturbances in a mountain stream in the Upper Colorado Basin, USA
Bibliographic record
Abstract
Abstract Compounding changes in climate and human activities stand to increase sediment input to rivers in many landscapes, including via discrete perturbations such as post‐fire debris flows. Because sediment supply is a dominant control on river morphology, understanding mountain river responses to sediment regime perturbations is critical to predicting and addressing downstream effects to infrastructure, water security and aquatic habitat. A growing body of literature explores the causes, likelihood, size and composition of post‐fire debris flows, but the channel response to these disturbances remains poorly studied. This study used repeat field surveys, time‐lapse photographs and pre‐ and post‐disturbance remote sensing datasets to document and analyse space‐ and time‐varying channel response to post‐fire debris flows along a steep mountain stream in the Upper Colorado River Basin, USA. Specifically, we evaluated channel morphology and bed composition changes, correlations between channel changes and valley and channel attributes, and the relative importance of spring snowmelt versus summer monsoon events. Several cross‐sectional channel change types were observed from lidar a month after post‐fire debris‐flow events, including channelized and braided incision into deposits, incision into the pre‐fire channel bed, bank erosion and no change. Channel changes were most correlated with pre‐fire channel width, valley width and unit stream power, and these relationships could be tested in other burned locations to evaluate their transferability. Repeat channel surveys before and after snowmelt indicate rapid recovery and channel narrowing following major sediment disturbances, although sediment deposits remained in the channel margins. Together, these results highlight the importance of field and remote sensing‐based channel surveys to improve understanding of, and potential to predict, mountain channel response to compounding climate disturbances.
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.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| 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".