User Tools

Site Tools


analyzer-en

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
analyzer-en [2019/03/09 22:17]
rainerk
analyzer-en [2019/04/22 01:50] (current)
rainerk [Limitations]
Line 104: Line 104:
 |< >| |< >|
 ^  Important change from Rev. 15.164+ ​ ^ ^  Important change from Rev. 15.164+ ​ ^
-|  :!: It must always be clearly formed with **0...65535**((=16bit value)) numbered connector pairs.\\ The previously possible use of the numbers **0...9** for multiple connector pairs leads to the termination of the Analyzer run. \\ The orthogonal positioning and mutually facing cut surfaces of both symbols are no longer considered.\\ **So that the track plan for the analyzer is "​healthy"​ \\ and previous pairings remain valid in the future, the "​old"​ connector pairs 0...9 \\ must be changed into a unique numbering for all levels in the entire track plan.** ​ |+|  :!: It must always be clearly formed with **0...65535**((=16bit value)) numbered connector pairs.\\ The previously possible use of the numbers **0...9** for multiple connector pairs leads to the termination of the Analyzer run. \\ The orthogonal positioning and mutually facing cut surfaces of both symbols are no longer considered. ​\\ This includes divided bridge element (tracknr 2). {{symbols:​track-2.png?​20}} ​\\ **So that the track plan for the analyzer is "​healthy"​ \\ and previous pairings remain valid in the future, the "​old"​ connector pairs 0...9 \\ must be changed into a unique numbering for all levels in the entire track plan.** ​ |
 ====Why connectors ?==== ====Why connectors ?====
 Connectors can be used to connect distant elements: The analyser is seeking for a counterpart (second connector) in the same direction and ignores gaps and elements between these two.\\ ​ Connectors can be used to connect distant elements: The analyser is seeking for a counterpart (second connector) in the same direction and ignores gaps and elements between these two.\\ ​
Line 113: Line 113:
 | \\ || | \\ ||
 ^ Connectors illustrating a bridge ^^ ^ Connectors illustrating a bridge ^^
-|  {{:​analyzer:​bridge.png}} ​\\ {{:​analyzer:​bridge-connector-example.png}}  ​|  {{:​analyzer:​bridge-crossing-example.png}} ​ | +|  {{:​analyzer:​bridge.png}} |  {{:​analyzer:​bridge-crossing-example.png}} ​ | 
-|  Bridge with two connectors \\ Top with track type "​connector" ​\\ Below with track type "​tracknr"​ = **2**  ​|  Bridge with one symbol of track type "​tracknr"​ = **3** \\ Thus the analyzer is able to recognize and generate the possible routes A- < > B+ und C- < > D+  |+|  Bridge with two connectors \\ with track type "​connector"​ |  Bridge with one symbol of track type "​tracknr"​ = **3** \\ Thus the analyzer is able to recognize and generate the possible routes A- < > B+ und C- < > D+  |
 \\ \\
-  * Connectors configured with **[[tracks-gen-en#​number|a track number]]** between **0** and **99** must have one corresponding connector with the same  number anywhere in the plan. The direction of the counterpart doesn'​t matter. The counterpart may be on a different track plan level.\\+  * Connectors configured with **[[tracks-gen-en#​number|a track number]]** between **0** and **65535** must have one corresponding connector with the same  number anywhere in the plan. The direction of the counterpart doesn'​t matter. The counterpart may be on a different track plan level.\\
  \\  \\
  
 ==== Avoid connectors on module plans ==== ==== Avoid connectors on module plans ====
-With module plans, connectors can be used at the module transitions when paired are defined with the **same** number in the range **0...99**.+With module plans, connectors can be used at the module transitions when paired are defined with the **same** number in the range **0...65535**.
  
 **Disadvantages:​**\\ **Disadvantages:​**\\
-Connectors at the module transition without a partner with the same number ​in the range **0...99** ​the analyzer reports as error. \\ +Connectors at the module transition without a partner with the same number the analyzer reports as error. \\ 
-If the module layout is set up in a different compilation,​ affected connector pairs with numbers in the range **0...99** ​must be adapted. \\ +If the module layout is set up in a different compilation, ​the numbering of affected connector pairs must be adapted. \\ 
-If in the compilation two connectors with the same number ​in the range **0...99** ​are forgotten somewhere, "​strange"​ routes can arise.+If in the compilation two connectors with the same number are forgotten somewhere, "​strange"​ routes can arise.
  
 **Recommendation:​**\\ **Recommendation:​**\\
Line 151: Line 151:
   * Roads are not supported.   * Roads are not supported.
   * Only a few objects of the **[[switch-gen-en#​accessory|Switch type "​Accessory"​]]** and the **[[tracks-gen-en#​type|Track typ "​tracknr"​]]** are recognized:   * Only a few objects of the **[[switch-gen-en#​accessory|Switch type "​Accessory"​]]** and the **[[tracks-gen-en#​type|Track typ "​tracknr"​]]** are recognized:
-\\ + 
-^Switch Type "​Accessory"​^^ +|< >| 
-^Accessory#​^Description^+ Switch Type "​Accessory" ​ ^^ 
 + Accessory# ​ ^Description^
 |  1  | double track railroad crossing, obsolete | |  1  | double track railroad crossing, obsolete |
 |  10  | single track railroad crossing, ungated| ​ |  10  | single track railroad crossing, ungated| ​
Line 161: Line 162:
 |  41  | single track flap bridge | |  41  | single track flap bridge |
 | || | ||
-^Track Typ "​tracknr"​^^ + Track Typ "​tracknr" ​ ^^ 
-^Number^Description^ + Number ​ ^Description^
-|  2  | bridge connector |+
 |  3  | bridge crossing | |  3  | bridge crossing |
-\\ 
 Other accessory or track numbers are __not supported__ . It doesn'​t know the various grid sizes and orientations of these symbols. Therefore, before starting the analyser these objects should be replaced __temporarily__ (and possibly later again) with normal track objects. \\ Other accessory or track numbers are __not supported__ . It doesn'​t know the various grid sizes and orientations of these symbols. Therefore, before starting the analyser these objects should be replaced __temporarily__ (and possibly later again) with normal track objects. \\
 > **Note:** Do not use two or more double track items consecutively. The Analyser will generate some wrong routes :!: > **Note:** Do not use two or more double track items consecutively. The Analyser will generate some wrong routes :!:
analyzer-en.1552166245.txt.gz · Last modified: 2019/03/09 22:17 by rainerk