When editing the Optimization cell of a goal-driven optimization system, selecting the Objectives and Constraints node in the Outline view allows you to define design goals in the Table view in the form of the objectives and constraints to use to generate optimized designs. You can set additional optimization properties in the Properties view. The optimization approach used in the design exploration environment departs in many ways from traditional optimization techniques, giving you added flexibility in obtaining the desired design configuration.
Note: If you are using an external optimizer, DesignXplorer filters objectives and constraints according to the optimization method selected, displaying only the types that the method supports. For example, if you have selected an optimizer that does not support the Maximize objective type, DesignXplorer does not display as a choice for .
The following optimization settings are available in both the Table and Properties view.
Allows you to define an objective for each parameter. If desired, you can also enter
a name for the objective. Each objective is given a default name based on its defined
properties that is updated each time the objective is modified. For example, when an
objective is defined to Minimize parameter P1,
the objective name is set to Minimize P1. If the objective type
is changed to Maximize, the objective name becomes
Maximize P1. Then, if a constraint type of Values
>= Bound is added and Lower Bound is set to
3, the objective name becomes Maximize P1; P1 >=
3. The name is displayed under the Objectives and
Constraints node in the Outline view.
The Objective Name property also allows you to edit the name of the objective. In the Outline view, you can edit the name of an objective. Additionally, you can select the Objectives and Constraints node and edit the name in the Table view. You can also select the objective in the Outline view and edit the name in either the Properties or Table view. Once you edit Objective Name, the name persists and is no longer changed by modifications to the objective. To resume the automated naming system, you must delete the custom name, leaving the property empty.
Available options depend on the type of parameter and whether it is an input or output.
| Parameter Type | Supported Settings |
|---|---|
| Continuous input without manufacturable variables | Objective only |
| Continuous input with manufacturable variables | Constraint only |
| Discrete input | Constraint only |
| Output | Objective and Constraint |
Allows you to select the input or output parameter for which the objective or constraint is being defined.
Available for continuous input parameters without manufacturable values and output parameters. Allows you to define an objective by specifying the objective type. See the following tables for available objective types.
Available for continuous input parameters with manufacturable values, discrete input parameters, and output parameters. Allows you to define a constraint by specifying the constraint type. See the following tables for available constraint types.
For a parameter that has Objective Type set to Seek Target, allows you to specify the target value for the objective.
For a parameter with a constraint type other than Lower Bound <=
Values <= Upper Bound, set Lower Bound to the
target value for the constraint.
For a parameter with a constraint type of Lower Bound <= Values <=
Upper Bound, set both Lower Bound and Upper
Bound to define an acceptable range for the output. The second value must
be greater than the first. Available only for continuous output parameters.

