aeroPerformance: adjustment of the aeroLimitsMap

[MarAlder]

cpacs/vehicles/aircraft/analyses/aeroPerformance/aeroMap:

At the previous stakeholder meeting @CLiersch reported about first practical experiences with the aeroLimitsMap from the current v3.3-beta release. It has been shown that is not clear what the semantic meaning of the limits is. Furthermore, maximum values are correlated and the schema does not distinguish between independent and dependent variables.

Therefore, we need to take closer look at the aeroLimitMap to clearly specify the meaning of the corresponding variables and to decide whether to implement the proposal into the upcoming release candidate or not.

If you like to participate in a working group on this topic, please comment to this issue or contact us via e-Mail (Those who volunteered at the meeting are already on my list).

[MarAlder]

Result of the working group

Since operationLimits must involve more than just aerodynamics (e..g, weight&balance, structural elasticity, etc.) the aeroMap is maybe not a good place for such a multidisciplinary analysis result. Therefore, the operationLimit element needs more detailed discussion with a larger group of stakeholders. We can not include this anymore in CPACS 3.3. Before having a better idea of how to deal with operation limits in CPACS we should also not simply remove the node. Instead, we propose a small fix for the current implementation to account for the close coupling between angleOfAttack and angleOfSideslip:

Schema

Documentation remarks