Skip to Content

Changes for page Documentation

Last modified by Soeren Domroes on 2025/01/30 12:05
From version 16.1
edited by krat
on 2014/06/18 15:19
Change comment: There is no comment for this version
To version 12.1
edited by sna
on 2014/06/17 23:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.krat
1 +XWiki.sna
Content
... ... @@ -117,8 +117,6 @@
117 117  
118 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 -Contact reading in triggers should only used when it is clearly determined which train will fire the contact.
121 -
122 122  === TrainController ===
123 123  
124 124  Train-Schedules should be modelled by putting together the Station-to-Station-Controllers for every train in individual regions.
... ... @@ -126,7 +126,7 @@
126 126  === Speed: ===
127 127  
128 128  * SLOW: for the stations
129 -* CAUTION: for slowdown (and optional points)
127 +* CAUTION: for points and slowdown
130 130  * NORMAL: for the other tracks
131 131  
132 132  == Codestyle ==
... ... @@ -139,41 +139,8 @@
139 139  bool <track>_req[<trainAmount>] contains the requests for each track and train. Before the availability of arrays, we used bool <train>_<track>_req.
140 140  int <track>_perm contains the trainnumber of the train, who is allowed to drive on <track>.
141 141  
142 -== Deadlock Prevention ==
140 +== Quit, Pause and Cleanup ==
143 143  
144 -An example controller for deadlock prevention is located in// rail-repo: docs/deadlocks/resolve_deadlock.sct//
145 -
146 -Sidings should only be used in one direction.
147 -
148 -Trains trying to leave a station in order to use KIO_LN_0 or KIO_LN_1 should, if they do not receive the locks for all segments, release them for two ticks.
149 -
150 -= C Controller =
151 -
152 -The C controller wraps the basic railway interface and creates an correct environment to run the generated controller.
153 -
154 -== Make Script ==
155 -
156 -A make script written in Python is located in rail-repo: code/make.py
157 -
158 -This script will compiel the whole controller for simulation or real railway and optionally executes it.//
159 -//
160 -
161 -Calling**// python// //make.py//** without further command-line arguments will print a help message with all available command line options.
162 -
163 -Make Script Features:
164 -
165 -* Header-file will be included automatically
166 -
167 -Results are located in //rail-repo: code/build///
168 -
169 -== Railway Interface ==
170 -
171 -Provided functions are defined in// rail-repo: code/hostcode/controller.h//
172 -
173 -== Interaction ==
174 -
175 -=== Quit, Pause and Cleanup ===
176 -
177 177  Quit, pause and cleanup functionality is handled in the c interface.
178 178  
179 179  **CTRL+C** (SIGINT)** **quits the controller
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -9471043
1 +9470997
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/SS14Railway/pages/9471043/Documentation
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/SS14Railway/pages/9470997/Documentation