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> |
|
| CONPT | <INTEGER> No default |
|
| RID | <INTEGER> No default |
|
| 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 |
|
| CONREL | <INTEGER> Default = blank |
If CONREL is specified in the 7th entry, the RIGID element IDs must be unique. |
| CONVOL | <INTEGER> Default = blank |
|
Comments
- There can be multiple PFPATH cards with the same SID. However, the connection points should be the same across all the PFPATH entries.
- 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.
- 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.