MétaCan
Menu
← Back to cohort
Record W7095200243

Guidelines for Using Centerline Rumble Strips in Virginia 6. Performing Organization Code 7. Author(s)

2005· article· en· W7095200243 on OpenAlexaboutno aff

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicTraffic and Road Safety
Canadian institutionsnot available
Fundersnot available
KeywordsRumbleCrashMileTruckLicenseData collection
DOInot available

Abstract

fetched live from OpenAlex

Following the wide and successful use of continuous shoulder rumble strips, many state departments of transportations (DOTs) installed centerline rumble strips (CLRS) on rural two-lane and undivided multilane highways in an effort to reduce cross-over-the-centerline (COCL) crashes. COCL crashes include head-on, sideswipe opposite direction, fixed object run-off-the-road left, and non-collision. The purpose of this research was to develop guidelines for using CLRS in Virginia based on a review of best practices and the analysis of Virginia COCL crash data from 2001 through 2003. The analysis procedures included data query and analyses of crash frequency, density, and rate. Areas and route locations with the highest COCL crashes and densities were identified as potential candidate sites for CLRS. As of 2003, 24 state DOTs and two Canadian provinces were using CLRS. They are generally installed on a case-by-case basis. CLRS design patterns vary greatly among states, but the most commonly used types are continuous grooves 12 to 16 inches in length, 6 to 7 inches in width, and 0.5 inch in depth spaced 12 or 24 inches apart. The optimal CLRS patterns remain unknown. Data analyses revealed that the distribution of COCL crashes in Virginia varied significantly with roadway system, road type, jurisdictional area, and road location. The statewide COCL crash densities were 0.13 and 0.71 crash per mile for secondary and

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 imitation

Not 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.

metaresearch head score (Codex)0.014
metaresearch head score (Gemma)0.053
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.214
Threshold uncertainty score0.716

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0140.053
Meta-epidemiology (narrow)0.0020.003
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0070.007
Science and technology studies0.0030.001
Scholarly communication0.0050.003
Open science0.0050.003
Research integrity0.0030.003
Insufficient payload (model declined to judge)0.2140.302

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.053
GPT teacher head0.308
Teacher spread0.255 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreMethods

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".

Quick stats

Citations0
Published2005
Admission routes1
Has abstractyes

Explore more

Same topicTraffic and Road Safety→French-language works237,207→