Tied to DB. LOOKUP_TABLE_ENTRIES.VALUE Tied to DB. LOOKUP_TABLE_ENTRIES.LABEL Describes valid values for an input. Think enumerations, (a list of valid values). Tied to DB. LOOKUP_TABLES.NAME Specifies an input requirement for a module. Image dimensions and image file locations (repository or other format) should not be specified with this. Image dimensions are intrisic to an image. They do not represent a special requirement. Image file locations and contents are specified by other elements. Specifically, RawImageFile, RawImageFilePath, XYPlaneFile, and XYPlaneFilePath. OME interprets this as a recommendation rather than a requirement. Tied to DB. Table FORMAL_INPUTS Column USER_DEFINED Specifies how many counts of this formal input are expected. Meanings are specified below ! = exactly one ? = zero or one + = one or more * = zero or more Valid characters are alphanumeric and spaces. Specifies an output element of a module. Concerning MakeNewFeature attribute of ExecutionInstructions, if a new feature type is made, then there are two possible places a formal output attribute can be stored: It can be stored as an attribute of the FeatureIterator, or it can be stored as an attribute of the new Feature. This tag is supposed to specify which. Can be left blank if module does not make new iterator. Tied to DB. FORMAL_OUTPUTS.FEATURE_TAG Processed before storage to DB Specifies how many counts of this formal output will be produced. Meanings are specified below ! = exactly one ? = zero or one + = one or more * = zero or more THIS IS REQUIRED for every formal output outside of the importer. The importer doesn't know what it will run into before it executes, so it can't declare the semantic type of its outputs. If you are writing a module, I HIGHLY HIGHLY recommend that you type your formal outputs. States module requirements. Formal Inputs are optional because input requirements may be specified by guaranteed image attributes. For example, OME_Image_XYZ_stats requires a path to the OME repository file, and Dimensions. These are given by <RawImageFilePath>, <sizeX>, <sizeY>, <sizeZ>, <sizeT>, and <sizeW>. Describes an interface to use with a program. This is a stub for future development. The database location doesn't even exist yet. If the output of the analysis will be the same when pixel positions are scrambled, the analysis is a stream algorithm. Examples of stream algorithms are: A statistics module that produces mean, geometric mean, standard deviation, etc. for pixel intensities. A module to cross correlate pixel intensities across wavelengths. Example of an algorithms that is not a stream algorithm is: FindSpots. (It's a module to find blobs in an image.) If a module is a stream algorithm, it can function across the x, y, z, and time dimensions. Tied to DB. Table PROGRAMS Column IS_STREAM_ALGORITHM As more handlers, are added, this part of the schema needs to be changed Tied to DB. Table PROGRAMS Column MODULE_TYPE If the module iterates over a feature, specify the iterator here. It will reference a feature via the TAG column of the FEATURES table. An example of a module that does not iterate over a feature is Find Cells. It examines one image at a time, hence it iterates over an image, not a feature. It produces zero or more features (Çell) per image. These Cell features belong to an image. This module would not get a FeatureIterator attribute. An example of a module that iterates over a feature is Find Golgi. It examines one CELL at a time. A cell is a feature, hence the module iterates over features, not images or datasets. It produces zero or more Golgi features per Cell feature. These Golgi features belong to a Cell feature. This module would get a FeatureIterator attribute of "CELL". Tied to DB. Table PROGRAMS Column DEFAULT_ITERATOR If this module makes new features, then the new Feature's name needs to be specified here. If the module does not make new features, do not specify a value for this attribute. Tied to DB. PROGRAMS.NEW_FEATURE_TAG References a Category. Eventually will refer to a program. Currently program installation is NOT implemented. So this value is the path to the installed binary file. The script should interface with the OME API to find all information it needs. (i.e. installation path) It also needs to set the location of the program after the program is installed. The location should be set through the API, but it will propogate to the LOCATION column of the PROGRAMS table. Contains a packaged or zipped installation files (binaries or source code). This is a stub for future development. Don't bother with it unless you know more about it. Specifies the packaging and/or compression format of the Installation file. Stores an installation package and installation script for a program. This currently is NOT implemented. Program name. Unclear how this would be used. DB location PROGRAMS.PROGRAM_NAME is populated by XML attribute AnalysisModule.Name. Currently unused An analysis module is defined by two things: 1) A program 2) An interface A single program may have multiple interfaces. Why do you need multiple interfaces? Pretend you have a program that calculates simple statistics on the pixels of an image. You can specify which statistics you want via parameters. Typing ./stats -mean -sigma image1 will ouput Image | mean | sigma image1 12.4 1 Typing ./stats -geomean -mean image1 will output Image | geomean | mean image1 12.2 12.4 The outputs are completely different. You need to specify an interface for each of these behaviors. Or pretend you have a powerful program that can do 10 unrelated tasks, each of which outputs an image. While the outputs are the same type and format, they represent 10 completely different things. In this case, it might make sense to define 10 corrosponding AnalysisModule to represent the 10 logical functions. In any case, use AnalysisModule to define an interface and Program to store installation software for a program. Just some free-form text to describe Images, Screens and Projects. The content model is ANY, which means that en entire XML sub-document can be placed here. Categories are organized into heirarchical structures. This specifies the full path of this category in the following format. Path = "GrandParent name.Parent name.Category name" If you defined a sub category, we Strongly encourage you to also define all ancestor categories that are not part of the core OME specification.