MétaCan
Menu
Back to cohort

Community-Based, Macrolevel Collision Prediction Model Use with a Regional Transportation Plan

2009· article· en· W2135274264 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

VenueJournal of Transportation Engineering · 2009
Typearticle
Languageen
FieldEngineering
TopicTraffic and Road Safety
Canadian institutionsOkanagan University CollegeUniversity of British Columbia, Okanagan CampusUniversity of British Columbia
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsPlan (archaeology)Transport engineeringCollisionComputer scienceTransportation planningProcess (computing)EngineeringGeographyComputer security

Abstract

fetched live from OpenAlex

This paper describes the application of previously developed community-based, macrolevel collision prediction models (CPMs) to evaluate the road safety of a regional transportation plan. The research objective was to present and test model-use guidelines in a regional road safety planning application. The data was extracted from over 400 Greater Vancouver neighborhoods in British Columbia, Canada, including output from the regional transportation model. The CPMs predicted a lower mean collision frequency region-wide due to a proposed three-year transportation plan, versus a do-nothing scenario. Recommendations have been made for future use of the CPMs in regional road safety planning applications. The application of macrolevel CPMs to this regional case study proved a solid step in the development of new and improved empirical tools for planners and engineers to include road safety in the planning process. It is hoped that these models and model-use guidelines will facilitate improved decisions by community planners and engineers, and ultimately, facilitate improved neighborhood traffic safety for residents and other road users.

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.447
Threshold uncertainty score0.682

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.001
Open science0.0000.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.020
GPT teacher head0.199
Teacher spread0.179 · 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