MétaCan
Menu
Back to cohort

The Influence of Explosive and Rock Mass Properties on Blast Damage in a Single-Hole Blasting

2024· preprint· en· W4391610549 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenuePreprints.org · 2024
Typepreprint
Languageen
FieldEngineering
TopicGeotechnical and Geomechanical Engineering
Canadian institutionsUniversity of Alberta
Fundersnot available
KeywordsExplosive materialRock blastingRock mass classificationGeologyForensic engineeringMaterials scienceMining engineeringGeotechnical engineeringEngineeringGeographyArchaeology

Abstract

fetched live from OpenAlex

In rock blasting for mining production, stress waves play a major role in rock fracturing along with explosion gases. Better energy distribution improves fragmentation and safety, lowers production costs, increases productivity, and controls ore losses and dilution. Blast outcomes vary significantly with the choice of the explosive and the properties of the rock mass encountered. This study analyzes the effects of rock mass and explosives properties on the blast outcomes through numerical simulation using data from the case study and later validates the simulation results from the field blast fragmentation. The outcomes suggest that, for a given set of rock properties, the choice of explosive has a major influence on the resulting fragmentation. Strong explosives favor large fracture extents in hard rocks, while less strong explosives offer a better distribution of explosive energy and fractures. The presence of rock structures such as rock con-tacts and joints influences the propagation of stress waves and fractures depending on the structures' material properties, intensity and orientations, and the direction and strength of the stress wave. To achieve effective fragmentation, the blast design should mitigate the effect of variability in the rock mass by ensuring adequate energy distribution within the limits of geo-metrical design.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.295
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.002
Research integrity0.0000.002
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.058
GPT teacher head0.247
Teacher spread0.189 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it