MétaCan
Menu
Back to cohort
Record W631880921

Active transit signal priority for streetcars: experience in Melbourne and Toronto

2008· article· en· W631880921 on OpenAlex
Graham Currie, Amer Shalaby

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.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueTransportation Research Board 87th Annual MeetingTransportation Research Board · 2008
Typearticle
Languageen
FieldSocial Sciences
TopicTransportation Planning and Optimization
Canadian institutionsnot available
Fundersnot available
KeywordsPublic transportTransport engineeringTraffic congestionBus priorityOperations researchTransit (satellite)Computer scienceTraffic signalFutures contractEngineeringBusinessReal-time computingFinance
DOInot available

Abstract

fetched live from OpenAlex

Active traffic signal priority (TSP) has been identified as a cost effective way to better manage traffic systems to make on-street public transport more reliable, faster and more cost effective. While the implementation of TSP is growing throughout the world, there are relatively few studies which have examined their application to streetcar based systems. This paper reviews the experiences of TSP in Melbourne, Australia and Toronto, Canada. These cities run some of the world's oldest and largest streetcar based TSP systems. This paper describes the TSP systems adopted in both cities including key experiences. TSP performance is reviewed including an assessment of problems and issues identified. The review established that TSP systems in both cities have many similarities including the configuration of approach/request loop and stop line/cancel loop detection, the degree of priority provided and the targeting of clearance phases for turning traffic at intersections. There are some slight differences in the handling of bunching trams and opposing tram movements, which are better handled in the Toronto case. Both systems see rather different futures for TSP development. Toronto is focussed on full system-wide TSP implementation and advancement of TSP algorithms, while Melbourne aims to make priority more conditional on the degree of lateness of trams and on the degree of traffic congestion experienced.

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.006
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Science and technology studies
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.511
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0060.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.002
Science and technology studies0.0030.002
Scholarly communication0.0000.002
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.098
GPT teacher head0.424
Teacher spread0.326 · 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