Page 1 of 1
| 79-80 Timetable Problem 02/11/2020 at 12:00 #133476 | |
jcharnley
16 posts |
I was running the 79-80 Friday timetable until 5S24 and 1P46 became marooned when their 0T01 shunter failed to appear. On investigation, it turned out that this was because 0T01/CSTP1FMX did not enter at Upperby at 0430. I restarted the sim at an earlier time and amended the shunter's timetable code to 0T01/CSTP1MX, which resolved the problem. Presumably the original code was interpreted as Monday and Friday excepted. This is a great timetable which I thoroughly enjoy.
Log in to reply |
| 79-80 Timetable Problem 02/11/2020 at 12:59 #133477 | |
postal
5265 posts 
|
jcharnley in post 133476 said:I was running the 79-80 Friday timetable until 5S24 and 1P46 became marooned when their 0T01 shunter failed to appear. On investigation, it turned out that this was because 0T01/CSTP1FMX did not enter at Upperby at 0430. I restarted the sim at an earlier time and amended the shunter's timetable code to 0T01/CSTP1MX, which resolved the problem. Presumably the original code was interpreted as Monday and Friday excepted. This is a great timetable which I thoroughly enjoy.Thanks for the nice words; lots of people seem to enjoy the challenges the TT presents. The entry of CSTP1FMX is governed by a rule linking it to the arrival of 5M18MX into Upperby. When you changed the UID to CSTP1MX then ran the sim there would be no rule governing the entry which is why it entered OK. However, that would not do as a permanent fix as you would then get a rogue 04:30 entry of a Cl.08 at Upperby on a Monday morning. CSTP1FMX follows the convention that the UIDs for the pilot workings are listed as CSTP1A, CSTP1B, CSTP1C etc with the days of running then suffixed onto the core UID. The F in CSTP1FMX is part of the sequencing rather than days of running. During the hundreds of hours of testing that this TT has undergone, CSTP1FMX has always entered as expected. Did you have any problems earlier in the run which caused you to "lose" 5M18MX? This would cause the non-entry of CSTP1FMX. “In life, there is always someone out there, who won’t like you, for whatever reason, don’t let the insecurities in their lives affect yours.” – Rashida Rowe Last edited: 02/11/2020 at 12:59 by postal Reason: None given Log in to reply |
| 79-80 Timetable Problem 05/11/2020 at 11:56 #133574 | |
|
jcharnley
16 posts |
Thank you for explaining how the UID for 0T01/CSTP1FMX works, and that its entry is governed by a timetable rule. Checking back through my snapshots, I found that 5M18 had exited at Upperby at 0342, somewhat late because I was running the timetable with a fairly high delay probability (but no track failures). At 0429, 0T01 was shown as due to enter 21 late, but at 0519 the timetable showed it as having entered, but it was not on the train list. What happened between these two times I do not know, but the most likely explanation may well be a blunder on my part. Many thanks again.
Log in to reply |
| 79-80 Timetable Problem 05/11/2020 at 13:12 #133576 | |
|
postal
5265 posts
|
jcharnley in post 133574 said:Thank you for explaining how the UID for 0T01/CSTP1FMX works, and that its entry is governed by a timetable rule. Checking back through my snapshots, I found that 5M18 had exited at Upperby at 0342, somewhat late because I was running the timetable with a fairly high delay probability (but no track failures). At 0429, 0T01 was shown as due to enter 21 late, but at 0519 the timetable showed it as having entered, but it was not on the train list. What happened between these two times I do not know, but the most likely explanation may well be a blunder on my part. Many thanks again.You may have been concentrating on something else and just pushed it back into Upperby after it entered. “In life, there is always someone out there, who won’t like you, for whatever reason, don’t let the insecurities in their lives affect yours.” – Rashida Rowe Log in to reply |