VisionX V4V3SCVisionX V4
NAME

v3sc − 3D component selection

SYNOPSIS

v3sc [if=<inputfile>] [of=<outputfile>] [s=<value>] [v=<value>] [e=<value>] [c=<value>] [m=<value>] [-e] [-m] [-v]

DESCRIPTION

V3sc performs component selection on a 3D image. Produces an image with with only the selected component(s) and, optionally, set to a specified intensity. The major (greatest volume) or an arbitrary component may be selected. In addition, the components touching the x-y bounding box in each z-slice may optionally be removed.

CAVEATS

The output of v3sc will be without frame markes; they can be recreated using the command vdim

OPTIONS

if=<output file>

specifies a VisionX (integer or byte) input file.

of=<output file>

specifies a VisionX output file. This file will have the same type as the input image.

s=<index>

specifies the image component to be selected. All elements of this intensity will be kept.

v=<value>

specifies the value to which all remaining image components will be set, following processing. This is useful in creating a "binary" image, where all elements have a value of zero or v.

e=<value>

specifies the distance (in pixels) from the x-y bounding box in each z-slice within which components should be marked for deletion. Removes those components (near or) touching the edges of an image seqence. This is useful in certain object segmentation techniques.

-e

delete all components touching the x-y bounding box in each z-slice. Removes those components touching the edges of an image seqence. This is the same as specifying e=0.

t=<value>

delete all components smaller than <value> voxels.

c=<value>

Select the component on pixel location (xc,yc,zc).

m=<value>

keep only the "m" largest volume components. Note that the volume determinations are made after removal of edge components when the -e flag is given.

-m

keep only the major component (the intensity occupying the greatest volume in the 3D image). This is the same as specifying m=1.

-v

verbose operation. Gives some runtime information, including a running count of the number of components identified.

SEE ALSO

v3connect(1), vdim(1)

AUTHOR

W. J. Kostis, A. M. Biancardi