Signal Failures
Jump to navigation
Jump to search
Contents | Developers pages | Command Line Options | Timetables | Scenario Creation | Developing Installers
Signals that use incandescent light bulbs to display an aspect can suffer failures. The lamps often have two filaments for redundancy. When one of these filaments is broken, the second filament takes over. Scenarios can be written to specify when and how signals can become defective.
All signal failure tags are enclosed within the Irregularities tags. Each signal failure is defined like the following:
<Irregularities>
<SignalFailure signal="12" aspect="STOP" canRepair="false" defectType="EXTINGUISHED" />
</Irregularities>
The attributes for each signal failure are as follows:
- signal
- name of the signal
- aspect
- either STOP or CLEAR
- defines which aspect cannot be properly displayed
- defectType
- either EXTINGUISHED or BROKENFILAMENT
- defines the type of failure
- EXTINGUISHED: all filaments are broken (light is completely off)
- BROKENFILAMENT: only one filament is broken, and relying on at least one redundant filament
- canRepair
- (optional)
- either true or false (true by default)
- indicates whether a signal can be repaired (it should be false when using startTime and endTime)
- startTime
- (optional)
- time (HH:mm:ss)
- when omitted, there is no lower bound (that is, signal failures can occur as soon as simulation starts)
- endTime
- (optional)
- time (HH:mm:ss)
- when omitted, there is no upper bound (that is, signal failures can occur right to the end of the simulation, however long that may be)
- afterOccurrence
- (optional)
- either true or false (true by default)
- true: signal fails at the moment the signal changes aspect
- false: signal fails at the time specified by the startTime attribute and is repaired at the time specified by the endTime attribute
Contents | Developers pages | Command Line Options | Timetables | Scenario Creation | Developing Installers