<?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 = "concept"/><meta name = "abstract" content = "For the consideration of damage data during optimization, a durability analysis is performed after each finite element solver run in the optimization loop. The results of the finite element analysis are directly read in the durability solver and a damage calculation is performed. The results of the damage analysis are provided in a special result block. Then Tosca Structure modifies the components surface based on the damage distribution."/><meta name = "description" content = "For the consideration of damage data during optimization, a durability analysis is performed after each finite element solver run in the optimization loop. The results of the finite element analysis are directly read in the durability solver and a damage calculation is performed. The results of the damage analysis are provided in a special result block. Then Tosca Structure modifies the components surface based on the damage distribution."/><meta name = "DC.format" content = "HTML5"/><meta name = "DC.identifier" content = "tso-c-usr-solver-durab-workflow"/><meta name = "DC.language" content = "en"/><link rel = "stylesheet" type = "text/css" href = "../DSDocUI_XML34.css"/><title>Workflow</title>
<script type = "text/javascript" src = "../DSDocUI_Highlight34.js">
  	/* */
  	</script></head><body onLoad = "highlightSearchTerms();" id = "tso-c-usr-solver-durab-workflow">
<a name = "hj-top"> </a><table class = "table1" id = "table11"><tr><td><table class = "DocHeader"><tr><td class = "DocHeader1" colspan = "2"><h1>Workflow</h1></td></tr><tr><td class = "DocHeader4" colspan = "2"/></tr><tr><td class = "DocHeader3" colspan = "2"><table class = "DocThemeIntro" id = "table12"><tr><td class = "Intro1Only"><p class = "header"><p class = "abstract">
<span class = "shortdesc">For the consideration of damage data during optimization,
a durability analysis is performed after each finite element solver run
in the optimization loop. The results of the finite element analysis
are directly read in the durability solver and a damage calculation is
performed. The results of the damage analysis are provided in a special
result block. Then <span class = "ph">Tosca Structure</span>
modifies the components surface based on the damage distribution.</span>

</p>
<p>This page discusses: </p><ul><li><a href = "#tso-c-usr-solver-durab-workflow__tso-c-usr-solver-durab-workflow-prep" id = "toc_rg" title = "">Preprocessing</a></li><li><a href = "#tso-c-usr-solver-durab-workflow__tso-c-usr-solver-durab-workflow-lifeFile" id = "toc_rg" title = ""> Adding Life File to FEM_INPUT</a></li><li><a href = "#tso-c-usr-solver-durab-workflow__tso-c-usr-solver-durab-workflow-objFun" id = "toc_rg" title = "">Defining the Objective Function</a></li><li><a href = "#tso-c-usr-solver-durab-workflow__tso-c-usr-solver-durab-workflow-startInGUI" id = "toc_rg" title = ""> Starting the  Optimization in <span class = "ph">Tosca Structure.gui</span></a></li><li><a href = "#tso-c-usr-solver-durab-workflow__tso-c-usr-solver-durab-workflow-startInCL" id = "toc_rg" title = "">Starting the Optimization  on the Command Line</a></li><li><a href = "#tso-c-usr-solver-durab-workflow__tso-c-usr-solver-durab-workflow-post" id = "toc_rg" title = "">Post-Processing</a></li></ul>
</p></td></tr></table></td></tr></table>




<div class = "body conbody">
<div class = "section" id = "tso-c-usr-solver-durab-workflow__tso-c-usr-solver-durab-workflow-prep"><h2 class = "title sectiontitle">Preprocessing</h2>

<p>The preprocessing of the durability analysis must be performed additionally
to the finite element and the optimization preprocessing. All control
files must be generated before starting the optimization procedure.
A damage calculation run should be performed in advance to check if
all necessary data is available and the durability analysis runs in batch
mode without any errors.</p>
</div>

<div class = "section" id = "tso-c-usr-solver-durab-workflow__tso-c-usr-solver-durab-workflow-lifeFile"><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"> Adding Life File to FEM_INPUT</h2>

<p><span class = "ph">Tosca Structure</span>
needs information about the used input file(s) for the life solver. This
is added in the <code class = "ph codeph">FEM_INPUT</code> command:</p>
<pre class = "codeblock">
<code class = "ph codeph">
FEM_INPUT
 ID_NAME   = FILE_INFO
 FILE      = static_analysis.ext
 LIFE_FILE = life_input.ext
END_
</code>
</pre>
<div class = "note"><span class = "run-in.note">Note:
			</span><span class = "notecontent"><p><ul class = "ul">
<li class = "li">The name of <code class = "ph codeph">LIFE_FILE</code> might have any name. </li>
<li class = "li">The <code class = "ph codeph">LIFE_FILE</code> command might be repeated more times
for life solvers that support the ONF 601-format (<code class = "ph codeph">DRESP TYPE
= DAMAGE_LC</code>).</li>
</ul></p></span></div>
<p>For some life solvers, it is often needed to add some extra files in the working
directory - files that <span class = "ph">Tosca Structure</span>
not always recognizes as default files. The easiest way to copy these
files into the optimization working directory is by using the <code class = "ph codeph">COPY_FILE</code>
command:</p>
<pre class = "codeblock">
<code class = "ph codeph">
FEM_INPUT
 ID_NAME   = FILE_INFO
 FILE      = static_analysis.ext
 LIFE_FILE = life_input.ext
 COPY_FILE = some_extra_file.ext
 COPY_FILE = some_other_extra_file.ext
