1. Home
  2. Library
  3. Data

Upcoming Games

(UTC times)

Full list
Add a game

Upcoming Events

No events to display

Who's Online

442s3, andi, mh1978muc, jem771, GeoffM, Person82, geswedey (7 users seen recently)

Timetables for chaining

You are here: Home > Forum > General > Timetabling > Timetables for chaining

Page 1 of 1

Timetables for chaining 28/02/2022 at 10:23 #145447
lukebriner
Avatar
56 posts 		I suspect that creating a timetable suitable for chaining can take a long time and involves extracting the correct parts from a master timetable for each sim.

What happens if you open a timetable e.g. in Wolverhampton, that contains locations that are beyond Wolverhampton like Birmingham NS or Coventry? Are they simply ignored once a train reaches Galton Junction?

In other words, would it be possible to use the same timeable in all the chained sims and allow the sims simply to ignore the locations they don't understand?

For example, if a working had WV dep 12:00, Galton Jn pass 12:15, BNS arr: 12:30 dep 12:35 etc. Coventry arr 13:00, would that entry work in Wolverhampton, BNS and Coventry sims, as long as it contained both the TIPLOC for exit points and the entry code for entries?

Just trying to work out if there is an easier way to split these timetables out of a large master timetable or just do it automatically in some way. I guess the elephant is that the entry code needs to be the EntryPoint for the timetable, not just another location so as long as the example above became something like:

===Wolverhampton TT=== ===BNS TT===
WV dep 12:00 GJ enters 12:15
GJ pass 12:15 BNS arr 12:30 etc.

Then it would be all OK. Hmmm
Log in to reply
Timetables for chaining 28/02/2022 at 16:42 #145456
Meld
Avatar
1111 posts 		Luke,

Below is a XML Schedule for 6D43 Jarrow Lindsey Oil tanks - this will import as part of a full schedule set or an individual schedule. So Tyneside, York NS & Doncaster North will all allocate the entry point at the correct location, so one schedule does all simulations. Hope his gives you a few ideas.


