<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE html
  SYSTEM "about:legacy-compat">
<html xmlns:mml = "http://www.w3.org/1998/Math/MathML" lang = "en"><head><meta charset = "UTF-8"/><meta name = "copyright" content = "(C) Copyright 2020"/><meta name = "DC.rights.owner" content = "(C) Copyright 2020"/><meta name = "DC.type" content = "reference"/><meta name = "abstract" content = "Determines the attributes (nodal boundary conditions) of the FE model that should be loaded in TOSCA_PREP and TOSCA_OPT and which other actions should be considered during loading (for example, automatic determination of the surface nodes). This command must be defined before the FEM_INPUT command in the parameter file to be known during model import."/><meta name = "description" content = "Determines the attributes (nodal boundary conditions) of the FE model that should be loaded in TOSCA_PREP and TOSCA_OPT and which other actions should be considered during loading (for example, automatic determination of the surface nodes). This command must be defined before the FEM_INPUT command in the parameter file to be known during model import."/><meta name = "DC.relation" scheme = "URI" content = "../TsoUserMap/tso-m-usr-model-dataLoadOptions-sb.htm#tso-m-usr-model-dataLoadOptions-sb"/><meta name = "DC.format" content = "HTML5"/><meta name = "DC.identifier" content = "tso-r-cmd-options"/><meta name = "DC.language" content = "en"/><link rel = "stylesheet" type = "text/css" href = "../DSDocUI_XML34.css"/><title>OPTIONS</title>
<script type = "text/javascript" src = "../DSDocUI_Highlight34.js">
  	/* */
  	</script></head><body onLoad = "highlightSearchTerms();" id = "tso-r-cmd-options">
<a name = "hj-top"> </a><table class = "table1" id = "table11"><tr><td><table class = "DocHeader"><tr><td class = "DocHeader1" colspan = "2"><h1>OPTIONS</h1></td></tr><tr><td class = "DocHeader4" colspan = "2"/></tr><tr><td class = "DocHeader3"><table class = "DocHeaderIntro" id = "table12"><tr><td class = "Intro1Only"><p class = "header"><p class = "abstract">
<span class = "shortdesc">
Determines the attributes (nodal boundary conditions) of the FE model that should be
loaded in <code class = "ph codeph">TOSCA_PREP</code> and <code class = "ph codeph">TOSCA_OPT</code> and which other
actions should be considered during loading (for example, automatic determination of the
surface nodes). This command must be defined before the <code class = "ph codeph">FEM_INPUT</code>
command in the parameter file to be known during model import.
</span>

<p>
By default, in <code class = "ph codeph">TOSCA_PREP</code> only the nodes and elements are loaded with
the command <code class = "ph codeph">FEM_INPUT</code>. In <code class = "ph codeph">TOSCA_OPT</code>, all required stresses and
displacements are loaded. In addition, parameters for the output of information during the
optimization might be defined.
<div class = "note collapse"><span class = "run-in.note">Note:
    		</span><span class = "notecontent">The <code class = "ph codeph">OPTIONS</code> command must be before the <code class = "ph codeph">FEM_INPUT</code> command in the parameter file.</span></div>

</p>
</p>
<p>This page discusses: </p><ul><li><a href = "#tso-r-cmd-options__tso-r-cmd-options-readParams" id = "toc_rg" title = "">Read Parameters</a></li><li><a href = "#tso-r-cmd-options__tso-r-cmd-options-optRunParams" id = "toc_rg" title = "">Parameters for the Optimization Run</a></li><li><a href = "#tso-r-cmd-options__tso-r-cmd-options-abaqusParams" id = "toc_rg" title = "">Parameters usable with <span class = "ph">Abaqus</span></a></li><li><a href = "#tso-r-cmd-options__tso-r-cmd-options-NasParams" id = "toc_rg" title = ""> Parameters usable with <span class = "ph">MSC Nastran®</span></a></li><li><a href = "#tso-r-cmd-options__tso-r-cmd-options-outputParams" id = "toc_rg" title = "">Output Parameters</a></li><li><a href = "#tso-r-cmd-options__tso-r-cmd-options-rmk" id = "toc_rg" title = "">Remarks</a></li></ul>
</p></td></tr></table></td><td class = "DocHeader2"><table class = "DocTopicsSeeAlso" id = "table13"><tr><td class = "TopicsTitle">See Also</td></tr></table><table class = "DocTopicsInOtherGuides" id = "table14"><tr><td height = "8px"/></tr><tr><td class = "TopicsTitleNormal">In Other Guides</td></tr><tr><td><a title = "The default settings for loading the FE data can be changed with the OPTIONS command." href = "../TsoUserMap/tso-m-usr-model-dataLoadOptions-sb.htm#tso-m-usr-model-dataLoadOptions-sb">Options for Loading FE Data (OPTIONS)</a></td></tr></table></td></tr></table>




