DVPREL2 – Relates Design Variables to Analysis Model Properties via Relationship Defined by User-supplied Equation
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. |
|
|
|
|
|
|
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 |
|
|
|
|
|
|
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 |
|
|
|
|
|
|
|
(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 identity. Each DVPREL2 card must have a unique ID. No default (Integer > 0) |
|
TYPE |
Property type to be related (see table below). No default (Character) |
|
PID |
Property Identification Number or, when PTYPE is PCOMPG, G# may be used, where # is the GPLYID. See comment 5. No default (Integer > 0) |
|
PNAME/ |
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 |
DESVAR flag indicating DESVAR ID numbers follow. |
|
DVIDi |
DESVAR ID. No default (Integer > 0) |
|
DTABLE |
DTABLE flag indicating DTABLE labels follow. |
|
LABLi |
Constant label on DTABLE card. No default (Character) |
Depending on the TYPE entry, the FID of the appropriate design parameter can be determined from the table below.
|
Type |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
|
CONM2 |
|
|
|
|
M |
X1 |
X2 |
X3 |
|
|
|
FID 11-20 |
|
I11 |
I12 |
I22 |
I13 |
I23 |
I33 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Type |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
|
PBAR |
|
|
|
A |
I1 |
I2 |
J |
NSM |
|
|
|
FID 11-20 |
|
C1 |
C2 |
D1 |
D2 |
E1 |
E2 |
F1 |
F2 |
|
|
FID 21-30 |
|
K1 |
K2 |
I12 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Type |
Field numbers are not allowed for PBARL. |
|||||||||
|
PBARL |
DIMi |
NSM |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Type |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
|
PBEAM |
|
|
|
A(A) |
I1(A) |
I2(A) |
I12(A) |
J(A) |
NSM(A) |
|
|
FID 11-20 |
|
C1(A) |
C2(A) |
D1(A) |
D2(A) |
E1(A) |
E2(A) |
F1(A) |
F2(A) |
|
|
FID 21-30 |
|
|
|
|
|
|
|
|
|
|
|
FID 31-40 |
|
K1(A) |
K2(A) |
|
|
NSI(A) |
NSI(B) |
|
|
|
|
FID 41-50 |
|
M1(A) |
M2(A) |
M1(B) |
M2(B) |
N1(A) |
N2(A) |
N1(B) |
N2(B) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Type |
Field numbers are not allowed for PBEAML. |
|||||||||
|
PBEAML |
DIMi |
NSM |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Type |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
|
PBUSH |
|
|
|
K1 |
K2 |
K3 |
K4 |
K5 |
K6 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Type |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
|
PCOMP |
|
|
Z0 |
NSM |
|
|
|
|
|
|
|
FID 11-20 |
|
|
T1 |
THETA1 |
|
|
T2 |
THETA4 |
|
|
|
FID 21-30 |
|
|
T3 |
THETA3 |
|
|
… |
… |
|
|
|
… |
|
|
… |
… |
|
|
… |
… |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Type |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
|
PCOMPG |
|
|
Z0 |
NSM |
|
|
|
|
|
|
|
FID 11-20 |
|
|
|
T1 |
THETA1 |
|
|
|
|
|
|
FID 21-30 |
|
|
|
T2 |
THETA2 |
|
|
|
|
|
|
… |
|
|
|
… |
… |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Type |
Field numbers do not apply for PCOMPG when referencing global plies. See comment 5. |
|||||||||
|
PCOMPG |
T |
THETA |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Type |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
|
PELAS |
|
|
K1 |
|
S1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Type |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
|
PMASS |
|
|
M |
|
M |
|
M |
|
M |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Type |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
|
PROD |
|
|
|
A |
|
|
NSM |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Type |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
Field |
|
PSHELL |
|
|
|
T |
|
12*I/T3 |
|
TS/T |
NSM |
|
|
FID 11-20 |
|
Z1 |
Z2 |
|
|
|
|
|
|
|
Type cannot be PSOLID.
When Type is PBARL or PBEAML, users should pay close attention to the variable ranges to avoid invalid dimensions.
PBEAML definitions with more than one section definition may not be referenced by a DVPREL1.
Properties of PBARL/PBEAML have to be controlled through DIMs (i.e., cannot be controlled directly), with the exception of NSM.
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.
Go To
Guidelines for Bulk Data Entries
Alphabetical List of Bulk Data Entries