MétaCan
Menu
Back to cohort
Record W2013549738 · doi:10.3141/1748-14

Breakdown-Related Capacity for Freeway with Ramp Metering

2001· article· en· W2013549738 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.
fundA Canadian funder is recorded on the work.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueTransportation Research Record Journal of the Transportation Research Board · 2001
Typearticle
Languageen
FieldEngineering
TopicTraffic control and management
Canadian institutionsIBI Group (Canada)Ministry of Transportation of OntarioUniversity of WaterlooToronto Metropolitan University
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsMetering modeMerge (version control)Highway Capacity ManualTransport engineeringComputer scienceEnvironmental scienceSimulationEngineeringAutomotive engineeringLevel of service

Abstract

fetched live from OpenAlex

Research was conducted to better understand the breakdown phenomenon and look for ways of strategically increasing capacity and travel speed by reducing breakdowns on a section of freeway in Mississauga, Ontario, that is subject to ramp metering. The major task was to quantify the probability of breakdown as an increasing function of volume at the critical location. Data from 71 peak periods during which breakdown occurred at the critical merge were used to estimate the function, which was then used in a computer simulation of fixed- and variable-rate metering to demonstrate the potential benefits of using the probability-of-breakdown concept as a basis for ramp metering. The results indicate, for example, that variable-rate metering that complements a constant merge flow limit of 2,320 veh/h per lane could increase peak-hour throughput from about 6,460 to 6,600 veh/h at this location. They also indicate that 2,500 veh/h might be allowed, provided stringent metering for quick recovery to free flow is feasible.

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: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.741
Threshold uncertainty score0.980

Codex and Gemma teacher scores by category

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