Skip to Content

Changes for page Interfaces and Rulesets

Last modified by cbu on 2025/01/30 12:05
From version 5.1
edited by nbw
on 2014/06/27 07:41
Change comment: There is no comment for this version
To version 9.1
edited by krat
on 2014/08/11 11:24
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.nbw
1 +XWiki.krat
Content
... ... @@ -9,8 +9,8 @@
9 9  * Each train has a trainnumber.\\
10 10  ** Apart from identification the trainnumber is used for prioritization, when multiple trains compete for the same track.
11 11  ** Lower numbers mean higher priorities, e.g. train 0 has the highest priority.
12 -** Priorities can't be changed dynamicly.
13 -* Each train has one home-track at each station.
12 +** Priorities can't be changed dynamically.
13 +* Each train has one home-track.
14 14  * For binding purposes the variable should have the name **trainNum**.
15 15  
16 16  The numbering is derived from the initial positions of the trains.
... ... @@ -78,7 +78,7 @@
78 78  
79 79  === Tracks ===
80 80  
81 -* Stopping on tracks without contacts is permitted.
81 +* Stopping on tracks without contacts is **not** allowed!
82 82  * Tracks without contacts must be reserved and used with an adjacent "safe" track.
83 83  * When requesting multiple locks, deadlocks must be prevented
84 84  * Three different speed settings are available, adjusted to the individual trains:
... ... @@ -132,6 +132,7 @@
132 132  )))
133 133  
134 134  * If the preferred station track is blocked the trains can switch to any other free track.
135 +While **cleanup** is active the trains on IC_ST_1, OC_ST_3 or KH_ST_1 circle until all tracks are done.
135 135  
136 136  == Rulesets ==
137 137  
... ... @@ -151,7 +151,7 @@
151 151  
152 152  === Deadlock Prevention ===
153 153  
154 -* When attempting to reserve more than one segment (Entering a station, passing a junction) a separate protocol for deadlock prevention must be adhered to.
155 +* When attempting to reserve more than one segment (entering a station, passing a junction) a separate protocol for deadlock prevention must be adhered to.
155 155  * In each tick the controller must check if only partial permissions were granted.
156 156  * If partial permission was granted the train waits for one tick and releases all locks.
157 157  * In the following tick the locks are requested again.
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -9471287
1 +9471680
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/SS14Railway/pages/9471287/Interfaces and Rulesets
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/SS14Railway/pages/9471680/Interfaces and Rulesets