Keyword type: step

With *CONSTRAINT one can define constraints on design responses in a feasible direction step. It can only be used for design variables of type COORDINATE. Furthermore, exactly one objective function has to be defined within the same feasible direction step (using the *OBJECTIVE keyword).

A constraint is an inequality expressing a condition on a design response function. The inequality can be of type “smaller than or equal” (LE) or “larger than or equal” (GE). The reference value for the inequality is to be specified by a relative portion of an absolute value (the latter in the units used by the user). For instance, suppose the user introduces an absolute value of 20 and a relative value of 0.9 for a LE constraint on the mass. Than the mass is not allowed to exceed 0.9 $ \times$ 20 = 18 mass units. If the absolute value is zero, the initial value is taken, e.g. for the mass this corresponds to the mass at the start of the calculation. If no relative value is given 1. is taken.

Right now, the following design responses are allowed:

First line:

Second line:

Repeat this line if needed.



specifies that the mass of element set E1 should not exceed 3 in the user's units.

Example files: opt1.