You cannot just change things because a train has shown up at a Home signal. The arrivals into Penn Station and routing to the correct platform track is carefully choreographed, and its effect stretches all the way back to Swift and even Dock and Rea. Little do they realize some of the mess that will befall them if they were not held. an NEC train held for an MTD or an MTD held for one or more NEC, and that inevitably leaves the folks in the train that is holding, fuming. To a casual observer it may appear weird that they are held at Swift while an MTD comes in ahead of you and that happens at times because of the timetable padding that exists in that area. You don t just do what you think works for you locally. At that point you play one of the alternate playbooks. If not you don't, unless something falls outside tolerance. If an overtake is in the timetable, that is what you do. It is absolutely critical to run trains in timetable order that are within tolerance to avoid a complete unholy mess.
#TRAIN DISPATCHER 3.5 TORRENT SIMULATOR#
On dispatching the High Line through Swift, Portal, Lack, Erie, Allied, Bergen and onto A, I have played around on a train dispatching simulator using then current timetable, and Thirdrail you are absolutely right.
Has that changed since I was last there? Of course a hapless new comer to the Secaucus labyrinth probably would not know to walk to the western end of the platform to find the escalators to that concourse.
Thirdrail, as I recall the west end concourse at Secaucus across the lower level allows passengers to cross over from any LL platform to any other LL platform without crossing any barriers.
0 kommentar(er)
