
<section id='BaseOps_FlightProfileChunk_id'
webfilename='flightprofilechunk'>
    <title>
        Editing Flight Profiles
    </title>
    <para>
        A flight profile describes the operational characteristics (height,
        power setting, airspeed, etc.) of an aircraft as it flies along
        a <link target='#BaseOps_FlightTrackChunk_id'>flight track</link>.
    </para>
    <para>
        In BaseOps, flight profiles are defined as a sequence of one or
        more <termtext>flight profile segments</termtext>: sections of
        a flight track where the operational characteristics are either
        constant or vary linearly. Each segment begins with a <termtext>profile
        point</termtext>: a location where the operational characteristics
        are specified. The location of profile points along a flight track
        is specified by the linear track distance, measured from the start
        of the track.
    </para>
    <exhibit>
        <img src='BaseOps_FlightProfile_Figure.png'
        standard_colors='true'/>
    </exhibit>
    <para>
        Flight profiles are used by the NMap, AAM, and RNM noise models.
        Unless one of these models is selected, the parts of the BaseOps
        user interface dealing with flight profiles will be hidden. See
        <iref target='BaseOps_NoiseModelsUsed_id'/>.
    </para>
    <para>
        To work with flight profiles, choose Flight Profiles from the
        <link target='#BaseOps_ListPane_id'>object type selector dropdown
        list</link>. Flight profiles can be added, duplicated, and deleted
        as described in <iref target='BaseOps_ListPane_id'/>.
    </para>
    <para>
        To edit a flight 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>.
        Flight profiles have numerous properties. These are listed below,
        grouped for easy reference.
    </para>
    <section>
        <title>
            Profile Name and Notes
        </title>
        <exhibit>
            <img
            src='BaseOps_FlightProfileChunk_NameAndNotes_ScreenCap.png'/>
        </exhibit>
        <unorderedlist>
            [-include "BaseOps_NameLongNameNotes_ListItems.rxl" ObjectTypeName='flight profile'-]
        </unorderedlist>
    </section>
    <section>
        <title>
            Operation Counts
        </title>
        <exhibit>
            <img
            src='BaseOps_FlightProfileChunk_Operations_ScreenCap.png'/>
        </exhibit>
        <para>
            The operation counts specify the average number of times per calendar
            day that the flight 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 is set to three for this BaseOps case.
        </para>
    </section>
    <section>
        <title>
            Flight Track Information
        </title>
        <exhibit>
            <img
            src='BaseOps_FlightProfileChunk_FlightTrackInformation_ScreenCap.png'/>
        </exhibit>
        <unorderedlist>
            <listitem>
                <para>
                    <italic>Flight Track</italic> - The flight track associated with
                    this flight profile. Select the track from the dropdown list.
                    Press the Add Flight Track button <img
                    src='intres:WCF_AddPlusSignToolbarButtonBitmap'/> to add a new
                    track. Press the Go To Flight Track button <img
                    src='intres:BaseOps_GotoToolbarButtonBitmap'/> to edit the selected
                    track. See <iref target='BaseOps_FlightTrackChunk_id'/> for more
                    information.
                </para>
                <para>
                    The length of the selected flight track is displayed.
                </para>
            </listitem>
            <listitem>
                <para>
                    <italic>Displacement</italic> - The takeoff and/or landing runway
                    displacements associated with this flight profile. The displacements
                    that are requested (takeoff, landing, or both) will depend on
                    the flight track type (arrival, departure, etc.).
                </para>
                <para>
                    The takeoff displacement is the distance, measured from the beginning
                    of the runway, to the point where the aircraft begins its takeoff
                    roll. For all flight track types except for arrival, the takeoff
                    displacement is the origin from which flight profile cumulative
                    track distances are measured.
                </para>
                <para>
                    The landing displacement is the distance, measured from the beginning
                    of the runway, to the point where the aircraft touches down. For
                    arrival flight tracks, the landing displacement is the origin
                    from which flight profile cumulative track distances are measured.
                </para>
                <para>
                    You can change the units used to specify runway displacements:
                    see <iref target='BaseOps_CaseUnits_id'/>.
                </para>
                <!-- <note type='warning'>
                    <para>
                        Currently, the NMap noise model implements runway displacements
                        incorrectly. Instead of shifting the flight profile points along
                        the flight track, NMap instead shifts the entire flight track
                        down the runway. When an updated version of NMap becomes available,
                        a new version of Noisemap will be released.
                    </para>
                </note> -->
            </listitem>
        </unorderedlist>
    </section>
    <section>
        <title>
            Aircraft Information
        </title>
        <exhibit>
            <img
            src='BaseOps_FlightProfileChunk_AircraftInformation_ScreenCap.png'/>
        </exhibit>
        <unorderedlist>
            <listitem>
                <para>
                    <italic>A/C Category</italic> - The aircraft category is used
                    to group flight profiles into broad categories. Specifying the
                    category is not strictly necessary. However, doing so is useful
                    for organizational and documentation purposes.
                </para>
                <para>
                    The categories are defined in the A/C Category group: see <iref
                    target='BaseOps_GroupChunk_id'/>. If desired, you can add additional
                    categories.
                </para>
            </listitem>
            <listitem>
                <para>
                    <italic>Aircraft</italic> - The aircraft associated with this
                    flight profile. Only those aircraft applicable to the selected
                    noise model(s) are displayed: see <iref
                    target='BaseOps_NoiseModelsUsed_id'/>.
                </para>
            </listitem>
            <listitem>
                <para>
                    <italic>Engine</italic> - The aircraft engine associated with
                    this flight profile. The available engines will depend on the
                    selected aircraft.
                </para>
            </listitem>
            <listitem>
                <para>
                    <italic>Power Units</italic> - The units used to specify engine
                    power settings for this flight profile. The available units will
                    depend on the selected aircraft and engine.
                </para>
            </listitem>
        </unorderedlist>
    </section>
    <section>
        <title>
            Runup Information
        </title>
        <exhibit>
            <img src='BaseOps_FlightProfileChunk_Runup_ScreenCap.png'/>
        </exhibit>
        <para>
            Some aircraft perform a static runup of their engines before beginning
            a takeoff roll. The <termtext>runup</termtext> is the duration
            of this static runup.
        </para>
        <para>
            The runup is displayed only for certain aircraft when operating
            on departure and interfacility flight tracks. For interfacility
            tracks, the runup is not displayed if the initial airspeed is
            greater than zero. This allows interfacility tracks to be used
            in a manner similar to INM's overflight tracks.
        </para>
        <para>
            You can change the units used to specify times: see <iref
            target='BaseOps_CaseUnits_id'/>.
        </para>
        <note type='note'>
            <para>
                The aircraft's power setting when conducting the static runup
                is specified in the first row of the flight profile segments table.
            </para>
        </note>
    </section>
    <section id='BaseOps_FlightProfileChunk_Segments_id'>
        <title>
            Segments
        </title>
        <exhibit>
            <img src='BaseOps_FlightProfileChunk_Segments_ScreenCap.png'/>
        </exhibit>
        <para>
            A flight profile's segments are specified using a table, where
            each table row represents the profile point of a segment. The
            following table columns are defined. Note that only those columns
            applicable to the flight profile's aircraft will be displayed.
        </para>
        <unorderedlist>
            <listitem>
                <para>
                    <italic>Distance</italic> - The location of this profile point,
                    specified as a linear distance along the flight track, measured
                    from the runway displacement.
                </para>
                <para>
                    You can change the units used to specify track distances: see
                    <iref target='BaseOps_CaseUnits_id'/>.
                </para>
            </listitem>
            <listitem>
                <para>
                    <italic>Height</italic> - The aircraft height at this profile
                    point. [-include "BaseOps_HeightInputControl_UsageSentence.txt"-]
                </para>
                <para>
                    You can change the units used to specify heights: see <iref
                    target='BaseOps_CaseUnits_id'/>.
                </para>
            </listitem>
            <listitem>
                <para>
                    <italic>Power</italic> - The aircraft engine power setting at
                    this profile point. Type the numeric power level, then choose
                    the operation power description (for example, "Takeoff"). For
                    some operation power descriptions (for example, "Afterburner"),
                    the numeric power level is fixed and cannot be changed.
                </para>
                <para>
                    Power settings are applicable only to NMap and AAM fixed-wing
                    aircraft. The operation power description is applicable only to
                    NMap aircraft.
                </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
                    flight profile's aircraft and engine. If the aircraft conducts
                    a static runup prior to beginning its takeoff roll, the available
                    operation power descriptions in the first row of the flight profile
                    segments table (where the runup power is set) will be those for
                    static operations.
                </para>
                <para>
                    Information about the Noisefile record that corresponds to each
                    flyover operation power description is displayed below the segment
                    table.
                </para>
                <exhibit>
                    <img
                    src='BaseOps_FlightProfileChunk_NoisefileRecordsTable_ScreenCap.png'/>
                </exhibit>
                <para>
                    The <italic>Range</italic> column specifies the range of power
                    levels for which NMap 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 NMap 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>
            </listitem>
            <listitem>
                <para>
                    <italic>Aircraft Configuration</italic> - The state of the aircraft's
                    landing gear, flaps, etc. at this profile point. The aircraft
                    configuration is applicable only to fixed-wing AAM aircraft.
                </para>
            </listitem>
            <listitem>
                <para>
                    <italic>Airspeed</italic> - The aircraft airspeed at this profile
                    point, in knots. Airspeeds are not applicable to rotary-wing NMap
                    aircraft.
                </para>
            </listitem>
            <listitem>
                <para>
                    <italic>Yaw Angle</italic> -<linebreak/>
                    <italic>Angle of Attack</italic> -<linebreak/>
                    <italic>Roll Angle</italic> -<linebreak/>
                    <italic>Thrust Vector Angle</italic> -<linebreak/>
                    <italic>Nacelle Tilt Angle</italic> - The aircraft orientation
                    angles, in degrees. These are applicable only to AAM and RNM aircraft.
                    The angles displayed will vary, depending on the aircraft type
                    (RNM rotary-wing, AAM fixed-wing, etc.).
                </para>
                <para>
                    The sign conventions for the applicable orientation angles are
                    displayed below the profile segments tables.
                </para>
                <exhibit>
                    <img
                    src='BaseOps_FlightProfileChunk_AngleSignConventionsDisplay_ScreenCap.png'/>
                </exhibit>
                <note type='note'>
                    <para>
                        The angle of attack and the yaw angle are technically applicable
                        to non-helicopter AAM aircraft. However, for these aircraft, accurate
                        values of these parameters are difficult to obtain, and their
                        values rarely depart significantly from zero. Therefore, by default,
                        zero is assumed for these parameters, and the corresponding columns
                        are hidden in the profile segments table.
                    </para>
                    <para>
                        If you have specialized needs, you can choose to display and edit
                        these parameters. See <iref
                        target='BaseOps_AAMAdvancedOptions_id'/> of <iref
                        target='BaseOps_CaseChunk_id'/> for more information.
                    </para>
                </note>
            </listitem>
            <listitem>
                <para>
                    <italic>Left Dispersion Width</italic> -<linebreak/>
                    <italic>Right Dispersion Width</italic> - The AAM noise model
                    supports the concept of flight dispersion. This allows you to
                    model aircraft operations that have a lateral Gaussian probability
                    distribution with respect to a flight track.
                </para>
                <para>
                    To activate flight dispersion, enter non-zero dispersion widths
                    for each flight profile segment. The widths define ±3 standard
                    deviations. Since separate left and right widths are defined,
                    the Gaussian distribution is not necessarily symmetrical with
                    respect to the flight track.
                </para>
                <para>
                    When specifying dispersion widths, left and right are with respect
                    to the direction the aircraft is flying. That is, they are left
                    (port) and right (starboard) from the pilot's point of view.
                </para>
                <para>
                    You can change the units used to specify flight dispersion widths:
                    see <iref target='BaseOps_CaseUnits_id'/>.
                </para>
            </listitem>
            <listitem>
                <para>
                    <italic>Climb Angle</italic> -<linebreak/>
                    <italic>Climb Rate</italic> -<linebreak/>
                    <italic>Duration</italic> - These non-editable information-only
                    fields are optional. See <iref
                    target='BaseOps_FlightProfileAdvancedOptions_id'/> of <iref
                    target='BaseOps_CaseChunk_id'/> for instructions on choosing which
                    of these fields you'd like to display.
                </para>
                <para>
                    <italic>Climb Angle</italic> indicates the angle of the aircraft's
                    flight path as it flies each segment, measured in degrees from
                    horizontal. The angle is rounded to the closest tenth of a degree.
                    Negative angles indicate that the aircraft is descending.
                </para>
                <para>
                    <italic>Climb Rate</italic> indicates the rate at which the aircraft
                    is gaining or losing altitude while flying each segment, measure
                    in feet per minute (fpm). The rate is rounded to the closest 100
                    fpm. A negative climb rate indicates that the aircraft is descending,
                    while a rate of zero indicates level flight.
                </para>
                <para>
                    <italic>Duration</italic> indicates the time it takes the aircraft
                    to fly each segment, rounded to the nearest second. It is calculated
                    based upon the average speed over an entire segment (i.e., the
                    average of the airspeeds at the beginning and end of the segment).
                    For the purpose of this calculation, ground speed is assumed to
                    be equal to airspeed.
                </para>
            </listitem>
            <listitem>
                <para>
                    <italic>Notes</italic> - Miscellaneous information about this
                    profile segment. There is no restriction on the text that can
                    be typed into this box. The notes are not used by the noise models;
                    they are for your use to record any information you believe is
                    relevant.
                </para>
            </listitem>
        </unorderedlist>
        <para>
            The triangle icon <img
            src='intres:BaseOps_RowSelectionIcon_Selected_CroppedForDocumentation'/>
            indicates the selected flight profile segment. To select another
            segment, either click somewhere on that segment's row, or navigate
            to that segment using the <keytext>Tab</keytext> key.
        </para>
        <para>
            To add a new segment, either press the Add Segment button <img
            src='intres:BaseOps_AddPlusSignSmallButtonBitmap'/>, or press
            <keytext>Ctrl + A</keytext>. The new segment will be added directly
            below the selected segment. Alternatively, using the Add mouse
            tool <img src='intres:BaseOps_AddTool_ToolbarButton'/>, click
            on the location along the flight track where the new profile point
            should be added. See <iref target='BaseOps_MouseTool_Add_id'/>
            for more information.
        </para>
        <para>
            To delete the selected segment, either press the Delete Segment
            button <img src='intres:WCF_DeleteCrossToolbarButtonBitmap'/>,
            or press <keytext>Ctrl + Del</keytext>.
        </para>
        <para>
            To move the selected segment 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>. Press the Sort
            Segment Table button <img
            src='intres:WCF_SortToolbarButtonBitmap'/> to automatically sort
            the segment table by increasing distance.
        </para>
        [-include "BaseOps_CopyPasteSegments.rxl" segment_name_lowercase='segment' segment_name_uppercase='Segment' object_name='flight profile'-]
        <para>
            When you add a new segment, BaseOps simply duplicates the selected
            segment. If desired, you can use the quick-add feature, which
            lets you efficiently add a segment while simultaneously specifying
            its properties. To add a segment, type a quick-add command into
            the text box, then press the Add Segment 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 segments 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>
        <note type='tip'>
            <para>
                Using the Select and Edit map tool, you can graphically edit a
                flight profile's segments. See <iref
                target='BaseOps_MouseTool_SelectAndEdit_id'/> for more information.
            </para>
        </note>
        <note type='tip'>
            <para>
                Press the Show Profile Height Graph button to view a graphical
                representation of the profile's height as a function of track
                distance.
            </para>
            <exhibit>
                <img
                src='BaseOps_FlightProfileChunk_HeightGraph_ScreenCap.png'/>
            </exhibit>
        </note>
    </section>
    <!-- <section id='BaseOps_StandardFlightProfileLibrary_id'>
        <title>
            The Standard Profile Library
        </title>
        <exhibit>
            <img
            src='BaseOps_FlightProfileChunk_StandardProfileButtons_ScreenCap.png'/>
        </exhibit>
        <para>
            BaseOps ships with a library of standard flight profiles for many
            aircraft. These default profiles are useful if you are unable
            to obtain the actual flight profile flown by an aircraft at the
            site you are modeling.
        </para>
        <para>
            To load a standard profile from the library, press the Load Standard
            Profile button. Alternatively, select multiple flight profiles
            in the <link target='#BaseOps_ListPane_id'>object list</link>
            (see <iref target='BaseOps_SelectingMultipleObjects_id'/>), then
            choose <menutext>Load Standard Profile Tool</menutext> from the
            <menutext>Tools</menutext> menu (see <iref
            target='BaseOps_LoadStandardProfileTool_id'/>).
        </para>
        <para>
            A dialog box appears, listing the available standard profiles
            that apply to your profile's aircraft, engine, and flight track
            type.
        </para>
        <exhibit>
            <img
            src='BaseOps_FlightProfileChunk_StandardProfile_SelectDialogBox_ScreenCap.png'/>
        </exhibit>
        <para>
            Select the desired profile, then press OK. The following properties
            in your target flight profile(s) will be updated to match the
            library profile.
        </para>
        <unorderedlist>
            <listitem>
                <para>
                    Power Units
                </para>
            </listitem>
            <listitem>
                <para>
                    Runway Displacement(s)
                </para>
            </listitem>
            <listitem>
                <para>
                    Runup Duration
                </para>
            </listitem>
            <listitem>
                <para>
                    Profile Segments
                </para>
            </listitem>
        </unorderedlist>
        <para>
            If desired, you can save your own flight profiles to the standard
            profile library. To save the current profile, press the Save as
            Standard Profile button. A dialog box appears, asking for the
            name that this profile will be known by in the library.
        </para>
        <exhibit>
            <img
            src='BaseOps_FlightProfileChunk_StandardProfile_SaveDialogBox_ScreenCap.png'/>
        </exhibit>
        <note type='tip'>
            <para>
                Your user library of standard flight profiles is stored in the
                file <filetext>Standard Flight Profile Library - User.baseops</filetext>,
                which is located in the BaseOps home directory. This is a regular
                BaseOps case file. If desired, you can load this case into BaseOps
                and edit it. If you choose to do so, note these points.
            </para>
            <unorderedlist>
                <listitem>
                    <para>
                        Make sure each profile's Long Name contains a description of the
                        profile (even if the description is simply something generic like
                        "Standard Departure" or "Standard Arrival"). The long name is
                        the text that is displayed to the user when displaying a list
                        of standard profiles to choose from.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        Make sure that the profile's flight track is set to either Arrival
                        or Departure, depending on whether the profile is for arrivals
                        or departures.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        The height of all flight profile segments should be specified
                        using AGL, not MSL.
                    </para>
                </listitem>
            </unorderedlist>
            <para>
                The BaseOps library (as opposed to the user library) of standard
                flight profiles is stored in the file <filetext>Standard Flight
                Profile Library - BaseOps.baseops</filetext>. Only BaseOps' developers
                should edit this file, as it will be overwritten whenever a new
                version of BaseOps is installed.
            </para>
        </note>
    </section> -->
    <section id='BaseOps_NoiseSignificanceBoundary_id'>
        <title>
            AAM Noise Significance Boundary
        </title>
        <para>
            AAM noise modeling methodology includes the concept of the noise
            significance boundary, a 10 dB margin around the noise grid and
            all points of interest. It is recommended that all AAM arrivals
            and departures extend beyond this boundary to insure accurate
            noise calculations.
        </para>
        <note type='note'>
            <para>
                The noise significance boundary is based on the same logic as
                AAM's computational efficiency proximity checks, which determine
                if a particular source-receiver combination is worthy of acoustic
                analysis.
            </para>
            <para>
                The boundary is implemented as a 30,000-foot margin. This distance
                is consistent with the "terrain and operations should be considered
                at least 5 miles from a point of interest" rule of thumb often
                used for noise modeling in National Parks, and is also consistent
                with a 10 dB decrease in noise energy assuming spherical spreading
                from an aircraft at around 10,000 feet AGL.
            </para>
        </note>
        <para>
            When creating an AAM <filetext>.ops</filetext> file, BaseOps will
            display a warning for any AAM flight profiles that fail to extend
            beyond the boundary. You are encouraged to lengthen such profiles.
        </para>
        <para>
            You can display the noise significance boundary in BaseOps' <link
            target='#BaseOps_MapPane_id'>map pane</link>. This can be useful
            when editing AAM flight profiles and their associated flight tracks.
        </para>
        <caption type='figure'>
            <title>
                An AAM departure flight profile with the noise significance boundary
                denoted by a dotted red line. The star symbols denote points of
                interest, one of which is less than 30,000 feet from the edge
                of the noise grid and therefore causes a bulge in the boundary.
                Note that BaseOps would raise a warning for this profile, as its
                last profile point is within the boundary.
            </title>
            <img src='BaseOps_NoiseSignificanceBoundary_Figure.png'/>
        </caption>
        <para>
            To display the noise significance boundary, follow these steps.
        </para>
        <orderedlist>
            <listitem>
                <para>
                    Display the <link target='#BaseOps_CaseOptionsDialogBox_id'>Case
                    Options dialog box</link>.
                </para>
            </listitem>
            <listitem>
                <para>
                    Go to the Noise Significance Boundary page of the Case Options
                    dialog box.
                </para>
                <exhibit>
                    <img
                    src='BaseOps_NoiseSignificanceBoundary_DisplayStyle_ScreenCap.png'/>
                </exhibit>
            </listitem>
            <listitem>
                <para>
                    Check the box labeled <italic>Show AAM Noise Significance Boundary</italic>.
                </para>
            </listitem>
            <listitem>
                <para>
                    If desired, edit the characteristics (color, width, and solid-dot-dashed
                    pattern) of the line used to indicate the boundary on maps. See
                    <iref target='WCF_ColorControl_id'/> and <iref
                    target='WCF_LinePatternControl_id'/> for more information.
                </para>
            </listitem>
        </orderedlist>
    </section>
</section>
