Avalanche Hazard Management at the East Toba River and Montrose Creek Hydroelectric Project, South Coast Range, British Columbia
Bibliographic record
Abstract
at East Toba River and Montrose Creek connected by 156 km of 230 kV transmission line, as well as diversion dams, penstocks, powerhouses and roads. 101 avalanche paths were identified in the project area capable of affecting facilities. These paths were mapped on a GIS and used for location planning of facilities, planning for mitigation and ultimately the avalanche atlas for the construction avalanche safety program. Due to other site constraints (engineering, hydrology, etc.), the Montrose Creek intake was located in the runout zone of a very large avalanche path which has the potential to produce Size 5 avalanches. Size 3-4 avalanches reached the intake site during each of the last 4 winters. The intake design was modified to account for impact pressures from direct avalanche impacts as well as large vertical snow loads from deposits and snow fall. The intake design included the construction of a 120 m long by 15 m high deflection berm that will keep more frequent avalanches out of the intake reservoir and reduce the impact pressure of less frequent, larger avalanches. Construction of various aspects of the project, including work at the Montrose intake site, was conducted during 2009-2010 and required an
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.001 |
| Science and technology studies | 0.002 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| 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".