
<section id='BaseOps_TrainingProfileChunk_id'
webfilename='trainingprofilechunk'>
    <title>
        Editing Airspace Profiles
    </title>
    <para>
        An <italic>airspace profile</italic> describes the operational
        characteristics (engine power setting, altitude profile, frequency
        of operations, etc.) of an aircraft operating in a either a <link
        target='#BaseOps_MilitaryOperatingAreaChunk_id'>military operations
        area</link> (MOA) or a <link
        target='#BaseOps_MilitaryTrainingRouteChunk_id'>military training
        route</link> (MTR).
    </para>
    <para>
        Airspace profiles are used by the MRNMap noise model. Unless that
        model is selected, the parts of the BaseOps user interface dealing
        with airspace profiles will be hidden. See <iref
        target='BaseOps_NoiseModelsUsed_id'/>.
    </para>
    <para>
        To work with airspace profiles, choose Airspace Profiles from
        the <link target='#BaseOps_ListPane_id'>object type selector dropdown
        list</link>. Airspace profiles can be added, duplicated, and deleted
        as described in <iref target='BaseOps_ListPane_id'/>.
    </para>
    <para>
        To edit a airspace profile, first select it in the <link
        target='#BaseOps_ListPane_id'>object list</link>, then edit it
        in the <link target='#WCF_ApplicationMainWindow_id'>text pane</link>.
        Airspace profiles have numerous properties. These are listed below,
        grouped for easy reference.
    </para>
    <section>
        <title>
            Profile Name and Notes
        </title>
        <exhibit>
            <img
            src='BaseOps_TrainingProfileChunk_NameAndNotes_ScreenCap.png'/>
        </exhibit>
        <unorderedlist>
            [-include "BaseOps_NameLongNameNotes_ListItems.rxl" ObjectTypeName='airspace profile'-]
        </unorderedlist>
    </section>
    <section>
        <title>
            Area or Route Information
        </title>
        <exhibit>
            <img
            src='BaseOps_TrainingProfileChunk_AreaOrRouteInformation_ScreenCap.png'/>
        </exhibit>
        <unorderedlist>
            <listitem>
                <para>
                    <italic>Area or Route</italic> - The MOA or MTR associated with
                    the airspace profile. This defines the geographic region where
                    the aircraft operates.
                </para>
                <para>
                    Select the MOA or MTR from the dropdown list. Press the Add button
                    <img src='intres:WCF_AddPlusSignToolbarButtonBitmap'/> to add
                    a new MOA or MTR. Press the Go To button <img
                    src='intres:BaseOps_GotoToolbarButtonBitmap'/> to edit the selected
                    MOA or MTR.
                </para>
                <para>
                    See <iref target='BaseOps_MilitaryOperatingAreaChunk_id'/> and
                    <iref target='BaseOps_MilitaryTrainingRouteChunk_id'/> for more
                    information.
                </para>
            </listitem>
            <listitem>
                <para>
                    <italic>Standoff</italic> - The distance from the boundary of
                    a MOA where an aircraft begins to turn while operating in that
                    MOA. In the turning zone, the frequency of aircraft operations
                    linearly decreases, reaching zero at the MOA's boundary.
                </para>
                <para>
                    The standoff distance is only applicable to MOAs, and is hidden
                    when an MTR is selected.
                </para>
                <para>
                    You can change the units used to specify the standoff distance:
                    see <iref target='BaseOps_CaseUnits_id'/>.
                </para>
            </listitem>
        </unorderedlist>
    </section>
    <section>
        <title>
            Operation Counts
        </title>
        <exhibit>
            <img
            src='BaseOps_TrainingProfileChunk_Operations_ScreenCap.png'/>
        </exhibit>
        <unorderedlist>
            <listitem>
                <para>
                    <italic>Annual Ops</italic> - The average number of times per
                    year that the airspace profile is flown during the day, evening,
                    and night. Note that day, evening, and night are precisely defined
                    periods: see <iref target='BaseOps_CaseChunk_Operations_id'/>.
                    The evening period will be displayed only if the number of daily
                    periods for this BaseOps case is three.
                </para>
                <para>
                    The number of monthly operations is calculated by dividing the
                    annual operations by 12. The number of daily operations is calculated
                    by dividing the monthly operations by the average flying days
                    per month: see <iref target='BaseOps_CaseChunk_Operations_id'/>.
                </para>
            </listitem>
            <listitem>
                <para>
                    <italic>Air Time</italic> - The length of time that the aircraft
                    operates in a MOA as part of a single operation. The MOA's average
                    daily usage time for the airspace profile is calculated by multiplying
                    the air time by the number of daily operations.
                </para>
                <para>
                    Air time is only applicable to MOAs, and is hidden when an MTR
                    is selected.
                </para>
                <para>
                    You can change the units used to specify air times: see <iref
                    target='BaseOps_CaseUnits_id'/>.
                </para>
            </listitem>
        </unorderedlist>
    </section>
    <section>
        <title>
            Aircraft Information
        </title>
        <exhibit>
            <img
            src='BaseOps_TrainingProfileChunk_AircraftInformation_ScreenCap.png'/>
        </exhibit>
        <unorderedlist>
            <listitem>
                <para>
                    <italic>Aircraft</italic> - The aircraft associated with this
                    airspace profile.
                </para>
            </listitem>
            <listitem>
                <para>
                    <italic>Engine</italic> - The aircraft engine associated with
                    this airspace profile. The available engines will depend on the
                    selected aircraft.
                </para>
            </listitem>
            <listitem>
                <para>
                    <italic>Power</italic> - The aircraft engine power setting used
                    by the aircraft when operating as part of this airspace profile.
                    Type the numeric power level, choose the operation power description
                    (for example, "Normal Rated Thrust"), and choose the units used
                    to specify the power level (for example, "% NC"). Note that for
                    some operation power descriptions (for example, "Afterburner"),
                    the numeric power level is fixed and cannot be changed.
                </para>
                <para>
                    The operation power description is used to select which Noisefile
                    interpolation curve to use. Expert users can select the interpolation
                    curve directly by selecting either "Variable" or "Parallel" in
                    place of the operation power description.
                </para>
                <para>
                    The available operation power descriptions will depend on the
                    airspace profile's aircraft and engine. As an aid to the user,
                    information about the Noisefile record that corresponds to each
                    operation power description is displayed.
                </para>
                <exhibit>
                    <img
                    src='BaseOps_TrainingProfileChunk_NoisefileRecordsTable_ScreenCap.png'/>
                </exhibit>
                <para>
                    The <italic>Range</italic> column specifies the range of power
                    levels for which MRNMap can extrapolate the measured Noisefile
                    noise data. You can enter power settings outside of this range
                    (and are encouraged to do so to accurately record real-world flight
                    parameters). Power levels are clipped to the extrapolation range
                    when MRNMap is <link target='#BaseOps_RunningCases_id'>run</link>.
                </para>
                <para>
                    The <italic>Interpolation</italic> and <italic>OPC</italic> columns
                    specify the Noisefile interpolation method and operational power
                    code, respectively.
                </para>
                <para>
                    <italic>Airspeed</italic> - The aircraft's airspeed when operating
                    as part of this airspace profile.
                </para>
            </listitem>
        </unorderedlist>
    </section>
    <section>
        <title>
            Altitude Bands
        </title>
        <para>
            Each airspace profile has a distribution of heights at which the
            aircraft operates as part of that profile. The distribution is
            defined by a set of one or more altitude bands (delimited by floor
            and ceiling heights), along with the relative amount of time spent
            in each band.
        </para>
        <exhibit>
            <img
            src='BaseOps_TrainingProfileChunk_AltitudeBands_ScreenCap.png'/>
        </exhibit>
        <para>
            The altitude bands are specified using a table, where each table
            row represents one band. The following table columns are defined.
        </para>
        <unorderedlist>
            <listitem>
                <para>
                    <italic>Floor</italic> -<linebreak/>
                    <italic>Ceiling</italic> - The minimum and maximum flight levels
                    of this altitude band. [-include "BaseOps_HeightInputControl_UsageSentence.txt"-]
                </para>
                <para>
                    At least one band must be specified, and each band's ceiling must
                    be at least as high as its floor. Otherwise, no restrictions are
                    placed on the band heights. Bands with a zero height range are
                    allowed: i.e., the floor can equal the ceiling. Bands can be listed
                    in any order, and the height range of different bands can overlap.
                    Uses as many bands as needed to model the distribution of heights
                    at which the aircraft flies.
                </para>
                <para>
                    You can change the units used to specify heights: see <iref
                    target='BaseOps_CaseUnits_id'/>.
                </para>
            </listitem>
            <listitem>
                <para>
                    <italic>Relative Utilization</italic> - The relative amount of
                    time the aircraft spends in this altitude band. The utilization
                    numbers are unitless. MRNMap compares the utilization numbers
                    for each band to determine the relative amount of time the aircraft
                    spends in each band.
                </para>
                <para>
                    For example, assume you have two altitude bands, with relative
                    utilization numbers of 10 and 30, respectively. In this case,
                    MRNMap would model the aircraft flying 25% of the time in the
                    first band and 75% of the time in the second.
                </para>
            </listitem>
        </unorderedlist>
        <para>
            The triangle icon <img
            src='intres:BaseOps_RowSelectionIcon_Selected_CroppedForDocumentation'/>
            indicates the selected altitude band. To select another band,
            either click somewhere on that band's row, or navigate to that
            band using the <keytext>Tab</keytext> key.
        </para>
        <para>
            To add a new band, either press the Add Altitude Band button <img
            src='intres:BaseOps_AddPlusSignSmallButtonBitmap'/>, or press
            <keytext>Ctrl + A</keytext>. The new band will be added directly
            below the selected one.
        </para>
        <para>
            To delete the selected band, either press the Delete Altitude
            Band button <img
            src='intres:WCF_DeleteCrossToolbarButtonBitmap'/>, or press <keytext>Ctrl
            + Del</keytext>.
        </para>
        <para>
            To move the selected band up or down in the table, press the Move
            Up and Move Down buttons <img
            src='intres:WCF_MoveUpToolbarButtonBitmap'/> and <img
            src='intres:WCF_MoveDownToolbarButtonBitmap'/>, or press <keytext>Ctrl
            + U</keytext> and <keytext>Ctrl + D</keytext>. This capability
            is provided solely for your own organizational purposes; MRNMap
            attributes no meaning to the order in which bands are listed.
        </para>
        [-include "BaseOps_CopyPasteSegments.rxl" segment_name_lowercase='altitude band' segment_name_uppercase='Altitude Band' object_name='airspace profile'-]
        <para>
            When you add a new altitude band, BaseOps simply duplicates the
            selected one. If desired, you can use the quick-add feature, which
            lets you efficiently add an altitude band while simultaneously
            specifying its properties. To add a band, type a quick-add command
            into the text box, then press the Add Altitude Band button <img
            src='intres:BaseOps_AddPlusSignSmallButtonBitmap'/> or the <keytext>Enter</keytext>
            key.
        </para>
        <para>
            The quick-add commands are somewhat cryptic, but once learned,
            they allow you to add bands very quickly. Frequent users will
            find it worthwhile spending a few minutes learning the quick-add
            commands. To display a list of the quick-add commands that you
            can use, either press the Quick-Add Hints button <img
            src='intres:BaseOps_QuickAddSmallButtonBitmap'/>, or press <keytext>Ctrl
            + H</keytext>.
        </para>
    </section>
</section>
