aeroLimitsMap Element |
Aerodynamic limitations
Namespace: Empty
Schema: Empty
Name | Occurrences | Description |
---|---|---|
All | ||
altitude | Altitude [m] | |
angleOfSideslip | Angle of sideslip | |
incrementMaps | [0, 1] | Increment maps for limitation values due to movable device deflections |
machNumber | Mach number | |
operationLimit | [0, 1] | Vehicle operation limit |
Name | Type | Required | Description |
---|---|---|---|
externalDataDirectory | string | ||
externalDataNodePath | string | ||
externalFileName | string |
This map explicitly specifies limitations of a vehicle in terms of angles of attack and sideslip angles. All vectors, i.e. altitude, machNumber, angleOfSideslip and angleOfAttack, must have the same length. To avoid redundancy with the aeroPerformanceMap, this type does not contain any aerodynamic coefficients.
Since angleOfSideslip and angleOfAttack are closely interdependent for a given machNumber and altitude combination, a positive and negative maximum angleOfAttack is defined for a given combination of machNumber, altitude and angleOfSideslip. The limits of angleOfSideslip can be determined by evaluating the nominal decrease of angleOfAttack values or by agreeint with the data supplier that the minimum and maximum value of the angleOfSideslip vector corresponds with physical limits.
In order to avoid data redundancy, the operational limits should not reflect the extrema of aerodynamic coefficients as these can be extracted from the performanceMap via interpolation.
Note: In future CPACS versions, a revision of the aeroLimitsMap will be targeted, since operational limits are not a purely aerodynamic issue.