Skip to Content

Changes for page Documentation

Last modified by Soeren Domroes on 2025/01/30 12:05
From version 14.1
edited by Alexander Schulz-Rosengarten
on 2014/06/18 13:11
Change comment: There is no comment for this version
To version 11.1
edited by sna
on 2014/06/17 23:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.als
1 +XWiki.sna
Content
... ... @@ -113,10 +113,12 @@
113 113  
114 114  === Station-to-Station ===
115 115  
116 -Fuctions **void railArrival(int train, int station)** and **int railDeparture(int train)** should be used at the end of every Station-to-Station-Controller.
116 +Fuctions $void railArrival(int train, int station)$ and $int railDeparture(int train)$ should be used at the end of every Station-to-Station-Controller.
117 117  
118 -At the end of every Station-to-Station-Controller the trains should stand in one station, because every controller starts with the train in standstill.
118 +At the end of every Station-to-Station-Controller the trains should stand in one station, because every Controller starts with the train in standstill.
119 119  
120 +
121 +
120 120  === TrainController ===
121 121  
122 122  Train-Schedules should be modelled by putting together the Station-to-Station-Controllers for every train in individual regions.
... ... @@ -123,8 +123,10 @@
123 123  
124 124  === Speed: ===
125 125  
128 +
129 +
126 126  * SLOW: for the stations
127 -* CAUTION: for slowdown (and optional points)
131 +* CAUTION: for points and slowdown
128 128  * NORMAL: for the other tracks
129 129  
130 130  == Codestyle ==
... ... @@ -137,33 +137,8 @@
137 137  bool <track>_req[<trainAmount>] contains the requests for each track and train. Before the availability of arrays, we used bool <train>_<track>_req.
138 138  int <track>_perm contains the trainnumber of the train, who is allowed to drive on <track>.
139 139  
140 -= C Controller =
144 +== Quit, Pause and Cleanup ==
141 141  
142 -The C controller wraps the basic railway interface and creates an correct environment to run the generated controller.
143 -
144 -== Make Script ==
145 -
146 -A make script written in Python is located in rail-repo: code/make.py
147 -
148 -This script will compiel the whole controller for simulation or real railway and optionally executes it.//
149 -//
150 -
151 -Calling**// python// //make.py//** without further command-line arguments will print a help message with all available command line options.
152 -
153 -Make Script Features:
154 -
155 -* Header-file will be included automatically
156 -
157 -Results are located in //rail-repo: code/build///
158 -
159 -== Railway Interface ==
160 -
161 -Provided functions are defined in// rail-repo: code/hostcode/controller.h//
162 -
163 -== Interaction ==
164 -
165 -=== Quit, Pause and Cleanup ===
166 -
167 167  Quit, pause and cleanup functionality is handled in the c interface.
168 168  
169 169  **CTRL+C** (SIGINT)** **quits the controller
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -9471001
1 +9470996
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/SS14Railway/pages/9471001/Documentation
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/SS14Railway/pages/9470996/Documentation