MétaCan
Menu
Back to cohort
Record W4415240046 · doi:10.1080/00423114.2025.2573163

Rail profile design optimisation for a broad-gauge heavy haul line

2025· article· en· W4415240046 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

VenueVehicle System Dynamics · 2025
Typearticle
Languageen
FieldEngineering
TopicRailway Engineering and Dynamics
Canadian institutionsNational Research Council Canada
Fundersnot available
KeywordsLine (geometry)Railway lineMathematical modelRail transportation

Abstract

fetched live from OpenAlex

Increasing axle loads and speeds in heavy-haul railway systems have intensified rail and wheel damage, leading to elevated maintenance costs and reduced operational efficiency. A promising solution to this issue without compromising service demands is enhancing wheel – rail interaction through optimisation of rail profiles. This study introduces a rail profile optimisation framework tailored for a broad-gauge heavy-haul network experiencing excessive rail wear, utilising Non-dominated Sorting Genetic Algorithm II (NSGA-II). The framework is designed to minimise wear and rolling contact fatigue (RCF) while maintaining satisfactory and safe vehicle dynamic performance. The framework includes optimisation of both high and low rail profiles for sharp and mild curves, as well as optimisation of two rail profiles for tangent track to improve contact point distribution and reduce hollow wear. The optimisation process is based on in-service profiles to ensure practical grindability and incorporates multi-body simulations (MBS) to assess wheel and rail damage as well as vehicle dynamic behaviour. The results indicate that the optimised profiles substantially reduce wear and RCF across various track sections. Furthermore, long-term wear and RCF evaluation of rail profiles on sharp and mild curves confirm the superior performance of optimised profiles, thereby validating their potential for integration into maintenance practices.

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 categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.935
Threshold uncertainty score1.000

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.009
GPT teacher head0.213
Teacher spread0.204 · 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