<div class = "body refbody">
<div class = "section" id = "tso-r-cmd-options__tso-r-cmd-options-readParams"><h2 class = "title sectiontitle">Read Parameters</h2>

<table class = "table" id = "tso-r-cmd-options__aa1770514"><caption/><colgroup><col/><col/><col/></colgroup><tbody class = "tbody">
<tr class = "row">
<td class = "entry"><p>READ_SF_IDENT</p></td>
<td class = "entry"/>
<td class = "entry"><p>Determination of the surface nodes for shape optimization while reading the finite element model.</p></td>
</tr>
<tr class = "row">
<td class = "entry"/>
<td class = "entry"><p>= ON</p></td>
<td class = "entry"><p>Surface nodes are identified.</p></td>
</tr>
<tr class = "row">
<td class = "entry"/>
<td class = "entry"><p><span class = "ph uicontrol">= OFF</span></p></td>
<td class = "entry"><p>Surface nodes are not identified.</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>READ_SF_MIDNODE</p></td>
<td class = "entry"/>
<td class = "entry"><p>Treatment of the midside nodes during the determination of the surface nodes.</p></td>
</tr>
<tr class = "row">
<td class = "entry"/>
<td class = "entry"><p>= ON</p></td>
<td class = "entry"><p>Midside nodes are considered during the determination of the surface nodes.</p></td>
</tr>
<tr class = "row">
<td class = "entry"/>
<td class = "entry"><p><span class = "ph uicontrol">= OFF</span></p>
</td>
<td class = "entry"><p>Midside nodes are not considered during the determination of the surface nodes.</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>READ_BC</p></td>
<td class = "entry"/>
<td class = "entry"><p>Treatment of the boundary conditions of the finite element model.</p></td>
</tr>
<tr class = "row">
<td class = "entry"/>
<td class = "entry"><p><span class = "ph uicontrol">= ALL</span></p></td>
<td class = "entry"><p>Boundary conditions are read.</p></td>
</tr>
<tr class = "row">
<td class = "entry"/>
<td class = "entry"><p>= NOT</p></td>
<td class = "entry"><p>No boundary conditions are read.</p></td>
</tr>
<tr class = "row">
<td class = "entry"/>
<td class = "entry"><p>= ID, &lt;<code class = "ph codeph">id_1</code>&gt;, &lt;<code class = "ph codeph">id_2</code>&gt;, ...</p></td>
<td class = "entry"><p>Only some boundary condition sets are read (dependent on the interface).</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>READ_LOAD</p></td>
<td class = "entry"><p><span class = "ph uicontrol">= ON</span></p>
                      <p>= OFF</p></td>
<td class = "entry"><p>Loaded nodes / elements are identified while reading the finite element model.</p></td>
</tr>



<tr class = "row">
<td class = "entry"><p>READ_ELEM_QUALITY</p></td>
<td class = "entry"><p>= ON</p>
                      <p><span class = "ph uicontrol">= OFF</span></p></td>
<td class = "entry"><p>Check the element qualities during the import of the finite element model.</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>GROUP_NAME_COMPATIBILITY</p></td>
<td class = "entry"><p><span class = "ph uicontrol">= YES</span></p>
                      <p>= NO</p></td>
<td class = "entry"><p>Compatibility mode for group names: If a group defined in
                         the solver input file contains blanks, two groups are created: one where the
                         blanks are replaced with underscores '_' and the other with blanks in the name.</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>ALLOW_MISSING_LOADCASES</p></td>
<td class = "entry"><p>= YES</p>
                      <p><span class = "ph uicontrol">= NO</span></p></td>
