DVPREL1

Bulk Data Entry

DVPREL1 – Relates Design Variables to Analysis Model Properties

Description

Linearly relates a design variable to an analysis model property using the equation:

$image\pi=co.gif$

Format

(1)	(2)	(3)	(4)	(5)	(6)	(7)	(8)	(9)	(10)
DVPREL1	ID	TYPE	PID	PNAME/FID			C0
	DVID1	COEF1	DVID2	COEF2	Etc.

Example 1

To relate the thickness value on a PSHELL card (field 4) to Design Variable 5.

(1)	(2)	(3)	(4)	(5)	(6)	(7)	(8)	(9)	(10)
DVPREL1	88	PSHELL	1	4			0.0
	5	1.

Example 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)
DVPREL1	88	PSHELL	1	T			0.0
	5	1.

Associated Card

DESVAR 5 5.00 1.50 9.90

Field	Contents
ID	Response identity. Each DVPREL1 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/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)
C0	Constant in relationship equation. Default = 0.0 (Real. Default=0.0)
DVIDi	DESVAR ID. No default (Integer > 0)
COEFi	Coefficient in relationship equation. Default = 1.0 (Real. Default = 1.0)

Types

Depending on the TYPE entry, the FID of the appropriate design parameter can be determined from the table below.

Type	Field 1	Field 2	Field 3	Field 4	Field 5	Field 6	Field 7	Field 8	Field 9	Field 10
CONM2					M	X1	X2	X3
FID 11-20		I11	I12	I22	I13	I23	I33

Type	Field 1	Field 2	Field 3	Field 4	Field 5	Field 6	Field 7	Field 8	Field 9	Field 10
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 1	Field 2	Field 3	Field 4	Field 5	Field 6	Field 7	Field 8	Field 9	Field 10
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 1	Field 2	Field 3	Field 4	Field 5	Field 6	Field 7	Field 8	Field 9	Field 10
PBUSH				K1	K2	K3	K4	K5	K6

Type	Field 1	Field 2	Field 3	Field 4	Field 5	Field 6	Field 7	Field 8	Field 9	Field 10
PCOMP			Z0	NSM
FID 11-20			T1	THETA1			T2	THETA4
FID 21-30			T3	THETA3			…	…
…			…	…			…	…

Type	Field 1	Field 2	Field 3	Field 4	Field 5	Field 6	Field 7	Field 8	Field 9	Field 10
PCOMPG			Z0	NSM
FID 11-20				T1	THETA1
FID 21-20				T2	THETA2
…				…	…

Type	Field numbers do not apply for PCOMPG when referencing global plies. See comment 5.
PCOMPG	T	THETA

Type	Field 1	Field 2	Field 3	Field 4	Field 5	Field 6	Field 7	Field 8	Field 9	Field 10
PELAS			K1		S1

Type	Field 1	Field 2	Field 3	Field 4	Field 5	Field 6	Field 7	Field 8	Field 9	Field 10
PMASS			M		M		M		M

Type	Field 1	Field 2	Field 3	Field 4	Field 5	Field 6	Field 7	Field 8	Field 9	Field 10
PROD				A			NSM

Type	Field 1	Field 2	Field 3	Field 4	Field 5	Field 6	Field 7	Field 8	Field 9	Field 10
PSHELL				T		12*I/T3		TS/T	NSM
FID 11-20		Z1	Z2

Comments

TYPE cannot be PSOLID.
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.

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 PBARL or PBEAML, users should pay close attention to the variable ranges to avoid invalid dimensions. For example, the inner radius of a tube cross section cannot exceed the outer radius. It is necessary to prevent combinations of dimensions from taking on values that are physically meaningless. Some constraints are applied automatically on section dimensions. The table below summarizes these constraints. Constraints are satisfied when they are < 0.0.

Section Type	Constraint
TUBE	DIM2 – DIM1
I	DIM4 – DIM2
	DIM4 – DIM3
	DIM5 + DIM6 – DIM1
CHAN	2 * DIM4 – DIM2
	DIM3 – DIM1
T	DIM3 – DIM2
	DIM4 – DIM1
BOX	DIM4 – DIM1
	DIM3 – DIM2
CROSS	DIM4 – DIM3
H	DIM4 – DIM3
T1	DIM4 – DIM1
I1	DIM3 – DIM4
CHAN1	DIM3 – DIM4
Z	DIM3 – DIM4
CHAN2	DIM2 – DIM3
	2 • DIM1 – DIM4
T2	DIM4 – DIM1
	DIM3 – DIM2
BOX1	DIM4 + DIM3 – DIM2
	DIM5 + DIM6 – DIM1
HEXA	2 * DIM1 – DIM2
HAT	2 * DIM2 – DIM1
	2 * DIM2 – DIM3
L	DIM3 – DIM2
	DIM4 – DIM1
HAT1	DIM3 – DIM1
	2 * DIM4 – DIM2
	2 * DIM4 + DIM5 – DIM2

Go To

Bulk Data Section

Guidelines for Bulk Data Entries

Alphabetical List of Bulk Data Entries

The Input File

Return to Altair HyperWorks Index