<?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 = "This section describes the different kinds of input files."/><meta name = "description" content = "This section describes the different kinds of input files."/><meta name = "DC.format" content = "HTML5"/><meta name = "DC.identifier" content = "tso-c-usr-model-femInputFiles"/><meta name = "DC.language" content = "en"/><link rel = "stylesheet" type = "text/css" href = "../DSDocUI_XML34.css"/><title>FEM_INPUT Files</title>
<script type = "text/javascript" src = "../DSDocUI_Highlight34.js">
  	/* */
  	</script></head><body onLoad = "highlightSearchTerms();" id = "tso-c-usr-model-femInputFiles">
<a name = "hj-top"> </a><table class = "table1" id = "table11"><tr><td><table class = "DocHeader"><tr><td class = "DocHeader1" colspan = "2"><h1>FEM_INPUT Files</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">This section describes the different kinds of input files.</span>

</p>
<p>This page discusses: </p><ul><li><a href = "#tso-c-usr-model-femInputFiles__tso-c-usr-model-femInputFiles-life" id = "toc_rg" title = "">LIFE_FILE</a></li><li><a href = "#tso-c-usr-model-femInputFiles__tso-c-usr-model-femInputFiles-temperature" id = "toc_rg" title = "">TEMPERATURE_FILE</a></li><li><a href = "#tso-c-usr-model-femInputFiles__tso-c-usr-model-femInputFiles-add" id = "toc_rg" title = "">ADD_FILE</a></li><li><a href = "#tso-c-usr-model-femInputFiles__tso-c-usr-model-femInputFiles-copy" id = "toc_rg" title = "">COPY_FILE</a></li><li><a href = "#tso-c-usr-model-femInputFiles__tso-c-usr-model-femInputFiles-specialCommands" id = "toc_rg" title = "">Special FEM_INPUT Commands</a></li></ul>
</p></td></tr></table></td></tr></table>




<div class = "body conbody">
<div class = "section" id = "tso-c-usr-model-femInputFiles__tso-c-usr-model-femInputFiles-life"><h2 class = "title sectiontitle">LIFE_FILE</h2>

<p>Is used to define input files for the durability solver (life_solver).
See <a class = "xref" href = "tso-m-usr-solver-durab-sb.htm#tso-m-usr-solver-durab-sb" title = "The homogenization of the stresses on a components surface often indirectly leads to a reduction of the maximum damage in these areas. In SIMULIA Tosca Structure, a durability analysis can be included in the optimization loop. The direct use of damage results for the homogenization strategy leads to a minimization of the maximum damage in the critical areas. In SIMULIA Tosca Structure, the damage values must be provided as equivalent stress values. The coupling of a durability analysis enables the consideration of the load-time histories. The notions fatigue, durability, and life analysis will all be used in the following as the same thing.">Shape Optimization Based on a Durability Analysis</a>.</p>
</div>

<div class = "section" id = "tso-c-usr-model-femInputFiles__tso-c-usr-model-femInputFiles-temperature"><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">TEMPERATURE_FILE</h2>

<p>This parameter allows <span class = "ph">Abaqus</span>
users to specify an <span class = "ph">Abaqus</span>
input file for a sequential temperature analysis. First, a temperature
calculation is carried out, of which the results are used as boundary
conditions for the following finite element calculation.</p>
<p>The input file, which is used for the temperature calculation, can
be specified using the <code class = "ph codeph">TEMPERATURE_FILE</code> command. All
model changes due to the optimization are also changed to the temperature
model.</p>
</div>

<div class = "section" id = "tso-c-usr-model-femInputFiles__tso-c-usr-model-femInputFiles-add"><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">ADD_FILE</h2>

<p>In certain circumstances, it is useful to define additional nodes and
elements in the optimization model that are not required in the FE analysis.
In this case,   it is practical to write the additional nodes and elements
in a separate file. This file can be read using the item the 
<code class = "ph codeph">FEM_INPUT</code> definition in <span class = "ph">Tosca Structure.gui</span>.</p>
<p>For example, these additionally loaded elements can be used to define
restriction areas of any form. To simplify the selection of the elements
in the parameter file, it is recommended to assign these elements with
specific element properties, which can be used as selection criteria.</p>
<p>Remarks</p>
<ol class = "ol">
<li class = "li">The item <code class = "ph codeph">ADD_FILE</code> can be repeated several times. All nodes and elements stored
          in the file referenced with this item are not available for the optimization. This item
          can be used for the specification of neighboring elements for the definition of
          manufacturing constraints.</li>
<li class = "li"><span class = "ph">SIMULIA Tosca Structure</span> cannot manage double numbers. The user should be aware of this and be sure that there
          is no conflict of numbers during file loading (for example, elements with identical numbers in
          the different files in the <code class = "ph codeph">MODEL_LINK</code> or <code class = "ph codeph">FEM_INPUT</code>
          command). </li>
</ol>
</div>

<div class = "section" id = "tso-c-usr-model-femInputFiles__tso-c-usr-model-femInputFiles-copy"><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">COPY_FILE</h2>

<p>The <code class = "ph codeph">COPY_FILE</code> command is the easiest way to copy
a file into the working directory of <span class = "ph">Tosca Structure</span>.
This could be an extra configuration file for your FE-solver or another
file that has no direct influence on <span class = "ph">Tosca Structure</span>.</p>
<p>The item might be repeated several times.</p>
<p>Example:</p>
<p>If the file <code class = "ph codeph">my_copy_file</code> should be present in the
working directory, for example, because it is required by the user’s solver
or for use in a script call, it could be copied as follows:</p>
<pre class = "codeblock">
<code class = "ph codeph">FEM_INPUT
  ID_NAME        = optimization_model
  FILE           = holeplate.inp
  COPY_FILE      = my_copy_file
END_
</code></pre>
</div>

<div class = "section" id = "tso-c-usr-model-femInputFiles__tso-c-usr-model-femInputFiles-specialCommands"><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">Special FEM_INPUT Commands</h2>

<p>The special extra commands: <code class = "ph codeph">FILE_SOLVER_EXE</code>, <code class = "ph codeph">FILE_CMDLINE</code>,
<code class = "ph codeph">FILE_ADD_CALL</code>, <code class = "ph codeph">LIFE_FILE_SOLVER_EXE</code>,
<code class = "ph codeph">LIFE_FILE_CMDLINE</code>, <code class = "ph codeph">LIFE_FILE_ADD_CALL</code>
are all related to the last <code class = "ph codeph">FILE</code>
or <code class = "ph codeph">LIFE_FILE</code> command. These are only be used in very
advanced setups and should normally be avoided.</p>
</div>

</div>

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