constraintSettingsType

Specification of performance constraints.

Constraints allow vectors of double values to define parameter lapses within a mission segment. The example below illustrates this by means of an exemplary climb profile of a conventional airliner, in which multiple physical and regulatory speed constraints are simultaneously specified over several altitudes (e.g., to account for the crossover altitude):

<endCondition>
    <positionGeo>
        <altitude relationalOperator="ge" uID="altClimb">10058.4</altitude> <!-- FL330 -->
    </positionGeo>
</endCondition>
<constraint>
    <referenceEndConditionUID>altClimb</referenceEndConditionUID>
    <endConditionRatio>0.0;0.303</endConditionRatio> <!-- FL0, FL100 -->
    <continuity>discrete</continuity>
    <calibratedAirSpeed relationalOperator="le">128.61;154.33</calibratedAirSpeed> <!-- 250 [kt], 300 [kt] -->
    <machNumber relationalOperator="le">0.78;0.78</machNumber>
    <prioritySetting>velocity</prioritySetting>
</constraint>

From FL0 until FL100, the vehicle should fly at a velocity less than or equal to CAS = 250 kt or M = 0.78. In this first segment at low altitudes, the constraint on CAS is triggered.

From FL100 until FL330, the vehicle should fly at a velocity less than or equal to CAS = 300 kt or M = 0.78. In this second segment, the vehicle starts by increasing velocity until 300 kt, the constraint on maximum machNumber triggers from the crossover altitude onwards