<?xml version="1.0" encoding="UTF-8"?>
<timetable>
<title>Export</title>
<description>Exported from the SimSig website on 28 February 2022 at 16:31:04</description>
<schedule scheduleID="H13913" trainID="6D43">
<trainCategory categoryID="2446">
<startDate>2014-12-22</startDate>
<endDate>2015-05-15</endDate>
<days>
<monday>true</monday>
<tuesday>true</tuesday>
<wednesday>true</wednesday>
<thursday>true</thursday>
<friday>true</friday>
</days>
</trainCategory>
<operatorID>ZZ</operatorID>
<operatorName>ZZ</operatorName>
<startDate>2014-12-22</startDate>
<endDate>2015-05-15</endDate>
<days>
<monday>true</monday>
<tuesday>true</tuesday>
<wednesday>true</wednesday>
<thursday>true</thursday>
<friday>true</friday>
</days>
<originName>Jarrow Shell</originName>
<originTime>15:45:00</originTime>
<destName>Lindsey Oil Refinery</destName>
<destTime>20:32:00</destTime>
<scheduleLocation>
<locationID>JARROWS</locationID>
<departureTime>15:45:00</departureTime>
<trainCategory categoryID="2446">
<startDate>2014-12-22</startDate>
<endDate>2015-05-15</endDate>
<days>
<monday>true</monday>
<tuesday>true</tuesday>
<wednesday>true</wednesday>
<thursday>true</thursday>
<friday>true</friday>
</days>
</trainCategory>
</scheduleLocation>
<scheduleLocation>
<locationID>PELAW</locationID>
<departureTime>16:00:00</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>PKLNJN</locationID>
<departureTime>16:04:00</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>GRNSFDJ</locationID>
<departureTime>16:06:00</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>KEBGEJN</locationID>
<departureTime>16:11:00</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>KEBGSJN</locationID>
<departureTime>16:12:00</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>LOWFELJ</locationID>
<departureTime>16:17:00</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>BRTLYJN</locationID>
<departureTime>16:21:00</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>DRHM</locationID>
<departureTime>16:31:00</departureTime>
<passingTime>true</passingTime>
<platformCode>1</platformCode>
</scheduleLocation>
<scheduleLocation>
<locationID>TURSDLJ</locationID>
<departureTime>16:40:00</departureTime>
<passingTime>true</passingTime>
<lineCode>SL</lineCode>
</scheduleLocation>
<scheduleLocation>
<locationID>FYHLSJN</locationID>
<departureTime>16:46:30</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>NORTONW</locationID>
<departureTime>17:05:30</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>NORTONS</locationID>
<departureTime>17:06:30</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>HRTBJN</locationID>
<departureTime>17:11:30</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>STOCCJN</locationID>
<departureTime>17:13:30</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>EGLSCLF</locationID>
<departureTime>17:15:30</departureTime>
<passingTime>true</passingTime>
<platformCode>1</platformCode>
</scheduleLocation>
<scheduleLocation>
<locationID>BOROBDR</locationID>
<departureTime>17:34:30</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>LNGLNDJ</locationID>
<departureTime>17:37:30</departureTime>
<passingTime>true</passingTime>
<lineCode>SL</lineCode>
</scheduleLocation>
<scheduleLocation>
<locationID>THIRSK</locationID>
<departureTime>17:44:30</departureTime>
<passingTime>true</passingTime>
<lineCode>SL</lineCode>
</scheduleLocation>
<scheduleLocation>
<locationID>TOLERTN</locationID>
<departureTime>17:57:30</departureTime>
<passingTime>true</passingTime>
<lineCode>SL</lineCode>
</scheduleLocation>
<scheduleLocation>
<locationID>SKELTNB</locationID>
<departureTime>18:06:30</departureTime>
<passingTime>true</passingTime>
<lineCode>SL</lineCode>
</scheduleLocation>
<scheduleLocation>
<locationID>SKELTON</locationID>
<departureTime>18:10:30</departureTime>
<passingTime>true</passingTime>
<lineCode>SL</lineCode>
</scheduleLocation>
<scheduleLocation>
<locationID>YORKYSJ</locationID>
<arrivalTime>18:15:00</arrivalTime>
<departureTime>18:31:00</departureTime>
<lineCode>LSL</lineCode>
</scheduleLocation>
<scheduleLocation>
<locationID>COLTONN</locationID>
<departureTime>18:41:30</departureTime>
<passingTime>true</passingTime>
<lineCode>NNL</lineCode>
</scheduleLocation>
<scheduleLocation>
<locationID>COLTONJ</locationID>
<departureTime>18:43:30</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>HAMBLNJ</locationID>
<departureTime>18:52:30</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>TEMPLHJ</locationID>
<departureTime>18:58:30</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>JNCROFT</locationID>
<departureTime>19:09:30</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>APLHRSJ</locationID>
<departureTime>19:12:30</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>TMSHJN</locationID>
<departureTime>19:13:30</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>HTFLASF</locationID>
<departureTime>19:21:30</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>THORNEJ</locationID>
<departureTime>19:23:30</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>CROWLE</locationID>
<departureTime>19:31:30</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>SCNTHRP</locationID>
<arrivalTime>19:50:00</arrivalTime>
<departureTime>19:52:00</departureTime>
<platformCode>1</platformCode>
</scheduleLocation>
<scheduleLocation>
<locationID>SCNTAPP</locationID>
<departureTime>19:59:00</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>ELSHAM</locationID>
<departureTime>20:04:00</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>WRAWBYJ</locationID>
<departureTime>20:07:00</departureTime>
<passingTime>true</passingTime>
<lineCode>FL</lineCode>
</scheduleLocation>
<scheduleLocation>
<locationID>BNTBY</locationID>
<departureTime>20:11:00</departureTime>
<passingTime>true</passingTime>
<platformCode>2</platformCode>
</scheduleLocation>
<scheduleLocation>
<locationID>BKBY</locationID>
<departureTime>20:17:00</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>ULCEBY</locationID>
<departureTime>20:22:00</departureTime>
<passingTime>true</passingTime>
</scheduleLocation>
<scheduleLocation>
<locationID>IMNGLOR</locationID>
<arrivalTime>20:32:00</arrivalTime>
</scheduleLocation>
</schedule>
</timetable>
Passed the age to be doing 'Spoon Feeding' !!!
Last edited: 28/02/2022 at 16:43 by Meld
Reason: None given
Log in to reply
The following user said thank you: lukebriner
Timetables for chaining 28/02/2022 at 17:31 #145458
headshot119
Avatar
4869 posts 		I'll use Sandhills as an example here. If you are talking about the .WTT format, then if a timetable contains an entry point of Dee Marsh Junction (EDMARSHJ) and the location Dee Marsh Junction (DMARSHJ) in that order you'll get a validation error of no path found between the entry point and first location.

