MétaCan
Menu
Back to cohort
Record W2963420714 · doi:10.1155/2019/6965728

Optimization of Bus Bridging Service under Unexpected Metro Disruptions with Dynamic Passenger Flows

2019· article· en· W2963420714 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.

venuePublished in a venue whose home country is Canada.
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

VenueJournal of Advanced Transportation · 2019
Typearticle
Languageen
FieldSocial Sciences
TopicTransportation Planning and Optimization
Canadian institutionsnot available
Fundersnot available
KeywordsBridging (networking)Transport engineeringService (business)Computer scienceService levelPublic transportOperations researchEngineeringComputer networkBusiness

Abstract

fetched live from OpenAlex

A metro disruption is a situation where metro service is suspended for some time due to unexpected events such as equipment failure and extreme weather. Metro disruptions reduce the level of service of metro systems and leave numerous passengers stranded at disrupted stations. As a means of disruption management, bus bridging has been widely used to evacuate stranded passengers. This paper focuses on the bus bridging problem under operational disruptions on a single metro line. Unlike previous studies, we consider dynamic passenger flows during the disruption. A multi-objective optimization model is established with objectives to minimize total waiting time, the number of stranded passengers and dispatched vehicles with constraints such as fleet size and vehicle capacity. The NSGA-II algorithm is used for the solution. Finally, we apply the proposed model to Shanghai Metro to access the effectiveness of our approaches in comparison with the current bridging strategy. Sensitivity analysis of the bus fleet size involved in the bus bridging problem was conducted.

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

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.001
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.008
GPT teacher head0.268
Teacher spread0.260 · 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