By the way, when they start out an extra train set to cover the regular train schedule of a late train, we get the following four scenarios because of the way Amtrak Status Maps (ASM) works. In order to keep the network traffic to a minimum, ASM only looks for a train at a station when it's possible. For example, on the 3/3/2014 version of 94 in the last post, being 7H 49M late in ALX, it wouldn't even start looking for the train in WAS until 9.24 p.m. (regular arrival time 1.35 p.m.) because it thinks that 94 couldn't possibly get to Washington before that. This leads to four scenarios:
A) Amtrak identifies the extra train as the original train, and unidentifies the late train when it gets to the origin station for the extra train. On the maps this will show original 94 up through WAS and then stalled until new-94's time gets late enough for ASM to start looking for it again. Then suddenly it will jump way up the line.
B) Amtrak does not identify the extra train as the original train. In this case the new train will be invisible and never appear on the maps at all.
C) Amtrak identifies BOTH trains as the original train. In this case the maps will show the progress of the original train. The extra train will be invisible.
D) Amtrak unidentifies BOTH trains. In this case the extra train will be invisible and the original train will seem to stall.
That's enough of these thought experiments. I've got to get ready to go to work.
Edited by John Bobinyec, 14 August 2015 - 01:28 PM.
LDS Been On:
Old: Phoebe Snow (EL), Montrealer (AT), Laurentian (D&H)
RBBB: St. Petersburg - W. Palm Beach, Lakeland - Atlanta, Baltimore - NYC, Rochester, NY - Hartford, Albuquerque - Salt Lake City, Denver - Chicago
Modern: Ocean (VIA), Silver Star, Capitol Limited, Texas Eagle, Autotrain, Carolinian, Southwest Chief, California Zephyr, Lake Shore Limited