The contour computation is done using morphological operations.
The resulting output regions consist only of the minimal border of the input
regions. Their positions depend on the value of BoundaryTypeBoundaryTypeBoundaryTypeBoundaryTypeboundaryTypeboundary_type,
accepting the following values:
'inner'"inner""inner""inner""inner""inner": The contour lies within the original region.
'inner_filled'"inner_filled""inner_filled""inner_filled""inner_filled""inner_filled": The contour lies within the original
region, holes in the interior of the input region are suppressed.
Due to algorithm optimization this contours may slightly differ
from corresponding ones obtained with 'inner'"inner""inner""inner""inner""inner".
'outer'"outer""outer""outer""outer""outer": The contour is one pixel outside of the original
region.
Execution Information
Multithreading type: reentrant (runs in parallel with non-exclusive operators).
Multithreading scope: global (may be called from any thread).
List of values: 'inner'"inner""inner""inner""inner""inner", 'inner_filled'"inner_filled""inner_filled""inner_filled""inner_filled""inner_filled", 'outer'"outer""outer""outer""outer""outer"
Let A be the area of the input region. Then the runtime
complexity for one region is
Result
boundaryboundaryBoundaryBoundaryBoundaryboundary returns TRUE if all parameters are correct. The
behavior in case of empty or no input region can be set via:
no region:
set_system('no_object_result',<RegionResult>)