<td class = "entry"><p>Controls the behavior of the preprocessor if no
                       <span class = "ph">load case</span>
                       is found in the first solver input file: a value of <span class = "ph uicontrol">YES</span> would let the preprocessor continue,
                       while the default value of <span class = "ph uicontrol">NO</span> triggers an error message and stops the execution. This option
                       is useful in a multiple input file scenario where the
                       <span class = "ph">load case</span>
                       definition(s) might appear in the second, third, etc. input files. </p>
</td>
</tr>
</tbody></table>
</div>

<div class = "section" id = "tso-r-cmd-options__tso-r-cmd-options-optRunParams"><p><map name = "FPMap1"><area href = "#hj-top" title = "Back to Top" shape = "rect" coords = "416, 0, 435, 10"/></map><span class = "itemsprite"/></p><h2 class = "title sectiontitle">Parameters for the Optimization Run</h2>

<table class = "table" id = "tso-r-cmd-options__aa1770747"><caption/><colgroup><col/><col/><col/></colgroup><tbody class = "tbody">
<tr class = "row">
<td class = "entry"><p>READ_RESULTS</p></td>
<td class = "entry"/>
<td class = "entry"><p>Checking the presence of the finite element results.</p></td>
</tr>
<tr class = "row">
<td class = "entry"/>
<td class = "entry"><p><span class = "ph uicontrol">= STRICT</span></p></td>
<td class = "entry"><p>Optimization is stopped if results are missing.</p>
</td>
</tr>
<tr class = "row">
<td class = "entry"/>
<td class = "entry"><p>= IGNORE</p></td>
<td class = "entry"><p>Optimization is continued even if some results are missing.</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>IGNORE_NUM_OF_CONSTRAINTS</p></td>
<td class = "entry"><p>= YES</p>
                      <p><span class = "ph uicontrol">= NO</span></p></td>
<td class = "entry"><p>Continue with the optimization if the definition of the problem exceeds the number of 50 constraints.</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>IGNORE_NUM_OF_OBJF_TERMS</p></td>
<td class = "entry"><p>= YES</p>
                      <p><span class = "ph uicontrol">= NO</span></p></td>
<td class = "entry"><p>Continue with the optimization if the definition of the problem exceeds the number of 50 objective functions terms.</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>IGNORE_OBJ_FUNC_TYPE</p></td>
<td class = "entry"><p>= YES</p>
                      <p><span class = "ph uicontrol">=</span><span class = "ph uicontrol">NO</span></p></td>
<td class = "entry"><p>Ignore the limitation for <code class = "ph codeph">MINMAX</code> objective function for controller-based optimization.</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>SHAPE_FORCE_VOLUME</p></td>
<td class = "entry"><p><span class = "ph uicontrol">= ON</span></p>
                      <p>= OFF</p></td>
<td class = "entry"><p>Shape optimization forces volume constraint in the first design cycle.</p>
                      <p>It is not recommended to turn this setting <code class = "ph codeph">OFF</code>. If the mesh
                         is distorted in first iteration, your volume constraint is probably too small
                         or large. Changing this to <code class = "ph codeph">OFF</code> will simply cause more design cycles
                         before the mesh is corrupted.</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>SHAPE_AUTO_REMOVE_INNER_NODES</p></td>
<td class = "entry"><p><span class = "ph uicontrol">= ON</span></p>
                      <p>= OFF</p></td>
<td class = "entry"><p>Shape optimization removes inner nodes from design area automatically. Inner
                         nodes might still cause trouble by certain <code class = "ph codeph">DVCON_SHAPE</code>
                         where inner nodes are not allowed.</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>SHAPE_FORCE_MIDSIDE_INTERPOL</p></td>
<td class = "entry"><p>= YES</p>
                      <p>= NO</p></td>
<td class = "entry"><p>Shape optimization interpolates midside nodes linear if one of the neighbors has been moved.</p>
                      <p>If set to <code class = "ph codeph">YES</code>, midside nodes are always interpolated for mesh smooth elements.
                         </p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>IGNORE_UNKNOWN_NODES</p></td>
<td class = "entry"><p>= YES</p>
                      <p>= NO</p></td>
<td class = "entry"><p>If an input file references nodes that are unknown to
                         <span class = "ph">Tosca Structure</span>,
                         these nodes can be ignored and a warning is printed (<code class = "ph codeph">YES</code>) or the optimization is aborted (<code class = "ph codeph">NO</code>).</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>DISABLE_TET_SELECTION_DETECTION</p></td>
