# Parameters

Parameter entities parameterize FE entity and geometric entity attributes.

## Abaqus Cards

To properly read and import parameters, independent parameters must be defined before dependent parameters. If parameters are not properly defined, Abaqus will abort the evaluation, and an error message will display.

In the image below, parameter2 must be defined ahead of parameter1. Parameters are evaluated and their values are determined by the solver. The final value, after the evaluation of the parameter, will be written in the input deck. The order in which the parameters are written determines the value assigned to the parameter. The value of Parameter1, regardless of where Parameter1 is written in the input deck, will be 2.
*PARAMETER
parameter1 = 1.0
**HMNAME PROPERTY          1 property1
*SHELL SECTION, ELSET=property1, MATERIAL=Steel
<parameter1>,         5
*PARAMETER
Parameter1 = 2.0

During export, parameters are exported in the order in which they were created. Parameter information is written at the top of the input deck. If a parameter is in an Include file, then it will be written at the top of the Include file.

The keywords, *Parameter Dependence and *Parameter Table are not yet supported.
Card Description
*PARAMETER Defines numerical values through algebraic expressions of parameter names referenced throughout the input file.
Note: Supported:
• Parameters can be created, imported, and exported.
• Edit parameters in the .
• Parameter expressions are evaluated on the fly.
• Parameter expressions can reference another parameter.
• If you edit the value of a parameter, the other parameters that references it will be updated accordingly.
• Edit parameterized variables in the .
• You can create and assign parameters from the fields of an entity in .
• Load magnitude, element node ID, Node coordinate, and so on can all be parameterized.
Limitations:
• Support is limited to all properties and materials.
• Parameterization of entity IDs is not supported.
• Unsupported parameterized entities and fields are replaced with corresponding parameter values during import, to avoid the loss of data.
• In macros and browsers, if any parameterized variable is changed, you will receive a warning message in the message bar and the value will not be updated.
• The creation of duplicate parameters is not supported. During import, duplicate parameters and their corresponding expression will be replaced with the resolved value in the input deck.

## LS-DYNA Cards

Card Description
• *PARAMETER
• *PARAMETER_LOCAL
Defines numerical values of parameter names referenced throughout the input file.
Note: Supported:
• Parameters can be created, imported, and exported.
• Edit parameter expressions in the .
• Parameter expressions are evaluated on the fly.
• A parameter expression can reference another parameter.
• If you edit the value of a parameter, the other parameters that references it will be updated accordingly.
• Edit parameterized values in the .
• Same parameters can be used for negation by prefixing negative signs “-“.
• You can create and assign parameters from the fields of an entity in .
• Parameters can be referenced in angular brackets, along with the usual reference using “&”.
• When more than one *PARAMETER with the same name exist in a deck, the first one will be retained.
• Parameters with same names are maintained when *PARAMTER_LOCAL is used and they are specified in different include files.
• Free format is supported.
Limitations:
• Support is limited to all FE entities except elements and nodes.
• Parameterization of entity ID’s is only supported for Components, Properties, Materials and Curve.
• Parameterization of entity ID’s is not supported.
• Unsupported parameterized entities and fields are replaced with corresponding parameter values during import, to avoid the loss of data.
• In macros and browsers, if any parameterized variable is changed a warning message will appear in the message bar and the value will not be updated.
• *PARAMETER_EXPRESSION
• *PARAMETER_EXPRESSION_LOCAL
Defines numerical values through algebraic expressions of parameter names referenced throughout the input file.
Note: Supported:
• Parameters can be created, imported, and exported.
• You can edit parameters and parameter expressions in the .
• Parameter expressions are evaluated on the fly.
• Parameter expression can reference another parameter.
• If you edit the value of a parameter, the other parameters that references it will be updated accordingly.
• Same parameters can be used for negation by prefixing negative signs “-“.
• Edit parameterized variables in the .
• Parameters can be referenced in angular brackets, along with the usual reference using “&”.
• When more than one *PARAMETER_EXPRESSION with the same name exists in a deck, the first one will be retained.
• Parameters with the same names are maintained when *PARAMTER_EXPRESSION_LOCAL is used and they are specified in different include files.
• Free format is supported.
Limitations:
• Support is limited to all FE entities except elements and nodes.
• Parameterization of entity ID’s is only supported for Components, Properties, Materials and Curves.
• Parameterization of entity ID’s is not supported.
• Unsupported parameterized entities and fields are replaced with corresponding parameter values during import, to avoid the loss of data.
• In Macros and Browser, if any parameterized variable is changed a warning message will appear in the message bar and the value will not be updated.

## Nastran Cards

Card Description
%DEFREPSYM Defines default parameter values.
Note: Can be created, imported, and exported.

Edit in the .

