Working with the CAE solver languages: property tables

Property tables are the other key component of the solver language system. In CAE, most entities have an associated property table. For example, all loads, constraints, mesh collectors, regions, physical properties, solver-specific solution objects, solver-specific modeling objects, and solutions have associated property tables.

Understanding property tables

Each property table contains a list of all available properties for that entity. For each property, the NX Open for CAE documentation lists:

• the user interface name for the property

• the emphasis or automation name for the property

• the valid input types, such as integer or double value

When you create NX Open for CAE applications, you must correctly specify the name for the property and use the appropriate input type.

Determining the allowable property table settings and inputs

When you create an NX Open for CAE application, there are two different ways to determine an entity’s allowed property table settings and input. You can:

• Create a journal for the entity. Then, look through the journal to find the available properties and their input types.

• Find the entity in the NX Open for CAE documentation. For more information, see NX Open for CAE documentation resources.

Example: using a journal to determine valid properties and settings

For example, when you are working in Pre/Post and Simcenter Nastran is your specified solver, when you use the Hydrostatic Load dialog box, you can specify a value for the Surface Pressure property.

However, if you wanted to create an NX Open for CAE application to automatically specify a Surface Pressure value, you would use the neutral name for Surface Pressure, initialPressure, in your code and make sure that the specified value for the pressure is scalar.

For example, the journal code below sets the initialPressure to a value of 55 lbf/in3.

Python

    scalarFieldWrapper1 = propertyTable1.GetScalarFieldWrapperPropertyValue(        "initialPressure")    expression1 = scalarFieldWrapper1.GetExpression()    unit1 = workSimPart.UnitCollection.FindObject(“PoundForcePerSquareInch”)    workSimPart.Expressions.EditWithUnits(expression1, unit1, "55")    scalarFieldWrapper1.SetExpression(expression1)

VB.NET

Dim scalarFieldWrapper1 As Fields.ScalarFieldWrapperscalarFieldWrapper1 = _ 	propertyTable1.GetScalarFieldWrapperPropertyValue("initialPressure")Dim expression1 As Expressionexpression1 = scalarFieldWrapper1.GetExpression()Dim unit1 As Unit = CType(workSimPart.UnitCollection.FindObject _ 	("PoundForcePerSquareInch"), Unit)workSimPart.Expressions.EditWithUnits(expression1, unit1, "55")scalarFieldWrapper1.SetExpression(expression1)

Notice how only the initialPressure neutral name is used to identify this property. The user interface name, Surface Pressure, does not appear in the journal.

Learn more

NX Open for CAE terminology and concepts

CAD terminology and concepts

CAE terminology and concepts

The importance of the work part in CAE applications

Overview of the CAE data model

Working with objects in the CAE data model

Overview of the CAE solver languages

Working with the CAE solver languages: name strings

Creating undo marks and forcing model updates

Look up more details

NX Open for CAE documentation resources

NX Open for CAE code examples

Quick links

Command reference

Pre/Post video examples

Bulk Entry Descriptions

Simcenter 3D tutorials

Browse Simcenter 3D help by product area

Working with the CAE solver languages: property tables, 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 } });