MétaCan
Menu
Back to cohort
Record W2042550318 · doi:10.5038/2375-0901.7.3.4

Impacts of Various Parameters on Transit Signal Priority Effectiveness

2004· article· en· W2042550318 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 Public Transportation · 2004
Typearticle
Languageen
FieldSocial Sciences
TopicTransportation Planning and Optimization
Canadian institutionsUniversity of British Columbia
FundersNatural Sciences and Engineering Research Council of CanadaUniversity of British Columbia
KeywordsVisSimHeadwayTransit (satellite)SIGNAL (programming language)Bus priorityTraffic volumeTraffic simulationVolume (thermodynamics)Traffic signalComputer scienceDetectorSimulationSimulation softwareTransport engineeringSoftwareReal-time computingAutomotive engineeringEngineeringMicrosimulationPublic transportTelecommunicationsOperating systemPhysics

Abstract

fetched live from OpenAlex

This research examines the impacts of a number of traffic parameters on the effectiveness of a Transit Signal Priority (TSP) application. TSP is tested with the 98 B-line rapid buses along Granville Street in the City of Vancouver as a case study. VISSIM, a micro-simulation software (PTV 2002), is used to simulate TSP operation on the corridor. The traffic parameters studied include: bus approach volume, cross street volume/ capacity (v/c) ratio, bus headway, bus stop location, bus check-in detector location, left turn condition, and signal coordination. Based on results from these experiments, recommendations are provided for TSP application on Granville Street. In general, it is found that a TSP application would be most effective under a traffic condition that has moderate-to-heavy bus approach volume, little or no turning volume hindering bus movement, slight-to-moderate cross street v/c ratio, farside bus stop, and signal coordination for traffic running in the peak direction.

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.002
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.761
Threshold uncertainty score0.392

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.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.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.023
GPT teacher head0.291
Teacher spread0.268 · 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