Hi All Timetablers and running to Schedulers
I offer a friendly challenge to implement a timetable for the running of trains to a prepared schedule.
There has been some discussion about what can and can't be done using the various time and portal rules. Why don't we pool our efforts to help ourselves and other members of the community understand these various options?
With your agreement and guidance I propose to design a simple route and a simple schedule, post the route on the DLS, then let each person design a scenario/session that implements the schedule using whatever method they wish. They would post this to the DLS, suitably documented if required, so everyone could understand and experience the joys and pitfalls of timetabling using TRS2006.
I propose the following:
Segy
My initial list of timetable schedule features, please suggest others:
========================================================================================================
Here is my first suggestion for a route. This is schematic of course and covers 3 x 1 boards
TM--TM--TM--TM--TM--TM--TM-\
...............................................\
------Portal.Basic------------------\....................................................../---TM--TM--TM--TM--TM--TM--TM---
...................................................\.............../--Platform2--\.............../
------Portal--------------------------\---\-/---/---------------\............/-----Portal.Basic-----------------
...........................................................x.............................\........./
------Portal--------------------------/---/-\---\----Platform.1----\----/-------Portal-----------------------
.................................................../...............\
------Portal.Basic------------------/..................\-----------------\
................................................/....................\-Multiple.Industry-\---
TM--TM--TM--TM--TM--TM--TM-/
--TM--TR--TM--TR--TM--TR--------- Separate timing track ----TM--TR--TM--TR--TM--TR-------------
Please read . (periods) as spaces - the forum wont allow me to put in leading spaces, nor to use a fixed width font on an edit
1. I have kept it relatively simple although there are plenty scenarios where contention for a path may arise
2. If your timetabling method of creating trains requires other facilities please let me know
3. There will be lots of other track marks and triggers, if your method requires these to be in specific locations please let me know
4. I propose that signaling will be 'route setting' configuration for simplicity
5. Only built-in content used for route
6. Clone the base scenario then use whatever rules you need for your scenario/session
7. Use only built-in vehicles
I offer a friendly challenge to implement a timetable for the running of trains to a prepared schedule.
There has been some discussion about what can and can't be done using the various time and portal rules. Why don't we pool our efforts to help ourselves and other members of the community understand these various options?
With your agreement and guidance I propose to design a simple route and a simple schedule, post the route on the DLS, then let each person design a scenario/session that implements the schedule using whatever method they wish. They would post this to the DLS, suitably documented if required, so everyone could understand and experience the joys and pitfalls of timetabling using TRS2006.
I propose the following:
- I would design a simple route (or someone could donate/suggest one ) with a few junctions/switches, portals at the extremities, lots of trackmarks for the unportal users, a separate track for trigger users etc. This would be posted on the DLS.
- Suggestions for design of route to be posted by end of September 30.
- Suggestions for design of schedule to be posted by end of September 30.
- No more than one industry (if any) and 2 platforms.
- Scenic simplicity
- All communications through this thread
- Schedule to involve train arrival, departure, locomotive change, shunting, random delays and any other element suggested before September 30
- For TRS2006 SP1 only!
- Possibly one user controlled train, all others to be controlled by the timetabling system
- A plus point of your timetable proposals would be whether the session could be saved and restarted correctly at any time
Segy
My initial list of timetable schedule features, please suggest others:
- Passenger train arrives at station at specific time
- Passenger train loads at station, waits until a specific time of day until departing
- Passenger train arrives at station, waits for a specific elapsed time until departing
- Train held at signals, or in other location until another train has completed a movement
- Train enters route at specific time
- At least 10 trains are scheduled
- Loco detaches from train, another couples, journey proceeds - all at specific times of day
- Allowance for user controlled train throughout
- Allow user to take over a train already running to a schedule, drive it, then relinquish control back to schedule
- 8.00 Train1 arrives platform1 from north(up)
- 8.01 Train2 arrives platform2 from south (down)
- 8.02 Train1 departs to south
- 8.03 Train3 through from north to south
- 8.04 Train2 departs to north
- etc
========================================================================================================
Here is my first suggestion for a route. This is schematic of course and covers 3 x 1 boards
TM--TM--TM--TM--TM--TM--TM-\
...............................................\
------Portal.Basic------------------\....................................................../---TM--TM--TM--TM--TM--TM--TM---
...................................................\.............../--Platform2--\.............../
------Portal--------------------------\---\-/---/---------------\............/-----Portal.Basic-----------------
...........................................................x.............................\........./
------Portal--------------------------/---/-\---\----Platform.1----\----/-------Portal-----------------------
.................................................../...............\
------Portal.Basic------------------/..................\-----------------\
................................................/....................\-Multiple.Industry-\---
TM--TM--TM--TM--TM--TM--TM-/
--TM--TR--TM--TR--TM--TR--------- Separate timing track ----TM--TR--TM--TR--TM--TR-------------
Please read . (periods) as spaces - the forum wont allow me to put in leading spaces, nor to use a fixed width font on an edit
1. I have kept it relatively simple although there are plenty scenarios where contention for a path may arise
2. If your timetabling method of creating trains requires other facilities please let me know
3. There will be lots of other track marks and triggers, if your method requires these to be in specific locations please let me know
4. I propose that signaling will be 'route setting' configuration for simplicity
5. Only built-in content used for route
6. Clone the base scenario then use whatever rules you need for your scenario/session
7. Use only built-in vehicles
Last edited: