Property entities are used to define and store 1D, 2D, and 3D property definitions for a model. Properties are created, edited, deleted, and shown under the Property folder within the Model browser. Properties also have a property view within the Model browser.
Properties do not have a display state, but they do have a "by property" visualization color mode which colors the model according to the colors assigned to each property based on element property relationships. The "by property" visualization color mode is automatically set when you enter the property view within the Model browser. In addition, you can manually set the "by property" visualization color mode using the element color mode icon on the Model browser toolbar. Element property relationships are user profile (solver interface) dependent and are described in the section Element Property and Material Assignment Rules. In general, when a component is assigned a property, that property assignment is applied to all elements collected by that component. The method of assigning properties at the component level is therefore referred to as indirect property assignment. Direct property assignment is performed directly on the elements themselves. Direct property assignments always take precedence over indirect property assignments.
Properties have an active and export state. The active state of a property controls the listing of the property in the Model browser and any of its views. If a property entity is active, then it is listed in the Model browser and any of its views. If a property entity is inactive, then it is not listed in the Model browser or any of its views.
The export state of a property entity controls whether or not that property is exported when the custom export option is utilized. The all export option is not affected by the export state of a property. The active and export states of property entities can be controlled using the Entity State browser.
The data names associated with properties can be found in the data names section of the HyperMesh Reference Guide.
Solver Card Support for Properties
RADIOSS (Block Format) has many properties and most of them are supported. In addition RADIOSS allows you to program your own properties (mostly for springs) that can be used in a simulation. In order to handle the unsupported and user defined RADIOSS properties, a separate card image called "PROP_UNSUPPORTED" has been introduced. Any unsupported property will be read with card image PROP_UNSUPPORTED with its ID and its associativity with component preserved. You can also create the property in HyperMesh as well. In this card image, all property sub-options, parameters, and data lines are supported as simple text. HyperMesh does not check the validity or syntax of any data in this mode. You must manually check the validity of the data. No editing, updating, or review of the property data is intended. Also time step calculation, mass calculation, penetration check are not available for the component that refers to this property. The property is displayed in the Model browser, Solver browser, and in the Component table. The supported RADIOSS starter cards in RADIOSS (Block Format) 5.1, 9.0, 10.0 and 11.0 are listed below. You can quickly create these cards by right-clicking in the Solver browser and selecting Create Cards.
|
The property data cards for OptiStruct can be created by loading and editing card images into property collectors. Properties can be assigned to components or elements.
|
The following Abaqus keywords are supported as properties:
|
|
|
|
Only one card image can be loaded into each property collector. 1D elements can be grouped into components with 2D and 3D elements for display purposes. The component groupings are maintained on export and import. To assign 1D elements to property collectors, select the property collector from property = in the appropriate 1D element panel. Properties for PBAR and PBEAM cards can be manually input in the card image or automatically created using the HyperBeam module. See the HyperBeam online help for more information. The HM_ELAS card defines properties for an HM_Spring element.
The Nastran and OptiStruct interfaces allow the property between groups to have the same ID. For example, PBAR3, PSHELL 3, PSOLID 3, etc. Duplicate IDs within the same group is not allowed. Nastran and OptiStruct properties are grouped as follows:
|
|
The following property data blocks are supported in the PERMAS interface:
|
The following cards are supported in the Samcef interface:
|
HyperMesh Entities & Solver Interfaces