Separated, aggregated, and file reference loads

When you create a solution from a load recipe, attach a load recipe to an existing solution, or update a load recipe currently attached to a solution, you are prompted to specify how to create the loads:

• Separated—The load recipe creates a separate load for each node, which can create a large number of objects in the Simulation Navigator. However, you can edit separated loads after they are created. The software also creates reference fields and coordinate systems as needed, and shares them between the loads.

• Aggregated—The load recipe creates a single load for each load type, such as force, pressure, enforced velocity, and so on. Aggregating loads can significantly reduce the time it takes to create the solution and to display the loads in the Simulation Navigator. However, you cannot edit aggregated loads after they are created, and no fields or coordinate systems are created.

• File Reference—As with an aggregated load, the load recipe creates a single a single load for each load type. In this case, the solver reads the data directly from the data source file. This can further improve performance, but you cannot modify any of the data from the data source when you create the load recipe. You likewise cannot edit file reference loads after they are created, and no fields or coordinate systems are created.

The available options vary, depending on the load recipe target type (FEM or mode set). Mode set load recipes always create file reference loads. For a FEM load recipe, the label matching strategy affects the available options. With user-defined matching, you can create only separated or aggregated loads. With file-based matching, you should create only file reference loads.

Note:

If you use separated loads and the data sources contain spatial results, the software converts the spatial results data to function data. This can cause significant performance issues if there is a large amount of data. It is recommended that you use aggregated loads for spatial results data.

Separated loads

With separated loads, for each subcase, the loads can be organized into folders or load sets, depending on the solver language. The software creates one container for each load type, node, and load type parameter (that is, the degree of freedom or pressure). For example, if a load recipe applies force and enforced acceleration on four nodes with one degree of freedom, the Loads node for each subcase would include eight containers (2 load types * 4 nodes * 1 degree of freedom).

The software also creates reference fields and assigns them to the excitation load set instead of to the loads. The function data is referenced in the load set.

In the Simulation Navigator, separated loads use the following naming convention:

on :()

You can edit the names of the containers and the load, as well as each load's properties.

In addition, when you create a solution from a load recipe that includes function attributes (such as spectrum scaling), the software creates one field for each function, load type, and load type parameter. For example, if a load recipe with five function attributes applies force on a node with three degrees of freedom, the software would create 15 fields. The function field is assigned to the mapped magnitude property. Parameter usage is indicated by its mapped magnitude property scaling factor value on the load. A value of 1 means used and 0 means not used. For more information, see Function Attributes (SORT2 Only) in Load Recipe dialog box.

The software also creates coordinate systems as needed, and shares them between the loads.

Aggregated loads

With aggregated loads, for each subcase, the software creates a single load for each load type. For example, if a load recipe applies enforced accelerations, enforced displacements, and enforced velocities on 500 nodes, the Loads node for each subcase would include three nodes. No fields or coordinate systems are created.

In the Simulation Navigator, aggregated loads use the following naming convention:

::()

You can rename each node, but not edit its properties.

In addition, when you create a solution from a load recipe that includes function attributes, the software creates a single field that includes all the functions that have the same independent and dependent variables, load conditions, function attributes, and so on. For more information, see Function Attributes (SORT2 Only) in Load Recipe dialog box.

File reference loads

With file reference loads, the software creates a single load for each load type. No fields or coordinate systems are created.

For a FEM load recipe, file reference loads use the following naming convention:

from External File::()

For a mode set load recipe, the file reference loads use the following naming convention:

Filtered Modal Participation Factors::MPFs ()()

You can rename each node, but not edit its properties.

With file reference loads, the software does not create any fields or coordinate systems.

How do I

Create a load recipe from a data source

Create a load recipe from solution process results

Create a solution from a load recipe

Attach a load recipe to a solution

Update a solution from a load recipe

Learn more

Load recipes

Using modal participation factors in a load recipe

Load recipe validation

Look up more details

Load recipe data source file types

Quick links

Command reference

Pre/Post video examples

Bulk Entry Descriptions

Simcenter 3D tutorials

Browse Simcenter 3D help by product area

Separated, aggregated, and file reference loads, 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 } });