USER_FILE

Defines which data of the FE model, the FE calculation or the optimization should be saved in a specified file.

Related Topics
In Other Guides
User Defined Output Files (USER_FILE)

ID_NAME

<id_name_of_user_file>

Name of the USER_FILE definition.

FILE_NAME

<file_name>

Name of the file.

FILE_OPTION

 

Specification of file attributes.

 

= FIX

File is created only once. With a new written statement this file is overwritten.

 

= ADD

New written statement is added to the end of the file.

 

= VAR

File name is extended with a numerator (iteration number) .

 

= VAR2

File name is extended with a numerator (iteration number-1) .

FORMAT

 

Determining the written format of the file.

 

= ASCII

File is created as an ASCII file.

 

= ONF

Output is in optimization Neutral File (ONF) format.

 

= HTML

Output is in HTML.

EL_GROUP

= <name_of_element_group>

Name of the element group which is used to define the USER_FILES.

ND_GROUP

= <name_of_node_group>

Name of the node group which is used to define the USER_FILES.

TYPE

 

Type of data that is to be written. Depends on the FORMAT.

for FORMAT = ASCII:

TYPE

= TABULAR

Output of variables in tables.

 

= CATIA_RSO

Output of geometry modifications by shape optimization for transfer to CATIA RSO module.

 

= NX_DEFORM_ORG

 
 

= NX_DEFORM_MOD

 

for FORMAT = ONF:

TYPE

= GROUPS

Definition of node groups and element groups.

 

= SHAPE_DATA

Specific data for shape optimization.

 

= BEAD_DATA

Specific data for bead optimization.

 

= TOPO_DATA

Specific data for topology optimization.

 

= SIZING_DATA

Specific data for sizing optimization.

 

= TEST_SHAPE_LEVEL

Output for

TEST_SHAPE
command.

= FINITE_MODEL, <coordinate_system_option>

Output of node and ele­ ment information of the FE model.

= TOPO_WITH_SENS

= SHAPE_WITH_SENS

= BEAD_WITH_SENS

for FORMAT = HTML:

TYPE

= TABULAR

Output of variables in tables.

For TYPE=FINITE_MODEL only:

<coordinate _system_ option>

= LOCAL

Node coordinates are distributed in the local coordinate system.

= GLOBAL

Node coordinates are in the global Cartesian coordinate system.

For TYPE=TABULAR only:

DATA_TAB

= <var_name>

Determines which variables <var_name> are written.

TITLE_1

= <Title_1>

Title 1 for ASCII-file.

TITLE_2

= <Title_2>

Title 2 for ASCII-file.

For FORMAT = ASCII, TYPE = TABULAR only:

SEPARA­ TOR

Separation character between columns.

= SPACE

Blank.

= BLANK

Blank.

= TAB

Tabulator.

= COMMA

Comma.

= EXCLAM

Exclamation mark.

= <xx>

Any kind of character separator, maximum two characters.

For TYPE = ISO_MODEL only.

ISO_VALUE

= REL_DENS, <value>

Material distribution is used as the basis for iso surface calculations. The given relative density value must lie between 0 (minimum density) and 1 (maximum density).

= ABS_DENS, <value>

Material distribution is used as the basis for iso surface calculations. The given density value is an absolute density value.

= SIG, <value>

Stress distribution is used as the basis for iso surface calculations. The given value is an abso­ lute stress value

Remarks

  1. The data can be generated in different formats. The following entries are necessary in order to obtain a complete definition of the file to be generated using the command USER_FILE: Pre-settings already exist in the system for many of these settings. By entering a relevant value, these are overwritten. The settings are done using the command END_ and the active default values are checked for consistency of entries, to check if the written command can be executed. If the file cannot be generated due to entries canceling each other (e.g. an attempt to generate data referring to elements for a node group), the system shows a warning and the write command is not activated. Only when all entries are consistent, the file can be activated for writing.
    • Name of the file in which the results are to be shown
    • Type of file
    • Output format
    • Type of results
    • When the file should be created
    • Nodes and elements for which the data should be generated
  2. A maximum of 20 columns can be defined in a table.
  3. A total of maximum 200 columns can be defined.
  4. One variable can be in several columns at the same time and different vari­ ables cannot exist in one column.
  5. Columns not fully occupied and lying between the first column and the highest occupied column, are filled with zeros.
  6. When entering the file name, it is necessary to know that files can be deleted or saved in sub-directories at the end of the optimization. This can be controlled using "wildcards". Which files are to be moved or deleted can be set in the initialization file (see Bd.1, Chapter 8.1.3). Using the system settings, all files that end in ".txt" are moved to the directory TOSCA_POST after optimization has been completed.

Examples

uf_shape_onf

USER_FILE
 ID_NAME = uf_shape_onf
 FILE_NAME = SHAPE
 FORMAT = ONF
 EL_GROUP = all_elements
 DATA_TYPE = SHAPE_DATA
 WRITE = EVER
END_

Example for a table output

USER_FILE
 ID_NAME  = tab1
 FILE_NAME = freq_tab.dat
 FILE_OPTION = ADD
 FORMAT  = ASCII
 WRITE = EVER
 TYPE  = TABULAR
 SEPARATOR = EXCLAM
 DATA_TAB  = ITERATION
 DATA_TAB  = freq_1
 DATA_TAB = freq_2
 DATA_TAB  = freq_3
END_

uf_model_onf.mac

USER_FILE
 ID_NAME = UF_MODEL_ONF
 FILE_NAME  = MODEL_fem
 FILE_OPTION = FIX
 FORMAT = ONF
 EL_GROUP = all_elements
 TYPE = FINITE_MODEL
 WRITE = NOW
END_

Result transfer to CATIA RSO module (uf_shape_catia_rso.mac)

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.

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_