Glossary

Term Definition
Active Workflow The workflow currently loaded in a Project. A Project may store multiple workflow, but only one workflow - the Active Model - may be in use at a time.
Analysis Component A Component that is an analysis, that is, it has inputs, outputs, and an execute method. An Analysis Component also executes in a single pass. Examples include FileWrapper components on ModelCenter Remote Execution.
Analysis View A view that displays data flow within a workflow. This view displays components as boxes, with arrows between them indicating data flow.
Assembly Component A component whose sole function is to be a container for other components.
Backward Scheduler A Scheduler that uses backward chaining. The Backward Scheduler does not cause any components to run until values are explicitly requested from them. Anytime an input variable is changed, downstream values are immediately invalidated.
Carpet Plot Tool A trade study tool that generates a Carpet Plot. A Carpet Plot can be thought of as a multi-dimensional Parametric Study.
Common Component An Analysis Component that is built into ModelCenter. These components are accessible from the common folder of the Server Browser.
Component A part of a workflow. A component has inputs, outputs, and a way to execute. ModelCenter supports ModelCenter Remote Execution Components, Script Components (Legacy), VBScript Components, Driver Components, Assembly Components, and several built-in Common Components.
Component Plug-In Component Plug-Ins allows ModelCenter to tightly wrap other applications as components. This direct interface between ModelCenter and the external application permits advanced features such as:
  • Graphical Variable Specification - Component Plug-Ins build their wrappers at run-time. Thus the user can be presented with graphical dialogs for selecting variables to be used as inputs and outputs. The variables can also be reconfigured at run-time to add or remove variables.
  • Graphical Interaction with the Wrapped Tool - The direct connection between the plug-in and the wrapped application allows the plug-in to take advantage of specific functionality in the wrapped tool. This includes displaying the wrapped application's interface as needed so that the user to interact with it directly.
Example Component Plug-Ins include Excel, Matlab, and MathCAD. For more information on Plug-Ins in general, see the Plug-In Toolkit.
Component Tree The Component Tree displays the Model in a hierarchical fashion. The Component Tree is located on the left side of the ModelCenter window. Variable values can be modified directly in the Component Tree and invalid variables can be validated by clicking on them.
Data Collector

The Data Explorer has replaced the Data Collector, but references still exist to the Data Collector, mainly for backwards compatibility and for the distiction between Data Collector Plug-Ins and Data Explorer Plug-Ins.

Note: Both Data Collector Plug-Ins and Data Explorer Plug-Ins are deprecated. They appear here for compatability with older workflows containing older plug-ins.

Data Collector Plug-In

Note: Both Data Collector Plug-Ins and Data Explorer Plug-Ins are deprecated. They appear here for compatability with older workflows containing older plug-ins.

Data Collector Plug-Ins permit post-processing to data stored in the Data Explorer. It differs from a Data Explorer Plug-In in that it launches a separate window which has the capability of pulling data from the Data Explorer. The RSM Toolkit is implemented as a Java Plug-In for creating Response Surface Models from ModelCenter data. For more information on Plug-Ins in general, see the Plug-In Toolkit.

Data Explorer The Data Explorer is used to store data while a Trade Study tool is running.
Data Explorer Plug-In

Note: Both Data Collector Plug-Ins and Data Explorer Plug-Ins are deprecated. They appear here for compatability with older workflows containing older plug-ins.

Data Explorer Plug-Ins permit post processing to data stored in the Data Explorer in a more tightly integrated fasion than the old-style Data Collector Plug-Ins. They are embedded directly into the Data Explorer as pages and can interact with the user and the Data Explorer tightly.

