MétaCan
Menu
Back to cohort
Record W2085922089 · doi:10.1139/t99-108

Track and support rehabilitation for a mine company railroad

2000· article· en· W2085922089 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.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueCanadian Geotechnical Journal · 2000
Typearticle
Languageen
FieldEngineering
TopicRailway Engineering and Dynamics
Canadian institutionsnot available
Fundersnot available
KeywordsBallastAxleTrack (disk drive)Foundation (evidence)Aggregate (composite)Axle loadEngineeringGeotechnical engineeringMining engineeringStructural engineeringMechanical engineeringLaw

Abstract

fetched live from OpenAlex

The initial support and tie foundation problems of a railroad track built in 1974 to carry axle loads 21% greater than presently (1998) permitted under interchange laws at a speed of 88 km/h are presented. Some of the concerns related to and affecting the final rehabilitation that resulted in a final satisfactory performance are documented. The foundation engineer's interest is directed to the ballast, the tie, and to a lesser extent the rail's behaviour. Cobble-sized (75-150 mm) river gravel was used as the source for the ballast in the rehabilitation. The ballast's satisfactory performance has permitted the establishment of guidelines for future use of this type source of material where suitable quarried rock is not available. The railroad's satisfactory performance after rehabilitation has proven that the design concepts involving 36 t (40 tons) axle loads operating on 60 kg/m (119 lb/yd) continuously welded rail, concrete ties, and ballast manufactured by crushing from a river aggregate were achievable.Key words: railway track, concrete ties, ballast aggregate, aggregate, crushed face, rail, 36 t (40 tons) axle loads.

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.305
Threshold uncertainty score0.472

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.006
GPT teacher head0.199
Teacher spread0.193 · 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