User Tools

Site Tools


analyzer-en

Differences

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

Link to this comparison view

Next revision
Previous revision
analyzer-en [2018/11/12 08:56]
127.0.0.1 external edit
analyzer-en [2019/03/09 22:17] (current)
rainerk
Line 15: Line 15:
 ^Analyzer Route name changed^ ^Analyzer Route name changed^
 |:!: From Rev. 12.859+ is the "​**autogen-**"​-prefix (see below) by the option __**[[route-gen-en#​automatically_generated|Automatically generated]]**__ replaced. \\ For routes, which still contain the leading "​autogen",​ this will be removed during the next analyzer run and replaced by the new option. \\ In addition, "​Generated by the analyzer"​ is entered in the '​Description'​ field. \\ In the dialog __**[[route-index-en|Route:​ General]]**__ a leading "** * **" in the "​Description"​ column shows the activated option '​Automatically generated'​. \\ In the examples down on this page the changes did executed. | |:!: From Rev. 12.859+ is the "​**autogen-**"​-prefix (see below) by the option __**[[route-gen-en#​automatically_generated|Automatically generated]]**__ replaced. \\ For routes, which still contain the leading "​autogen",​ this will be removed during the next analyzer run and replaced by the new option. \\ In addition, "​Generated by the analyzer"​ is entered in the '​Description'​ field. \\ In the dialog __**[[route-index-en|Route:​ General]]**__ a leading "** * **" in the "​Description"​ column shows the activated option '​Automatically generated'​. \\ In the examples down on this page the changes did executed. |
 +Another important change: See __**[[#​connector|Connector]]**__ 
 + \\
  \\  \\
  
Line 100: Line 101:
  \\  \\
  
-==== Connector ===+===== Connector ​===== 
 +|< >| 
 +^  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.** ​ | 
 +====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.\\ ​
 +With connectors it's easy to connect different levels on the layout. \\
  
 ^ Examples for connectors \\ Avoiding track elements without function ^^ ^ Examples for connectors \\ Avoiding track elements without function ^^
Line 110: Line 116:
 |  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 \\ 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+  |
 \\ \\
-  ​* The maximum distance between corresponding connectors is unlimited \\ +  * 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 on the same track plan level where the orientation is in the way shown in the above example and the connectors face each other are handled as counterparts (Exception below)\\ +
-  ​* Connectors configured with **[[tracks-gen-en#​number|a track number]]** between ​10 and 99 must have one corresponding connector with the same track 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 ​\\ +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 **any** (also different) ​number in the range **0 - 9** opposite each other.. +
-or\\ +
-  * are defined with **the same** number in the range **10 - 99**.+
  
 **Disadvantages:​**\\ **Disadvantages:​**\\
-If a connector with a number in the range **0 - 9** has no partner at the transition, no other connector without partner may face in the direction up to the module plan edge. \\ +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 in the range **10 - 99** 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,​ affected connector pairs with numbers in the range **10 - 99** 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 in the range **10 - 99** are forgotten somewhere, "​strange"​ routes can arise.+
  
 **Recommendation:​**\\ **Recommendation:​**\\
 To the mentioned disadvantages - among others: Errors, high effort for changes, etc. - it is recommended to avoid connectors at the module transitions. \\ To the mentioned disadvantages - among others: Errors, high effort for changes, etc. - it is recommended to avoid connectors at the module transitions. \\
-Instead of the connectors, "​straight track elements"​ {{: spdrs60-track-norm.png}} should be positioned so that they match each other without interruption when compiling ​the modules. \\+Instead of the connectors, "​straight track elements"​ {{:​spdrs60-track-norm.png}} should be positioned so that they match each other without interruption when arrange ​the modules. \\
 This results in the perspective of the analyzer continuous track connections from which routes can be easily generated. This results in the perspective of the analyzer continuous track connections from which routes can be easily generated.
  
Line 136: Line 136:
 | On Module transitions use straight track elements :!:  | | On Module transitions use straight track elements :!:  |
 |  {{:​modules:​no-connector.png?​200}} ​ | |  {{:​modules:​no-connector.png?​200}} ​ |
 +
 +See also __**[[#​messages_in_the_server_log|Messages in the server log]]**__\\
 \\ \\
  
Line 216: Line 218:
 \\ \\
  
-==== Messages in the server log ====+===== Messages in the server log ====
 +To display the analyzer results, **[[rocrailini-trace-en#​calculation|Trace:​ calculation]]** must be activated. 
 +  * **Note:** \\ Activation of Trace level "​Analyze"​ is not recommended. \\ This option should be reserved for troubleshooting analyzer functions. 
 +==== Examples ==== 
 +// **Note:** The message to the last action is at the top of the log.//
  
-''​ANALYSER: max. recursion depth (101 > 100) reached''​ +** Server log at "​Analyze"​ with typical design plan error: ** 
-  * On search for routes between 2 blocks more than 100 track diagram elements were found \\ **[[http://​forum.rocrail.net/​viewtopic.php?​p=89410#​p89410|Look at this thread in the german forum]]** +<​code>​ 
-  ​=> Please follow the **[[goldenrules-en|Best practice]]**+17:23:09 route generator (re)created routes (0 -> 8) 
 +17:​23:​08 ​ANALYSER: max. recursion depth (101 > 100) reached 
 +17:23:08 ANALYSER: max. recursion depth (101 > 100) reached 
 +</​code>​ 
 +  * On search for routes between 2 blocks more than 100 track diagram elements were found //(Two messages = search in both directions)// ​\\ **[[http://​forum.rocrail.net/​viewtopic.php?​p=89410#​p89410|Look at this thread in the german forum]]** 
 +  ​Please follow the **[[goldenrules-en|Best practice]]** 
 + 
 +**Server log at "Clean all analyze"​ and then "​Analyze":​** 
 +<​code>​ 
 +23:45:36 route generator (re)created routes (0 -> 4) 
 +23:45:35 starting analyzer... 
 +23:45:25 route generator cleanup removed 4 routes (4 -> 0) 
 +23:45:24 starting analyzer cleanup... 
 +</​code>​ 
 +  - 4 routes have been deleted 
 +  - 4 routes were newly created 
 + 
 +**Server log at "​Analyze"​ with typical connectors errors:** 
 +<​code>​ 
 +14:08:06 Analyser skipped because plan has ERRORs 
 +14:08:06 ERROR: connector [tk5] at (6-5-1) number[3] : Too many counterparts (total 3) 
 +14:08:06 WARNING: connector [tk4] at (14-3-0) with number[2] : no counterpart found. 
 +14:08:06 ERROR: connector [tk3] at (14-1-0) number[3] : Too many counterparts (total 3) 
 +14:08:06 ERROR: connector [tk2] at (6-3-0) number[3] : Too many counterparts (total 3) 
 +</​code>​ 
 +  - There are more than two paired connectors with number **3** at the specified positions. // (Example: **6-3-0** = x-y-z) // 
 +  - The connector with number **2** is missing the partner. 
 +  - The Analyser run was aborted because of the listed errors in the track plan.
  
analyzer-en.1542009373.txt.gz · Last modified: 2018/11/12 08:56 by 127.0.0.1