Debug Monitor A tool used to directly communicate with ModelCenter Remote Execution. The Debug Monitor is useful to debug nonfunctioning components before using them in ModelCenter.
Design History A collection of multiple Snapshots. The Snapshots can be used to provide a history of the evolution of a design.
Design History Tool The tool used to create and view Design Histories.
Diff Tool A tool used to compare two Snapshots. The Diff Tool is launched from the Data Explorer.
DOE Design A matrix of values from the Design of Experiments (DOE) Tool. A DOE Design samples a Model at statistically significant points.
DOE Tool The Design of Experiments (DOE) Tool is a Trade Study tool used to collect a predetermined set of runs from a Model. The runs are referred to as a DOE Design.
Driver Component A component that introduces some kind of feedback into a workflow. For example, the Optimization Component will repeatedly set the value for a set of design variables until some objective is met.
ExcelWrapper A utility used by ModelCenter Remote Execution to wrap Microsoft Excel workbooks.
Favorites A feature used to save and restore commonly used Trade Study setups.
FileWrapper A utility used by ModelCenter Remote Execution to wrap file input/output-based analysis programs. The FileWrapper takes care of generating input files, running programs, and parsing the resulting output files.
Forward Scheduler A Scheduler that uses forward chaining. As soon as any input variable is modified, downstream Components are immediately run.
Geometry Component Any component that has a geometry variable as an output. This type of component is viewable in the Geometry View.
Geometry View A View that displays geometry associated with Geometry Components.
Input Shorthand for input variable. An input variable is a variable that feeds into a component. Inputs can be modified by the user.
Instantiate The process of adding a component to a workflow. When a component is dragged from the Server Browser and dropped into an Analysis View, it is instantiated into the workflow. In the Server Browser, it exists as just a type of component. When you instantiate the component into the workflow, a copy of the component actually starts up.
Invalid A state for an output variable. When an input to a component is modified, the component's outputs are said to be invalid. The outputs are only valid again once the component is run.
Link A connection between two or more variables. A link may have one or more inputs but only one output. Links are usually displayed as equations. For example, the equation Model.y = Model.a + Model.b means that the variable Model.y is linked to the variables Model.a and Model.b.
Link Editor A Model View that allows links to be viewed, created, and broken.
Mixed Mode Scheduler A Scheduler that is a mixture of forward and backward chaining. In general, links run in forward mode while other components run in backward mode. You can control whether Script Components (Legacy) run in forward or backwards mode in their options pane.
ModelCenter An application used to create workflows and perform trade studies on them.
ModelCenter Remote Execution A tool used to wrap analyses. ModelCenter Remote Execution (MCRE) can wrap file input/output-based programs, Excel workbooks, and Java Beans, among other things.
ModelCenter Remote Execution Component A component residing on ModelCenter Remote Execution server.
Model View ModelCenter supports two workflow Views: the Analysis View and the Geometry View.
Optimization Tool A trade study tool used to systematically modify inputs in a workflow to achieve some objective.
Output Shorthand for output variable. An output variable is a variable that is calculated by a Component. The user cannot directly modify Outputs.
Parametric Study Tool A trade study tool used to collect data from a workflow for a sweep of values for an input variable.
Plug-In ModelCenter has a number of ways that experienced users can add customizations using the Plug-In Architecture.
Port An identifier used for network communication. By default ModelCenter Remote Execution runs on port 1835.
Probabilistic Analysis Tool A trade study tool used to study the effects of variability in inputs on a bunch of outputs.
Project A feature used to store and organize results from one or more trade studies.
Project Tree The Project Tree is used to display the contents of a Project. The Project Tree is displayed on the left side of the ModelCenter window.
Project Item Any item stored in a Project, for example, an Optimization or Parametric Study.
Project Items Dialog A dialog used to display all the items in a Project. The dialog supports features for sorting and filtering Project Items.
Properties Editor A tool that presents the variable and component properties of a workflow in a concise, tabular form that streamlines the editing of said properties. This tool can also be used for generating a report of a workflow.
RSM Toolkit A toolkit for Response Surface Modeling.  
Scheduler The Scheduler is responsible for maintaining the states of variables and knowing when to run components.
Script Component (Legacy) An Analysis Component that lets the user write the run method directly in ModelCenter using a scripting language.
Server Browser The Server Browser is used to locate components on different servers. The Server Browser is located on the bottom of the ModelCenter window. To instantiate a component, drag it from the Server Browser and drop it into an Analysis View.
Smart Edit Bar The Smart Edit Bar is used to quickly view and edit links without using the Link Editor View. The Smart Edit Bar is located under the toolbar and will display links or values for variables as they are selected in the Component Tree.
Snapshot A Snapshot stores the current values and states of all variables in a workflow. Snapshots can be generated at anytime and stored as part of a Project. The Design History Tool can be used to view, compare, and contrast multiple Snapshots.
Telnet A program used for communicating across a network with another program. To telnet to ModelCenter Remote Execution, type telnet hostname 1835.
Trade Study The process of collecting data from a workflow in some systematic way. ModelCenter supports Optimization, Parametric Study, Design of Experiments (DOE), and Carpet Plot Trade Study tools. Users can define their own third party Trade Studies with the Plug-In Toolkit.
Trade Study Plug-In Trade Study Plug-Ins allow custom optimization, robust design, and other algorithms to be tightly integrated with ModelCenter. Example tools include DAKOTA, NPSOL, and SNOPT. For more information on Plug-Ins in general, see the Plug-In Toolkit.
Valid A state for an output variable. An output is valid after the component that it is an output of has been run. An output will be invalid again after any of the inputs to the component are modified.
Validate The process of requesting a valid value for an output variable. Invalid variables may be validated by clicking on the red X next to them. Validating a variable causes the Scheduler to execute the proper components required to calculate a value.
Variable A single piece of data within a workflow. Variables are usually thought of as inputs or outputs of a component. Output variables may also be valid or invalid. ModelCenter supports several variable types including reals, integers, strings, booleans, and arrays.
Workflow A collection of one or more Components. A workflow is saved in a .pxcz file.
Wrapper An interface around something. The interface translates between the native system's functionality and the desired functionality. For example, a FileWrapper wrapper converts a file input/output-based program into a format usable by ModelCenter.