Snowmelt runoff processes in a headwater lake and its catchment, subarctic Canadian Shield
Bibliographic record
Abstract
Abstract During the snowmelt season, surface runoff into northern Canadian Shield lakes is governed by the distribution of snow and its ablation, storage in catchment slopes and valleys, and flow delivery from uplands, bottomlands and from upper lakes. For the lake studied, time lags exist between the commencement of snowmelt and the arrival of runoff to the lake, with evaporation from the uplands and bottomlands consuming some of the meltwater produced. Inflow from an upper lake is delayed. With all these inputs, the lake becomes flooded, first forming a moat, followed by an expansion of the open water areas, which are subject to evaporation loss. Lake outflow begins when water level rises above the outlet threshold. For the snowmelt season, outflow constitutes 40% of total melt and rainfall. The lake itself is a major storage that continues to maintain outflow until the lake level drops below the threshold in early summer, after which flow ceases. Snowmelt is the main period when runoff is generated from the headwater catchment to replenish storage depleted in the previous summer, and to produce flow along the Shield valley that contains a chain of lakes. Copyright © 2006 John Wiley & Sons, Ltd.
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.001 | 0.002 |
| Science and technology studies | 0.003 | 0.001 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.001 |
| 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".