Click or drag to resize
OIV.ImageViz.Engines Namespace

ImageViz engines allow the application of computational algorithms on data extracted from images.

Classes
Structures
  StructureDescription
Public structureSoImageVizEngineEventArg

Structure given to callback when an event is raised.

Enumerations
  EnumerationDescription
Public enumerationSoImageVizEngineComputeModes

Compute Mode This enum specifies whether the main input will be interpreted as a 3D volume or a stack of 2D images for processing.

Public enumerationSoImageVizEngineNeighborhood3ds

Neighborhood Connectivity 3D.

Remarks

Some engines work on images and provide output images, others provide numerical results, and others may work on vector data that represents segments of object edges. Some engines work only with 2D images, or only with 3D images and some work with both.

Naming conventions

Dimensional compatibility

Engines names may end with 2d or 3d:

  • 2d indicates that an engine only supports 2D images,

  • 3d indicates that an engine only supports 3D images,

  • If this information is omitted, the engine works on both types of images.

Type of computation

A keyword in the engine name, just before the dimensional information, indicates the kind of action the engine performs.

By convention :

  • A field name beginning with in represents an input data object,

  • A field name beginning with out represents an output data object,

  • A field name beginning neither with in, nor out represents a parameter.

A field name beginning with in or out represents data. A key-word specifies the type of data:

The automatic memory management of the .NET framework is not efficient with ImageViz engines. Engines are connected to data that can have a consequent size. The garbage collector assesses only the memory allocated in the managed space, omitting the amount of memory allocated in the non managed space. The demo GettingStarted/04.5.MemoryManagement illustrates how a C# .NET user can use features of the garbage collector to improve the memory consumption of an application.