Akamina Parkway Reconstruction and Hazard Mitigation
Bibliographic record
Abstract
Waterton National Park is in southwestern Alberta, it is the southernmost National Park in the Canadian Rocky Mountains. On June 19, 2013, over a 24 hour period, between 60 mm and 125 mm of rain fell (rainfall records provided by Parks Canada for the Akamina and Waterton Warden Office) on the steep mountain sides adjacent to the Akamina Parkway triggering catastrophic flooding, landslides, debris flows and debris floods. The widespread impacts from the various natural hazards resulted in severe impacts to the roadway and severed access to Akamina Lake, Cameron Lake and the associated nearby hiking and camping areas. The flooding and damage as experienced by the city of Calgary, during the same precipitation event, is described by the Government of Alberta as the worst in its recorded history. The Parkway is located in a geomorphically active mountainous area subject to regular flooding and debris flow events. The processes that led to the road damage were primarily related to inadequate control of debris and water passage at eight locations. Tetra Tech EBA was retained by Parks Canada, through their emergency services contractor, Maglio Installations, to provide emergency analyses and design guidance for remediation and mitigation along the Parkway. Tasks included: hydrology assessments, hydraulic analysis, design drawings for culvert replacements, debris storage catchment basins, debris berms, debris racks, rock scaling, retaining walls, specification of riprap prescription and reinforcement of roadway, support for bridge construction, and general field design guidance. The initial design criteria included the 100 year clear water event and the 10 year debris flow event. Gabion and rock walls were designed and constructed at wash-out locations to re-open the vital tourist access. Tetra Tech EBA also provided construction monitoring and materials testing services for this fast-paced project and has adapted designs to suit field conditions. Construction began in July 2013 and was substantially completed by November 30, 2013.
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.002 | 0.002 |
| Science and technology studies | 0.003 | 0.000 |
| Scholarly communication | 0.003 | 0.001 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.016 | 0.002 |
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".