OPTIMIZE


ID_NAME	= <`id_name_of_optimize`>	Name of the optimization problem.
DV	= <`name_of_DV_TOPO`> = <`name_of_DV_SHAPE`> = <`name_of_DV_BEAD`> = <`name_of_DV_SIZING`> = <`name_of_DV_GENERIC`>	Name of a `DV_TOPO`, `DV_SHAPE`, `DV_BEAD`, `DV_SIZING` or `DV_GENERIC` entry.
OBJ_FUNC	=<`name_of_OBJ_FUNC`>	Name of the `OBJ_FUNC` definition.
DVCON	= <`name_of_DVCON_TOPO`> = <`name_of_DVCON_SHAPE`> = <`name_of_DVCON_BEAD`> = <`name_of_DVCON_SIZING`> = <`name_of_DVCON_GENERIC`> = <`family_name_dvcon_entries`>*	Name of a `DVCON_TOPO`, `DVCON_SHAPE`, `DVCON_BEAD`, `DVCON_SIZING` or `DVCON_GENERIC` entry or a name log followed by '*'.
CONSTRAINT	=<`name_of_CONSTRAINT`>	Name of a `CONSTRAINT` definition.
MESH_SMOOTH	=<`name_of_MESH_SMOOTH`>	Name of a `MESH_SMOOTH` definition.
STRATEGY	=<`Optimization strategy`> = BEAD_SENSITIVITY = BEAD_CONTROLLER = SIZING_SENSITIVITY = SHAPE_CONTROLLER = SHAPE_SENSITIVITY = TOPO_SENSITIVITY = TOPO_CONTROLLER	Name of the optimization strategy which should be used.

Remarks

Several DVCON entries can be referenced together. It is possible to only enter the name log followed by '*'. For example, DVCON = MY_DVCON_* means the same as DVCON = MY_DVCON_1, DVCON=MY_DVCON_2, DVCON=MY_DVCON_XXX etc.
There is only one CONSTRAINT for controller-based shape, bead, and topology optimization.
For sensitivity-based topology, shape, bead, and sizing optimization there are several entries for the item CONSTRAINT possible.
If no MESH_SMOOTH entry is referenced in shape optimization (MESH_SMOOTH with the name <id_name_of_optimize>), an attached character string '_MESH' is internally created and allocated to OPTIMIZE.
In shape optimization, the DVCON entries have the sequence according to their order in OPTIMIZE. Nodes can be addressed several times. The DVCON entries already entered can be modified by the following DVCON entries.
Only for topology optimization a user-defined controller input is specified in the OPTIMIZE command. For shape and bead optimization the controller input can be referenced in the DRESP command.
For easing the change of strategy from sensitivity-based to controller strategy, inequality constraints are accepted for controller strategy as well. This means you can change from a sensitivity-based topology optimization to controller-based by simply changing the STRATEGY parameter in OPTIMIZE - assuming that the optimization problem is admissible for both strategies, that is, minimize compliance with a volume constraint.

Examples

OPTIMIZE
  ID_NAME     = SHAPE_OPTIMIZATION
  DV          = DESIGN_NODES
  DVCON       = DVCON_FIX_*
  OBJ_FUNC    = MISES_STRESS
  CONSTRAINT  = CONSTANT_VOLUME
  MESH_SMOOTH = EL_OF_MESH_SMOOTH
  STRATEGY    = SHAPE_CONTROLLER
END_

Controller-based topology optimization:

OPTIMIZE
  ID_NAME    = TOPOLOGY_OPTIMIZATION
  DV         = DESIGN_ELEMENTS
  DVCON      = DVCON_FROZEN
  DVCON      = DVCON_CAST
  OBJ_FUNC   = MIN_ENERGY
  CONSTRAINT = CONSTR_VOLUME
  STRATEGY   = TOPO_CONTROLLER
END_

Sensitivity-based topology optimization:

OPTIMIZE
  ID_NAME    = TOPOLOGY_OPTIMIZATION
  DV         = DESIGN_ELEMENTS
  DVCON      = DVCON_FROZEN
  DVCON      = DVCON_CAST
  OBJ_FUNC   = MIN_ENERGY
  CONSTRAINT = CONSTR_VOLUME
  CONSTRAINT = CONSTR_DISP_X_113
  CONSTRAINT = CONSTR_REACTFORCE_1
  STRATEGY   = TOPO_SENS
END_