<?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 = "Within this section, the durability solver FEMFAT® is discussed."/><meta name = "description" content = "Within this section, the durability solver FEMFAT® is discussed."/><meta name = "DC.format" content = "HTML5"/><meta name = "DC.identifier" content = "tso-c-usr-solver-durab-femfat"/><meta name = "DC.language" content = "en"/><link rel = "stylesheet" type = "text/css" href = "../DSDocUI_XML34.css"/><title>FEMFAT®</title>
<script type = "text/javascript" src = "../DSDocUI_Highlight34.js">
  	/* */
  	</script></head><body onLoad = "highlightSearchTerms();" id = "tso-c-usr-solver-durab-femfat">
<a name = "hj-top"> </a><table class = "table1" id = "table11"><tr><td><table class = "DocHeader"><tr><td class = "DocHeader1" colspan = "2"><h1><span class = "ph">FEMFAT®</span></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">Within this section, the durability solver <span class = "ph">FEMFAT®</span> is discussed.</span>

</p>
<p>This page discusses: </p><ul><li><a href = "#tso-c-usr-solver-durab-femfat__tso-c-usr-solver-durab-femfat-gen" id = "toc_rg" title = "">General</a></li><li><a href = "#tso-c-usr-solver-durab-femfat__tso-c-usr-solver-durab-femfat-changes" id = "toc_rg" title = "">Changes in the <span class = "ph">FEMFAT®</span> FFJ File</a></li><li><a href = "#tso-c-usr-solver-durab-femfat__tso-c-usr-solver-durab-femfat-batch" id = "toc_rg" title = "">Start of <span class = "ph">FEMFAT®</span> in BATCH mode</a></li></ul>
</p></td></tr></table></td></tr></table>




<div class = "body conbody">
<div class = "section" id = "tso-c-usr-solver-durab-femfat__tso-c-usr-solver-durab-femfat-gen"><h2 class = "title sectiontitle">General</h2>

<p>For a shape optimization with <span class = "ph">Tosca Structure</span> in combination with <span class = "ph">FEMFAT®</span>, special results must be requested in the <span class = "ph">FEMFAT®</span> preprocessing. The requested results files can be read by <span class = "ph">Tosca Structure</span> and allow the correct interfacing of the two software packages. Note that when using <span class = "ph">FEMFAT®</span> together with <span class = "ph">Nastran</span>, only <span class = "ph">Nastran</span> mode i4 is allowed. </p>
<p>The following result formats for <span class = "ph">Tosca Structure</span>
might be requested in <span class = "ph">FEMFAT®</span>:</p>
<ul class = "ul">
<li class = "li"><code class = "ph codeph">ONF 600 </code><span class = "ph">Tosca Structure</span>
optimization neutral file. This data block contains a node list and a
damage value for each node.</li>
<li class = "li"><code class = "ph codeph">ONF 601 </code><span class = "ph">Tosca Structure</span> optimization neutral file with <span class = "ph">load case</span> information. This additional data block contains <span class = "ph">load case</span> information. This allows several <span class = "ph">FEMFAT®</span> Basic calculations that might later be combined in <span class = "ph">Tosca Structure</span>.</li>
</ul>
<table class = "Remark" id = "table132"><tr><td class = "Remark"><span class = "run-in.important">Important:
				</span><span class = "notecontent"><p>The type of <code class = "ph codeph">DRESP</code> determines the result format. Use:</p>
<pre class = "codeblock"><code class = "ph codeph">TYPE = DAMAGE          ! For ONF 600</code>
<code class = "ph codeph">TYPE = DAMAGE_LC       ! For ONF 601</code></pre>
<p>It is important that the result from the life analysis has the same name
as the life-solver input file except for the file extension.</p></span></td></tr></table>
<p>For example:</p>
<pre class = "codeblock"><code class = "ph codeph">&lt;life_input_file&gt;.ffj</code>
</pre>
<p>must produce a results file called:</p>
<pre class = "codeblock"><code class = "ph codeph">&lt;life_input_file&gt;_600.onf  (or &lt;life_input_file&gt;_601.onf)</code>
</pre>
<table class = "Remark" id = "table132"><tr><td class = "Remark"><span class = "run-in.important">Important:
				</span><span class = "notecontent"><p>If the latter file does not exist in the working directory of the
<span class = "ph">Tosca Structure</span>
Job, the optimization will stop due to missing results. A corresponding
error message will be output to the user.</p></span></td></tr></table>

<table class = "table" id = "tso-c-usr-solver-durab-femfat__ab1123808"><caption/><colgroup><col/></colgroup><tbody class = "tbody">
<tr class = "row">
<td class = "entry"><br/><img class = "image" src = "../TsoUserImages/solver_femfat.png" width = "500"/><br/></td>
</tr>
</tbody></table>

