Page 1 of 1
| Not safe to have those kind of activities at this location 02/01/2024 at 13:09 #154945 | |
ajax103
1120 posts |
Just hope someone can explain why this error pops up but in the 2003 TT, there's a Class 2 that becomes a Class 5 at Hornsey as per the May 2003 WTT Section YA however the simulation throws up a error which I've never encountered saying it's not safe to do this there. Is this something that is Core Code related and affects others simulations or is this something that the Kings Cross developer has put in place for King's Cross? Log in to reply |
| Not safe to have those kind of activities at this location 02/01/2024 at 13:19 #154946 | |
Stephen Fulcher
2078 posts |
It’s due to how the location is coded into the sim. A simple N:xxxx activity will likely be fine, it’s more an issue for joins and divides.
Log in to reply The following user said thank you: ajax103 |
| Not safe to have those kind of activities at this location 02/01/2024 at 13:30 #154947 | |
|
bill_gensheet
1413 posts |
Also more of an issue on sims with ACI & ARS, in that the TD will not get changed automatically.
Log in to reply The following user said thank you: ajax103 |
| Not safe to have those kind of activities at this location 02/01/2024 at 15:03 #154948 | |
|
ajax103
1120 posts |
Stephen Fulcher in post 154946 said:It’s due to how the location is coded into the sim. A simple N:xxxx activity will likely be fine, it’s more an issue for joins and divides.That's just it, the train arrives at Hornsey as 2B99 and becomes 5B01 with the activity showing up as what ought to be a simple N: XXXX activity but doesn't accept that. It's not splitting or joining at all hence querying it. I've double checked the WTT in case there was a error from the timetable writer and there's no error, the only fix that I can think of is to run the 5B01 in the path of the 2B99 from Kings Cross and cancel 2B99 which as a staff train I don't think it matters if drivers travel between Kings Cross and Hornsey Depot on ECS moves or non ECS moves. bill_gensheet in post 154947 said: Also more of an issue on sims with ACI & ARS, in that the TD will not get changed automatically.While Kings Cross does have ACI for some key locations, the location in question doesn't and would require the signaller to manually change head code, if it was a location with ACI available than I could understand it but when it's a location that doesn't have ACI, I can't see why this error would come up. As I've never encountered this kind of error before, I just wondered why it was coming up that's all. Log in to reply |
| Not safe to have those kind of activities at this location 02/01/2024 at 17:26 #154949 | |
|
bill_gensheet
1413 posts |
ajax103 in post 154948 said:Accept the warning is what it is (N: activity at non-key location), you know why, you are happy it is of no consequence in this case, so no change required. I have it on my timetables for Motherwell (at Kirkwood) and Edinburgh (at Cardenden) for similar reasons. I think I put a mention in the TT guide notes, no more. I do not see a clean logic to propose as a change that would suppress the warning reliably. Circumstances that would result in not changing the TD is a reasonable thing to warn about. Log in to reply The following user said thank you: ajax103 |
| Not safe to have those kind of activities at this location 03/01/2024 at 07:35 #154958 | |
|
clive
2789 posts |
ajax103 in post 154948 said:Okay, here's why. For some reason I've never understood (perhaps Geoff can explain) locations in the sim are divided into "key" and "non-key" locations. Among other things, trains can only reverse direction at key locations. Non-key locations are supposed to be things like stations along plain line where it doesn't matter if they're omitted from the schedules of trains not stopping there. Some of the core code that handles train movement and activity ignores non-key locations. Therefore if you schedule something to happen at a non-key location, it's quite possible that it won't happen or that it won't happen properly. Because of this, the analyzer issues the warning you're seeing. Note that, even if the activity you want to do works now, I can't guarantee that it will always work. There may be technical reasons in the future to move the code that does it elsewhere, perhaps into "key-only" code. While we try to avoid making such changes, sometimes they're necessary. (I don't anticipate anything in this area; I'm just alerting you.) Log in to reply The following users said thank you: bill_gensheet, ajax103 |