<td class = "entry"><p>=<span class = "ph uicontrol">NO</span></p>
                      <p>= YES</p></td>
<td class = "entry"><p>If tetrahedral elements are located at a corner in such a way that the corner node belongs solely
                         to that element and not all faces of the element shall be considered for normal direction calculation,
                         special effort must be taken to determine the correct or expected direction. This special effort can
                         be disabled by setting this option to <code class = "ph codeph">YES</code>.</p></td>
</tr>





</tbody></table>
</div>


<div class = "section" id = "tso-r-cmd-options__tso-r-cmd-options-abaqusParams"><p><map name = "FPMap1"><area href = "#hj-top" title = "Back to Top" shape = "rect" coords = "416, 0, 435, 10"/></map><span class = "itemsprite"/></p><h2 class = "title sectiontitle">Parameters usable with <span class = "ph">Abaqus</span></h2>

<table class = "table"><caption/><colgroup><col/><col/><col/></colgroup><tbody class = "tbody">
<tr class = "row">
<td class = "entry"><p>USE_ABQ_SENS</p></td>
<td class = "entry"/>
<td class = "entry"><p> This option is obsolete and has no influence on the optimization procedure.</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>SENS_CALC_MODE</p></td>
<td class = "entry">=<span class = "ph uicontrol">AUTOMATIC</span>/SOLVER/TOSCA/HYBRID</td>
<td class = "entry"><p>Controls whether the DRESPs values and sensitivities should be calculated by the solver or by
                         the optimization system. If this option is set to
                         <code class = "ph codeph">AUTOMATIC</code>, the optimization system will
                         chose the best calculation mode. If <code class = "ph codeph">HYBRID</code> is
                         chosen the design response values and the corresponding
                         sensitivities will be calculated by solver if they are supported
                         and by the optimization system for all other cases. To be able
                         to use older versions of <span class = "ph">Abaqus</span>
                         (older than 3DEXPERIENCE2017x FP1721), set <code class = "ph codeph">SENS_CALC_MODE = TOSCA</code>. </p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>SOLVER_RUN_MODE</p></td>
<td class = "entry">=<span class = "ph uicontrol">AUTOMATIC</span>/SEQUENTIAL/SIMULTANEOUS</td>
<td class = "entry"><p>Controls whether the solver should be called (check out licenses, run preprocessor, solve the
                         modified job, output the results, shut down) in each iteration
                         in sequential sessions or a single/simultaneous solver session
                         (start the solver once at the beginning of the optimization,
                         communicate modifications of the model by distribution tables,
                         and solve the job in each iteration, shut down the solver by the
                         end of optimization) should be started. If this option is set to
                         <code class = "ph codeph">AUTOMATIC</code> the optimization system chooses
                         the best solver run mode.</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>ABQ_SENS_ABSENT_SET_ZERO</p></td>
<td class = "entry">=YES/<span class = "ph uicontrol">NO</span></td>
<td class = "entry"><p>In case of using the sensitivities calculated by
                         <span class = "ph">Abaqus</span>,
                         this option controls whether to set the missing sensitivity values to zero or not. This option should be set,
                         for example, when <code class = "ph codeph">*model change</code> command is used in the solver input file. </p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>FORCE_SIM_YES</p></td>
<td class = "entry">=FALSE/<span class = "ph uicontrol">TRUE</span></td>
<td class = "entry"><p>In case of using the sensitivities calculated by
                         <span class = "ph">Abaqus</span>,
                         if mode tracking is present in the analysis this option converts any
                         <code class = "ph codeph">SIM=NO</code> command to <code class = "ph codeph">SIM=YES</code> in the input file.</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>KEEP_SFILM</p></td>
<td class = "entry">=TRUE/<span class = "ph uicontrol">FALSE</span></td>
<td class = "entry"><p>This option turns off the modification of <code class = "ph codeph">*sfilm</code> card during the optimization. It
                         allows the user to keep the original surface film boundary condition throughout
                         the optimization even if the actual surface has changed.</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>USE_ABQ_UNROLL</p></td>
<td class = "entry">= YES/NO/ON/<span class = "ph uicontrol">OFF</span>/SELECTIVE</td>
<td class = "entry"><p>Controls the enrolling of *LOADCASEs inside a *STEP.</p>
                      <div class = "note"><span class = "run-in.note">Note:
			</span><span class = "notecontent">SELECTIVE means that the unrolling only happens if the first *STEP is a preloading step </span></div>
