Exeter November 11 2018

You are here: Home > Forum > Simulations > Timetables > Exeter > Exeter November 11 2018

Page 1 of 1

Exeter November 11 2018 18/11/2018 at 00:37 #113373
AlexRail575
Avatar
136 posts 		This is an experiment based on my recent fiddling around with the XML timetable format. Doesn't completely alleviate the necessity to manually enter train category and next working information, but does speed up the process since all train timings are there.

The timetable hasn't been tested, and the allocations are a best guess (based on what information is available, and in cases where it was not possible, once all the impossibles had been removed, whatever I had left is what is in the timetable), but timetable analysis doesn't bring up any issue.

There are three possessions. The headcodes for these and the one freight train are guesses, the UID is correct.

Description:
Quote:
Timetable as run on the 11th of November 2018. The data for passenger workings was extracted from the National Rail data feeds; the few freight workings (mostly engineering trains) are taken from realtimetrains
A few notes on the possessions:
6Z23 does not depart from Hele LC until 8:00. The level crossing will indicate it has failed, this is normal, in real life the crossing would be locally operated for the duration of the possession (per Rule Book Module TS9 section 3.7)
6Z64 does not depart from Dainton until 8:34. Nothing special to worry about here.
6Z24 is going to a possession at Crediton branch. Make sure it is the last train there. In normal circumstances this shouldn't pose any problems.
Last edited: 18/11/2018 at 00:39 by AlexRail575
Reason: formatting
Log in to reply
Exeter November 11 2018 18/11/2018 at 13:53 #113381
AlexRail575
Avatar
136 posts 		Question:

If I have updated versions, do I just submit the new files (as I did with the original ones)?
Log in to reply
Exeter November 11 2018 18/11/2018 at 16:52 #113392
Steamer
Avatar
3997 posts 		AlexRail575 in post 113381 said:
Question:

If I have updated versions, do I just submit the new files (as I did with the original ones)?
Navigate to the timetable in the Downloads area (I'm assuming it's this one, then click the 'Edit' button next to the 'Download' button. You can then change the name/version info, and upload a new file. Note that the new file will only be available to download when a Mod has approved it (usually within a few hours of upload).
"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
Exeter November 11 2018 18/11/2018 at 18:20 #113402
AlexRail575
Avatar
136 posts 		Thanks!
Log in to reply
Exeter November 11 2018 19/11/2018 at 09:05 #113410
DriverCurran
Avatar
695 posts 		Alex

If you want the information for an update to this timetable feel free to make use of this

6Z23 in reality was 6J81 which is formed of a tamper number DR73920 (18 metres)
which on arrival at Tiverton Loop then became
6Z24 with the same details

6Z64 in reality was 6U25 which is formed of a stoneblower number DR80205 (32 metres)

With on track machines the train ID actually indicates the individual machine number.

Hope this may be of some use.

Paul
You have to get a red before you can get any other colour
Last edited: 19/11/2018 at 09:13 by DriverCurran
Reason: Correction to OTP machine numbers
Log in to reply
The following user said thank you: AlexRail575
Exeter November 11 2018 19/11/2018 at 13:54 #113418
AlexRail575
Avatar
136 posts 		Thanks Pau! I personally didn't have any info for the train IDs (the effect of living across the pond...)

Looking for more information on that (googling the DR number), I found this page, which, by pure coincidence, allowed me to fix the headcode for the freight train (6Y15) and gives me all the information on the consist of said freight train - which is in fact yet another NR train. With that I'm going to update the train length to about 900 metres (2 Class 66 + 43 * 20 m). The updated description:
Quote:
Timetable as run on the 11th of November 2018. The data for passenger workings was extracted from the National Rail data feeds; the few freight workings (mostly engineering trains) are taken from realtimetrains

A few notes on the possessions:
6J81 does not depart from Hele LC until 8:00. The level crossing will indicate it has failed, this is normal, in real life the crossing would be locally operated for the duration of the possession (per Rule Book Module TS9 section 3.7). Later in the day, this train goes to the Crediton branch. Make sure it is the last train there. In normal circumstances this shouldn't pose any problems.
6U25 does not depart from Dainton until 8:34. Nothing special to worry about here.

Updates:
0.9.1 Category cleanup
0.9.2 Engineering train details
Again, thanks!

[Latest update]:
0.9.3 Fixed chaining inconsistencies + times at Aish X-overs
Last edited: 19/11/2018 at 16:00 by AlexRail575
Reason: update
Log in to reply
Exeter November 11 2018 19/11/2018 at 16:15 #113425
DriverCurran
Avatar
695 posts 		Alex

That is no trouble, even over this side of the pond it is highly likely that you would struggle to get the real running number for a lot of the freight trains, although I didn't know about the site you found. I actually work for the railways and have access to certain systems which will show the real 4 character number.

At the time of getting the 3 on track machines I hadn't downloaded the timetable so was unable to see what sort of timing the missing freight had to get that one for you.

Paul
You have to get a red before you can get any other colour
Log in to reply
Exeter November 11 2018 26/11/2018 at 01:08 #113573
Edgemaster
Avatar
332 posts 		From the timetable, it looks like the Exmouth Junction reversers need to be signalled across the junction to allow other services to pass. In particular, 5F09 and 2F08 conflict. I'm assuming that the CE Works headshunt is used to reverse?

Looking further at the NR data, there doesn't appear to be a TIPLOC for the headshunt, so I guess the Junction TIPLOC also covers it. The timetable should probably be updated to use the SimSig location 'Exmouth Jn EJ7/EJ20 (Rev)'. (This location doesn't work for a mainline reversal with points keyed and authorised at EJ4).
Twitter
Last edited: 26/11/2018 at 02:13 by Edgemaster
Reason: None given
Log in to reply
Exeter November 11 2018 26/11/2018 at 04:05 #113574
AlexRail575
Avatar
136 posts 		Yeah, noticed that.

As you can notice from this example, information is not provided further than "Exmouth Jn". Because of the way the timetable was made, that is copying the data from the National Rail data feeds and only adapting it for the SimSig format, what I (or rather, the program I wrote) ended up doing was taking this:
Quote:
<Journey rid="201811116741515" uid="C41515" trainId="5B75" ssd="2018-11-11" toc="GW" trainCat="EE" isPassengerSvc="false">
<OPOR tpl="EXETERC" act="TB" plat="3" wtd="11:16" />
<OPIP tpl="EXMOTHJ" act="RMOP" wta="11:19" wtd="11:54" />
<OPDT tpl="EXETERC" act="TF" plat="2" wta="11:57" />
</Journey>
And transforming it into something like this:
Quote:
<Timetable>
<ID>5B75</ID>
<UID>C41515</UID>
[...]
<Trips>
<Trip>
<Location>EXETERC</Location>
<DepPassTime>40560</DepPassTime>
<Platform>3</Platform>
</Trip>
<Trip>
<Location>EXMOTHJ</Location>
<DepPassTime>42840</DepPassTime>
<ArrTime>40740</ArrTime>
</Trip>
<Trip>
<Location>EXETERC</Location>
<DepPassTime>43020</DepPassTime>
<ArrTime>43020</ArrTime>
<Platform>2</Platform>
</Trip>
</Trips>
</Timetable>
The timetable analysis, of course, did not report anything wrong with that timetable and so, after I had fixed everything that it reported, it went unnoticed... I have fixed it.
Log in to reply
Back