Mine waste cover system design – considerations for cold regions
Bibliographic record
Abstract
The contaminated sites program of Aboriginal Affairs and Northern Development Canada (AANDC) is responsible for closure of contaminated sites on Crown land throughout the Canadian north. A significant percentage of the closure liabilities faced by AANDC are associated with abandoned mines. Of these mine-related liabilities, many involve the need to construct earthen cover systems over potentially reactive tailings and waste rock in cold regions. AANDC will be implementing cover systems at sites in the very near future and therefore require that critical questions in regards to cold regions cover systems be addressed: i) what are the key processes that will affect performance of different types of cover systems within a cold regions context; ii) how should the design process incorporate these issues; and iii) what are the risks to long-term performance as a result of these cold regions phenomena. This paper outlines the technical guidance approach for cover systems in cold regions that has been developed by AANDC with the assistance of a Technical Advisory Group (TAG). Extreme climatic conditions in cold regions result in the ground surface reacting in ways not experienced in warmer regions of the world. These terrain features are caused by frost action processes. Frost action refers to soil behaviours that are the result of freezing and thawing of water within the soil matrix. Key points from the guidance document are presented. Cover system design philosophy as it relates to cold regions is discussed including utilising attributes of cold regions in design. Designing for sustainability highlights the importance of final landform design and key failure mechanisms for covers in cold regions: thermokarst, solifluction, and glaciation of surface water management systems. An emphasis is placed on robust landform design as well as the importance of risk assessment to evaluate final cover design. A generic case study is presented to provide an example of a cold regions cover design and the results of a risk assessment.
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.002 | 0.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.005 | 0.001 |
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".