<?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 = "Optimization with Tosca Structure always refers to one or more analysis files which provide the design space and necessary values for the optimization as results of a finite element analysis run."/><meta name = "description" content = "Optimization with Tosca Structure always refers to one or more analysis files which provide the design space and necessary values for the optimization as results of a finite element analysis run."/><meta name = "DC.relation" scheme = "URI" content = "../TsoCmdMap/tso-r-cmd-femInput.htm"/><meta name = "DC.format" content = "HTML5"/><meta name = "DC.identifier" content = "tso-c-usr-model-optAnaFileFemInp"/><meta name = "DC.language" content = "en"/><link rel = "stylesheet" type = "text/css" href = "../DSDocUI_XML34.css"/><title>Analysis Files for Optimization (FEM_INPUT)</title>
<script type = "text/javascript" src = "../DSDocUI_Highlight34.js">
  	/* */
  	</script></head><body onLoad = "highlightSearchTerms();" id = "tso-c-usr-model-optAnaFileFemInp">
<a name = "hj-top"> </a><table class = "table1" id = "table11"><tr><td><table class = "DocHeader"><tr><td class = "DocHeader1" colspan = "2"><h1> Analysis Files for Optimization (<code class = "ph codeph">FEM_INPUT</code>)</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">Optimization with <span class = "ph">Tosca Structure</span>
always refers to one or more analysis files which provide the design
space and necessary values for the optimization as results of a finite
element analysis run.</span>

</p>
<ul><li><a href = "#tso-c-usr-model-optAnaFileFemInp__tso-c-usr-model-optAnaFileFemInp-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 = "Specifies the Finite Element Input Files for the optimization. In addition, files with nodes and elements for defining restrictions can be imported." href = "../TsoCmdMap/tso-r-cmd-femInput.htm">FEM_INPUT</a></td></tr></table></td></tr></table>




<div class = "body conbody">
<p>A single finite element file or several finite element files are referenced
in the item <code class = "ph codeph">FILE</code> in the command <code class = "ph codeph">FEM_INPUT</code>.
However, all finite element files should have the same number of elements,
nodes, material properties, element groups, nodes groups etc. The only
difference allowed between the different input finite element files
is that the analysis types can vary. The analysis type can either be
linear static, nonlinear static, modal eigenfrequency or frequency response
analysis. </p>
<p>The <code class = "ph codeph">FEM_INPUT</code>
command is applied for reading the finite element files in the following
way:</p>
<pre class = "codeblock">
<code class = "ph codeph">
FEM_INPUT
 ID_NAME = id_read_files
 FILE    = fe_file_name_1
 FILE    = fe_file_name_2
 FILE    = fe_file_name_3
 ...
