Table Of Contents

Optical Flow (Optical Flow (HS)) (G Dataflow)

Last Modified: June 25, 2019

Computes the optical flow (velocity flow) information in two successive images using the Horn-Schunck algorithm.

connector_pane_image
datatype_icon

stopping criteria

Conditions that need to be met to stop the optical flow computation.

datatype_icon

type

Type of stopping criteria to use.

Choose one of the following criteria.

Name Description
Iterations Specifies that the computation should stop after the number of iterations in the max. iterations control.
Epsilon Specifies the computation should stop after the value of epsilon has been reached.
Both Specifies the computation should stop after the maximum iterations and Epsilon value have both been reached.
datatype_icon

max. iterations

Maximum iterations to run the optical flow computation.

datatype_icon

epsilon

Maximum difference allowed between the velocity information computed between two successive iterations.

datatype_icon

ROI descriptor

Descriptor that defines the region of interest (ROI) within which the optical flow is computed.

datatype_icon

global rectangle

Coordinates of the bounding rectangle.

datatype_icon

contours

Individual shapes that define an ROI.

datatype_icon

ID

Object specifying if contour is the external or internal edge of an ROI.

datatype_icon

Type

Shape type of the contour.

datatype_icon

Coordinates

Relative position of the contour.

datatype_icon

current frame

Reference to the current source image.

datatype_icon

previous frame

Reference to the previous source image.

datatype_icon

velocity component 1 in

Reference to the image that will contain the horizontal component or the magnitude component of the computed velocity at each pixel.

datatype_icon

velocity component 2 in

Reference to the image that will contain the vertical component or the phase component of the computed velocity at each pixel.

datatype_icon

smoothing parameter

Smoothing effect to apply to the velocity information in the image.

datatype_icon

error in

Error conditions that occur before this node runs.

The node responds to this input according to standard error behavior.

Standard Error Behavior

Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

error in does not contain an error error in contains an error
If no error occurred before the node runs, the node begins execution normally.

If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.

If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

Default: No error

datatype_icon

velocity representation

Computed velocity information represented in Cartesian or polar coordinates.

datatype_icon

use previous

Boolean value which, when True, uses the information in velocity component 1 in and velocity component 2 in as the initial estimates of the velocity to compute the current velocity.

datatype_icon

current frame out

Duplicate of the input current frame.

datatype_icon

velocity component 1 out

Reference to the image that contains the horizontal component or the magnitude component of the computed velocity at each pixel.

datatype_icon

velocity component 2 out

Reference to the image that contains the vertical component or the phase component of the computed velocity at each pixel.

datatype_icon

error out

Error information.

The node produces this output according to standard error behavior.

Standard Error Behavior

Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

error in does not contain an error error in contains an error
If no error occurred before the node runs, the node begins execution normally.

If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.

If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

Where This Node Can Run:

Desktop OS: Windows

FPGA: Not supported

Web Server: Not supported in VIs that run in a web application


Recently Viewed Topics