-
-
Notifications
You must be signed in to change notification settings - Fork 34
/
OBJECTIVE.html
6 lines (5 loc) · 1.46 KB
/
OBJECTIVE.html
1
2
3
4
5
6
<html><head><link rel="stylesheet" type="text/css" href="style.css"/></head><body> <H2> <BR> *OBJECTIVE </H2> <P> Keyword type: step <P> With *OBJECTIVE one can define the objective function for which a feasible direction shall be computed in a *FEASIBLE DIRECTION step. The feasible direction is basically the sensitivity of a design response function defined as objective, possibly corrected by design responses defined as constraints and/or geometric constraints. Right now, the calculation of a feasible direction can only be done for TYPE=COORDINATE design variables. The objective function can be any design response function defined in a previous *SENSITIVITY step. It is referred to by using its name given on the *DESIGN RESPONSE line. <P> There is one optional parameter TARGET. If TARGET=MIN (= default) the sensivity is calculated for a minization of the objective, if TARGET=MAX for a maximization. The difference comes into play when determining which constraints are active. Exactly one *OBJECTIVE keyword is required in a *FEASIBLE DIRECTION step. This keyword has to be followed by exactly one design response name. <P> <P><P> <BR> <P> First line: <UL> <LI>*OBJECTIVE. </LI> <LI>the parameter target, if needed. </LI> </UL> <P> Second line: <UL> <LI>name of a design response </LI> </UL> <P> <PRE>
Example:
*OBJECTIVE
DR1
</PRE> <P> defines the design response with name DR1 as the objective. <P> <P><P> <BR> Example files: opt1, opt3. <P> </body></html>