HyperWorks Solvers

MATUSR

»Click here to display Table of Contents« OptiStruct > Reference Guide > Input Data > Bulk Data Section:

MATUSR
MATUSR

Bulk Data Entry

MATUSR – Specifies material properties and parameters for user-defined material.

Description

The MATUSR bulk data entry defines material properties and parameters for user-defined material.

Format

(1)	(2)	(3)	(4)	(5)	(6)	(7)	(8)	(9)	(10)
MATUSR	MID	PARAM1	VALUE1	PARAM2	VALUE2	PARAM3	VALUE3
	PARAM4	VALUE4	…
	…
	PROPERTY	PROP1	PROP2	PROP3	PROP4	PROP5	PROP6	PROP7
		PROP8	…

(1)	(2)	(3)	(4)	(5)	(6)	(7)	(8)	(9)	(10)
MATUSR	12	USUBID	5	NDEPVAR	1	EXPAN	ISO
	PROPERTY	210000.0	0.4	320.0	500.0	0.0	180.0	1.2e+2
		1.2e-6

Field	Contents
ID	Each MATUSR Bulk Data Entry should have a unique ID. No default (Integer > 0)
USUBID	User subroutine ID. This allows you to define different types of material properties. Default = Blank (Integer > 0)
NDEPVAR	User-defined variable. Default = 0 (Integer ≥ 0)
EXPAN	Type of thermal expansion coefficients defined on the PROPERTY continuation line (Comment 4). Default = ISO (ISO, ORTHO, or ANISO)
GROUP	User-defined group specified on the group argument of the LOADLIB entry. This field is used to identify the LOADLIB entry to load the corresponding .dll. (Character String)
PROPERTY	Indicates that user-defined material property data are to be defined in the subsequent fields. Thermal expansion coefficient data are defined at the end of the property data (Comments 2, 3, and 4).
PROPi	User-defined material property data. Thermal expansion coefficient data are defined at the end of the property data (Comments 2, 3, and 4). Default = blank (Real)

Comments

1.	The corresponding dynamic linked libraries (.dll) for the user-defined material is loaded based on the LOADLIB entry. If LOADLIB entry is not defined (or if the GROUP parameter is not specified), then OptiStruct loads the umat.dll file from the working directory.

2.	All parameter and value pairs listed before the PROPERTY continuation line are in free format. Therefore, the pair of parameter name and its value can be located anywhere in the defined fields.

3.	The PROPi data are directly passed to the loaded .dll file where it used by the subroutine identified by the USUBID parameter.

4.	If EXPAN parameter is defined, then the final one (ISO), final three (ORTHO), or final six (ANISO) PROPi values are used as the corresponding thermal expansion coefficients.

5.	Parameters other than NOPCL are ignored for Nonlinear Quasi-Static Analysis.

See Also:

Bulk Data Section

Guidelines for Bulk Data Entries

Bulk Data Entries by Function