Capacity Analysis of a Passenger Rail Hub Using Integrated Railway and Pedestrian Simulation
Bibliographic record
Abstract
Abstract As the level of passenger demand in rail transit systems increases, major railway stations in urban centres face serious capacity issues. Both analytical and simulation methods have been used to analyse complex station areas; however, prior efforts have only focused on either train or pedestrian movements with over-simplified assumptions that do not properly capture the impact of their interaction on capacity. This study applies an integrated crowd and transit simulation platform “Nexus” to simultaneously study the impact of pedestrian and train movements on the system performance of a complex railway station. Unlike other methods such as sequential simulation methods, the integrated simulation platform permits linkage between commercial-grade simulators. Instead of treating each simulator separately, this integrated method enables detailed modelling of how the train and crowd dynamic interact at station platforms. Such integration aims to explore the interactive effect on both types of movement and enable performance analysis possible only through this combination. To validate the model, a case study is performed on Toronto’s Union Station. Extensive data were collected, processed and input into railway and pedestrian models constructed using OpenTrack and MassMotion, respectively, and integrated via Nexus. Examining scenarios of increased levels of train and passenger volumes, a 9% drop in on-time performance of train operation is observed, while the level of service experienced by passengers on the platform deteriorates significantly due to crowding. Both length and variation in dwell time due to pedestrian movement are recognized as the main factors of performance deterioration, especially when the system approaches capacity limit. The simulation model produces estimates of the practical track-side capacity of the station and associated platform crowding levels, and helps identify locations where passengers experience severe overcrowding, which are not easily obtainable from mathematical models.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".