Importing output requests (Simcenter Samcef)

The software can import Samcef .SAI output requests with the following limitations:

• The software only parses the ARCHIVE, COMP, STYP, and STRUCTURE parameters of the Samcef .SAI command.

• The output requests support can be the whole structure, nodes or a group of elements. The parsed Samcef .SAI command syntaxes are:.SAI ARCHIVE STRUCTURE STYP - to import output requests defined on the whole model. You can import classical nodal or per element output requests (Samcef codes 1xxx, 3xxx, etc...) or time history output requests (Samcef codes 9xxx)..SAI ARCHIVE STYP - to import output requests defined on elementsYou can import classical per element output requests (Samcef codes 1xxx, 3xxx, etc...) or by element time history output requests (Samcef codes 9xxx). is a list of element labels that can be defined through an explicist list (ELEMENT I -) or through a group of entities (GROUP -)..SAI ARCHIVE COMP - STYP - to import nodal time history output requests.You can import nodal time history output requests (Samcef codes 9xxx). is a list of node labels that can be defined through an explicist list (NODE I -) or through a group of entities (GROUP -).

• The software ignores other .SAI parameters that select entities (or subsets of entities) like SPLY, DDL, etc...

Output requests and the importance of families of codes

In Simcenter Samcef, you define Output requests by selecting families of codes that match a physical result.

For instance, the Cauchy Stress Tensor result of a Non-linear analysis is defined by the following families of codes:

Physical Quantity	Volumes	Shells (med/up/low)	Beams	Rods
Cauchy Stress Tensor	x442	x448 / x478 / x408	-	x442

• For volumes and rods: the x442 family.

• For shells: the x448, x478, and x408 families, because on shells, you can output results on the lower and lower skins, and on the midplane.

For more information on families of codes, see Families of results in structural and thermal output requests (Simcenter Samcef).

The import of Samcef output requests mechanism

When the software imports Samcef output requests selection, it will try to group codes into families of codes because in Simcenter Samcef Output Requests you select family of result codes, not individual result codes.

The software will:

• first filter support entities on which you define the same result code (or list of result codes).

• then filter support entities to match as possible a family of codes:if you define specifc individual result codes of a same family, the software will select all the codes of that family: see example 2 below.If you define different result codes of a same family of codes but on different entities, the software will group the entities into a single set: see example 3 below.

The following examples describe some of the important steps of this mechanism.

Example 1: importing an individual result code

If you import the .SAI ARCHIVE STYP 1408 Samcef output request, where is a list of shell labels, the software will enable the Cauchy Stress tensor Output requests,

• with the Location (1) set to Lower Skin (2),

• with the Type (1) set to Element Nodal (2),

• and with the Entity referencing the given list of shell labels.

Example 2: importing several result codes that belong to the same family of codes

If now you import the following .SAI ARCHIVE GROUP STYP 1408 1478 Samcef output request that will select both the upper and lower skin Samcef results, the software cannot only enable for the same family of codes the lower skin and the upper skin result code.

That is why the software will set All for the Location: in that situation, the midplane result (x448) is also enabled.

The Entity will still reference the given list of shell labels.

Example 3: importing several result codes that belong to one family of codes but that are set on different entities

Now, suppose we import the following Samcef output requests selection:

.SAIARCHIVE <elem_sel1> STYP 1408ARCHIVE <elem_sel2> STYP 1478

where refers, for instance to shells of labels 1 and 2, and refers to shells of labels 2, 3, and 4.

In this case, due to limitations of the Output Requests feature, the software:

• will sef for the Entity feature the union of both lists of shell labels.

• will set All for the Location: in that situation, the midplane result (x448) is also enabled.

Unsupported codes

Results codes that are not supported by the Simcenter Samcef output requests are imported in User Codes Arrays that contain several Nodal User Codes or Element User Codes modeling objects.

For more information, see User-defined output requests (Simcenter Samcef).

How do I

Import a finite element model (Simcenter Samcef)

Append finite element data to a model (Simcenter Samcef)

Learn more

Supported entities for import (Simcenter Samcef)

Import overview (Simcenter Samcef)

Creation of mesh collectors during import (Simcenter Samcef)

Entity labels and names during import (Simcenter Samcef)

Importing functions to fields or expressions (Simcenter Samcef)

Importing coordinate systems (Simcenter Samcef)

Storing unsupported parameters and commands at import (Simcenter Samcef)

Appending at import (Simcenter Samcef)

Importing solution parameters (Simcenter Samcef)

Importing macro commands (Simcenter Samcef)

Importing laminates (Simcenter Samcef)

Common issues when importing a model (Simcenter Samcef)

Importing Samcef groups to Pre/Post regions (Simcenter Samcef)

Orphan nodes after import (Simcenter Samcef)

Automatically setting the correct analysis and solution (Simcenter Samcef)

Import Nastran data to a current Simcenter Samcef model

Import of Element Associated Data defined on solid elements (Simcenter Samcef)

Quick links

Command reference

Pre/Post video examples

Bulk Entry Descriptions

Simcenter 3D tutorials

Browse Simcenter 3D help by product area

Importing output requests (Simcenter Samcef), Simcenter 3D 2021.1 Series

© 2020 Siemens

window.mainLanguage="en_US"

window.delivId=""

window.projectId=""

MathJax.Hub.Config({ TeX: { extensions: ["autoload-all.js"] }, tex2jax: { displayMath: [ ] }, "SVG": { scale: 125 } });