<?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 = "In addition to the standard output files TOSCA.OUT, TOSCA.LOG, and optimization_report.csv, the files in user-defined output can be generated. For the evaluation or documentation of the optimization results, it is useful to specifically write some information from the large amount of data to individual files. With the USER_FILE command, the user can create customized output files. These files contain specific information from selected groups in a special format."/><meta name = "description" content = "In addition to the standard output files TOSCA.OUT, TOSCA.LOG, and optimization_report.csv, the files in user-defined output can be generated. For the evaluation or documentation of the optimization results, it is useful to specifically write some information from the large amount of data to individual files. With the USER_FILE command, the user can create customized output files. These files contain specific information from selected groups in a special format."/><meta name = "DC.relation" scheme = "URI" content = "../TsoCmdMap/tso-r-cmd-userFile.htm#tso-r-cmd-userFile"/><meta name = "DC.format" content = "HTML5"/><meta name = "DC.identifier" content = "tso-c-usr-post-toolbox-usrOut"/><meta name = "DC.language" content = "en"/><link rel = "stylesheet" type = "text/css" href = "../DSDocUI_XML34.css"/><title>User-Defined Output Files (USER_FILE)</title>
<script type = "text/javascript" src = "../DSDocUI_Highlight34.js">
  	/* */
  	</script></head><body onLoad = "highlightSearchTerms();" id = "tso-c-usr-post-toolbox-usrOut">
<a name = "hj-top"> </a><table class = "table1" id = "table11"><tr><td><table class = "DocHeader"><tr><td class = "DocHeader1" colspan = "2"><h1>User-Defined Output Files (<span class = "ph">USER_FILE</span>)</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">In addition to the standard output files <code class = "ph codeph">TOSCA.OUT</code>,
                <code class = "ph codeph">TOSCA.LOG</code>, and <code class = "ph codeph">optimization_report.csv</code>, the files
            in user-defined output can be generated. For the evaluation or documentation of the
            optimization results, it is useful to specifically write some information from the large
            amount of data to individual files. With the <code class = "ph codeph">USER_FILE</code> command, the
            user can create customized output files. These files contain specific information from
            selected groups in a special format.</span>

</p>
<p>This page discusses: </p><ul><li><a href = "#tso-c-usr-post-toolbox-usrOut__tso-c-usr-post-toolbox-usrOut-example" id = "toc_rg" title = "">Examples</a></li><li><a href = "#tso-c-usr-post-toolbox-usrOut__tso-c-usr-post-toolbox-usrOut-rem" id = "toc_rg" title = "">Remarks</a></li><li><a href = "#tso-c-usr-post-toolbox-usrOut__tso-c-usr-post-toolbox-usrOut-tabOut" id = "toc_rg" title = "">Tabular Output</a></li><li><a href = "#tso-c-usr-post-toolbox-usrOut__tso-c-usr-post-toolbox-usrOut-catia" id = "toc_rg" title = "">Modification File for CATIA RSO Module</a></li><li><a href = "#tso-c-usr-post-toolbox-usrOut__tso-c-usr-post-toolbox-usrOut-onf" id = "toc_rg" title = "">ONF Output</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 = "Defines which data of the FE model, the FE calculation, or the optimization should be saved in a specified file." href = "../TsoCmdMap/tso-r-cmd-userFile.htm#tso-r-cmd-userFile">USER_FILE</a></td></tr></table></td></tr></table>




<div class = "body conbody">
<p>These files can be used, for example, to evaluate the results in a
spreadsheet program (<code class = "ph codeph">ASCII </code>data) or convert geometric
information (<code class = "ph codeph">ONF</code> format) into data for viewer or post-processor.To generate results files, several settings
must be set for every output file created:</p>
<ul class = "ul" id = "tso-c-usr-post-toolbox-usrOut__ul_3D8CAE11563B4AA6BA44397B043D28B0">
<li class = "li">Name of the output file.</li>
<li class = "li">Output format (default: <code class = "ph codeph">ASCII</code>).</li>
<li class = "li">Type of result data.</li>
<li class = "li">Node or element group for which the results data should
                be written.</li>
<li class = "li">Point in time when the file should be generated.</li>
</ul>
<p>The most important property is the type of the results. Different types
of data are permitted depending on the output format set. More information
concerning what kind of data is allowed for a certain output format
can be found in the Commands Manual. The node coordinates or the properties
of the nodes in the shape optimization (free or restricted) are examples
of useful output results. The values can be written at the end of the
optimization or for each optimization iteration.</p>

<div class = "section" id = "tso-c-usr-post-toolbox-usrOut__tso-c-usr-post-toolbox-usrOut-example"><h2 class = "title sectiontitle">Examples</h2>

