Random restart delays in timetable mode
This blueprint proposes to introduce random restart delays in timetable mode.
Presently, trains which are stopped, e.g. for signal at danger, station stop, reversal move etc. immediately restart if the stop condition is lifted, e.g. when the signal clears.
This is not realistic, for in real life there is always some delay as the driver needs time to react. This can vary from a few seconds after a signal is cleared, to the time required by the driver to walk along the length of the train in case of a reversal.
It is proposed to introduce a random restart delay to trains in such situations.
Different values can be set for the different situations, e.g. on signal stop, station stop, attach/detach action etc.
Each delay consists of a fixed part and a random part. The random values are taken from a set of values between 0 and the defined value using lineair distribution. The overall delay is therefor a value between the brackets [fixed_value] and [fixed_value + random_value], with a lineair distribution.
In case of reversal action, an additional value is added to this delay. This value is defined as delaytime per meter, and is calculated using the length of the train. This represents the time required by the driver to walk from one end of the train to the other. In this case, the total delay will therefor be a value between the brackets [fixed_
All delays are set to a default value but can be set to a specific value per train.
A future extention may be that these values can be set as user option or, preferably, be included in specific route settings.
Discussion: http://
Roadmap: https:/
Blueprint information
- Status:
- Complete
- Approver:
- James Ross
- Priority:
- Medium
- Drafter:
- r.roeterdink
- Direction:
- Approved
- Assignee:
- r.roeterdink
- Definition:
- Approved
- Series goal:
- None
- Implementation:
- Implemented
- Milestone target:
- 1.3
- Started by
- r.roeterdink
- Completed by
- James Ross
Related branches
Related bugs
Sprints
Whiteboard
Implemented in X3863.