PFPATH

Bulk Data Entry Defines a one-step transfer path analysis.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PFPATH SID CONPT RID RTYPE CONEL CONREL CONVOL    

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
PFPATH 10 11 12 DISP 18 23      

Definitions

Argument Options Description
SID <INTEGER>
setid
SID is referenced by a PFPATH card in the control section.
CONPT <INTEGER>

No default
gsid
The connection points with a SID of type GRID SET.
RID <INTEGER>

No default
rsid
The response SID of type GRIDC. Contribution to each response DOF through the connection points will be calculated.
RPTYPE DISP/VELO/ACCE

Default = DISP

 Criterion for the type of the response; the response type corresponding to a structural degree of freedom could be displacement, velocity or acceleration.
CONEL <INTEGER>

Default = blank
esid
The ELEMENT set consists of elements connected to the connection GRIDs in CONPT. These elements represent connecting paths from the rest of the system to the user-defined control volume.
CONREL <INTEGER>

Default = blank
rsid
The RIGID set consists of the RIGID elements, connected to the connection GRIDs in CONPT. These rigid elements represent connecting paths from the rest of the system to the user-defined control volume.

If CONREL is specified in the 7th entry, the RIGID element IDs must be unique.
CONVOL <INTEGER>

Default = blank
cysid
The GRID set consists of Grids used to define the control volume.

Comments

  1. There can be multiple PFPATH cards with the same SID. However, the connection points should be the same across all the PFPATH entries.
  2. If CONEL and/or CONREL are specified, the set should consist of all the elements outside the control volume connected to the connection GRID's in CONPT.
  3. If CONVOL is not specified, OptiStruct will export a file called, <filename>_outsidecv.fem, which contains a list of all GRID's outside the control volume. This file can be imported into HyperMesh to visualize the grids outside the control volume.