 |
|
The Objective Node identifies a numeric variable that is computed within the Data Flow as a function of input, output and transfer variables, and it is used as an optimization objective. Any design for which one or more objective does not hold a legal numeric value is considered invalid.
Configuring an objective node requires setting the following parameters:
Name: the name that will be used throughout modeFRONTIER to identify the objective. The name must be unique within the set of node names, and must follow the guidelines for node names.
Description: the node description will appear as tooltip when the mouse stop over the node in the Work Flow canvas.
Enabled: specifies whether the objective must be considered or ignored by scheduler algorithms.
Format: the numeric format that will be used in the various tables to display the value for the objective. The legal syntax for this parameter is described elsewhere (see Section 4.2.7, "Number Format Legal Syntax").
User Expression: the expression that must be used to compute the value for this objective. The expression must be a mathematical function of input and output variables. It can be either inserted manually, or the Expression Editor can be invoked by clicking on the icon next to the expression field.
Type: the objective type. It is used to indicate to the optimization algorithm whether this objective should be minimized (i.e., the best value is minus infinity) or maximized (i.e., the best value is plus infinity).
This node cannot be manually connected to any input. However, the nodes for the variables that are used within the user expression are automatically connected to this node.
This node has no output.
Two error messages can be associated with an objective node:
| 110 | MISSING EXPRESSION | No user expression has been provided |
| -1 | [An expression parser error] | The user expression provided is not a legal expression, and cannot be evaluated properly. The actual message should help the user understand where the problem lies. |
