Instructions for executing a matlab function.
Assigns a execution point for the analysis. Refer to the Analysis Engine for more Info. Alternately, plague ome-devel with requests for more documentation.
An ordered list of the function's inputs
An ordered list of the function's outputs
Will pass a numeric matrix into the function.
Translates a module input of Semantic Type Pixels (or any psuedo subclass of Pixels) to a numeric matrix. Limits specified by PixelsSlice or its subclasses will be honored.
References a FormalInput by name
An input ID.
In the future, can be used to establish references.
The Pixels array will be converted to the (MATLAB) datatype specified.
A 1x1 numeric or logical matrix -OR- a char matrix. Used only with inputs of arity 1 (i.e. Count='!')
Refers to a semantic element of a formal input. Syntax is formal input name, a period, and the semantic elment name. i.e. "Texture Direction.Direction_Value"
The MATLAB scalar will be converted to the (MATLAB) datatype specified.
Specifies a constant scalar input.
Will translate a numeric array to a Formal Output of Semantic Type Pixels (or any psuedo subclass of Pixels). If PixelsSlice appears in the pseudo inheritance chain, the extents will be set to the extents of the Pixels.
References a FormalOutput by name
An output ID.
In the future, can be used to stitch together data from different function outputs into a single module output, or establish references.
Useful when a function outputs a Pixels type that is unsupported by OME. The permitted list is the matlab types supported by OME.
Note to perl developers: This list should stay syncronized with the Matlab Class to OME pixel-type mapping hash $self->{ _matlab_class_to_pixel_type } that is defined in OME::Analysis::Handlers::MatlabHandler->new()
A 1x1 numeric or logical matrix -OR- a char matrix.
References a Template this value will be inserted into.
Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic elment name. i.e. "Angular Second Moment.ASM"
The MATLAB scalar will be converted to the (MATLAB) datatype specified. The permitted list is the matlab types supported by OME.
Note to perl developers: This list should stay syncronized with the Matlab Class to OME SE Type mapping hash $self->{ _matlab_class_to_ome_datatype} that is defined in OME::Analysis::Handlers::MatlabHandler->new()
Struct outputs are expected to have the same structure and field names as the STs of their formal outputs. We do not anticipate this to be a widely used feature.
References a FormalOutput by name
An output ID.
In the future, can be used to stitch together data from different function outputs into a single module output, or establish references.
A one dimensional matrix output.
Specifies decoding instructions. This should match the ID of a VectorDecoder element
Used to add structure & explicit data description to function outputs such as ChannelComponents or LogicalChannels.
The contents of this element should follow CustomAttribute syntax and conventions.
Instructions for extracting data from a one dimensional matlab matrix.
Maps a location on the Vector to an output data location. Can be used in conjuction with Templates.
Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic elment name. i.e. "Angular Second Moment.ASM"
A numeric index into the matlab vector. Numbering starts at 1 to follow matlab convention.
References a Template this value will be inserted into.
An output ID.
In the future, can be used to stitch together data from different function outputs into a single module output, or establish references.
The MATLAB scalar that is part of a MATLAB vector will be converted to the (MATLAB) datatype specified. The permitted list is the matlab types supported by OME.
Note to perl developers: This list should stay syncronized with the Matlab Class to OME SE Type mapping hash $self->{ _matlab_class_to_ome_datatype} that is defined in OME::Analysis::Handlers::MatlabHandler->new()
An output ID.
In the future, can be used to stitch together data from different function outputs into a single module output, or establish references.