</td>
</tr>
<tr class = "row">
<td class = "entry"><p>NODAL_MODIFICATION</p></td>
<td class = "entry"> = DISTRIBUTION_TABLE /<span class = "ph uicontrol">INPUT_FILE</span></td>
<td class = "entry"><p>Controls how node modifications from shape optimization are communicated to the FE solver. Only
                         usable in combination with solver sensitivities. </p>
                      <p> DISTRIBUTION_TABLE: Write node modifications only in the
                      distribution table. </p>
                      <p> INPUT_FILE: Write node modifications directly into the
                      solver input file.
                      </p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>DRESP_GROUP_OPER_AGGREGATION</p></td>
<td class = "entry">= ON / <span class = "ph uicontrol">OFF</span></td>
<td class = "entry"><p>This option controls if the group in the design response will be evaluated using the existing
                         <span class = "ph">Tosca</span> algorithm or a new algorithm introduced in 2021x based on
                         <span class = "ph">Abaqus</span> sensitivities.
                         The new algorithm provides performance benefits in case of large groups or multiple
                         <span class = "ph">load cases</span>. The
                         default is <code class = "ph codeph">OFF</code> means only the existing algorithm will be used.</p></td>
</tr>
</tbody></table>
</div>

<div class = "section" id = "tso-r-cmd-options__tso-r-cmd-options-NasParams"><p><map name = "FPMap1"><area href = "#hj-top" title = "Back to Top" shape = "rect" coords = "416, 0, 435, 10"/></map><span class = "itemsprite"/></p><h2 class = "title sectiontitle"> Parameters usable with <span class = "ph">MSC Nastran®</span></h2>

<table class = "table"><caption/><colgroup><col/><col/><col/></colgroup><tbody class = "tbody">
<tr class = "row">
<td class = "entry"><p>MSC_NASTRAN_BAILOUT</p></td>
<td class = "entry">= TRUE/<span class = "ph uicontrol">FALSE</span></td>
<td class = "entry"><p>This option writes <code class = "ph codeph">PARAM BAILOUT -1</code> to the modified input file.
                         It ensures that the Nastran analyses will not abort even if there are errors in
                         the model.</p></td>
</tr>
</tbody></table>
</div>


<div class = "section" id = "tso-r-cmd-options__tso-r-cmd-options-outputParams"><p><map name = "FPMap1"><area href = "#hj-top" title = "Back to Top" shape = "rect" coords = "416, 0, 435, 10"/></map><span class = "itemsprite"/></p><h2 class = "title sectiontitle">Output Parameters</h2>

<table class = "table" id = "tso-r-cmd-options__aa1398560"><caption/><colgroup><col/><col/><col/></colgroup><tbody class = "tbody">
<tr class = "row">
<td class = "entry"><p>CONSTRAINT_OUTPUT</p></td>
<td class = "entry"/>
<td class = "entry"><p>Controls the output of the <code class = "ph codeph">CONSTRAINT</code>s in <code class = "ph codeph">TOSCA.OUT</code>.</p></td>
</tr>
<tr class = "row">
<td class = "entry"/>
<td class = "entry"><p><span class = "ph uicontrol">= DEFAULT</span></p></td>
<td class = "entry"><p>Default output is that a satisfied <code class = "ph codeph">CONSTRAINT</code> &lt; 1.0 for the normalized output.
                         It does not matter if the <code class = "ph codeph">CONSTRAINT</code> is <code class = "ph codeph">LE_VALUE</code>,
                         <code class = "ph codeph">GE_VALUE</code> or <code class = "ph codeph">EQ_VALUE</code>.</p></td>
</tr>
<tr class = "row">
<td class = "entry"/>
<td class = "entry"><p>= STANDARD</p></td>
<td class = "entry"><p>Constraint value is normalized with the constraint value.</p></td>
</tr>
<tr class = "row">
<td class = "entry"/>
<td class = "entry"><p>= NONORM</p></td>
<td class = "entry"><p>Do not normalize constraints.</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>REPORT_FILE</p></td>
<td class = "entry"><p><span class = "ph uicontrol">= STANDARD</span></p>
                      <p>= ALL</p>
                      <p>= NONE</p></td>
