Measure Factory Project Requirements

Measure Factory projects in Workbench have a recommended project structure and require certain files.

The project structure is flexible, but should contain the following recommended files and folders:

• Factory configuration file—This main configuration file can be located anywhere in the project, but typically it is stored in the config folder. The file extension is factory and the file is typically named cfg.factory, although you can use a file name that fits your project and data sets.

  NOTE: In Workbench 7.1(13) and later, portions of cfg.factory can be located in factory-data-set and factory-scope files.

• Input sources—These sources are referenced by their path in data-set blocks in the factory configuration file. They can be in any location accessible from the factory project (including within the project or by way of a project or system alias if external to the project).

  NOTE: Prior to Workbench 7.1(13), a cBase is required as the input data source. In Workbench 7.1(13) and later, input sources include both data and plugin sources. For more information, see About Data Sets.

• Lookup table files—Lookup table files are referenced by name from lookup-table blocks in the factory configuration file and must be in the same directory as the factory configuration file.

  NOTE: Prior to Workbench 7.1(13), lookup table files are always text files and must be in the same directory as the factory configuration file. In Workbench 7.1(13) and later, lookup tables can be any Spectre input type and located using the path tag.

• Flag table files—Flag table files are referenced by name from flag-table blocks in the factory configuration file and must be in the same directory as the factory configuration file.
• Plugins folder—Each factory plugin is placed within a sub-folder in the plugins directory. Each sub-folder is named for the plugin and has a plugin configuration file that must be named cfg.factory-plugin. The plugin is referenced in the plugin block of the factory configuration file by the plugin folder name.

This example shows a typical project structure.