|
|
| Re: Canarsie Tunnel Single Track Operation (1500405) | |||
 |
|||
| Home > SubChat | |||
|
[ Read Responses | Post a New Response | Return to the Index ] |
|
||
|
Re: Canarsie Tunnel Single Track Operation |
|
|
Posted by Stephen Bauman on Fri Jan 18 19:05:21 2019, in response to Re: Canarsie Tunnel Single Track Operation, posted by ClearAspect on Fri Jan 18 18:46:11 2019. Was it late arrivalsDownload the spreadsheet. It shows the arrivals and departures for each station in both directions. There's enough data in those spreadsheets to condemn a lot of operations. The RT0 columns are the original schedule for a particular trip. The time above it is when the schedule was issued. It should be 30 minutes before departure. If it's significantly less than 30 minutes, the trip is probably amended as a result of a dispatcher's action. Schedules are updated during the trip. The RTN columns show the arrival and departure times for the last updated schedule showing that particular station. This is not good engineering practice because it hides problems. The POS columns show the position feed for the train. The position data is crude. It shows only the station and status: stopped_at; in_transit_to; and incoming. The position feed is broadcast every 30 seconds. The first stopped_at status coincides with when the countdown turns steady orange with 0 time to arrival. The incoming status coincides with the countdown clock flashing an orange 0 time to arrival. The in_transit_to status means the train is in motion. I'm not happy with my methodology because I use the last time I get a stopped_at status for the departure time. This is because some feeds show only the stopped_at status. I'd also be happier if the feed came every 7.5 seconds rather than every 30 seconds. That would obey the Nyquist Sampling rate. |
|
|
|