<< return to Pixycam.com

User Tools

Site Tools


wiki:v2:line_expert

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
wiki:v2:line_expert [2018/06/06 16:54]
pixycam
wiki:v2:line_expert [2018/06/07 13:35]
pixycam
Line 1: Line 1:
  
-===== Line tracking ​expert ​tab =====+===== Line tracking ​Expert ​tab =====
  
 This tab contains more advanced parameters for adjusting various line tracking things. To bring up this tab, you must be running the _line\_tracking_ program by selecting it in the **Program** menu, and then bringing up the Configure Dialog (click on the gear icon {{wiki:​v2:​image_291.png}} or select **File➜Configure**). Now select the **Expert** tab under **Pixy Parameters**. This tab contains more advanced parameters for adjusting various line tracking things. To bring up this tab, you must be running the _line\_tracking_ program by selecting it in the **Program** menu, and then bringing up the Configure Dialog (click on the gear icon {{wiki:​v2:​image_291.png}} or select **File➜Configure**). Now select the **Expert** tab under **Pixy Parameters**.
Line 20: Line 20:
   * **Barcode filtering:​** Increasing this parameter leads to more filtering and can result in less false positive barcode detections, but with some added latency regarding when new barcodes are reported.   * **Barcode filtering:​** Increasing this parameter leads to more filtering and can result in less false positive barcode detections, but with some added latency regarding when new barcodes are reported.
   * **Default turn angle:** This parameter sets the path the algorithm takes when encountering an intersection. ​ The algorithm will pick the path that is _closest_ to the specified angle. ​ Turn angles are specified in degrees, with 0 being straight ahead, left being 90 and right being -90 (for example), although any valid angle value can be used. Valid angles are between -180 and 180.  This parameter is usually set to 0, which essentially means "go straight at intersections (or pick the straightest path) unless I tell you otherwise." ​ Telling the algorithm otherwise is done through **setNextTurn()** in the [[wiki:​v2:​line_api|API]].   * **Default turn angle:** This parameter sets the path the algorithm takes when encountering an intersection. ​ The algorithm will pick the path that is _closest_ to the specified angle. ​ Turn angles are specified in degrees, with 0 being straight ahead, left being 90 and right being -90 (for example), although any valid angle value can be used. Valid angles are between -180 and 180.  This parameter is usually set to 0, which essentially means "go straight at intersections (or pick the straightest path) unless I tell you otherwise." ​ Telling the algorithm otherwise is done through **setNextTurn()** in the [[wiki:​v2:​line_api|API]].
-  * **Delayed turn:​** ​ This parameter tells the algorithm to stop choosing paths at intersections automatically. ​ It requires the client program to indicate the path with **setNextTurn()** in the [[wiki:​v2:​line_api|API]] _before the intersection goes out of frame_. ​ It's an extra expert option. ​ It's included because sometimes you might not know which way to turn at the next intersection until you actually see the intersection (the number of branches and their angles, for example.) ​ It's also fun to set it because PixyMon will dutifully label the intersections:​ "3-way intersection",​ "4-way intersection",​ etc. because it doesn'​t know which way to turn yet.+  * **Delayed turn:​** ​ This parameter tells the algorithm to stop choosing paths at intersections automatically. ​ It requires the client program to indicate the path with **setNextTurn()** in the [[wiki:​v2:​line_api|API]] _before the intersection goes out of frame_. ​ It's an extra expert option. ​ It's included because sometimes you might not know which way to turn at the next intersection until you actually see the intersection (the number of branches and their angles, for example.) ​ It's also useful? ​funto set it because PixyMon will dutifully label the intersections:​ "3-way intersection",​ "4-way intersection",​ etc. because it doesn'​t know which way to turn yet.
   * **Manual vector select:​** ​ When the algorithm initializes,​ it needs to figure out which line should be the Vector, a.k.a. the line you want to follow. It will automatically choose the Vector based on some characteristics that it thinks are attractive, like a line that intersects the bottom of the frame and/or a line that is close to vertical. ​ You can bypass this selection process by enabling this parameter. ​ The algorithm will then set the Vector based on **setVector()** calls through the [[wiki:​v2:​line_api|API]].   * **Manual vector select:​** ​ When the algorithm initializes,​ it needs to figure out which line should be the Vector, a.k.a. the line you want to follow. It will automatically choose the Vector based on some characteristics that it thinks are attractive, like a line that intersects the bottom of the frame and/or a line that is close to vertical. ​ You can bypass this selection process by enabling this parameter. ​ The algorithm will then set the Vector based on **setVector()** calls through the [[wiki:​v2:​line_api|API]].
  
 {{page>​wiki:​v2:​expert_tab_common}} {{page>​wiki:​v2:​expert_tab_common}}
wiki/v2/line_expert.txt · Last modified: 2018/06/07 13:35 by pixycam