jis
Permanent Way Inspector
Staff member
Administator
Moderator
AU Supporting Member
Gathering Team Member
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. 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.
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. It is absolutely critical to run trains in timetable order that are within tolerance to avoid a complete unholy mess. If an overtake is in the timetable, that is what you do. If not you don't, unless something falls outside tolerance. At that point you play one of the alternate playbooks. You don;t just do what you think works for you locally.
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. Happens both ways, i.e. 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. Little do they realize some of the mess that will befall them if they were not held. 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. You cannot just change things because a train has shown up at a Home signal.
MODERATOR NOTE: This post discusses 2 different topics and, at the suggestion of the poster, discussions regarding Train Dispatching Simulators were moved from this thread in the Amtrak forum to the Railroad Simulation forum/Train Dispatcher Simulation. Rather than cut and paste this post, this moderator opted to copy the entire post and duplicate it so that the post will appear in 2 different threads.
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. It is absolutely critical to run trains in timetable order that are within tolerance to avoid a complete unholy mess. If an overtake is in the timetable, that is what you do. If not you don't, unless something falls outside tolerance. At that point you play one of the alternate playbooks. You don;t just do what you think works for you locally.
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. Happens both ways, i.e. 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. Little do they realize some of the mess that will befall them if they were not held. 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. You cannot just change things because a train has shown up at a Home signal.
MODERATOR NOTE: This post discusses 2 different topics and, at the suggestion of the poster, discussions regarding Train Dispatching Simulators were moved from this thread in the Amtrak forum to the Railroad Simulation forum/Train Dispatcher Simulation. Rather than cut and paste this post, this moderator opted to copy the entire post and duplicate it so that the post will appear in 2 different threads.
Last edited by a moderator: