define({"217":{y:0,u:"../Content/ViDi-Topics/setup/use-vidi-subtask-access-data-marking-output.htm",l:-1,t:"Add the Marking Output",i:0.00129943000761505,a:"To pass the Marking data from the ViDi Tool Block, you have to create an output pin from the ViDi Sub Task block. Select the Marking output pin from your ViDi Tool Block. Drag the Marking link to the output block within the ViDi Sub Task block. This will automatically create the output pin, with the ..."},"218":{y:0,u:"../Content/ViDi-Topics/setup/use-vidi-subtask-access-data-create-tags.htm",l:-1,t:"Create Tags for the Data",i:0.00129943000761505,a:"In order to share the information returned by the ViDi tools throughout the Designer environment, data tags should be created to facilitate that data transfer. In this example, tags will be created to record the view count, and to store the X, Y and area data contained in the pose. In this example, ..."},"219":{y:0,u:"../Content/ViDi-Topics/setup/use-vidi-subtask-access-data-script-refs.htm",l:-1,t:"Add the Script Block and References",i:0.00129943000761505,a:"With the Marking output pin in place on your ViDi Sub Task block, to access the data, a Script block must be used. Before the Script block can access the Marking data, the appropriate References must be added. If you will have multiple Script blocks accessing ViDi Tool Block data, every Script block ..."},"220":{y:0,u:"../Content/ViDi-Topics/setup/use-vidi-subtask-access-data-write-script.htm",l:-1,t:"Write the Script to Access the Data",i:0.00129943000761505,a:"With the References added, you are ready to write the code that will access the data in the ViDi Tool Block. This topic contains sample code that stores the center of the first defect region in the $result.X1 and $result.Y1 tags. var view = ViDiSubTask_Analyze_Marking.Views[0];\n{\n    $result.Count = ..."},"221":{y:0,u:"../Content/ViDi-Topics/setup/command-line-arguments.htm",l:-1,t:"Command Line Arguments",i:0.00129943000761505,a:"The topics in this section cover the various command line arguments that can be processed by a ViDi plugin within a Designer application. The name of the service application you will be issuing the commands to is ViDi Suite GUI or ViDi Suite Service.exe . The applications are located in ..."},"222":{y:0,u:"../Content/ViDi-Topics/setup/device-commands.htm",l:-1,t:"Deep Learning Devices and Workspace Commands",i:0.00129943000761505,a:"When a Deep Learning Device options are specified via a command line argument, this will override any Deep Learning Device settings made in the Designer application. This applies to Deep Learning Devices created for new projects, existing Devices in deployed projects, and existing Devices in ..."},"223":{y:0,u:"../Content/ViDi-Topics/setup/gpu-mode-commands.htm",l:-1,t:"GPU Mode Command Line Initialization",i:0.00129943000761505,a:" GPU Mode Command Line Initialization There are several command line arguments that can be used on startup for library initialization. The commands are issued using Windows Command Prompt, and navigating to the %ProgramFiles%\\Cognex\\ViDi Suite\\3.3 directory. You issue the commands by first ..."},"224":{y:0,u:"../Content/ViDi-Topics/overview/graphics.htm",l:-1,t:"ViDi Tool Graphics",i:0.00140988184436181,a:"ViDi Tool Graphics The  Cognex ViDi Tools  utilize overlay graphics and color codes to illustrate information about the system and its state. These graphics are referred to as  Labeling  and  Markings ."},"225":{y:0,u:"../Content/ViDi-Topics/overview/mismatches.htm",l:-1,t:"Mismatches",i:0.00335339118650934,a:"The ViDi tools indicate a mismatch with an orange marking. A mismatch refers to a feature that is found by the system in an image that you labeled, but there is either a mismatch between a corresponding label, or there are possibly more instances of a labeled feature. If encountering a mismatch, the ..."},});