Load Recipe dialog box

For all load recipes, the Data Sources and Load Conditions tabs appear. The Waterfall, Order Cut, Mapping, and Modal Participation Factors tabs might also appear, depending on the target type and data type used by the load recipe. To view the target type and data type, use the Load Recipes command to display the Load Recipes Manager dialog box.

Note:

To change the name or description of an existing load recipe, use the Load Recipes command to display the Load Recipes Manager dialog box. In the table, click the row that contains the load recipe and then click again in the Name or Description cell. When the cell becomes editable, type the desired name or description.

Data Sources tab

List
List	Lists the data sources in the load recipe.For each data source, this table includes the following information:File—The path to the data source file.Type—The file type.For more information about the supported file types, see Load recipe data source file types.Format—The format handler that is used to interpret the data.Label—A descriptive name for the data source.
Add	For a mode set load recipe, available when no data sources appear in the data sources table.Lets you select a data source file to add to the data sources table.
Delete	Available when a data source is selected in the data sources table.Deletes the selected data source.
Information	Available when a data source is selected in the data sources table.Displays information about the selected data source.
File
Available when a data source is selected in the data sources table. These options let you modify the information that appears in the data sources table for the selected data source.
File	Sets the path to the data source file.You can click Browse to browse to the file.If the path is valid, Infers Relative Path appears next to the file name. If it is not, Invalid File Reference appears instead. The selected data source file must have a valid path.
Format	Specifies the format handler to use to interpret the data from the data source.
Data Source Label	Sets the text that appears in the Label column in the data sources table, as well as the name that appears in the Load Condition column on the Load Conditions tab.Note: Any changes to this text do not appear in the Label or Load Condition column until after you click OK.
Processing Options
Processing Options	Controls the format-specific settings, which can include unit conversion details or other options to process the information from the data source.AttributeDisplays an identifier for the attribute.ValueSpecifies the value for the attribute.For some attributes, you can change the value by right-clicking the cell and choosing the appropriate option. For example, if the attribute is Unit System, you might be able to choose a specific unit of measurement.For other attributes, you can specify the value by clicking the cell and typing data.DescriptionDisplays a description of the attribute.If you cannot see the full description in the table, you can hover over the displayed text to see the full description.
Function Attributes (SORT2 Only)
Available when at least one data source is a .unv, .op2, .pch, or .sc_h5 file that contains frequency loads. These file types do not provide values for the function attributes, so you can specify the values here.For an .lms file, each function in the file can define its own attributes, so it is not possible to show all the attributes for each function. Therefore, the displayed values might not reflect the data from the file.
Spectrum Scaling	Specifies the scaling for the spectrum, depending on the signal type and target application use (Unknown, Peak, or RMS).
Correction Mode	Specifies the spectrum correction mode for which you can apply a correction factor (Unknown, Amplitude corrected, or Energy corrected.Note: If you change the correction mode and then plot the load recipe, the signal is first uncorrected by dividing all values with the correction factor corresponding to the correction mode specified when the load recipe was created. Then, the signal is corrected for the new correction mode by multiplying all values with the correction factor corresponding to the new correction mode.
Energy Correction Factor	Sets the appropriate energy correction factor to compute the energy level of a signal from its spectrum.To set this automatically, click and select the appropriate window type on the Correction Factors Helper dialog box.
Amplitude Correction Factor	Sets the appropriate amplitude correction factor to compute the amplitude level of a signal from its spectrum.To set this automatically, click and select the appropriate window type on the Correction Factors Helper dialog box.
Correction Factors Helper	Opens the Correction Factors Helper dialog box where you select the type of window which was applied to the FFT (Fast Fourier transform) time signal.The window type you select sets the appropriate values for Energy Correction Factor and Amplitude Correction Factor.
Acoustical Weighting	Specifies the acoustical weighting scheme you want to use to represent the data (Unknown, None, A-Weighted, B-Weighted, C-Weighted, D-Weighted, AB-Weighted, or BC-Weighted).The acoustical weighting scheme scales the data for noise perception and measurement.
Load Condition Handling
Appears for a FEM load recipe.
Handling	Specifies the method for handling load conditions from multiple data sources.Create Union of Load Conditions across Data SourcesMerges the data from the different data sourcesFor example, suppose you have two data sources, one containing loads for nodes 1 to 50 and the other containing loads for nodes 51 to 100. If you merge the data, the load recipe creates one 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.For information about the criteria that must be met in order to merge the data from different source files, see Working with load conditions.Create Separate Load Conditions per Data SourceKeep 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 of enabling or disabling either or both load conditions. If you enable both, the load recipe creates two subcases, one for each load condition.If you keep the data separate, the data source label appears next to each load condition in the Load Conditions tab.
Extrapolation
Appears for a FEM load recipe.
Values Outside Table	Specifies the method for extrapolating values outside the data table in the data sources.ExtrapolateExtrapolates the two starting and ending data points to look up values for the data table when the value of the independent domain lies below and above the range of tabular data.ConstantUses a constant value as the lookup value for the data table when the value of the independent domain lies outside the range of tabular data.Don't ExtrapolateDoes not look up a value for the data table at values of the independent domain that lie outside the range of tabular data.Note: Select this option if you want to avoid extrapolating results at frequencies where loads are absent.
Autofill	Populates all the other tabs based on the data in the selected data sources.You can also populate each tab individually by clicking Autofill on that tab.All load conditions, waterfall values, order cut values, and modal participation factors (MPFs) are automatically enabled.If the data source contains only function data, the Mapping tab is populated with the available loads mapped to the appropriate target types.If the data source contains only spatial results data, the Mapping tab is populated with a single entry for the load type. Type is set to FEM and the target is the specified FEM. Depending on the content of the data source, the parameters are set to either Automatic Entity (AE in the mapping table) or Not Assigned (blank in the mapping table).If the data source contain both function and spatial results data, the Mapping tab is populated as it is for only spatial results data.
Run Validation Check	Checks the data in the load recipe and data source files.For more information, see Load recipe validation.
Autofill Options
For a FEM load recipe, any changes made here are also automatically made on the Mapping tab.
Strategy	Appears for a FEM load recipe.Specifies the strategy for automatically defining the mapping table.Data Source BasedMaps the data source IDs to node IDs in the specified FEM.Selection Recipe BasedMaps functions in the data source to selection recipes.The selection recipes must have the same names as the functions in the data source. If no selection recipe with a matching name exists for a particular function, that function is not mapped.
Assembly Component	For a FEM load recipe, appears when Strategy is set to Data Source Based.Specifies the assembly FEM or component FEM to use with this load recipe.For a mode set load recipe, the assembly component must be the FEM associated with the alternate representation.To search or filter the list of files, click More Options . For more information, see Filter options.

Load Conditions tab

Selection
Selection	Lists the load conditions from the data source.Load ConditionDisplays the data source label defined on the Data Sources tab, along with any other identifier from the data source.If the load conditions have been merged, the data source label does not appear.Enabled/DisabledSpecifies whether the load condition is enabled or disabled.To enable or disable any valid load condition, double-click that load condition. To enable or disable multiple load conditions simultaneously, select the load conditions from the list, right-click one, and choose Enable or Disable.Only enabled load conditions are used to create subcases in a solution that uses this load recipe.
Autofill	Populates the load conditions based on the data in the selected data sources.All the load conditions are automatically enabled.
Run Validation Check	Checks the data in the load recipe and data source files.For more information, see Load recipe validation.

Waterfall, Order Cut, and Modal Participation Factors tabs

The Waterfall tab appears when Data Type is set to Waterfall of Time Histories or Waterfall of Frequency Spectra in the Load Recipes Manager dialog box. The Order Cut tab appears when Data Type is set to Order Cut. The Modal Participation Factors tab appears when Target Type is set to Mode Set in the Load Recipes Manager dialog box.

Selection
Selection	Lists the waterfall values, order cut values, or MPFs from the data source.Waterfall/Order Cut/Modal Participation FactorsDisplays the waterfall values, order cut values, or MPFs in the data source.Enabled/DisabledSpecifies whether each waterfall value, order cut value, or MPF is enabled or disabled.To enable or disable any listed item, double-click that item. To enable or disable multiple items simultaneously, select the items from the list, right-click one, and choose Enable or Disable.Only enabled items are included in a solution that uses this load recipe.Note: For mode set load recipes, the enabled modes in the Modal Participation Factors tab must match the active modes in the mode set. For example, if you enable a mode in the Modal Participation Factors tab and subsequently deactivate that mode in the mode set, a warning appears when you solve the solution.
Autofill	Populates the waterfall values, order cut values, or MPFs based on the data in the selected data sources.All the items are automatically enabled.
Run Validation Check	Checks the data in the load recipe and data source files.For more information, see Load recipe validation.

Mapping tab

The Mapping tab appears when Target Type is set to Finite Element Model in the Load Recipes Manager dialog box.

The setting for Strategy in the Data Sources tab determines whether the automatic mapping uses node IDs or selection recipes.

Mapping
Label Matching Strategy	Specifies the method for mapping the data from the data source to the FEM.User Defined MappingLets you modify any mapping provided by the data source or manually add your own.For example, if a load is mapped to node 4 in the data source, you can change it to map the load to node 5.If you select this option, you can also add a load to a node, group, selection recipe, mesh, or FEM. When you do this, a corresponding function must exist in the data source.In addition, when you create a solution from this load recipe, attach this load recipe to an existing solution, or update this load recipe after it is attached to a solution, you can create only separated or aggregated loads. For more information, see Separated, aggregated, and file reference loads.Defined by the FileUses only the mapping provided by the data source, which you cannot change.Note: After you associate the load recipe with a solution, you can change the label matching strategy and update the solution. However, when you do this, the loads associated with your solution might change.
Label Matching
Boundary Condition Type	Displays a list of the type of loads that can be mapped.A filled red circle indicates a load type for which mapping exists.When you click a load type, the existing mapping data appears on the right side of the dialog box.Boundary Condition TypeDescriptionParameters****Force - NodeTranslational and rotational force on nodes.DOF1–3 represent translational force. DOF4–6 represent rotational force (moment).Force - Free CoordinatesTranslational and rotational force on arbitrary points in space.DOF1–3 represent translational force. DOF4–6 represent rotational force (moment).Pressure - NodePressure on a node.PressureEnforced DisplacementsTranslational and rotational displacement constraint on nodes. Supports using the coordinate system from the data source or the coordinate system from the model.DOF1–3 represent translational displacement. DOF4–6 represent rotational displacement (angle).Enforced VelocitiesTranslational and rotational velocity constraint on nodes. Supports using the annotated coordinate system from the data source or the coordinate system from the model.DOF1–3 represent translational velocity. DOF4–6 represent angular velocity.Enforced AccelerationsTranslational and rotational displacement constraint on nodes. Supports using the annotated coordinate system from the data source or the coordinate system from the model.DOF1–3 represent translational acceleration. DOF4–6 represent angular acceleration.	Boundary Condition Type	Description	Parameters	Force - Node	Translational and rotational force on nodes.	DOF1–3 represent translational force. DOF4–6 represent rotational force (moment).	Force - Free Coordinates	Translational and rotational force on arbitrary points in space.	DOF1–3 represent translational force. DOF4–6 represent rotational force (moment).	Pressure - Node	Pressure on a node.	Pressure	Enforced Displacements	Translational and rotational displacement constraint on nodes. Supports using the coordinate system from the data source or the coordinate system from the model.	DOF1–3 represent translational displacement. DOF4–6 represent rotational displacement (angle).	Enforced Velocities	Translational and rotational velocity constraint on nodes. Supports using the annotated coordinate system from the data source or the coordinate system from the model.	DOF1–3 represent translational velocity. DOF4–6 represent angular velocity.	Enforced Accelerations	Translational and rotational displacement constraint on nodes. Supports using the annotated coordinate system from the data source or the coordinate system from the model.	DOF1–3 represent translational acceleration. DOF4–6 represent angular acceleration.
Boundary Condition Type	Description	Parameters
Force - Node	Translational and rotational force on nodes.	DOF1–3 represent translational force. DOF4–6 represent rotational force (moment).
Force - Free Coordinates	Translational and rotational force on arbitrary points in space.	DOF1–3 represent translational force. DOF4–6 represent rotational force (moment).
Pressure - Node	Pressure on a node.	Pressure
Enforced Displacements	Translational and rotational displacement constraint on nodes. Supports using the coordinate system from the data source or the coordinate system from the model.	DOF1–3 represent translational displacement. DOF4–6 represent rotational displacement (angle).
Enforced Velocities	Translational and rotational velocity constraint on nodes. Supports using the annotated coordinate system from the data source or the coordinate system from the model.	DOF1–3 represent translational velocity. DOF4–6 represent angular velocity.
Enforced Accelerations	Translational and rotational displacement constraint on nodes. Supports using the annotated coordinate system from the data source or the coordinate system from the model.	DOF1–3 represent translational acceleration. DOF4–6 represent angular acceleration.
Orientation	Appears when the load type is anything other than Pressure - Node. Available when Label Matching Strategy is set to User Defined Mapping.Specifies the orientation of the coordinate system for the loads.Data SourceUses the coordinate system or direction as defined in the data source (if it is defined).NodalUses the coordinate system as defined on the nodes in the FEM.AbsoluteUses the absolute coordinate system of the Simulation file.
Mapping Table/Row Editing
Defines how the loads are mapped to entities in the model. You can define the mapping using either the mapping table or the options in the Row Editing group.
Type	Available when Label Matching Strategy is set to User Defined Mapping.Specifies the type of entity to which to apply the load.To change the entity type in the mapping table, right-click the cell in the Type column and choose one of the following types (depending on the load type). Alternatively, select the row in the table and select one of the following from the Type list in the Row Editing group.The available options vary, depending on the load type.NodeApplies the loads to a selected node.GroupApplies the loads to a selected group.Selection RecipeApplies the loads to a selected selection recipe.MeshApplies the loads to a selected mesh.FEMApplies all available data from the data sources to the entire model.
Target	Available when Label Matching Strategy is set to User Defined Mapping.Specifies the entity to which to apply the load.To change the target in the mapping table, click the cell in the Target column and type the appropriate value (such as the node ID or the name of the group). If the target is a mesh, include two colons and the FEM name without the file extension, such as mesh_name::FEM_name. If the target is a FEM, include the .fem file extension in the name.Alternatively, select the row in the table, click Target in the Row Editing group, and complete the Target Selection dialog box. For example, you might select a node in the graphics window, or select a group or selection recipe in the Simulation Navigator.
DOF1–DOF6	Appear when the load type is anything other than Pressure - Node. Available when Label Matching Strategy is set to User Defined Mapping.Specifies which function in the data source to apply to the target for each degree of freedom (DOF).For information about what each DOF represents, see the Load Type table above.To change the option in the mapping table, right-click the cell in the appropriate DOF column and choose one of the following options. Alternatively, select the row in the table and select one of the following from the DOF list in the Row Editing group.Not AssignedApplies no load to the target for the specified degree of freedom.When you select this option, the mapping table cell is blank.Automatic EntityApplies the load associated with the function in the data source that has the same identifier as the selected entity.For example, if the target is node 5, the software uses the function associated with node 5.If the model is an assembly FEM, in the Context box, type the context identifier to indicate whether the target is in the assembly FEM or a specific FEM.When you select this option, the mapping table cell displays AE.Manual EntityApplies the load associated with the specified function in the data source.For example, suppose the target is node 5, but you want to use the function associated with node 8. You would select Manual Entity and type 8 in the Entity box.With this approach, you can use the same function for multiple targets.When you select this option, the mapping table cell displays ME. If you define an entity ID, that ID appears as well (such as ME:8).Automatic FunctionApplies the load associated with a named function to the target that has the same name.For example, if the function in the data source is named Function1 and the target is a selection recipe named Function1, then the load associated with that function is applied to that target.When you select this option, the mapping table cell displays AF.Manual FunctionApplies the load associated with the specified function name.For example, suppose the target is a selection recipe named Function1, but you want to apply the load associated with a function named Function2. You would select Manual Function and type Function2 in the Function box.
Pressure	Appears when the load type is set to Pressure- Node. Available when Label Matching Strategy is set to User Defined Mapping.Defines the frequency-dependent enforced acoustic pressure that the software applies to the selected target.The options for Pressure (such as Not Assigned, Automatic Entity, Manual Entity, and so on) are the same as described for DOF1–DOF6 above.
Context	Appears when Automatic Entity is selected from the DOF or Pressure list. Available when Label Matching Strategy is set to User Defined Mapping.Sets the context identifier to indicate whether the target is in the assembly FEM or a specific FEM.
Entity	Appears when Manual Entity is selected from the DOF or Pressure list. Available when Label Matching Strategy is set to User Defined Mapping.Sets the entity identifier, such as the node ID associated with a function in the data source.If you do not specify an entity identifier, the software uses the last entity identifier to map the function. For example, suppose you set DOF1 to Manual Entity and type 8 in the Entity box. If you then set DOF2 to Manual Entity but do not type anything in the Entity box, the software automatically uses the function associated with the preceding entity identifier: 8.
Function	Appears when Manual Function is selected from the DOF or Pressure list. Available when Label Matching Strategy is set to User Defined Mapping.Sets the name of the function to use.
Add	Available when Label Matching Strategy is set to User Defined Mapping.Adds a new row to the mapping table.If you add a new mapping, make sure a corresponding function exists in the data source.
Delete	Available when Label Matching Strategy is set to User Defined Mapping and a row is selected.Deletes the selected rows from the mapping table.
Autofill	Populates the mapping table based on the data in the selected data sources and the setting for Label Matching Strategy.If the data source contains only function data, the mapping table is populated with the available loads mapped to the appropriate target types.If the data source contains only spatial results data, the mapping table is populated with a single entry for the load type. Type is set to FEM and the target is the available FEM. Depending on the availability, the parameters are set to Automatic Entity (AE in the mapping table) or Not Assigned (blank in the mapping table).If the data sources contain both function and spatial results data, the mapping table is populated as it is for spatial results data.
Spreadsheet	Available when Label Matching Strategy is set to User Defined Mapping.Lets you edit the mapping table using your spreadsheet application.The spreadsheet includes one sheet for each load type. The data in the cells must use the same syntax that appears in the mapping table in the Load Recipe dialog box. For example, to use a manual entry for entity 1 for DOF 1, you would type ME:1 in the appropriate cell in the DOF1 column in the spreadsheet.After you finish your changes, choose Add-Ins tab→Menu Commands group→Update Table and close the spreadsheet. The updated values appear in the Load Recipe dialog box.
Import	Available when Label Matching Strategy is set to User Defined Mapping.Lets you import a comma-separated values (CSV) file that contains the mapping definition.To see the appropriate file format, use the Export command to create an example.
Export	Lets you export the mapping table to a CSV file.
Run Validation Check	Checks the data in the load recipe and data source files.For more information, see Load recipe validation.
Autofill Options
Any changes made here are also automatically made on the Data Sources tab.
Strategy	Specifies the strategy for automatically defining the mapping table.Data Source BasedMaps the data source IDs to node IDs in the specified FEM.Selection Recipe BasedMaps functions in the data source to selection recipes.The selection recipes must have the same names as the functions in the data source. If no selection recipe with a corresponding name exists for a particular function, that function is not mapped.
Assembly Component	Appears when Strategy is set to Data Source Based.Specifies the assembly FEM or component FEM to use with this load recipe.To search or filter the list of files, click More Options . For more information, see Filter options.

How do I

Create a load recipe from a data source

Learn more

Load recipes

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 Recipe dialog box, 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 } });