MétaCan
Menu
Back to cohort
Record W2073309118 · doi:10.3141/2044-09

Safety Effect of Preventive Maintenance

2008· article· en· W2073309118 on OpenAlex
Tara Erwin, Susan Tighe

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.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueTransportation Research Record Journal of the Transportation Research Board · 2008
Typearticle
Languageen
FieldEngineering
TopicInfrastructure Maintenance and Monitoring
Canadian institutionsUniversity of Waterloo
Fundersnot available
KeywordsTransport engineeringEngineeringIntersection (aeronautics)CrashRoad surfaceForensic engineeringCivil engineeringComputer science

Abstract

fetched live from OpenAlex

Various North American transportation agencies have implemented several preventive maintenance techniques to improve pavement performance and safety. The York Region, located northeast of Toronto, Ontario, Canada, has been resurfacing and remedying pavements with microsurfacing treatments to improve the pavement surface conditions, but without a good understanding of how the treatment affects road safety. With data made accessible by the region, a before-and-after study was done, with the goal of gaining an understanding of how microsurfacing and resurfacing treatments affect road safety. The study concludes that microsurfacing and resurfacing can have a positive safety effect, with crash reduction factors as high as 54%. However, those activities are sensitive to the influence of treatment year data (which may be an anomaly period) and average annual daily traffic per lane. Generally, the findings illustrate that microsurfacing has a positive safety effect on locations susceptible to a number of conditions: regular occurrence of wet or slick (not dry) road surface conditions, a trend toward severe crashes, frequent intersection-related crashes, and a high occurrence of rear-end crashes. Findings of this study have opened the door to additional research; integration of safety under the pavement umbrella seems so logical and yet has barely been explored. For now, the crash reduction factors derived from the study can be applied by the region of York and by other jurisdictions to make more sound decisions at the network level when selecting pavement maintenance treatments.

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.003
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: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.127
Threshold uncertainty score0.822

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.001
Science and technology studies0.0000.001
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.002
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.028
GPT teacher head0.322
Teacher spread0.294 · 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