You are here: Start » AVL.NET » Function Reference » Computer Vision » Template Matching » AVL.LocateSingleObject_SAD

AVL.LocateSingleObject_SAD

Finds a single occurrence of a predefined template on an image by analysing the Square Average Difference between pixel values.

Namespace:AvlNet
Assembly:AVL.NET.dll

Syntax

C++
C#
 
public static void LocateSingleObject_SAD
(
	AvlNet.Image inImage,
	NullableRef<AvlNet.ShapeRegion> inSearchRegion,
	AvlNet.CoordinateSystem2D? inSearchRegionAlignment,
	AvlNet.GrayModel inGrayModel,
	int inMinPyramidLevel,
	int? inMaxPyramidLevel,
	bool inIgnoreBoundaryObjects,
	float inMaxDifference,
	INullable<AvlNet.Object2D> outObject
)

Parameters

Name Type Range Default Description
inImageAvlNet.ImageImage on which model occurrence will be searched.
inSearchRegionAvlNet.NullableRef<AvlNet.ShapeRegion>Possible centers of the object occurrence. Default value: atl::NIL.
inSearchRegionAlignmentAvlNet.CoordinateSystem2D?Adjusts the region of interest to the position of the inspected object. Default value: atl::NIL.
inGrayModelAvlNet.GrayModelModel which will be sought.
inMinPyramidLevelint<0, 12>0Defines the highest resolution level. Default value: 0.
inMaxPyramidLevelint?<0, 12>3Defines the number of reduced resolution levels that can be used to speed up computations. Default value: 3.
inIgnoreBoundaryObjectsboolFalseFlag indicating whether objects crossing image boundary should be ignored or not. Default value: False.
inMaxDifferencefloat<0.0f, INF>0.0fMaximum accepted average difference between pixel values. Default value: 0.0f.
outObjectAvlNet.INullable<AvlNet.Object2D>Found object. This parameter cannot be null.

Description

The operation matches the object model, inGrayModel, against the input image, inImage. The inSearchRegion region restricts the search area so that only in this region the centers of the objects can be presented. The inMaxDifference parameter determines the maximum average difference between corresponding pixel values of the valid object occurrence.

The computation time of the filter depends on the size of the model, the sizes of inImage and inSearchRegion, but also on the value of inMaxDifference. This parameter is a score threshold. Based on its value some partial computation can be sufficient to reject some locations as valid object instances. Moreover, the pyramid of the images is used. Thus, only the highest pyramid level is searched exhaustively, and potential candidates are later validated at lower levels. The inMinPyramidLevel parameter determines the lowest pyramid level used to validate such candidates. Setting this parameter to a value greater than 0 may speed up the computation significantly, especially for higher resolution images. However, the accuracy of the found object occurrences can be reduced. Lower inMaxDifference generates less potential candidates on the highest level to verify on lower levels. It should be noted that some valid occurrences with score above this score threshold can be missed. On higher levels score can be slightly lower than on lower levels. Thus, some valid object occurrences which on the lowest level would be deemed to be valid object instances can be incorrectly missed on some higher level. The diagMatchPyramid output represents all potential candidates recognized on each pyramid level and can be helpful during the difficult process of the proper parameter setting.

To be able to locate objects which are partially outside the image, the filter assumes that there are only black pixels beyond the image border.

The outObject.Point contains the model reference point of the matched object occurrence. The outObject.Angle contains the rotation angle of the object. The outObject.Match provides information about both the position and the angle of the found match combined into value of Rectangle2D type. The outObject.Alignment contains information about the transform required for geometrical objects defined in the context of template image to be transformed into object in the context of outObject.Match position. This value can be later used e.g. by 1D Edge Detection or Shape Fitting categories filters.

The SAD (Sum of Absolute Differences) method can be significantly slower than NCC (Normalized Cross-Correlation) method. Moreover, it is not illumination-invariant, as it is required in most applications. Thus, it is highly recommended to use the latter, NCC method instead.

Remarks

Read more about Local Coordinate Systems in Machine Vision Guide: Local Coordinate Systems.

Additional information about Template Matching can be found in Machine Vision Guide: Template Matching

Hardware Acceleration

This operation supports automatic parallelization for multicore and multiprocessor systems.

Hardware acceleration settings may be manipulated with Settings class.

Function Overrides

See also