MétaCan
Menu
Back to cohort
Record W2040084934 · doi:10.1504/ijmme.2014.066577

A multi-step approach to long-term open-pit production planning

2014· article· en· W2040084934 on OpenAlex
Mohammad Tabesh, Clemens Mieth, Hooman Askari Nasab

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

VenueInternational Journal of Mining and Mineral Engineering · 2014
Typearticle
Languageen
FieldEngineering
TopicMining Techniques and Economics
Canadian institutionsCanadian Natural ResourcesUniversity of Alberta
Fundersnot available
KeywordsInteger programmingScheduling (production processes)Mathematical optimizationHeuristicCluster analysisProduction planningComputer scienceOpen-pit miningLinear programmingKey (lock)Term (time)Hierarchical clusteringProduction (economics)EngineeringAlgorithmMathematicsMachine learning

Abstract

fetched live from OpenAlex

The objective of this paper is to develop, verify, and present a multi–step methodology for three interrelated key components of open–pit mine planning: controlled optimal phase–design, characterisation of selective mining–units, and long–term production scheduling optimisation. A hybrid solution methodology for open–pit phase–design using integer programming and a local search heuristic is presented. Next, a hierarchical clustering approach with size and shape control, which aggregates blocks into minable polygons constrained within the pushback boundaries, is presented; and finally, a mixed integer linear programming mathematical model, which uses the generated pushbacks and aggregates as the planning units to provide near–optimal practical life–of–mine schedules, is introduced. In addition, the model inherently solves the cut–off grade optimisation problem. Two case–studies of real–size deposits are presented to illustrate practicality of the developed methodologies, and also to compare the results against industrial conventional practices to assess validity, performance, strengths, and limitations of the developed methodologies.

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.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
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.058
Threshold uncertainty score0.530

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
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.000
Research integrity0.0000.000
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.027
GPT teacher head0.263
Teacher spread0.236 · 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