Addition of configuration node to describe aircraft and payload configurations

[ErwinMoerland]

It is suggested to add a node to the vehicle description in CPACS: /cpacs/vehicles/.../model/configurations/configuration, where the configuration settings are provided and linked to through uID's. Required for: weightAndBalance analysis, loadCase definitions, mission and point performance analysis

Within this node the following should be described:

• payload configuration
• aircraft configuration, controlling the following elements:
  • high lift devices + controlDistributors
  • landing gear, brakes, airbrakes
  • mass case transitions

[MarAlder]

A first implementation (21547a0) includes the needs from the loadCase working group (#637):

Control devices include all controllable elements, such as high lift devices, landing gear, brakes, airbrakes (and maybe afterburner as well).

In this context we also consided how we want to continue with the aircraft/model/global node. Maybe put the configuration node in there as well?

[MarAlder]

A current example from @HHOPs includes a configuration within the mission definition:

<configuration>
    <flaps relationalOperator="eq">0.0</flaps>
    <gear relationalOperator="eq">0.0</gear>
    <brake relationalOperator="eq">0.0</brake>
</configuration>

Is the relational operator required here or just used because it was defined like this in the schema at this point in time?

Furthermore, please check the completeness of the aircraft/analyses/trajectories/trajectory/ node. It looks like a powerful way to combine the general mission definition with aircraft specific information, such as configuration settings, atmospheric conditions or engine conditions.

[HHOPs]

I used the relational operator, as it was obligatory - would propose to set it optional, as a need can probably arise, when eventually introducing lapses for configuration changes (e.g. brake activation etc.)...

[MarAlder]

Ok, thanks for the clearification. I opened a dedicated brach for this issue where I propose the following:

In a first step I would try to avoid relational parameters as it has to be discussed how to deal with it when used by, e.g., aerodynamic analysis.

The mission definition (#634), load cases (#637) and maybe in future releases the aeroMaps (#505) could refer to this node by its uID.

[MarAlder]

Addition of control distributors as used in aeroMaps:

[MarAlder]

A configurationType has been added with #660 which can be used for aeroMaps, aeroCases etc. Here an example of the aeroMap:

It is furthermore implemented in the aeroCase element.