MSC Nastran > Running an Analysis > 3.15 Optimize
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">   
3.15 Optimize
When preparing for an optimization analysis run, select Optimize as the Action on the Analysis application form. This allows setup and submission of SOL 200 jobs.
The functionality is similar and in many cases identical to running a normal analysis as described in Review of the Analysis Form, 250 and other sections in this chapter. Each button and its subordinate form that appears when the Action is set to Optimize is explained briefly below.
Use the Optimize action for sizing optimization and combined sizing and topology optimization. For pure topology, topography and topometry optimization, use the Toptomize action explained in Toptomize, 455.
Button/Subordinate Form:
Description:
Design Study Select...
From this form, select the design study of interest. Design studies can contain multiple design objectives, responses, constraints, and variables. Any particular job can only have one design objective. The specific objective and constraints to be used in an optimization job are selected in the Global Objective / Constraint Select form or they are associated to a solution specific subcase. Design Studies are setup under the Design Study tool under the Tools pull down menu. A Default design study is present if none are previously created, however a design study without any design variable defined will not run through Nastran properly.
Global Obj/Constr Select...
Once a design study has been selected, you may select from this form the specific global design objective and constraints to be active for this job. You can only have one objective in an optimization job. A global objective will override any other objective associated to a solution specific subcase that may be associated to this job, therefore it is not necessary to select a global objective or constraints when defined at the subcase level.
Translation Parameters...
These parameters are described in Translation Parameters, 255 and are not specific to optimization.
Optimization Parameters...
This form is used to define optimization parameter for the job. Parameters set in this form and its subordinate form define some of the values on the DOPTPRM entry. These are explained in the MD Nastran Quick Reference Guide under this entry and the user is referred there for details. Note that no DOPTPRM entry is written if all values are default values. Valid values, such as which optimizer is available, depends on the setting of the Nastran version in the Translation Parameters form described above. Results file formats can also be set in this form as described in Results Output Format, 340.
Direct Text Input...
Use of this form is described in Direct Text Input, 266.
Select Superelements...
Use of this form is described in Select Superelements, 344.
Subcases...
Use of this form is described in Subcases, 346. There are two differences that are significant to this form, however. For optimization, subcases are created based on solution sequence, e.g. Statics 101, Normal Modes 103, etc. You must set the solution sequence on this form before creating the subcase, otherwise the default 101 will be used. Secondly, an additional subordinate form allows you to select existing constraint sets and an objective for the particular subcase being created if necessary. Objectives and constraints are created using the Design Study tool under the Tools pull down menu. Note that not all subcase parameters are identical between a normal analysis and an optmization analysis. Also see the note on Contact below: page 454.
Subcase Select...
Use of this form is described in Subcase Select, 444. One difference is that for optimization you must set the solution type to see the subcases defined for a particular solution sequence. Otherwise by default only SOL 101 subcases are displayed. A selected subcase will display the associated solution sequence number in front of its label.
Analysis Manager...
This gives access to the Analysis Manager for submitting, monitoring, aborting and generally managing a Nastran job. This button will not appear if the Analysis Manager is not installed or licensed.
Note: Using Contact Bodies in Optmization Jobs: Linear contact is supported in optimization jobs (SOL 200). If contact bodies are present in the model and included in the load cases associated to the the subcases created, then the contact bodies will be written to the deck. The most common scenario is using linear contact in optimization jobs to glue non-congruent meshes together. When this feature is used, you must “glue” the bodies together, which requires that you set up the proper contact tables to define body pairs that are properly glued. Usage of the contact table is described in Contact Table, 389.