Evolution of ground support designs for blasthole stoping in kimberlite at Diavik Diamond Mine
Bibliographic record
Abstract
Diavik Diamond Mine has used blasthole stoping (BHS) for the extraction of ore from the A154N orebody since 2010. As the only diamond mine globally to use this mining method for kimberlite extraction, there are several unique challenges that Diavik had to overcome with regards to ground support. Geotechnical variability of the kimberlite, mine sequencing, stope sizing and production output requirements have led to the development of a variety of ground support designs to overcome these challenges. A change from a vertical walled, rectangular stoping geometry to a geometry requiring partial undercutting of the stope crown led to a transformation in the overcut ground support requirements. New support elements including, pre-tensioned cable bolts and resin rebar, have been integrated into the designs to account for the change in stope geometry. Concurrently, higher-capacity inflatable friction bolt support has been required to account for the geotechnical variability of the kimberlite and the transition from primary stoping to secondary stoping. This paper describes the various ground support designs at Diavik Diamond Mine used for BHS in kimberlite and how these designs have evolved over the life of the mine in response to changing ground conditions and production requirements.
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.001 | 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.001 | 0.001 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 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".