MétaCan
Menu
Back to cohort
Record W4293221244 · doi:10.3390/mining2030028

Optimum Fleet Selection Using Machine Learning Algorithms—Case Study: Zenouz Kaolin Mine

2022· article· en· W4293221244 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

VenueMining · 2022
Typearticle
Languageen
FieldEngineering
TopicMining Techniques and Economics
Canadian institutionsUniversity of Alberta
Fundersnot available
KeywordsLoaderTruckExcavatorDecision treeBoosting (machine learning)Gradient boostingComputer scienceAlgorithmSelection (genetic algorithm)EngineeringRandom forestMachine learningAutomotive engineering

Abstract

fetched live from OpenAlex

This paper presents the machine learning (ML) method, a novel approach that could be a profitable idea to optimize fleet management and achieve a sufficient output to reduce operational costs, by diminishing trucks’ queuing time and excavators’ idle time, based on the best selection of the fleet. The performance of this method was studied at the Zenouz kaolin mine to optimize the type of loader and the number of trucks used to supply the processing plant’s ore demands. Accordingly, five years’ data, such as dates, weather conditions, number of trucks, routes, loader types, and daily hauled ore, were collected, adapted, and processed to train the following five practical algorithms: linear regression, decision tree, K-nearest neighbour, random forest, and gradient boosting algorithm. By comparing the results of the algorithms, the gradient boosting decision tree algorithm was determined to be the best fit and predicted test data values with 85% accuracy. Subsequently, 11,322 data were imported into the machine as various scenarios and daily hauled minerals as output results were predicted for each working zone individually. Finally, the data which had the minimum variation from the selected required scheduled value, and its related data concerning loader type and the number of demanded trucks, were indicated for each day of the working year.

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.033
Threshold uncertainty score0.995

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.0010.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.030
GPT teacher head0.251
Teacher spread0.222 · 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