Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 4, 2013 9:18:30 GMT
This covers both Overground and Bakerloo lines, so I decided to put it in "General"!
Just spotted this on wnxx:
|
|
|
|
Post by andypurk on Aug 4, 2013 15:33:14 GMT
This covers both Overground and Bakerloo lines, so I decided to put it in "General"! Just spotted this on wnxx: On Friday evening, the 3rd southbound train was read like it was over 21,600 minutes away (due to the platform and time running together)!! Maybe they are testing for the engineering work on the West Coast Mainline during August next year, rather than the server problems being claimed today. |
|
|
|
Post by norbitonflyer on Aug 4, 2013 18:34:26 GMT
Those aren't late. They are countdown indicators, telling you not how late the train is, but how soon it will come. And at 20:06, the 12:26 (next day) is due in 16 hours and 20 minutes, which is exactly 980 minutes.
How do they know the 12:16 will be 5 minutes late though?
|
|
|
|
Post by andypurk on Aug 4, 2013 22:05:08 GMT
How do they know the 12:16 will be 5 minutes late though? Almost certainly because it was late when feed from the server failed  |
|
|
|
Post by norbitonflyer on Aug 5, 2013 9:24:18 GMT
How do they know the 12:16 will be 5 minutes late though? Almost certainly because it was late when feed from the server failed That depends what the right hand column is telling you: is it saying that today's (Friday) 12:16 to Tring is running 975 minutes (16h15) late, (and if it was already 15 minutes late when the server failed, it would not have left Euston) in which case it will be expected at 04:31, or that tomorrow's 12:16 is expected in 975 minutes time, in which case it will arrive at 12:21 (975 minutres after 20:06, the time displayed on the clock)> According to the timetable, there is no 12:16 from H&W to Tring on Fridays, but there is on Saturdays. I the feed is telling you, on Friday evening, that there are no more trains until tomorrow afternoon. Waqs the station in fact closed on Saturday morning |
|
|
|
Post by andypurk on Aug 5, 2013 10:18:12 GMT
Almost certainly because it was late when feed from the server failed That depends what the right hand column is telling you: is it saying that today's (Friday) 12:16 to Tring is running 975 minutes (16h15) late, (and if it was already 15 minutes late when the server failed, it would not have left Euston) in which case it will be expected at 04:31, or that tomorrow's 12:16 is expected in 975 minutes time, in which case it will arrive at 12:21 (975 minutres after 20:06, the time displayed on the clock)> According to the timetable, there is no 12:16 from H&W to Tring on Fridays, but there is on Saturdays. I the feed is telling you, on Friday evening, that there are no more trains until tomorrow afternoon. Waqs the station in fact closed on Saturday morning I had forgotten that the xx.04 trains try to run a minute earlier on Saturdays; on weekdays they often arrive at Harrow at xx.16 but have a minute extra owing to following behind the Southern service (which also runs a minute earlier on Saturdays). As the server had crashed, who on earth knows whether what the screens were saying can be interpreted. However, I very much doubt that it was saying that any of the services was actually due in 975 mins (certainly not 975 minutes late). My point was that the 12.04 from Euston has the same headcode on Fridays and Saturdays (2T49) and so the display of information on the Friday may have got scrambled with that of the same train on the next day (assuming that a particular service had run late when the system went down). The system is quite capable of showing trains as being late before they are due to have left Euston, if control have bothered to enter the information. Also, there were certainly plenty of trains after the 20.06 on Friday and a full service was running on Saturday. |
|
