Scenario-defined trains: Difference between revisions

From SignalWiki
Jump to navigation Jump to search
No edit summary
Line 24: Line 24:
   4: Call
   4: Call
   5: ChangeDriver
   5: ChangeDriver
  6: SpotCars
   7: PullUp
   7: SpotCarsSpecify
   8: StopShort
   8: StableCars
   9: StopAhead
   9: PullUp
  10: SwitchLock
  10: StopShort
13: StableCars
  11: StopAhead
14: SpotCars
  12: SwitchLock
  ??: SpotCarsSpecify
  16: unknown - functional in Amsterdam CS simulation
  17: RunAround
  17: RunAround
  18: ContentChanges
  18: ContentChanges


{{ScenariosNav}}
{{ScenariosNav}}

Revision as of 18:56, 2 July 2011

It is possible to create a scenario that does not have any trains, either existing in the yard, or in the timetable. Trains can be created (spawned) at the boundaries of the yard from the timetable, and optionally, from an explicit definition. Additionally, trains can be placed at precise locations in the yard. All scenario-defined trains, either spawning or stabled, are defined within a set of Consists tags:

 <Scenario app="ProductName" description="MyScenario" startDate="1965-01-01" startTime="00:00:00" >
    <Consists loadFromTimetable="true">
        <!-- scenario-defined trains go here -->
    </Consists>
 </Scenario>

To load trains from the timetable defined for this scenario, set the mandatory attribute loadFromTimetable to true. To specify a scenario with no timetable trains, set loadFromTimetable to false.

Defining spawning trains

Defining stabled trains

Movement orders

You can define movement orders for each scenario-defined train, either a spawning train or stabled train The following types of Movement Orders are available:

 0: Renumber
 1: Turnaround
 2: Couple
 3: Uncouple
 4: Call
 5: ChangeDriver
 7: PullUp
 8: StopShort
 9: StopAhead
10: SwitchLock
13: StableCars
14: SpotCars
??: SpotCarsSpecify
16: unknown - functional in Amsterdam CS simulation
17: RunAround
18: ContentChanges



Return to Scenario Creation