The Floods of 1990 and 1996 on Peace River
Bibliographic record
Abstract
Abstract: In June 1990, the flood of record occurred on the regulated Peace River. In the summer of 1996, reservoir drawdown created a flood of comparable magnitude on the upper river, smaller on the lower river, but of greatly prolonged duration. These floods provide an exceptional opportunity to study the effect of flows along a regulated river similar to those experienced under pre-regulation conditions. The 1990 flood, resulting from an exceptional summer storm, imported a supply of fresh sediment to Peace River from flooding tributaries. Limited change was observed in the British Columbia reach, with aggradation downstream of Pine River. Throughout the Alberta Peace River, where the flood was the largest on record, significant sedimentation occurred in all reaches, but was restricted to the established channel zone. In 1996, the clear water release from the dam changed a significant number of sections in British Columbia from stable or aggrading to degrading for the first time since regulation. In Alberta, modest aggradation occurred in Reach AB1, while Reach AB2, below the Smoky River confluence, degraded. Significant sedimentation occurred in Reach AB3, where chronic sedimentation has occurred since regulation. In these events, the import of sediment from tributaries was a critical factor mediating the response of the 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.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| 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.005 | 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".