Load recipes

Load recipes let you define instructions for creating the following types of loads:

• Force (transient and frequency-dependent complex vector loading)

• Force on free coordinates/arbitrary points (transient and frequency-dependent complex vector loading)

• Moment (transient and frequency-dependent complex vector loading)

• Frequency-dependent enforced acoustic pressure

• Enforced displacement (transient and frequency)

• Enforced velocity (transient and frequency)

• Enforced acceleration (transient and frequency)

• Filtered modal participation factors (MPFs) for frequency-dependent enforced displacement, enforced velocity, or enforced acceleration

Note:

• The Simcenter 3D Acoustics BEM solver does not support force on free coordinates or pressure.

• Only the Simcenter 3D Noise and Vibration solver with a vibro-acoustic analysis type supports MPFs.

After you create a load recipe, you can:

• Create a new solution from the load recipe.This adds the loads to the model, creates the appropriate subcases for the solution, and assigns the loads to those subcases.

• Attach the load recipe to an existing solution.Like creating a new solution from a load recipe, this action adds the loads and subcases and assigns the loads to those subcases. If the solution is currently associated with a different load recipe, the original load recipe is replaced, all the subcases and loads associated with that load recipe are deleted, and new subcases with the appropriate loads are created based on the new load recipe.

• Update a solution that was created from a load recipe with an updated load recipe.This adds, updates, and deletes the loads and subcases based on the changes to the load recipe.

When a solution is associated with a load recipe, the load recipe name appears below the solution node in the Simulation Navigator.

Deleting a solution associated with a load recipe does not delete the load recipe, but it does delete the loads associated with the load recipe unless that load recipe is used by another solution as well.

Defining load recipes

When you create or edit a load recipe, you can:

• Specify the target type for the load recipe, which can be a finite element model (FEM) or a mode set.For a FEM load recipe, you can use data for which the independent variable is one of the following:Time (that is, a time history or waterfall of time histories)Frequency (that is, frequency spectra, a waterfall of frequency spectra, or order cuts).For a mode set load recipe, you can use only data related to frequency.

• Specify the external data source file to use, such as a .unv, .lms, .op2, .pch, .sc_h5, or .bdf file.Each data source file contains load data in the form of functions or spatial results. For more information about each data source file type, see Load recipe data source file types.If you create the load recipe from a Model and Load Pre-processing (MLPP) solution process rather than using the Load Recipes command, the load recipe automatically uses the .sc_h5 results file associated with that solution process.For a FEM load recipe, you can use a single data source or multiple data sources. If you use multiple data sources, you can optionally merge them, which lets you consolidate the load conditions and minimize the number of subcases for the solution.For a mode set load recipe, you can use only a single .op2, .pch, or .sc_h5 file as the data source. In addition, the data source can have only one MPF load type, such as only displacement or only velocity.Tip: If you have a .unv file that contains MPF data, you can use that .unv file as an input file for an MLPP solution process. After you solve the MLPP solution, you can use the resulting .sc_h5 file to create a load recipe.

• Configure how to handle the processing options such as the unit system, function identifier, and data priority, as well as function attributes for SORT2 data.

• Control whether and how the software extrapolates the starting and ending data points of a data table in a data source (FEM load recipes only).

• Review the load conditions, waterfall values, order cut values, and MPFs associated with the data source, and disable them as desired to prevent certain loads and subcases from being created.

• Map the loads to a node, group, selection recipe, mesh, or the entire FEM (FEM load recipes only).For all loads except pressure, you can also specify the orientation of the load coordinate system.

Working with load conditions

All load recipes must include at least one load condition, which represents a condition that was met when measuring data. For example, you might perform a durability analysis in which force is applied to an object, with one test performed at 10 N, one at 20 N, and one at 30 N. In this case, there would be three load conditions, one for each measurement.

If the data source includes a waterfall of time histories, a waterfall of frequency spectra, or order cut values, the data from the data source is grouped by the appropriate values. For example, you might perform an analysis in which a fan rotated at 250 RPM, 300 RPM, and 350 RPM. Each RPM value would constitute one waterfall value.

Typically, when you create or update a solution from a load recipe, the software creates one subcase for each load condition, or each combination of a load condition and a waterfall or order cut value. However, if your FEM load recipe uses multiple data sources whose data is grouped in load conditions with the same names, you can:

• Merge the data from the different data sources.For example, suppose you have two data sources, one containing a load condition for nodes 1 to 50 and the other containing the same load condition for nodes 51 to 100. If you merge the data, the load recipe creates a single load condition for nodes 1 to 100. This minimizes the number of load conditions and subcases, but also reduces the flexibility you would otherwise have in enabling or disabling specific load conditions.

• Keep the data separate.Using the preceding example, if you keep the data separate, the load recipe creates one load condition for nodes 1 to 50 and another for nodes 51 to 100. This gives you the option to enable or disable either or both load conditions. If you enable both, the load recipe creates two subcases, one for each load condition.

You can merge load conditions only when they have the same:

• Load condition name.

• Data type, such as waterfall or order cut value.

• Load type parameters (that is, the degrees of freedom).

• Data format, such as integer, floating point number, and so on.

• Unit of measurement.

Load handling

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, the loads can be handled in several ways:

• Separated—The load recipe creates a separate load for each node, which can create a large number of objects in the Simulation Navigator. You can edit separated loads after they are created.

• 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.

• File reference—The load recipe creates a single load for each load type. In this case, the solver reads the data directly from the data source file, which can further improve performance. However, you cannot modify any of the data from the data source when you create the load recipe, and you cannot edit file reference loads after they are created.

The available options vary, depending on the load recipe target type and other considerations. For more information, see Separated, aggregated, and file reference loads.

Creating post-processing scenarios from load recipes

You can visualize data from a load recipe using scenario-based post-processing. The data in your load recipe determines which scenarios are available.

For more information about post-processing scenarios, see Scenario-based post-processing.

Where do I find it?

Creating load recipes

Application	Pre/Post
Prerequisites	A Simulation file as the work part and displayed partA mode set as an alternate representation for the FEM (only for mode set load recipes)
Command Finder	Load Recipes

Creating a post-processing scenario from a load recipe

Application	Pre/Post
Prerequisites	A Simulation file as the work part and displayed partA load recipe exists
Simulation Navigator	Expand Load Recipe Container→right-click a load recipe node→Post-Processing Scenario

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

Using modal participation factors in a load recipe

Load recipe validation

Separated, aggregated, and file reference loads

Importing Simcenter Testlab data

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

Load recipes, 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 } });