Any locations the simulation doesn't recognise, are purged from the .WTT when saved from within the simulation. But you may get similar errors to the above example if you have locations in for which the simulation has no pathing data for whatever reason.
"Passengers for New Lane, should be seated in the rear coach of the train " - Opinions are my own and not those of my employer
Log in to reply
The following user said thank you: lukebriner
Timetables for chaining 28/02/2022 at 18:05 #145460
lukebriner
Avatar
56 posts 		I don't know if this is typical but I've just realised there is an overlap between the exit point of one sim and the entry point of the next.

For example, Wolverhampton exits at Galton Jn (GALTONJ) but the entry point for Birmingham New Street is Wolverhampton (EWOLV) and the same overlap in the other direction so it would only work if I could extract everything on an Up service up to and including Galton Jn for a WV timetable (ignoring the entry code EWOLV) but then extract everything from the EWOLV entry code through Galton Jn and south for Birmingham New Street.

Doable, I just need to think of the best way to do it and will look at the example above.

Thanks
Log in to reply
Timetables for chaining 28/02/2022 at 18:07 #145461
lukebriner
Avatar
56 posts 		So @meld are you saying I don't need to bother with the entry point at all and the individual sim will work that out from it's first location? I can't see an EntryPoint in the xml you posted.
Log in to reply
Timetables for chaining 28/02/2022 at 18:13 #145463
headshot119
Avatar
4869 posts 		lukebriner in post 145460 said:
I don't know if this is typical but I've just realised there is an overlap between the exit point of one sim and the entry point of the next.

For example, Wolverhampton exits at Galton Jn (GALTONJ) but the entry point for Birmingham New Street is Wolverhampton (EWOLV) and the same overlap in the other direction so it would only work if I could extract everything on an Up service up to and including Galton Jn for a WV timetable (ignoring the entry code EWOLV) but then extract everything from the EWOLV entry code through Galton Jn and south for Birmingham New Street.

Doable, I just need to think of the best way to do it and will look at the example above.

Thanks
It's typical, generally a simulation will extend to the next mandatory timing point outside of it's area of control and use that as the entry point, there are however exceptions where for various reasons the extension is further than that.

lukebriner in post 145461 said:
So @meld are you saying I don't need to bother with the entry point at all and the individual sim will work that out from it's first location? I can't see an EntryPoint in the xml you posted.
What Meld has posted is a schedule in a format which allows the simulation to import and decide exactly what it needs to do with it, this is how the majority of the "ground hog" day timetables are made initially, with tidying up then being done within the simulation itself. I don't know if the format is documented anywhere public facing at the moment.
"Passengers for New Lane, should be seated in the rear coach of the train " - Opinions are my own and not those of my employer
Log in to reply
The following user said thank you: lukebriner
Back