Common nomenclature: air speed

[MarAlder]

We should try to introduce a naming convention for velocities.

Current implementations in the 3.3 beta-release are:

• CAS:
  • constraintSettingsType
  • missionSegmentEndConditionType
  • missionStartConditionType
• vTAS: flightDynamicsTrimResultType
• cAS: flightPointType
• tAS: flightPointType
• vCAS: pointPerformanceConstraintsType
• trueAirSpeed: flightEnvelopeSpeedType

Decisions:

• Should we in future distinguish between calibrated and true air speed or rely on conversion with atmospheric model?
• Which style to use: calibratedAirSpeed, CAS, cAS or vCAS?

[HHOPs]

• I think we should rely on the ISA-atmosphere for conversion CAS2TAS - as this is normed and commonly used (ISO 2533:1975, https://www.iso.org/standard/7472.html)
• For the symbol representation I would recommend to use the respective norms - ISO 1151-1:1988, https://www.iso.org/standard/5699.html

[MarAlder]

For the symbol representation I would recommend to use the respective norms - ISO 1151-1:1988, https://www.iso.org/standard/5699.html

I have no access to this. What does the norm say?

I also got the feedback that we are writing most parameters as full names, e.g. machNumber, altitude, angleOfAttack, etc, and therefore we should also try to write velocities as calibratedAirSpeed and trueAirSpeed.

[MarAlder]

Renamed to calibratedAirSpeed and trueAirSpeed for:

• constraintSettingsType (missionDefinition)
• missionSegmentEndConditionType (missionDefinition)
• missionStartConditionType (missionDefinition)
• flightDynamicsTrimResultType (flightDynamics analysis)
• pointPerformanceConstraintsType (pointPerformance)
• flightEnvelopeSpeedType (flightEnvelope)

❗ ❗ ❗ This breaks backwards compatibility, so please review carefully. However, the upper types are used within current or planned changes in the 3.3-RC.

Not changed yet for (as no reply from stakeholder and currently strongly used in the trajectory node):

• flightPointType