END_
</code>
</pre>
<p>In the example above the two files <code class = "ph codeph">some_extra_file.ext</code>
and <code class = "ph codeph">some_other_extra_file.ext</code> are copied into the
working directory at the start of the optimization.</p></div>


<div class = "section" id = "tso-c-usr-solver-durab-workflow__tso-c-usr-solver-durab-workflow-objFun"><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">Defining the Objective Function</h2>

<p>The design response that is referenced in the <code class = "ph codeph">OBJ_FUNC</code>
command must have the <code class = "ph codeph">type = DAMAGE</code>. The objective function
is formulated as a minimization of the maximum damage.</p>
<pre class = "codeblock">
<code class = "ph codeph">DRESP</code><code class = "ph codeph">
 ID_NAME = dresp_damage
 DEF_TYPE = SYSTEM
 ND_GROUP = design_nodes
 TYPE = DAMAGE
 GROUP_OPER = MAX
 UPDATE = EVER</code><code class = "ph codeph">
END_

</code><code class = "ph codeph">OBJ_FUNC</code><code class = "ph codeph">
 ID_NAME = minimize_damage
 DRESP   = dresp_damage
 TARGET  = MIN</code><code class = "ph codeph">
END_
</code>
</pre>
</div>


<div class = "section" id = "tso-c-usr-solver-durab-workflow__tso-c-usr-solver-durab-workflow-startInGUI"><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"> Starting the  Optimization in <span class = "ph">Tosca Structure.gui</span></h2>

<p><ol class = "ol"><li class = "li">Select <span class = "ph uicontrol">Start Tosca</span> as <span class = "ph uicontrol">Module</span>. The damage solver must be specified.</li>
<li class = "li">Select your solver in the <span class = "ph uicontrol">LIFE SOLVER</span> list in the <span class = "ph uicontrol"> additional parameters</span>.</li></ol></p>
<table class = "table" id = "tso-c-usr-solver-durab-workflow__ab1123601"><caption/><colgroup><col/></colgroup><tbody class = "tbody">
<tr class = "row">
<td class = "entry"><br/><img class = "image" src = "../TsoUserImages/solver_tosca_durability.png" width = "450"/><br/><p> Start of <span class = "ph">Tosca Structure</span>
with a durability analysis (<span class = "ph">Tosca Structure.gui</span>)</p></td>
</tr>
</tbody></table>
</div>


<div class = "section" id = "tso-c-usr-solver-durab-workflow__tso-c-usr-solver-durab-workflow-startInCL"><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">Starting the Optimization  on the Command Line</h2>

<p>Specify the damage solver using the <code class = "ph codeph">’--life’</code> flag on the command line. </p><p>Example with Fe-Safe:</p>
<p><pre class = "codeblock">tosca hole_damage --solver mscnastran --life fesafe
</pre></p>
</div>


<div class = "section" id = "tso-c-usr-solver-durab-workflow__tso-c-usr-solver-durab-workflow-post"><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">Post-Processing</h2>

<p>After the optimization is finished, all <span class = "ph">Tosca Structure</span>
post-processing capabilities are available (see <a class = "xref" href = "tso-m-usr-post-sb.htm#tso-m-usr-post-sb" title = "Post-processing of Tosca Structure optimization results consists mainly of visualizing the model changes in the optimization process and regarding plots and tables of optimization relevant values. These data can be combined and provided using Tosca Structure.report. Visualization and processing are done using Tosca Structure.view. Certainly, the analysis results of the single optimization steps can be evaluated in your familiar FE-post-processing system by reading the corresponding solver result file from the SAVE.&lt;ext&gt; directory. Further, the results of your validation run can also be processed in your post-processing environment.">Post-Processing of Optimization Results</a> and <a class = "xref" href = "tso-m-usr-validation-sb.htm#tso-m-usr-validation-sb" title = "In the previous chapter, the visualization of unprocessed optimization results is discussed. Still, in order to be able to use the optimization results, they are to be processed (&#34;smoothed&#34;). In case of a three-dimensional model, the first processed result is the isosurface generated by Tosca Structure.smooth, that can be either written in a required format directly by Tosca Structure.smooth. If the starting model is two-dimensional, the workflow remains basically the same except that the surface simply gets modified and no remeshing is needed. Using Tosca Structure.view, one is able to view the processed optimization results with VTFX files that are also generated by Tosca Structure.smooth. A complete analysis of a finished optimization task can be only achieved by the validation run of the FE solver corresponding to the initial model. External post-processors can be used to generate a model for finite element analysis, using the results of Tosca Structure.smooth as starting point.">Result Transfer and Validation Run</a>).</p>
	<p>In addition, the damage
results might be used for post-processing. The corresponding result files
are stored in the <code class = "ph codeph">SAVE</code> directories of the optimization system.</p>
</div>

</div>

</td></tr></table><script type = "text/javascript" src = "../DSDocUI_Bottom34.js">/* */</script></body>
</html>
