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
analyzer-en [2019/09/22 10:51]
rjversluis old revision restored (2019/09/20 10:33)
analyzer-en [2019/09/22 10:53] (current)
rjversluis
Line 5: Line 5:
     * [[rocrailini-analyser-en|Rocrail setup dialog]]     * [[rocrailini-analyser-en|Rocrail setup dialog]]
  
- 
-\\ 
-^  W O R K - I N - P R O G R E S S  ^ 
- 
- \\ 
  
  
Line 28: Line 23:
  
 ==Note:== ==Note:==
-The Analyser ​was introduced as a tool especially for the new and inexperienced user allowing for quick access to fully automated model railroading. \\  +The Router ​was introduced as a tool especially for the new and inexperienced user allowing for quick access to fully automated model railroading. \\  
-However, with complex or unusual layouts the Analyser ​may fail to generate all routes possible or it may generate unexpected routes or in worst case it may even hang. \\  +However, with complex or unusual layouts the Router ​may fail to generate all routes possible or it may generate unexpected routes or in worst case it may even hang. \\  
-In all these cases settings have to be adjusted or completed by hand while those routes generated correctly by the Analyser ​can serve as a blueprint. \\+In all these cases settings have to be adjusted or completed by hand while those routes generated correctly by the Router ​can serve as a blueprint. \\
 See also **[[analyzer-en#​Limitations|section Limitations]]** See also **[[analyzer-en#​Limitations|section Limitations]]**
    
Line 41: Line 36:
   - All items must be connected without a space in between them. Exception: The [[#​connector|Connector]]   - All items must be connected without a space in between them. Exception: The [[#​connector|Connector]]
   - Only one item at one position in the plan is allowed. (**No overlapping.**) ​   - Only one item at one position in the plan is allowed. (**No overlapping.**) ​
-  - The analyser ​is based on the symbol sizes found in the default **[[:​symbols-themes-spdr60-en|SpDrS60]]** theme. (See also **[[symbols-theme-props-en#​basics|themes basics]]**)+  - The Router ​is based on the symbol sizes found in the default **[[:​symbols-themes-spdr60-en|SpDrS60]]** theme. (See also **[[symbols-theme-props-en#​basics|themes basics]]**)
  \\  \\
  
 ==== Activation ==== ==== Activation ====
-The Analyser ​can be activated manually.+The Router ​can be activated manually.
  
 The feature is started manually by The feature is started manually by
Line 82: Line 77:
  
 ==== Direction Tracks ==== ==== Direction Tracks ====
-Direction tracks (s. also **[[:​tracks-gen-en#​type|Types of Tracks]]**) can be used to restrict the routes generated by the analyser ​to one particular direction. For this purpose the direction track is placed between one or more blocks:+Direction tracks (s. also **[[:​tracks-gen-en#​type|Types of Tracks]]**) can be used to restrict the routes generated by the Router ​to one particular direction. For this purpose the direction track is placed between one or more blocks:
 |< >| |< >|
-^ Example ^ Description ^ Routes generated by the analyser ​^+^ Example ^ Description ^ Routes generated by the Router ​^
 | {{:​analyzer:​dir-no.png}} | Two blocks connected by tracks | From A to B __and__ from B to A | | {{:​analyzer:​dir-no.png}} | Two blocks connected by tracks | From A to B __and__ from B to A |
 | {{:​analyzer:​dir-all.png}} | Two blocks with a track indicating both directions in between | Same as above; the track for both directions is descriptive only but has no function | | {{:​analyzer:​dir-all.png}} | Two blocks with a track indicating both directions in between | Same as above; the track for both directions is descriptive only but has no function |
Line 104: Line 99:
 |  :!: 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.** ​ | |  :!: 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 Router ​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. \\ With connectors it's easy to connect different levels on the layout. \\
  
Line 141: Line 136:
  
 ===== Limitations ===== ===== Limitations =====
-  * The analyser ​ist not perfect, errors can occur.+  * The Router ​ist not perfect, errors can occur.
   * Not all '​weird'​ situations are recognized. ​   * Not all '​weird'​ situations are recognized. ​
-  * The analyser ​configures sensors (feedbacks) only after the option "​Assign sensors to blocks"​ in **[[rocrailini-analyser-en##​assign_feedbacks_to_blocks|Sensors in blocks]]** has been enabled (by default this option is off). +  * The Router ​configures sensors (feedbacks) only after the option "​Assign sensors to blocks"​ in **[[rocrailini-analyser-en##​assign_feedbacks_to_blocks|Sensors in blocks]]** has been enabled (by default this option is off). 
-  * If "​Assign feedbacks to blocks"​ is activated, the analyser ​tries only to allocate the sensors **enter** and / or **in** in generic routes that are not yet fully generated (whether manually configured by the user or already existed from previous analyzes). \\ **Note:** Previously configured **enter** and / or **in** sensors are maintained and the analyser ​does not change them (even if they were completely wrong).+  * If "​Assign feedbacks to blocks"​ is activated, the Router ​tries only to allocate the sensors **enter** and / or **in** in generic routes that are not yet fully generated (whether manually configured by the user or already existed from previous analyzes). \\ **Note:** Previously configured **enter** and / or **in** sensors are maintained and the Router ​does not change them (even if they were completely wrong).
  
   * The above applies only to the closest (there are exceptions in special situations) sensors near a block that are unique to this block.   * The above applies only to the closest (there are exceptions in special situations) sensors near a block that are unique to this block.
Line 165: Line 160:
 ^  Number ​ ^Description^ ^  Number ​ ^Description^
 |  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 Router ​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 Router ​will generate some wrong routes :!:
  
  \\  \\
Line 196: Line 191:
 ===== Tips and Tricks ===== ===== Tips and Tricks =====
 ==== Keep Routes ==== ==== Keep Routes ====
-Q: Why is analyser ​always overwriting or removing my changes?​\\ +Q: Why is Router ​always overwriting or removing my changes?​\\ 
-A: At first the analyser ​__deletes all__ routes with the activated option '​Automatically generated'​.\\+A: At first the Router ​__deletes all__ routes with the activated option '​Automatically generated'​.\\
 \\ \\
-Q: How can I prevent ​analyser ​to recreate a route?\\+Q: How can I prevent ​Router ​to recreate a route?\\
 A: By deactivating the option '​Automatically generated'​ (-> no deletion -> no recreating)\\ A: By deactivating the option '​Automatically generated'​ (-> no deletion -> no recreating)\\
 \\ \\
Line 214: Line 209:
   * delete/​remove "​[A-]-[B+]-42"​   * delete/​remove "​[A-]-[B+]-42"​
 - After: - After:
-  * calling ​analyser ​will leave "​[A-]-[B+]"​ untouched (the option '​Automatically generated'​ is deactivated) and will not create any alternative route from [A-] to [B+], because there is already a "​manually configured"​ route for this relation.+  * calling ​Router ​will leave "​[A-]-[B+]"​ untouched (the option '​Automatically generated'​ is deactivated) and will not create any alternative route from [A-] to [B+], because there is already a "​manually configured"​ route for this relation.
 \\ \\
  
Line 244: Line 239:
 **Server log at "​Analyze"​ with typical connectors errors:** **Server log at "​Analyze"​ with typical connectors errors:**
 <​code>​ <​code>​
-14:​08:​06 ​Analyser ​skipped because plan has ERRORs+14:​08:​06 ​Router ​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 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 WARNING: connector [tk4] at (14-3-0) with number[2] : no counterpart found.
Line 252: Line 247:
   - There are more than two paired connectors with number **3** at the specified positions. // (Example: **6-3-0** = x-y-z) //   - 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 connector with number **2** is missing the partner.
-  - The Analyser ​run was aborted because of the listed errors in the track plan.+  - The Router ​run was aborted because of the listed errors in the track plan.
  
analyzer-en.txt · Last modified: 2019/09/22 10:53 by rjversluis