%DEFREPWIDTH Defines default width information.
Note: Automatically created during export when a parameter is created in Engineering Solutions.
%SETREPSYM Defines default values.
Note: Cannot be created in Engineering Solutions, only imported and exported.
%UNDEFREPSYM Clears or unsets default parameter values.
Note: Cannot be created in Engineering Solutions, only imported and exported.
%UNSETREPSYM Clears or unsets parameter values.
Note: Cannot be created in Engineering Solutions, only imported and exported.
Materials that can be parameterized in the NastranMSC user profile.
• MAT1
• MAT10
• MAT2
• MAT4
• MAT5
• MAT8
• MAT9
• MATEP
• MATG
• MATHE
• MATHP
Properties that can be parameterized in the NastranMSC user profile.
• PAABSF
• PACBAR
• PACINF
• PAERO2
• PBEND
• PBUSH
• PBUSH1D
• PCOMP
• PCOMPG
• PCOMPP
• PCONVM
• PWELD
• PDAMP
• PELAS
• PELAST
• PFAST
• PGAP
• PHBDY
• PMASS
• PROD
• PSEAM
• PSHEAR
• PSHELL
• PSHELL1
• PTUBE
• PVISC

## OptiStruct Cards

• The parameter entity is supported in the OptiStruct interface, however support is limited to parameters that are created in Engineering Solutions and associated with parameters in HyperStudy.
• Scope is limited to material and property entity types. Also, within those entity types, parameterization is restricted to template attributes of type double.
• Parameterized attributes are unparameterized with their original value during export.
• Parameters cannot be exported or imported.

## Radioss Cards

Card Description
/GLOBAL/INT_EXPR/ Defines numerical values through algebraic expressions of parameter names referenced throughout the input file.
Note: Supported:
• Parameters can be created, imported, and exported.
• Edit parameter expressions in the =.
• Parameter expressions are evaluated on the fly.
• Parameter expressions can reference another parameter.
• If you edit the value of a parameter, the other parameters that references it will be updated accordingly.
• Same parameters can be used for negation by prefixing negative signs “-“.
• Edit parameterized variables in the .
Limitations:
• Support is limited to all FE entities except elements and nodes.
• Parameterization of entity IDs is not supported.
• Unsupported parameterized entities and fields are replaced with corresponding parameter values during import, to avoid the loss of data.
• In macros and browsers, if any parameterized variable is changed, you will receive a warning message in the message bar and the value will not be updated.
/GLOBAL/INTEGER/ Defines numerical values of parameter names referenced throughout the input file.
Note: Supported:
• Parameters can be imported, exported, and created.
• Edit parameter expressions in the .
• Create and assign parameters on the fly in .
• Same parameters can be used for negation by prefixing negative signs “-“.
• Edit parameterized variables in the .
Limitations:
• Support is limited to all FE entities except elements and nodes.
• Parameterization of entity IDs is not supported.
• Unsupported parameterized entities and fields are replaced with corresponding parameter values during import, to avoid the loss of data.
• In macros and browser, if any parameterized variable is changed, you will receive a warning message in the message bar and the value will not be updated.
/GLOBAL/REAL/ Defines numerical values of parameter names referenced throughout the input file.
Note: Supported:
• Parameters can be imported, exported, and created.
• Edit parameter expressions in the .
• Create and assign parameters on the fly in .
• Same parameters can be used for negation by prefixing negative signs “-“.
• Edit parameterized variables in the .
Limitations:
• Support is limited to all FE entities except elements and nodes.
• Parameterization of entity IDs is not supported.
• Unsupported parameterized entities and fields are replaced with corresponding parameter values during import, to avoid the loss of data.
• In macros and browser, if any parameterized variable is changed, you will receive a warning message in the message bar and the value will not be updated.
/GLOBAL/REAL_EXPR/ Defines numerical values through algebraic expressions of parameter names referenced throughout the input file.
Note: Supported:
• Parameters can be imported, exported, and created.
• Edit parameter expressions in the .
• Parameter expressions are evaluated on the fly.
• Parameter expressions can reference another parameter.
• If you edit the value of a parameter, the other parameters that references it will be updated accordingly.
• Same parameters can be used for negation by prefixing negative signs “-“.
• Edit parameterized variables in the .
Limitations:
• Support is limited to all FE entities except elements and nodes.
• Parameterization of entity IDs is not supported.
• Unsupported parameterized entities and fields are replaced with corresponding parameter values during import, to avoid the loss of data.
• In macros and browser, if any parameterized variable is changed, you will receive a warning message in the message bar and the value will not be updated.

## Samcef Cards

• The parameter entity is supported in the Samcef interface, however these parameters cannot be directly exported in HyperStudy.
• Scope is limited to material and property entity types.
• Parameters are exported as the macro command /ABRE in the deck.
• Parameters can be exported or imported.