User Tools

Site Tools


locations-details-en

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
locations-details-en [2021/11/07 13:09] – [Locations Details] smitt48locations-details-en [2024/01/22 11:26] (current) – [Requirements] rjversluis
Line 5: Line 5:
 // \\ // \\ // \\ // \\
  
-{{:location-details-en.png?750}}\\+{{:location-details-en.png?801}}\\ 
  
  \\  \\
 +===== Prioritization =====
 +Normal or blocklist selection.\\
 +See: __**[[:rocrailini-automode-en#location_prioritization|Location prioritization]]**__ \\
  
 + \\
 ===== Flow management ===== ===== Flow management =====
 The flow management of a location controls outgoing trains and is very well suited to manage hidden yards: The minimal occupancy grants the yard remains partly filled while the Fifo option allows the trains to exit alternately. The flow management of a location controls outgoing trains and is very well suited to manage hidden yards: The minimal occupancy grants the yard remains partly filled while the Fifo option allows the trains to exit alternately.
Line 16: Line 21:
   * The block type should be set to **Others** (see **[[:block-details-en|Block Details]]**).   * The block type should be set to **Others** (see **[[:block-details-en|Block Details]]**).
   * The __**[[:block-gen-en#mainline|Mainline]]**__ Block option must be disabled. :!:   * The __**[[:block-gen-en#mainline|Mainline]]**__ Block option must be disabled. :!:
 +  * All blocks must have the same orientation for some flow options.
  
  
Line 38: Line 44:
  
   * Schedules may be used together with flow management. However, the **[[:schedules-dest-en#time_processing|Time Processing]]** of the respective schedule should be set to **Relative** as the flow management takes priority over the schedule's departure times.   * Schedules may be used together with flow management. However, the **[[:schedules-dest-en#time_processing|Time Processing]]** of the respective schedule should be set to **Relative** as the flow management takes priority over the schedule's departure times.
-  * If a train has already received the exit permit, but has not yet left the block, he is no longer counted in the minimum occupation. \\ Even if only because the minimum occupation of the location seemingly - would be given no other train can drive out.+  * If a train has already received the exit permit, but has not yet left the block, it is no longer counted in the minimum occupation. \\ If this is the only reason why the minimum occupation of the locality apparently - would still be givenno other train can leave.
  
  
Line 73: Line 79:
 Set the maximal occupancy in the location if it needs some free blocks to move trains without deadlocking. A value of zero disables the maximal occupied option.\\ Set the maximal occupancy in the location if it needs some free blocks to move trains without deadlocking. A value of zero disables the maximal occupied option.\\
 This option can be specified for both enter sides.\\ This option can be specified for both enter sides.\\
-The Number of Commuter trains plus Others should be set equal to the total. No train can enter this location if both are set to zero.\\+The Number of Commuter trains plus Others**(("Other" here does not mean the type, but __all other types, except commuter trains__))** should be set equal to the total.\\
 ====Commuter train==== ====Commuter train====
 Maximal number of commuter trains in this location. (Independent of the enter side)\\ Maximal number of commuter trains in this location. (Independent of the enter side)\\
Line 97: Line 103:
 In case of actions the __**[[:text-gen-en#variables|%callertext%]]**__ variable will be set with plain ASCII or HTML.\\ In case of actions the __**[[:text-gen-en#variables|%callertext%]]**__ variable will be set with plain ASCII or HTML.\\
  
-> Tip: See the __**[[:users:nice2have:iot-fahrplananzeiger-de|User page of Gerrit for a Node-RED implementation]]**__. (DE)\\ {{:users:nice2have:iot-fpa.jpg?300}}\\+> Tip: See the __**[[:userpages:nice2have:iot-fahrplananzeiger-de|User page of Gerrit for a Node-RED implementation]]**__. (DE)\\ {{:users:nice2have:iot-fpa.jpg?300}}\\
  
 ====Publish==== ====Publish====
locations-details-en.1636286955.txt.gz · Last modified: 2021/11/07 13:09 by smitt48