This shows you the differences between two versions of the page.
|
basic_simconstruct [2010/07/31 04:09] uktrainman til/till replaced with until plus some minor grammatical corrections |
basic_simconstruct [2010/07/31 10:23] (current) peter-test |
||
|---|---|---|---|
| Line 38: | Line 38: | ||
| As well as being coded to the ‘official’ ULC covering the location it is possible to code any location to any ULC and that enables diverted trains to be ticked off as they pass. | As well as being coded to the ‘official’ ULC covering the location it is possible to code any location to any ULC and that enables diverted trains to be ticked off as they pass. | ||
| The LOC file contains all the locations, with their name, which ULC they can be found and where appropriate the stopping point within a ULC. If a location is a KEY location then it must be in the PTH file where all the paths between key locations are mapped out. Non key locations can be used anywhere in a timetable, though in the wrong place is not recommended. | The LOC file contains all the locations, with their name, which ULC they can be found and where appropriate the stopping point within a ULC. If a location is a KEY location then it must be in the PTH file where all the paths between key locations are mapped out. Non key locations can be used anywhere in a timetable, though in the wrong place is not recommended. | ||
| - | |||
| ====== PTH ====== | ====== PTH ====== | ||
| The path file contains the map of all linked key locations and at its simplest allows trains to be timetabled from entry to exit by setting out the start LOC / end LOC and the respective Up/Down direction at each. | The path file contains the map of all linked key locations and at its simplest allows trains to be timetabled from entry to exit by setting out the start LOC / end LOC and the respective Up/Down direction at each. | ||
| Eg. ENT1 to LOC1; LOC1 to LOC 2 and LOC3; LOC2 to LOC10, LOC 3 to LOC 8 and 12 and so on. Timetables can only be written if the sequence of key locations is recognised by the PTH file. | Eg. ENT1 to LOC1; LOC1 to LOC 2 and LOC3; LOC2 to LOC10, LOC 3 to LOC 8 and 12 and so on. Timetables can only be written if the sequence of key locations is recognised by the PTH file. | ||
| With ARS sims it becomes far more complicated as each possible PTH between LOCs needs to be spelt out in fine detail. | With ARS sims it becomes far more complicated as each possible PTH between LOCs needs to be spelt out in fine detail. | ||
| + | ====== INS ====== | ||
| + | It is possible to automatically insert key locations to timetables, primarily used for ARS sims but can be used in others. This is handy where the locations is not a mandatory timing point and saves working out a time. The time is set by applying a factor to the known times at the previous and subsequent location. If there are engineering or pathing allowances in the area the result has been known to be a bit off. | ||
| ====== ARS ====== | ====== ARS ====== | ||
| ARS Sims need two things, an ARS sub-area and a detailed PTH as mentioned above. | ARS Sims need two things, an ARS sub-area and a detailed PTH as mentioned above. | ||