Objectives for Continuous Input Parameters
| Objectives | Description | Mathematical Meaning |
|---|---|---|
| (X = an input parameter, XLower = lower limit, XUpper = Upper Limit) | ||
| No Objective | Keep the input parameter within its upper and lower bounds. | XLower <= X <= XUpper |
| Minimize | Minimize the input parameter within its range. | X → XLower |
| Maximize | Maximize the input parameter within its range. | X → XUpper |
| Seek Target |
Achieve an input parameter value that is close to the objective target . | X → XTarget |
Objectives for Output Parameters
| Objective | Description | Mathematical Meaning | GDO Treatment |
|---|---|---|---|
| (Y = output parameter, YTarget = Target) | |||
| No Objective | No objective is specified. | N/A | N/A |
| Minimize | Achieve the lowest possible value for the output parameter. | Minimize Y | Objective |
| Maximize | Achieve the highest possible value for the output parameter. | Maximize Y | Objective |
| Seek Target |
Achieve an output parameter value that is close to the objective target. | Y → YTarget | Objective |
Constraints for Discrete Input Parameters or Continuous Input Parameters with Manufacturable Values
| Constraints | Description | Mathematical Meaning |
|---|---|---|
| (X = an input parameter, XLower = Lower Bound, XUpper = Upper Bound, XTarget = Target) | ||
| No Constraint | Uses the full discrete range allowed for the parameter. | XLower <= X <= XUpper |
| Values = Bound |
Set the constraint to in-range values close to the lower bound. | X → XLowerBound |
| Values >= Lower Bound | Set the constraint to in-range values above the lower bound. | X >= XLowerBound |
| Values <= Upper Bound | Set the constraint to in-range values below the lower bound. | X <= XUpperBound |
Constraints for Output Parameters
| Constraints | Description | Mathematical Meaning | GDO Treatment |
|---|---|---|---|
| (Y = output parameter, YTarget = Target) | |||
| No Constraint | No constraint is specified. | N/A | N/A |
| Values = Bound | If a lower bound is specified, then achieve an output parameter value that is close to that bound. | Y → YLowerBound | Constraint |
| Values >= Lower Bound | If a lower bound is specified, then achieve an output parameter value that is above the bound. | Y > =YLowerBound | Inequality constraint |
| Values <= Upper Bound | If an upper bound is specified, then achieve an output parameter value that is below that bound. | Y <= YUpperBound | Inequality constraint |
|
Lower Bound <= Values <= Upper Bound |
If a lower bound and upper bound are specified, then achieve an output parameter that is within the defined range. | YLowerBound <= Y <=
YUpperBound given YLowerBound < YUpperBound | Constraint |
The following postprocessing properties are available and editable under Decision Support Process in the Properties view:
For any parameter with an objective or constraint defined, allows you to select the relative importance of that parameter in regard to the other objectives. The choices are , , and .
For each parameter that has a constraint type of Lower Bound <= Values
<= Upper Bound, allows you to enter a value for the Lower
Bound and Upper Bound, defining an acceptable range
for the output. The second value must be greater than the first. Available only for
continuous output parameters.
For any constrained parameter, allows you to specify the constraint handling for that parameter.
This option can be used for any optimization application and is best thought of as a "constraint satisfaction" filter on samples generated from optimization runs. This is especially useful for screening samples to detect the edges of solution feasibility for highly constrained nonlinear optimization problems. Choices are:
Relaxed: Samples are generated in the full parameter space, with the constraint only being used to identify the best candidates. When this option is selected, the upper, lower, and equality constrained objectives of the candidate points are treated as objectives. Therefore, any violation of the objective is still considered feasible.
Strict (default): Samples are generated in the reduced parameter space defined by the constraint. When this option is selected, the upper, lower, and equality constraints are treated as hard constraints. If any of these constraints is violated, the candidate point is no longer shown.

Objective and Constraint Requirements According to Optimization Method:
Screening uses the goals that are defined to color the samples in the Samples chart. It does not have any requirements concerning the number of objectives or constraints defined.
MOGA and Adaptive Multiple-Objective require that an objective is defined for at least one output parameter. This means that an objective type must be selected for at least one of the output parameters and that an objective value is defined. Multiple output objectives are allowed.
NLPQL, MISQP, and Adaptive Single-Objective require that an objective is defined for one output parameter. This means than an objective type must be selected as one of the output parameters and that an objective value is defined. Only a single output objective is allowed.
Non-Screening Optimization: When any method other than Screening is used for goal-driven optimization, the search algorithm uses the objective type and target value and the constraint type and target range of the output parameters, ignoring the similar properties of the input parameters. However, when the candidate points are reported, either the first Pareto fronts (for MOGA and Adaptive Multiple-Objective) or the best solution set (for NLPQL, MISQP, and Adaptive Single-Objective) are filtered through a decision support process that applies the objectives and constraints for the parameter and reports the returned candidate points. The candidate points do not necessarily correspond to the best input targets, but they do provide the best designs with respect to the output properties.
Screening Optimization: The Screening method is not strictly an optimization approach. It uses the properties of both the input and output parameters. Additionally, it uses the decision support process on a sample set generated by the Shifted Hammersley technique to rank and report the candidate points. The candidate points correspond to both the specified input and output objectives, although the candidate points do not correspond to the best optimal solutions.