HyperWorks Solvers

DVPREL2

DVPREL2

Previous topic Next topic Expand/collapse all hidden text  

DVPREL2

Previous topic Next topic JavaScript is required for expanding text JavaScript is required for the print function  

Bulk Data Entry

DVPREL2 – Relates Design Variables to Analysis Model Properties via Relationship Defined by User-supplied Equation

Description

Relates a design variable to an analysis model property using a relationship defined by a DEQATN card. The equation inputs come from the referenced DESVAR values and the constants defined on the DTABLE card.

Format

(1)

(2)

(3)

(4)

(5)

(6)

(7)

(8)

(9)

(10)

DVPREL2

ID

TYPE

PID

PNAME/FID

 

 

EQID

 

 

 

DESVAR

DVID1

DVID2

DVID3

DVID4

DVID5

DVID6

DVID7

 

 

 

DVID8

DVID9

etc.

 

 

 

 

 

 

DTABLE

LABL1

LABL2

LABL3

LABL4

LABL5

LABL6

LABL7

 

 

 

LABL8

etc.

 

 

 

 

 

 

hmtoggle_plus1Example 1

A rectangular bar of width W and depth D is defined using the PBAR card. The required fields on the PBAR for Area, I1 and I2 are all related to the width and depth, which are the design variables, by the referenced equations.

(1)

(2)

(3)

(4)

(5)

(6)

(7)

(8)

(9)

(10)

DVPREL2

201

PBAR

1

4

 

 

101

 

 

 

DESVAR

5

6

 

 

 

 

 

 

DVPREL2

203

PBAR

1

5

 

 

102

 

 

 

DESVAR

5

6

 

 

 

 

 

 

DVPREL2

204

PBAR

1

6

 

 

103

 

 

 

DESVAR

5

6

 

 

 

 

 

 

hmtoggle_plus1Example 2

This example is the same as example 1 (above), except that it defines PNAME.

(1)

(2)

(3)

(4)

(5)

(6)

(7)

(8)

(9)

(10)

DVPREL2

201

PBAR

1

A

 

 

101

 

 

 

DESVAR

5

6

 

 

 

 

 

 

DVPREL2

203

PBAR

1

I1

 

 

102

 

 

 

DESVAR

5

6

 

 

 

 

 

 

DVPREL2

204

PBAR

1

I2

 

 

103

 

 

 

DESVAR

5

6

 

 

 

 

 

 

Associated Cards

(1)

(2)

(3)

(4)

(5)

(6)

(7)

(8)

(9)

(10)

DESVAR

5

W

6.0

1.0

10.0

 

 

 

 

DESVAR

6

D

5.0

1.0

20.0

 

 

 

 

DEQATN

101

AREA(W,D) = W*D

DEQATN

102

I1(W,D) = (W*D**3)/12

DEQATN

103

I2(W,D) = (D*W**3)/12

PBAR

1

222

0.1

19e-4

1e-3

 

 

 

 

 

Field

Contents

ID

Relationship identification number.  ID must be unique with respect to other DVPREL1 cards.

No default (Integer > 0)

TYPE

Property type to be related (see DVPREL - Types).

No default (Character)

PID

Property identification number. When PTYPE is PCOMPG, G# may be used where # is the GPLYID. When PTYPE is PCOMPP, P# may be used where # is the PLY ID. See comment 5.

No default (Integer > 0)

PNAME/
FID

Property name, such as "A" or "T" (as in the documentation of the property cards), or field number in property card (see table below). For the PSHELL property 12I/T3, only the filed number (6) is allowed. For PBARL and PBEAML only property names are allowed, as different sections use different fields.

No default (Character or Integer > 0)

EQID

Equation ID of DEQATN data.

No default (Integer > 0)

DESVAR

Indicates DESVAR ID numbers follow.

DVIDi

DESVAR ID.

No default (Integer > 0)

DTABLE

Indicates DTABLE labels follow.

LABLi

Constant label on DTABLE card.

No default (Character)

Comments

1.Type cannot be PSOLID.
2.When Type is PBARL or PBEAML, users should pay close attention to the variable ranges to avoid invalid dimensions.
3.PBEAML definitions with more than one section definition may not be referenced by a DVPREL1.
4.Properties of PBARL/PBEAML have to be controlled through DIMs (cannot be controlled directly), with the exception of NSM.
5.When TYPE is PCOMPG, either global plies or property specific plies may be selected.

To select property specific plies, the format is similar to that used for other property types where the property identification number of the PCOMPG is entered in the PID field and then either PNAME or FID is used to identify the value to be related. In this scenario, only the property with an ID given in the PID field is affected.

To select global plies, G# is entered in the PID field where # is the GPLYID of a global ply. In this instance, FID is not applicable so T or THETA is used in the PNAME field to relate either the thickness or orientation, respectively. In this scenario, all plies that use the given GPLYID are affected.

When TYPE is PCOMPP, P# is entered in the PID field where # is the ID of a PLY entity. In this instance, FID is not applicable so T or THETA is used in the PNAME field to relate either the thickness or orientation, respectively.

6.In the PCOMP property, the damping coefficient, GE is a designable value and can be referenced in the PNAME/FID field.
7.This card is represented as an optimization designvariable in HyperMesh.

See Also:

Bulk Data Section

Guidelines for Bulk Data Entries

Bulk Data Entries by Function

The Input File