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 5.1
edited by nfl
on 2014/06/14 22:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.krat
1 +XWiki.nfl
Content
... ... @@ -86,7 +86,7 @@
86 86  |=(((
87 87  station
88 88  )))|=(((
89 -drive-through track
89 +track
90 90  )))
91 91  |(((
92 92  IC_station
... ... @@ -111,77 +111,12 @@
111 111  KH_ST_1
112 112  )))
113 113  
114 -=== Station-to-Station ===
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.
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.
119 -
120 -Contact reading in triggers should only used when it is clearly determined which train will fire the contact.
121 -
122 -=== TrainController ===
123 -
124 -Train-Schedules should be modelled by putting together the Station-to-Station-Controllers for every train in individual regions.
125 -
126 -=== Speed: ===
127 -
128 -* SLOW: for the stations
129 -* CAUTION: for slowdown (and optional points)
130 -* NORMAL: for the other tracks
131 -
132 132  == Codestyle ==
133 133  
134 134  Use entry-/exit-actions instead of actions on transitions, if possible.
135 -If using hostcode, only use functions delivered by our own C-Interface and not the Höhrmann-API.
117 +If using hostcode, only use functions delivered by our own C-Interface.
136 136  
137 137  == Mutual Exclusion ==
138 138  
139 -bool <track>_req[<trainAmount>] contains the requests for each track and train. Before the availability of arrays, we used bool <train>_<track>_req.
121 +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 -
142 -== Deadlock Prevention ==
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 -Quit, pause and cleanup functionality is handled in the c interface.
178 -
179 -**CTRL+C** (SIGINT)** **quits the controller
180 -
181 -**CTRL+\** (SIGQUIT)** **cleans up
182 -
183 -**CTRL+Z **(SIGSTP) pauses and continues
184 -
185 -
186 -
187 -
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -9471043
1 +9470977
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/9470977/Documentation