AECOMP
Bulk Data Entry Defines a component for use in monitoring point definition or external splines.
Format
(1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) |
---|---|---|---|---|---|---|---|---|---|
AECOMP | NAME | LISTTYPE | LISTID1 | LISTID2 | LISTID3 | LISTID4 | LISTID5 | LISTID6 | |
LISTID7 | etc. |
Example
(1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) |
---|---|---|---|---|---|---|---|---|---|
AECOMP | TAILSUR | CAERO | 200 | 300 |
Definitions
Field | Contents | SI Unit Example |
---|---|---|
NAME | Character string to identify the component. 1 (Character; up to 8 characters) |
|
LISTTYPE | Aerodynamic.
|
|
LISTIDi | Identification number of either CAERO1, AELIST, or SET1 entries that define the entities associated with the component. |
Comments
- The NAME field should be unique among all AECOMP and AECOMPL entries.
- If the component is defined on the
structure, LISTIDi should refer to
SET1 entries that define the list of associated GRID
points. For LISTTYPE= AELIST or
CAERO, the LISTIDs should refer to
AELIST or CAERO1 entries,
respectively. For Doublet Lattice Method (DLM) models
(CAERO1), the set of points defined by the
AELIST are the box identification numbers.
For example, if the control surfaces grids are desired, the same AELIST used for the AESURF can be referred to here. A particular AECOMP component should be either aerodynamic mesh or a structural mesh, but it cannot be both.
- The AECOMPL entry can be used to combine AECOMP entries into new components. When combining components, the structural and aerodynamic mesh-based components should always be separate.