<td class = "entry"><p>Descriptors of what is printed to the file <code class = "ph codeph">optimization_report.csv</code>. See also section Remarks.</p></td>
</tr>
<tr class = "row">
<td class = "entry"/>
<td class = "entry"><p>= D,F,W,R,C</p></td>
<td class = "entry"><p>See "Code" in the table at section Remarks.</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>PLOT_CTRL_INP_MINUS_REF</p></td>
<td class = "entry"><p>= YES</p>
                      <p><span class = "ph uicontrol">= NO</span></p></td>
<td class = "entry"><p>Plot the <code class = "ph codeph">CTRL_INPUT</code> with the subtracted reference value or with its original value.</p>
                      <p>This can make differences if more than one entry is present for the objective function.</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>DEFAULT_SMOOTH</p></td>
<td class = "entry"><p>= ON</p>
                      <p><span class = "ph uicontrol">= OFF</span></p></td>
<td class = "entry"><p>Default smoothing task (settings corresponding to <code class = "ph codeph">smooth_templates.mac</code>). Only
                         available for topology optimization.</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>DEFAULT_REPORT</p></td>
<td class = "entry"><p><span class = "ph uicontrol">= ON</span></p>
                      <p>= OFF</p></td>
<td class = "entry"><p>Default report generation (settings corresponding to <code class = "ph codeph">report_templates.mac</code>).</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>DEFAULT_REPORT_ON_ERROR</p></td>
<td class = "entry"><p><span class = "ph uicontrol">= ON</span></p>
                      <p>= OFF</p></td>
<td class = "entry"><p>Default report generation when optimization job fails</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>DEFAULT_REPORT_GROUP</p></td>
<td class = "entry"><p><span class = "ph uicontrol">= ALL_ELEMENTS</span></p>
                      <p>= __DESIGN__</p>
                      <p>= __MODEL__</p>
                      <p>= &lt;<code class = "ph codeph">group_name</code>&gt;</p></td>
<td class = "entry"><p>Report generated for all elements, specified group (from
                         analysis model or parameter file) or design area.</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>DEFAULT_SMOOTH_ISOVALUE</p></td>
<td class = "entry"><p>= &lt;<code class = "ph codeph">value</code>&gt;</p></td>
<td class = "entry"><p>Iso value for smoothing (between 0 and 1).</p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>DEFAULT_SMOOTH_VOLUME</p></td>
<td class = "entry"><p>= &lt;<code class = "ph codeph">value</code>&gt;</p>
                      </td>
<td class = "entry"><p>Target volume for smoothing, relative value set by user
                         (between 0 and 1) </p></td>
</tr>
<tr class = "row">
<td class = "entry"><p>DEFAULT_SMOOTH_GROUP</p></td>
<td class = "entry"><p><span class = "ph uicontrol">= ALL_ELEMENTS</span></p>
                      <p>= __DESIGN__</p>
                      <p>= __MODEL__</p>
                      <p>= &lt;<code class = "ph codeph">group_name</code>&gt;</p></td>
<td class = "entry"><p>Smoothing performed for all elements, specified group (from analysis model or parameter file) or design area.</p></td>
</tr>
</tbody></table>
</div>


<div class = "section" id = "tso-r-cmd-options__tso-r-cmd-options-rmk"><p><map name = "FPMap1"><area href = "#hj-top" title = "Back to Top" shape = "rect" coords = "416, 0, 435, 10"/></map><span class = "itemsprite"/></p><h2 class = "title sectiontitle">Remarks</h2>

