Upcoming Games

(UTC times)


Full list
Add a game

Upcoming Events

No events to display

Marylebone Station ARS

You are here: Home > Forum > Simulations > Released > Marylebone IECC > Marylebone Station ARS

Page 1 of 1

Marylebone Station ARS 15/07/2013 at 11:31 #47160
John
Avatar
884 posts
Marylebone Combined timetable 04:00 start.

Simulation running with failures switched off and with extra ARS switched on.

The time is 07.14 and ARS has been running the show faultlessly without any intervention required from me, when, for no apparent reason, it gives incorrect preference to 1H06 (07.19 arr) over 1G10 (07.15 dep).



I have also observed ARS's willingness to call 2H06 on into an occupied platform 3 for a join-up, but seem reluctant to call 1H08 on into platform 5 for a platform share.

I know that ARS is not perfect, but what might have caused these thus-far isolated incidents?

Log in to reply
Marylebone Station ARS 15/07/2013 at 12:29 #47164
Sacro
Avatar
1171 posts
Pretty sure that by default ARS isn't allowed to do platform sharing unless it's aware of the headcode it's sharing it with, however with a join, it has the headcode it's joining to and therefore it knows it's fine to issue the call-on route.
Log in to reply
Marylebone Station ARS 15/07/2013 at 13:11 #47165
John
Avatar
884 posts
" said:
Pretty sure that by default ARS isn't allowed to do platform sharing unless it's aware of the headcode it's sharing it with
I've just observed ARS refuse to allow 1H11 to share platform 6 with 1U14.

When I looked at 1H11's ARS routesetting status, it said "1U14 already on stretch" suggesting that ARS is aware that the two trains are booked to share.

Log in to reply
Marylebone Station ARS 15/07/2013 at 13:25 #47166
Steamer
Avatar
3984 posts
Online
" said:
" said:
Pretty sure that by default ARS isn't allowed to do platform sharing unless it's aware of the headcode it's sharing it with
I've just observed ARS refuse to allow 1H11 to share platform 6 with 1U14.

When I looked at 1H11's ARS routesetting status, it said "1U14 already on stretch" suggesting that ARS is aware that the two trains are booked to share.
'1U14 Already on stretch' means that 1U14 is blocking the route for 1H11, and ARS is waiting for 1U14 to move before setting the route for 1H11. In this case ARS has got confused and manual intervention is needed. The '... already on stretch' message can often be seen at junctions where ARS is waiting for another train to clear.

"Don't stress/ relax/ let life roll off your backs./ Except for death and paying taxes/ everything in life.../ is only for now." (Avenue Q)
Log in to reply
Marylebone Station ARS 15/07/2013 at 13:33 #47167
John
Avatar
884 posts
Coding issue, then, or this is the way it's supposed to be?
Log in to reply
Marylebone Station ARS 15/07/2013 at 13:39 #47168
Sacro
Avatar
1171 posts
" said:
When I looked at 1H11's ARS routesetting status, it said "1U14 already on stretch" suggesting that ARS is aware that the two trains are booked to share.
No, had it been aware that the two trains were to share a block it would have happily allowed them to.

Log in to reply
Marylebone Station ARS 15/07/2013 at 13:55 #47170
John
Avatar
884 posts
So, as the schedules of both trains were correct, and show them sharing platform 6, then in theory ARS should have allowed them to share?
Log in to reply
Marylebone Station ARS 15/07/2013 at 14:41 #47173
GeoffM
Avatar
6376 posts
" said:
Marylebone Combined timetable 04:00 start.

Simulation running with failures switched off and with extra ARS switched on.

The time is 07.14 and ARS has been running the show faultlessly without any intervention required from me, when, for no apparent reason, it gives incorrect preference to 1H06 (07.19 arr) over 1G10 (07.15 dep)
Incorrect depends on a lot of factors, many of which aren't evident from a picture I'm afraid. It all depends on overall predicted score - if it thinks it can tuck 1H06 inside the platforms before 1G10 is affected then it'll do so.


" said:
Pretty sure that by default ARS isn't allowed to do platform sharing unless it's aware of the headcode it's sharing it with, however with a join, it has the headcode it's joining to and therefore it knows it's fine to issue the call-on route.
The whole point of the platform share association is to allow ARS to set call-ons into occupied platforms as long as (a) only the specified trains are there (no others) and (b) they're in the right platform. If the platform is empty and the arriving train was expecting to share, that's not a problem - it'll route straight in. Only the second arrival needs to specify what to share with.

However, a bug has been identified which prevented SimSig ARS from doing so, which has been fixed ready for the next release.

Platform sharing used to be called double docking. It went out of favour for years but NR have asked for it in various places recently. If the stock for a train is different to that scheduled (or even that the sharing is inappropriate as scheduled), the signaller is expected to know and act accordingly in advance. So I am sure once the real railway gets it there will be hiccups. :)


" said:
So, as the schedules of both trains were correct, and show them sharing platform 6, then in theory ARS should have allowed them to share?
Correct.

SimSig Boss
Log in to reply
The following user said thank you: John
Marylebone Station ARS 15/07/2013 at 15:45 #47180
Albert
Avatar
1315 posts
The problem at Marylebone station from the 1st post, also happens at Richmond station on the NLL sim.

It appears that ARS will set a route for the incoming train anyway, ignoring the outgoing train unless that train has TRTS'd.

AJP in games
Log in to reply
Marylebone Station ARS 15/07/2013 at 17:17 #47183
Josie
Avatar
310 posts
The auto-working at Gunnersbury and Richmond has always been described as a basic first-come-first-served system, not proper ARS.
Log in to reply
Marylebone Station ARS 15/07/2013 at 19:45 #47192
UKTrainMan
Avatar
1803 posts
Leave your workstation briefly, head to the other desk to use the computer, and print out the appropriate form. Fill that out back at your workstation and it'll be sent off to DeltaRail for them to look at, download the reports, and correct where necessary.

B)

I say this because, whilst my group during the technical visit on Sunday 14th July 2013 were in Marylebone IECC, ARS had set the route for 2B22 into and through Platform 3 at Aylesbury before it had set the route for 2C29 out of Aylesbury Vale Parkway. The result of this was that the signaller had to get on the radio to 2B22 to advise him of the need to drop the route (likely resulting in an (Adverse) Change of Aspect); and then 2C29 ended up calling in as the driver of that was still awaiting the route. Signaller went to another computer in the room to print out a form which he duly filled out advising of this, and I'd expect it will have likely been sent off to DeltaRail for them to download the data and make any amendments needed.

Any views and / or opinions expressed by myself are from me personally and do not represent those of any company I either work for or am a consultant for.
Last edited: 15/07/2013 at 19:46 by UKTrainMan
Log in to reply
Marylebone Station ARS 16/07/2013 at 09:33 #47209
kbarber
Avatar
1742 posts
" said:

Platform sharing used to be called double docking. It went out of favour for years but NR have asked for it in various places recently. If the stock for a train is different to that scheduled (or even that the sharing is inappropriate as scheduled), the signaller is expected to know and act accordingly in advance. So I am sure once the real railway gets it there will be hiccups. :)

At Marylebone in the early '80s there were almost always one or two stock alterations during the peaks. At some point as things ramped up we'd get a phone call, usually from the Depot Supervisor, telling us any altered formations (as well as where to dispose each unit coming out of service and which splits/joins would be altered). Yes, you did need to be on your toes; only once did I ever drop an 8 on top of an 8...

Log in to reply