END_
</code></pre>
<p>The possibilities available to the user for loading the analysis model
when creating the optimization model depend on the chosen solver (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-solver-sb.htm#tso-m-usr-solver-sb" title = "This chapter describes the formats and functionalities of the different solvers supported by SIMULIA Tosca Structure. The topological and physical properties of the analysis model (finite element input file) are required for the optimization of an FE model. Normally, not all information contained in the analysis model is necessary for an optimization. The optimization module returns the modified model data to the FE solver. The node coordinates are changed during shape and bead optimization. New materials and element properties are generated during topology optimization and the assignments of the elements to the material definitions and material properties are changed. Therefore, there are very few restrictions to the FE modeling (finite element input file).">Solver Specific Features</a>) 
 and the option set 
 (<a class = "xref" href = "../TsoCmdMap/tso-r-cmd-options.htm" title = "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.">OPTIONS</a>).
 The model data is loaded using an internal interface.
After reading the model, the following FE objects are available for further
reference in the optimization task:</p>
<ul class = "ul">
<li class = "li">node groups</li>
<li class = "li">element groups</li>
<li class = "li">nodes</li>
<li class = "li">elements</li>
<li class = "li">coordinate systems</li>
<li class = "li">materials</li>
<li class = "li">properties</li>
<li class = "li">element types</li>
<li class = "li">boundary conditions (depending on the <code class = "ph codeph">OPTIONS</code>)</li>
  <li class = "li"><span class = "ph">load cases</span></li>
</ul>

<p>Analysis results used as terms for objective or constraint, so called
design responses 
(<code class = "ph codeph"><a class = "xref" href = "../TsoCmdMap/tso-m-cmd-dresp-sb.htm" title = "The design response command DRESP defines the system response for the current analysis model.">DRESP</a></code>),
are built by referring the <span class = "ph">load case</span>
numbers for the desired responses. </p>
<p>The <span class = "ph">load cases</span>
in the <span class = "ph uicontrol">first file</span> (<code class = "ph codeph">fe_file_name_1</code>)
are numbered using the original <span class = "ph">load case</span>
numbers used in the finite element file. </p>
<p>The <span class = "ph">load cases</span>
in the <span class = "ph uicontrol">second file</span> (<code class = "ph codeph">fe_file_name_2</code>)
are numbered using the original <span class = "ph">load case</span>
numbers used in the finite element file <span class = "ph uicontrol">plus 10.000</span>.
</p>
<p>The <span class = "ph">load cases</span>
in the <span class = "ph uicontrol">third file</span> (<code class = "ph codeph">fe_file_name_3</code>)
are numbered using the original <span class = "ph">load case</span>
numbers used in the finite element file <span class = "ph uicontrol">plus 20.000</span>
and etc. </p>
<p>For example, the <span class = "ph">load cases</span>
1, 3 and 4 in the first finite element file have the numbers 1, 3 and
4 in the parameter file, the <span class = "ph">load cases</span>
1, 3 and 4 in the second finite element file have the numbers 10001,
10003 and 10004 in the parameter file, the <span class = "ph">load cases</span>
1, 3 and 4 in the third finite element file have the numbers 20001, 20003
and 20004 in the parameter file and etc.</p>
<p>In 
<a class = "xref" href = "tso-m-usr-solver-sb.htm" title = "This chapter describes the formats and functionalities of the different solvers supported by SIMULIA Tosca Structure. The topological and physical properties of the analysis model (finite element input file) are required for the optimization of an FE model. Normally, not all information contained in the analysis model is necessary for an optimization. The optimization module returns the modified model data to the FE solver. The node coordinates are changed during shape and bead optimization. New materials and element properties are generated during topology optimization and the assignments of the elements to the material definitions and material properties are changed. Therefore, there are very few restrictions to the FE modeling (finite element input file).">Solver Specific Features</a>
the different allowed analysis types for the specific solvers
are described. In addition, 
<a class = "xref" href = "tso-c-usr-terms-combTermsLcSet.htm" title = "If more than one load case or substep exists, the user can choose the load case that is to be taken into consideration. In addition, for modal analysis where more than one eigenfrequency is calculated, a selection of the eigenfrequencies of interest is necessary.">About Load Case Specification (LC_SET)</a>
  describes how the <span class = "ph">load case</span>
numbers for the different finite element solvers are applied in the design
response definitions (<code class = "ph codeph">DRESP</code>).
This is especially important for the finite element input files using
no numbers when defining <span class = "ph">load cases</span>.
For the finite element solvers using no numbers the general rule is that
the <span class = "ph">load cases</span>
have the numbers according to the order within they are defined. Meaning
that the <span class = "ph">load case</span>
number one will always have the load number of one for <span class = "ph">Tosca Structure</span>
etc.</p>
<div class = "section" id = "tso-c-usr-model-optAnaFileFemInp__tso-c-usr-model-optAnaFileFemInp-rmk"><h2 class = "title sectiontitle">Remarks</h2>

<ol class = "ol">
<li class = "li"> A model link can only be made once for an optimization task, that is, the
command <code class = "ph codeph">FEM_INPUT</code> can only be used once in a parameter
file.</li>
<li class = "li">Several analysis files can be added, that is, the item <code class = "ph codeph">FILE</code>
can be repeated several times. The first file in the list of files will
be handled as main file, which means that the configuration of the
finite element model will be read from this file. The second and all
later referenced files will be used to perform a finite element calculation.
The model in these files must be identical to the original FE model.
The files will be modified during the optimization. </li>
</ol>
</div>

</div>


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