<p>The tension stress in a notch is homogenized using shape optimization.
All relevant nodes of the two-dimensional model are in the node group
nd_ground. The tension data should be written for all iterations in the
<code class = "ph codeph">ASCII</code> file, <code class = "ph codeph">GROUND.INFO</code>. </p>
<p>The necessary command sequence is the following:</p>
<pre class = "codeblock">
<code class = "ph codeph">
USER_FILE
 ID_NAME   = my_user_file
 FILE_NAME = ground.info
 FORMAT    = ASCII
 ND_GROUP  = nd_ground
 TYPE      = NODE_MOVE_PATH
 WRITE     = EVER
END_
</code>
</pre>
</div>

  
<div class = "section" id = "tso-c-usr-post-toolbox-usrOut__tso-c-usr-post-toolbox-usrOut-rem"><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>

<p>Experience has shown that certain user-defined command sequences are
often used to generate result files. Therefore, it is recommended that
the user collects these commands in a macro and saves this macro in a
directory. These macros can then be loaded with the command INCLUDE during
the optimization preprocessing. </p>
</div>


<div class = "section" id = "tso-c-usr-post-toolbox-usrOut__tso-c-usr-post-toolbox-usrOut-tabOut"><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">Tabular Output</h2>

<p>Per default, <span class = "ph">Tosca Structure</span>
always writes a file <code class = "ph codeph">optimization_report.csv</code> containing
the progress of the value(s) of the objective function and objective
function terms as well as the constraint terms. If other design responses
or variable values are required, these can be compiled to a table with
the following command sequence:</p>
<pre class = "codeblock">
<code class = "ph codeph">
DRESP
 ... (several DRESP definitions, for example, DRESP_MAX_MISES)
END_

VARIABLE
 ... (several variable definitions for later reference)
END_

USER_FILE
 ID_NAME     = tab1
 FILE_NAME   = my_table
 FILE_OPTION = ADD
 FORMAT      = ASCII
 WRITE       = EVER
 TYPE        = TABULAR
 SEPARATOR   = COMMA
 DATA_TAB    = ITER
 DATA_TAB    = DRESP_MAX_MISES
 DATA_TAB    = ...
END_
</code>
</pre>
<p>In addition, another file called <code class = "ph codeph">optimization_status_all.csv</code> is written per
                default. It not only contains the same information as
                    <code class = "ph codeph">optimization_report.csv</code>, but also the progress of values for
                all design responses and variables that are defined in the parameter file. In
                addition, a measure for the average change of objective function and design
                variables is listed. </p>
</div>


<div class = "section" id = "tso-c-usr-post-toolbox-usrOut__tso-c-usr-post-toolbox-usrOut-catia"><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">Modification File for CATIA RSO Module</h2>

<p>The results of the shape optimization can be transferred to the CAD model in such a way that the
    results are used to deform/modify the geometry of the CAD-based component. All modifications
    added by the optimization system will be applied. To obtain the modification file, a
     specific <code class = "ph codeph">USERFILE</code> definition must be activated in your parameter file. In
    your installation directory, the macro <code class = "ph codeph">uf_shape_catia_rso.mac</code> already contains
    the necessary output request.</p>
<pre class = "codeblock">
<code class = "ph codeph">
USER_FILE
 ID_NAME     = UF_RSO
 FILE_NAME   = RSO_OUTPUT.TXT
 FILE_OPTION = VAR
 FORMAT      = ASCII
 ND_GROUP    = all_nodes
 TYPE        = CATIA_RSO
 WRITE       = EVER
 SEPARATOR   = TAB
 TITLE_1     = x(mm) # y(mm) # z(mm) # 
 C1(mm) # C2(mm) # C3(mm)
END_
</code>
</pre>
</div>

  
 
<div class = "section" id = "tso-c-usr-post-toolbox-usrOut__tso-c-usr-post-toolbox-usrOut-onf"><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">ONF Output</h2>

<p>The output of optimization results and model information is required
in ONF format (Optimization Neutral Format) when other post-processing
possibilities are needed. Model and result information in <code class = "ph codeph">ONF</code>
format form the basis for the calculation of isosurfaces with <span class = "ph">Tosca Structure.smooth</span>.
<code class = "ph codeph">ONF</code> data is also needed for the preparation of the optimization
results for FE post-processing.</p>
<p>In general, <code class = "ph codeph">ONF </code>data is written per default. If the
user requires specific information (for example, only part of the model) this
can be requested with the user file command, parameter <code class = "ph codeph">FORMAT=ONF</code>.
The node and element information can be written using <code class = "ph codeph">TYPE=FINITE_MODEL</code>
(for an example, see the macro <code class = "ph codeph">uf_model_onf.mac</code><span class = "ph">)</span>.
The macro <code class = "ph codeph">uf_topo_onf.mac </code>defines the output of the
results of the topological optimization in <code class = "ph codeph">ONF</code> format.</p>

</div>

</div>

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