Combining Track Quality and Performance Measures to Assess Track Maintenance Requirements
Bibliographic record
Abstract
The serviceability of a section of railway highly depends on track stiffness and roughness. Railway operators regularly measure parameters associated with track stiffness and roughness to evaluate the track conditions. These measures are used in combination with performance observations to assess maintenance requirements. Although these assessments are mostly qualitative, railway operations have benefited from them. Railway operators keep comprehensive records of different types of track defects along their lines. These records are a measure of track performance and present an opportunity to quantify the relationship between track quality and performance. This brings the possibility of developing a performance-based approach for assessing the maintenance requirement along a railway track. In this paper, a database of track geometry defects along Canadian National Railway’s Lac la Biche subdivision (Alberta) has been compared against measured parameters associated with track roughness and stiffness. The analyses confirm the relationship between track stiffness and roughness, and the occurrence of track defects. This relationship is further used to define threshold values of track roughness and stiffness, and a hazard chart for maintenance requirements along the Lac la Biche subdivision is proposed.
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.002 | 0.006 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.005 | 0.004 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.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.
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".