<table class = "Remark" id = "table132"><tr><td class = "Remark"><span class = "run-in.important">Important:
				</span><span class = "notecontent"><p> For all design nodes that are used for shape optimization a damage value must be provided. So
          the area for damage calculation can be reduced to the design area to save calculation
          time.</p></span></td></tr></table>
</div>


<div class = "section" id = "tso-c-usr-solver-durab-femfat__tso-c-usr-solver-durab-femfat-changes"><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">Changes in the <span class = "ph">FEMFAT®</span> FFJ File</h2>

<p>During the fatigue life simulation preprocessing, the user selects the finite element solver
        results file interactively in <span class = "ph">FEMFAT®</span>. While exporting the <code class = "ph codeph">ffj</code> file, the absolute path settings for the stress
        input file(s) are stored to the control file. </p>
<pre class = "codeblock">
<code class = "ph codeph">setValue {0 {{setValue {} {} StressFileDatasetNumber 0}}} {0 ok}  StressInputFile C:\scratch\holeplate_dam.op2
</code>
</pre>
<p>If <span class = "ph">FEMFAT®</span> is called inside the <span class = "ph">Tosca Structure</span> optimization loop, it must be ensured, that <span class = "ph">FEMFAT®</span> is reading the modified stress data in each design cycle. The new results files are
        always generated in the <span class = "ph">Tosca Structure</span> optimization working directory. So <span class = "ph">Tosca Structure</span> is automatically modifying the <code class = "ph codeph">ffj</code> file and adapting the path of the
        stress input(s) to a relative path into the actual working directory. This is admissible as
        during the optimization procedure, <span class = "ph">FEMFAT®</span> is always running in the <span class = "ph">Tosca Structure</span> working directory.</p>
<pre class = "codeblock">
<code class = "ph codeph">setValue {0 {{setValue {} {} StressFileDatasetNumber 0}}} {0 ok}  StressInputFile ./holeplate_dam.op2
</code></pre>
<table class = "Remark" id = "table132"><tr><td class = "Remark"><span class = "run-in.important">Important:
				</span><span class = "notecontent"><p>Be careful: if a <span class = "ph">FEMFAT®</span> analysis should be executed outside <span class = "ph">Tosca Structure</span> based on a <span class = "ph">Tosca Structure</span>-modified <span class = "ph">FEMFAT®</span> input file. If <span class = "ph">FEMFAT®</span> is not running in the directory where the <code class = "ph codeph">ffj</code> file is located, the
          stress results files might not be found and <span class = "ph">FEMFAT®</span> will stop with an appropriate error message.</p></span></td></tr></table>

</div>

<div class = "section" id = "tso-c-usr-solver-durab-femfat__tso-c-usr-solver-durab-femfat-batch"><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">Start of <span class = "ph">FEMFAT®</span> in BATCH mode</h2>

<p>For the optimization, <span class = "ph">FEMFAT®</span> must run in batch mode. The following files must exist:
</p>
<ul class = "ul">
<li class = "li">Solver Input file(s) (<code class = "ph codeph">*.bdf, *.inp, *.cdb, ...</code>)</li>
<li class = "li"><span class = "ph">FEMFAT®</span> Jobfile <code class = "ph codeph">*.ffj</code> <p>The <span class = "ph">FEMFAT®</span> job file name and
the FE-input file name are not required to be the same.</p></li>
</ul>
<p>At the end of the job file, the <span class = "ph">FEMFAT®</span> calculation must be started. The
following entry must exist in the job file:</p>
<pre class = "codeblock"><code class = "ph codeph">setValue {} {} StartAnalysisLoop
</code></pre>
<p>This can be realized easily by exporting the <code class = "ph codeph">ffj</code> file from the <span class = "ph">FEMFAT®</span>
application after the execution of the analysis.</p>
<p>The <span class = "ph">FEMFAT®</span> batch run should be tested before the complete optimization
is started. The command line for a <span class = "ph">FEMFAT®</span> batch run is the following:</p>
<p><span class = "ph">Windows</span>:</p>
<pre class = "codeblock"><code class = "ph codeph">&lt;femfat_install&gt;\bin\femfat.bat -job=&lt;jobname&gt;.ffj
</code></pre>
<p><span class = "ph">Linux</span>:</p>
<pre class = "codeblock"><code class = "ph codeph">&lt;femfat_install&gt;/bin/femfat -job=&lt;jobname&gt;.ffj
</code></pre>
</div>


</div>

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