| MIL 10 Reference
| Customize Help
| Save Settings

MimConnectMap



See also
User Guide:
Reference:
Availability
Not available in MIL-Lite
Available in MIL

Available on Windows
Available on Linux

Partially supported on:
Partially supported on Matrox GPU processing driver

Fully supported on:
Fully supported on Host system
Fully supported on Matrox CronosPlus
Fully supported on Matrox GigE Vision driver
Fully supported on Matrox IEEE 1394 IIDC driver
Fully supported on Matrox Iris GT
Fully supported on Matrox Morphis
Fully supported on Matrox Morphis QxT
Fully supported on Matrox Orion HD
Fully supported on Matrox Radient eCL
Fully supported on Matrox Radient eV-CXP
Fully supported on Matrox Solios eA/XA
Fully supported on Matrox Solios ecl/xcl/ev-cl
Fully supported on Matrox USB3 Vision driver (requires Update 19)
Fully supported on Matrox Vio

For any information regarding a MIL system added during a MIL Update, see the MIL system’s release note

Available on Non-Matrox computer
Available on Matrox 4Sight-X
Available on Matrox 4Sight GP
Available on Matrox Supersight
function map Function map
Examples
Synopsis
Perform a 3x3 binary connectivity mapping.
Syntax
void MimConnectMap(
MIL_ID SrcImageBufId, //in
MIL_ID DstImageBufId, //in
MIL_ID LutBufId //in
)
Description

This function performs a 3x3 binary connectivity mapping. It calculates a connectivity code for each pixel in the source image, treating the source image as if it were binary (that is, all non-zero pixels are treated as 1); it then maps the codes through the specified LUT buffer. Specifically, for each source pixel, this function concatenates the binary values of the pixels in a pixel's 3x3 neighborhood, and then uses this 9-bit number to address the specified LUT. The value at this LUT address is then written in the specified destination buffer at the pixel's corresponding position.

Pixel connectivity codes are determined in the following order:

Result = LUTMAP[Connectivity code].

The overscan pixels are automatically set to 0 (zero), which will produce the most accurate possible results for the image border pixels.

Note that this function reference has not been updated for a MIL system added during a MIL update. Refer to the MIL system's release note to see which MIL system’s documentation you should use in its place and any possible differences.
Parameters
This function is not supported on the selected boards.
This function reference has not been updated for the selected MIL system. To show the content of this page, choose a second MIL system; refer to the MIL system's release note to see which MIL system’s documentation to choose and any possible differences.
Parameters
SrcImageBufId

Specifies the identifier of the source of the operation. This parameter must be given an image buffer identifier.

This image buffer must not have a region of interest (ROI) associated with it. Using an image buffer with an ROI will cause an error.

[Matrox GPU processing driver]

The source image buffer must be unsigned monochrome 8- or 16-bit.

DstImageBufId

Specifies the identifier of the destination of the results. This parameter must be given an image buffer identifier.

This image buffer must not have a region of interest (ROI) associated with it. Using an image buffer with an ROI will cause an error.

[Matrox GPU processing driver]

The destination image buffer must be unsigned monochrome 8- or 16-bit.

LutBufId

Specifies the identifier of the LUT buffer. Since each connectivity code has 9 bits, you should supply a LUT buffer with at least 512 (2 9 ) entries; otherwise, unpredictable results can occur.

Compilation information
Header Include mil.h.
Library Use mil.lib; milim.lib.
DLL Requires mil.dll; milim.dll.
PROC NONE PROC NONE