| handbookAero Element |
HandbookAero tool data
Namespace: Empty
Schema: Empty
Type
ParentsChildren| Name | Occurrences | Description |
|---|---|---|
 Sequence | ||
 tool | Tool identification | |
| aircraftModelUID | Reference to aircraft model | |
| datasetName | [0, 1] | Name of the dataset for HandbookAero calculation |
| referenceValues | [0, 1] | Reference values for aerodynamic computations |
 Choice | ||
| loadCases | Date for HandbookAero loadcase computation | |
| performanceMap | Handbook Aero performance map data | |
| toolParameters | Parameters for the HandbookAero tool |
Attributes| Name | Type | Required | Description |
|---|---|---|---|
 externalDataDirectory |  string | ||
| externalDataNodePath | string | ||
| externalFileName | string |
Remarks0. General overview
Toolspecific data for the HandbookAero tool. HandbookAero is a collection of handbook methods, that can be used to incorporate estimations for aerodynamic effects that are not covered by the simple, physics based aerodynamic models. HandbookAero can either be applied on a clean dataset (in terms of aerodynamics), or on an already existing dataset to extend / modify it. Currently, HandbookAero provides methodes for computing the skin friction drag (based on flat plate analogy) including a thickness correction and a formula based methodology to modify existing aerodynamic results.
In this toolspecific data block, two ways of input definition are possible: Framework integration and Tool input .
- Framework integration is the typical way, how LIFTING_LINE is used via an integration framework. Reference values are taken from the selected aircraft model's <reference> node and operating conditions are specified as links to the corresponding definitions in the selected aircraft model as well. During the input mapping phase (which is done in framework integration before the tool itself is started), reference values and operating conditions are copied into this toolspecific block to create a valid Tool input dataset for the tool itself.
- Tool input is the required input dataset for the HandbookAero tool itself. It is either created by the integration framework (see above), or - if HandbookAero is used as a stand-alone program - it has to be provided by the user.
1. <tool> (mandatory)
Identification of the tool. The <name> subnode is always "HandbookAero", the <version> subnode contains the used toolversion in the form "#x.#y with #x and #y as major and minor version numbers.
2. <aircraftModelUID> (mandatory)
Unique identifier (UID) of the aircraft model to be analyzed.
3. <datasetName> (optional)
Name of the dataset (used during HandbookAero computation only). If this node is missing, the CPACS dataset name is used as default.
4. <referenceValues> (Tool input only, mandatory)
Set of reference values used for HandbookAero computations. This node is required for the Tool input only. In Framework integration, these values are taken form the specified aircraft model's <reference> node (using <length> for all three HandbookAero reference lengths).
5. Either <loadCases>or <performanceMaps> (mandatory)
These nodes contain the operating conditions of the aircraft for the HandbookAero computations. HandbookAero distinguishes between two runmodes: <loadCases> and <performanceMaps> . In <loadCases> mode, a set of individual loadcases is computed. In <performanceMaps> mode, an aerodynamic performance map over a sweep of Mach- and Reynolds-numbers, angles of yaw and of attack is created or modified (optionally extended by delta-performance maps for control surfaces).
6. <toolParameters> (mandatory)
In this node, all the control parameters for HandbookAero are specified.
See Also