<ol class = "ol">
<li class = "li">
The <code class = "ph codeph">REPORT_FILE</code> item might be used to change the output in the file
<code class = "ph codeph">optimization_report.csv</code>: Iteration number and value
of the objective function (<code class = "ph codeph">OBJ_FUNC</code>) is always written to
<code class = "ph codeph">optimization_report.csv</code>. This is the only output with option
<code class = "ph codeph">NONE</code>. The default (<code class = "ph codeph">STANDARD</code>) output
is: <code class = "ph codeph">DRESP</code>, <code class = "ph codeph">OBJ_FUNC:DRESP</code>, and
<code class = "ph codeph">CONSTRAINT</code> values. All output in following table is
active with option <code class = "ph codeph">ALL</code>.
</li>
<li class = "li">Using the letter codes in the <code class = "ph codeph">REPORT_FILE</code> item the output might be customized as shown in the table below:
<table class = "table" id = "tso-r-cmd-options__aa2075032"><caption/><colgroup><col/><col/><col/></colgroup><thead class = "thead">
<tr class = "row">
<th class = "entry" id = "tso-r-cmd-options__aa2075032__entry__1"><p>Output name</p></th>
<th class = "entry" id = "tso-r-cmd-options__aa2075032__entry__2"><p>Description</p></th>
<th class = "entry" id = "tso-r-cmd-options__aa2075032__entry__3"><p>Code</p></th>
</tr>
</thead><tbody class = "tbody">
<tr class = "row">
<td class = "entry" headers = "tso-r-cmd-options__aa2075032__entry__1"><p>DRESP</p></td>
<td class = "entry" headers = "tso-r-cmd-options__aa2075032__entry__2"><p>All <code class = "ph codeph">DRESP</code>s referenced in <code class = "ph codeph">OBJ_FUNC</code> real values.</p></td>
<td class = "entry" headers = "tso-r-cmd-options__aa2075032__entry__3"><p>D</p></td>
</tr>
<tr class = "row">
<td class = "entry" headers = "tso-r-cmd-options__aa2075032__entry__1"><p>OBJ_FUNC:DRESP</p></td>
<td class = "entry" headers = "tso-r-cmd-options__aa2075032__entry__2"><p>The value of <code class = "ph codeph">DRESP</code> in <code class = "ph codeph">OBJ_FUNC </code>[weight*(dresp_value – ref_value)].</p></td>
<td class = "entry" headers = "tso-r-cmd-options__aa2075032__entry__3"><p>F</p></td>
</tr>
<tr class = "row">
<td class = "entry" headers = "tso-r-cmd-options__aa2075032__entry__1"><p>OBJ_FUNC: DRESP:Weight</p></td>
<td class = "entry" headers = "tso-r-cmd-options__aa2075032__entry__2"><p>Weight of <code class = "ph codeph">DRESP</code> in <code class = "ph codeph">OBJ_FUNC</code>.</p></td>
<td class = "entry" headers = "tso-r-cmd-options__aa2075032__entry__3"><p>W</p></td>
</tr>
<tr class = "row">
<td class = "entry" headers = "tso-r-cmd-options__aa2075032__entry__1"><p>OBJ_FUNC:DRESP:Ref</p></td>
<td class = "entry" headers = "tso-r-cmd-options__aa2075032__entry__2"><p>Reference value of <code class = "ph codeph">DRESP</code> in
                         <code class = "ph codeph">OBJ_FUNC</code>. This value can be interesting for shape optimization.</p></td>
<td class = "entry" headers = "tso-r-cmd-options__aa2075032__entry__3"><p>R</p></td>
</tr>
<tr class = "row">
<td class = "entry" headers = "tso-r-cmd-options__aa2075032__entry__1"><p>CONSTRAINT</p></td>
<td class = "entry" headers = "tso-r-cmd-options__aa2075032__entry__2"><p>The value of <code class = "ph codeph">DRESP</code> in <code class = "ph codeph">CONSTRAINT</code>s</p></td>
<td class = "entry" headers = "tso-r-cmd-options__aa2075032__entry__3"><p>C</p></td>
</tr>
</tbody></table>
</li>
<li class = "li">
Default result reports and smooth runs can be activated in the
parameter file to be created after the optimization (an example can be found in
the macro <code class = "ph codeph">report_templates.mac</code>). To get a
report with your topology optimization results including the smoothed model
with a defined iso value, you could add the following to
your parameter file:
</li>
<li class = "li">
<pre class = "codeblock">
<code class = "ph codeph">
OPTIONS
  DEFAULT_SMOOTH                = ON
  DEFAULT_REPORT                = ON
  DEFAULT_REPORT_GROUP          = ALL_ELEMENTS
  DEFAULT_SMOOTH_ADD_TO_REPORT  = ON
  DEFAULT_SMOOTH_VOLUME         = &lt;<code class = "ph codeph">value</code>&gt;
  DEFAULT_SMOOTH_GROUP          = ALL_ELEMENTS
END_
</code>
</pre>
</li>
</ol>
</div>

</div>

<div class = "related-links"/>
</td></tr></table><script type = "text/javascript" src = "../DSDocUI_Bottom34.js">/* */</script></body>
</html>
