MétaCan
Menu
Back to cohort
Record W2887645288 · doi:10.1155/2018/6292410

A Methodology for Choosing between Route Deviation and Point Deviation Policies for Flexible Transit Services

2018· article· en· W2887645288 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.
venuePublished in a venue whose home country is Canada.

Bibliographic record

VenueJournal of Advanced Transportation · 2018
Typearticle
Languageen
FieldSocial Sciences
TopicTransportation Planning and Optimization
Canadian institutionsUniversity of Victoria
FundersNational Natural Science Foundation of China
KeywordsTransit (satellite)Point (geometry)Service (business)Computer scienceStandard deviationAbsolute deviationTransport engineeringFunction (biology)Operations researchMathematical optimizationPublic transportEconomicsEngineeringMathematicsStatistics

Abstract

fetched live from OpenAlex

Flexible transit services, which bring together the characteristics of fixed-route transit and demand-responsive transit, have been proven to be cost-efficient in low-density residential areas. In this paper, a methodology is proposed to assist planners in making better decisions when choosing between route deviation policy and point deviation policy, which are two promising types of flexible transit services. A user cost function is developed to measure the service quality of the transit systems, and analytical models are constructed to compare the system performance under both expected and unexpected demand levels. Based on the experiments for various scenarios over a real-life transit example, the critical demands, which represent the switching point between the two competing service policies, have been derived. Our findings show that point deviation policy is more efficient at low-demand levels, while route deviation policy is a better choice at low-to-moderate demand levels. At unexpectedly high demand levels, route deviation policy is better able to accommodate rejected passengers than point deviation policy.

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.001
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: none
Teacher disagreement score0.741
Threshold uncertainty score0.437

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.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.056
GPT teacher head0.377
Teacher spread0.321 · 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