
<section id='BaseOps_RunningCases_id'
webfilename='runningcases'>
    <title>
        Running Cases
    </title>
    <para>
        After entering all of the data (runways, flight tracks, weather
        information, etc.) in a <link
        target='#BaseOps_IntroductionToCases_id'>BaseOps case</link>,
        you can <termtext>run</termtext> the case: that is, execute the
        noise model(s) that compute the predicted noise levels. To run
        the case, select <menutext>Run Case</menutext> from the <menutext>Case</menutext>
        menu.
    </para>
    <para>
        This chapter covers the details of running a case, along with
        other associated tasks such as checking a case for errors and
        viewing noise contours using NMPlot.
    </para>
    <section id='BaseOps_MessageReport_id'>
        <title>
            Checking a Case
        </title>
        <para>
            To check a case for errors and warnings, you can:
        </para>
        <unorderedlist>
            <listitem>
                <para>
                    Choose <menutext>Check Case</menutext> from the <menutext>Case</menutext>
                    menu
                </para>
            </listitem>
            <listitem>
                <para>
                    Press <keytext>Ctrl + K</keytext>
                </para>
            </listitem>
        </unorderedlist>
        <para>
            The <termtext>message report</termtext> is displayed, showing
            any errors or warnings found.
        </para>
        <exhibit>
            <img src='BaseOps_MessageReport_ScreenCap.png'/>
        </exhibit>
        <para>
            Errors must be corrected before the case is run. Warnings do not,
            but you should carefully consider each one.
        </para>
        <para>
            To fix errors in the case, click on the hyperlinks included in
            the message report. These hyperlinks take you to the objects that
            you must edit to correct the errors.
        </para>
        <note type='tip'>
            <para>
                After following a hyperlink, use the back button <img
                src='intres:WCF_BrowseBack_ToolbarButtonBitmap'/> to easily return
                to the message report. See <iref
                target='BaseOps_BackAndForwardButtons_id'/>.
            </para>
        </note>
        <para>
            At any time, you can go to the message report and view the results
            of the last error check by choosing Messages from the <link
            target='#BaseOps_ListPane_id'>object type selector dropdown list</link>.
        </para>
        <para>
            You can print the message report. See <iref
            target='BaseOps_PrintingSelectedObject_id'/>.
        </para>
    </section>
    <section id='BaseOps_GridChunk_id'>
        <title>
            Setting Grid Properties
        </title>
        <para>
            The noise models calculate noise levels at a two-dimensional grid
            of points covering your area of interest. This is referred to
            (depending on the context) as the <termtext>primary grid</termtext>,
            the <termtext>noise grid</termtext>, or sometimes simply <termtext>the
            grid</termtext>. You can set the primary grid's location, size,
            and resolution (distance between adjacent points).
        </para>
        <note type='note'>
            <para>
                The primary grid is always orientated so that its rows and columns
                run east-west and north-south.
            </para>
        </note>
        <para>
            To set the properties of your case's primary grid, first choose
            Grid from the <link target='#BaseOps_ListPane_id'>object type
            selector dropdown list</link>. Then set the grid properties in
            the <link target='#WCF_ApplicationMainWindow_id'>text pane</link>.
        </para>
        <exhibit>
            <img src='BaseOps_GridChunk_ScreenCap.png'/>
        </exhibit>
        <para>
            The primary grid has the following properties.
        </para>
        <unorderedlist>
            <listitem>
                <para>
                    <italic>Location of Center</italic> - The location of the center
                    of the grid, specified with respect to the case <link
                    target='#BaseOps_CaseReferencePoint_id'>reference point</link>.
                    Typically, the reference point is located near the center of the
                    area of interest, so the grid location will usually be close to
                    (0,&nbsp;0).
                </para>
                <para>
                    The grid location is always specified with respect to the case
                    reference point, regardless of the current <link
                    target='#BaseOps_CaseCoordinateSystem_id'>case coordinate system</link>.
                </para>
            </listitem>
            <listitem>
                <para>
                    <italic>Point Spacing</italic> - The distance between adjacent
                    grid points in the east-west and north-south directions.
                </para>
            </listitem>
            <listitem>
                <para>
                    <italic>Number of Points</italic> - The number of grid points
                    in the east-west and north-south directions. The size of the area
                    covered by the grid equals the number of grid points multiplied
                    by the grid point spacing.
                </para>
            </listitem>
        </unorderedlist>
        <note type='note'>
            <para>
                You can select the units used to specify the grid properties.
                See <iref target='BaseOps_CaseUnits_id'/> for more information.
            </para>
        </note>
        <para>
            Using the <link target='#BaseOps_MouseTool_SelectAndEdit_id'>Select
            and Edit map tool</link>, you can drag the edges of the primary
            grid to resize/reposition it.
        </para>
        <section id='BaseOps_GridChunk_Subgrids_id'>
            <title>
                Subgrids
            </title>
            <para>
                Noise models in the NOISEMAP family have traditionally supported
                noise computations only on a single, regular, rectangular, 2-dimensional
                grid of points (known as the primary grid). The grid point spacing
                of the entire grid is determined by the maximum resolution needed
                in any region of the computational domain. This results in a grid
                with a very large number of points.
            </para>
            <para>
                This has been tolerable in the past, when most noise calculations
                were done with NMAP, which runs very quickly. However, the increasing
                use of AAM, which due to its more accurate simulation-based design
                runs much slower than NMAP, has caused a crisis in noise model
                run times. To address this problem, support was added to AAM for
                multi-fidelity grids: i.e., grids whose point spacing varies with
                location. The grid point spacing can be varied depending on the
                resolution required in any given region.
            </para>
            <para>
                This multi-fidelity grid support is built upon the concept of
                nested subgrids. Each subgrid has an associated parent grid, which
                is either the primary grid or another subgrid. A subgrid has twice
                the resolution (i.e., the distance between adjacent grid points
                is one half that) of its parent grid, and covers a subset of the
                area that the parent covers. By repeatedly nesting subgrids, the
                noise field in a particular area of interest can be defined to
                any resolution desired.
            </para>
            <note type='important'>
                <para>
                    If you intend to use subgrids, ensure that you have AAM 3.1.0
                    or later installed.
                </para>
            </note>
            <note type='note'>
                <para>
                    Before using subgrids, it is recommended that you review the document
                    "<filetext>Run File Format - SUBGRIDS extension.docx</filetext>".
                    which is included with the BaseOps distribution in the "<filetext>NMap\Documentation</filetext>"
                    directory. It covers the concept of subgrids in more detail.
                </para>
            </note>
            <para>
                Subgrid support is active only if the <link
                target='#BaseOps_NoiseModelsUsed_id'>AAM noise model</link> is
                selected in the current BaseOps case.
            </para>
            <para>
                To add a new subgrid, use the Add mouse tool <img
                src='intres:BaseOps_AddTool_ToolbarButton'/> to drag a rectangular
                area defining the geographic region that the subgrid will cover.
                The parent of the new subgrid will be the grid (either the primary
                grid or another subgrid) underneath the point where you begin
                dragging the mouse.
            </para>
            <para>
                To edit a subgrid, use the Select and Edit mouse tool <img
                src='intres:WCF_ArrowMouseCursorToolbarButtonBitmap'/> to drag
                the grid's edges. You can also use this tool to edit the primary
                grid. As you drag a grid's edges, the parameters of any child
                subgrids will be modified so that they remain over the same geographic
                areas. If you shrink a grid, any child subgrids will also shrink
                as necessary so that a child grid never extends beyond the geographic
                boundary of its parent.
            </para>
            <para>
                To delete a subgrid, first use the <img
                src='intres:WCF_ArrowMouseCursorToolbarButtonBitmap'/>Select and
                Edit mouse tool to select it, then press <keytext>Ctrl + Del</keytext>.
            </para>
            <para>
                You can also edit subgrids using the <link
                target='#WCF_ApplicationMainWindow_id'>text pane</link>.
            </para>
            <exhibit>
                <img src='BaseOps_GridChunk_Subgrids_TextPane_ScreenCap.png'/>
            </exhibit>
            <para>
                The subgrids are listed in a table. The following table columns
                are defined.
            </para>
            <unorderedlist>
                <listitem>
                    <para>
                        <italic>Nesting Level</italic> - The depth to which the subgrid
                        is nested. Subgrids with a nesting level of 1 have the primary
                        grid as their parent. This is a non-editable information-only
                        column.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        <italic>iParent, jParent</italic> - The indices of the grid point
                        in the parent grid that serves as the subgrid's origin.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        <italic>NI, NJ</italic> - The number of subgrid points in the
                        east-west and north-south directions. Note that these values must
                        be odd integers >= 3.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        <italic>Grid Point Spacing</italic> - The grid resolution; the
                        distance between adjacent grid points in the east-west and north-south
                        directions. This is a non-editable information-only column.
                    </para>
                </listitem>
            </unorderedlist>
            <note type='tip'>
                <para>
                    While you can fully manage subgrids using the text-based table,
                    you will likely find it easier to rely exclusively on the graphical
                    map-based editing tools (described above). Similarly, if you have
                    defined subgrids, it's recommended that you use the graphical
                    editing tools if you need to change the primary grid's boundary.
                </para>
                <para>
                    When using the graphical tools, BaseOps automatically manages
                    the relationships between the primary and subgrid parameters.
                    When using the text-based controls, you are responsible for managing
                    all relationships and observing all constraints. If you do intend
                    to use the text-based controls to manage subgrids, you should
                    first read the "<filetext>Run File Format - SUBGRIDS extension.docx</filetext>"
                    document to ensure that you fully understand the subgrid parameters.
                </para>
            </note>
            <note type='tip'>
                <para>
                    Each nested subgrid increases the grid resolution by a factor
                    of 2. By pushing the edges of a subgrid right up to its parent's
                    edges, you can create areas where the grid resolution jumps by
                    a factor of 4, 8, or more. However, you are <bold>strongly discouraged</bold>
                    from doing so, as such large jumps in resolution can cause noticeable
                    anomalies in the noise contours.
                </para>
                <para>
                    To avoid this, leave a margin between each subgrid and its parent,
                    and increase the resolution gradually.
                </para>
                <caption type='figure'
                id='BaseOps_GridChunk_Subgrids_Nesting_Figure1_id'>
                    <title>
                        Improper verses proper nesting of subgrids. In this figure, the
                        light cyan area represents the primary grid, and the dark blue
                        lines represent subgrids. In the left example, the left edge of
                        two subgrids have been pushed up against their parents' left edges,
                        creating a region, highlighted in red, where the grid resolution
                        jumps by a factor of 4 or 8. This is strongly discouraged. In
                        the right example, an ample margin is left around each subgrid,
                        so the resolution never jumps by more than a factor of 2 at any
                        location.
                    </title>
                    <img src='BaseOps_GridChunk_Subgrids_Nesting_Figure1.png'/>
                </caption>
                <para>
                    Note, however, that is is fine for sibling subgrids to directly
                    abut.
                </para>
                <caption type='figure'
                id='BaseOps_GridChunk_Subgrids_Nesting_Figure2_id'>
                    <title>
                        An example of using two abutting subgrids to create a L-shaped
                        area with twice the resolution of the primary grid.
                    </title>
                    <img src='BaseOps_GridChunk_Subgrids_Nesting_Figure2.png'/>
                </caption>
            </note>
            <note type='tip'>
                <para>
                    When running a case, BaseOps creates a shapefile containing the
                    noise contours (see <iref target='BaseOps_ContoursChunk_id'/>).
                    You can add a background map layer of type "ARC/INFO Shapefile"
                    (see <iref target='WCGIS_BackgroundMapFormats_id'/>) that loads
                    this contour shapefile, and thereby display the noise contours
                    in BaseOps.
                </para>
                <exhibit>
                    <img src='BaseOps_GridChunk_Subgrids_Contours_Figure.png'/>
                </exhibit>
                <para>
                    This can be useful for placing your subgrids. First run your case
                    with only the primary grid defined. This gives you a rough draft
                    of the contours, which can serve as guides when positioning your
                    subgrids. In the above example, three subgrids have been added
                    to provide increasing resolution of the 65, 75, and 85 dB contour
                    areas.
                </para>
            </note>
        </section>
    </section>
    <section id='BaseOps_ContoursChunk_id'>
        <title>
            Setting Contour Properties
        </title>
        <para>
            As the final step in running a case, BaseOps exports each <link
            target='#BaseOps_ScenarioChunk_id'>scenario's</link> noise level
            contours to a file in ARC/INFO Shapefile format. You can then
            import the contours into a third-party Geographic Information
            System (GIS). Most GIS's can import shapefiles.
        </para>
        <note type='note'>
            <para>
                The NMPlot plotting application can also create contour shapefiles.
                BaseOps' contour exporting capability is provided as a convenience
                to those users whose contouring needs are relatively straight-forward.
                User with more demanding needs should use NMPlot: see <iref
                target='BaseOps_PlottingNoiseContours_id'/>.
            </para>
        </note>
        <para>
            To set the properties of the exported contours, first choose Contours
            from the <link target='#BaseOps_ListPane_id'>object type selector
            dropdown list</link>. Then set the contour properties in the <link
            target='#WCF_ApplicationMainWindow_id'>text pane</link>.
        </para>
        <exhibit>
            <img src='BaseOps_ContourChunk_ScreenCap.png'/>
        </exhibit>
        <para>
            The following contour properties can be set.
        </para>
        <unorderedlist>
            <listitem>
                <para>
                    <italic>Contour Levels</italic> - Type one or more numbers (separated
                    by commas) specifying the desired noise level(s) of the contours.
                    The contour levels are specified in dB's in the noise metric selected
                    when the case is run: see <iref
                    target='BaseOps_RunChunk_NoiseMetric_id'/>.
                </para>
            </listitem>
            <listitem>
                <para>
                    <italic>Coordinate System</italic> - Select the geographic coordinate
                    system of the contour shapefiles. See <iref
                    target='WCGISxWCF_CoordinateSystemControl_id'/> for more information.
                    Unless you have special needs, it is recommended that you use
                    degrees of longitude and latitude, datum WGS 84.
                </para>
            </listitem>
        </unorderedlist>
        <para>
            When BaseOps creates a noise contour shapefile, it also creates
            a metadata file containing information about the shapefile. This
            metadata file conforms to the Federal Geographic Data Committee's
            Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998).
        </para>
        <para>
            Using information drawn from the case, BaseOps can create a reasonable
            metadata file automatically. However, some users may wish to fine-tune
            the metadata. Therefore, BaseOps allows you to review the default
            metadata and, if desired, edit it on an element-by-element basis.
        </para>
        <exhibit>
            <img src='BaseOps_ContourChunk_Metadata_ScreenCap.png'/>
        </exhibit>
        <para>
            Initially, all metadata elements will have default values assigned
            to them. For example, the <fixedtext>Citation/Title</fixedtext>
            element's default value is the BaseOps case's case name. If you
            later edit the case name, this element's value will be automatically
            updated.
        </para>
        <para>
            You can edit the information displayed in any of the text boxes.
            When you do, the Reset Element button <img
            src='intres:BaseOps_ResetToDefaultValue_Disabled_SmallButton'/>
            will be enabled <img
            src='intres:BaseOps_ResetToDefaultValue_SmallButton'/>. This indicates
            that you have overridden the metadata element's default value.
            Once you have overridden an element's default value, its value
            is fixed; it will no longer be automatically updated by BaseOps.
            To restore the element's default value, press the Reset Element
            button.
        </para>
        <para>
            Press the Show Element Definition button <img
            src='intres:BaseOps_ShowInformation_SmallButton'/> to display
            a metadata element's documentation from the FGDC standard.
        </para>
        <exhibit>
            <img
            src='BaseOps_ContourChunk_MetadataDefinition_ScreenCap.png'/>
        </exhibit>
        <note type='note'>
            <para>
                BaseOps is not intended to be a general-purpose metadata editor.
                The FGDC metadata standard defines a large number of elements.
                The metadata files generated by BaseOps only contain those elements
                that are expected to be commonly applicable to Noisemap noise
                contour shapefiles.
            </para>
            <para>
                Furthermore, BaseOps' Contours page only displays those elements
                for which there was judged to be a reasonable likelihood that
                a user would need to override the default value. Elements whose
                values could be unambiguously calculated (for example, the bounding
                coordinates) are not displayed on the Contours page, but are included
                in the metadata file.
            </para>
            <para>
                Should you have exceptional needs, you can use a third-party metadata
                editor (or, in its absence, a simple text editor) to fine-tune
                the generated metadata file. If there are FGDC metadata elements
                that BaseOps currently does not support, but that you believe
                are generally applicable to noise contour shapefiles, then contact
                BaseOps' developers. It may be possible to include those elements
                in a future version.
            </para>
        </note>
    </section>
    <section id='BaseOps_RunChunk_id'>
        <title>
            Setting Run Options
        </title>
        <para>
            There are numerous options that affect the computations performed
            when you run a <link target='#BaseOps_IntroductionToCases_id'>BaseOps
            case</link>. To set these options, first choose Run from the <link
            target='#BaseOps_ListPane_id'>object type selector dropdown list</link>.
            Then set the options in the <link
            target='#WCF_ApplicationMainWindow_id'>text pane</link>.
        </para>
        <section id='BaseOps_RunChunk_NoiseMetric_id'>
            <title>
                Noise Metric
            </title>
            <exhibit>
                <img src='BaseOps_RunChunk_NoiseMetric_ScreenCap.png'/>
            </exhibit>
            <para>
                There are several commonly-used mathematical methods for calculating
                a single scalar number representing the impact of noise at a location.
                These are referred to as <italic>noise metrics</italic>.
            </para>
            <para>
                Select the noise metric that will be calculated when the case
                is run. Note that only those metrics applicable to the selected
                noise model(s) are displayed: see <iref
                target='BaseOps_NoiseModelsUsed_id'/>
            </para>
            <exhibit>
                <table>
                    <tableheader>
                        <tablecolumnheader horzjust='center'>
                            Name
                        </tablecolumnheader>
                        <tablecolumnheader horzjust='left'>
                            Description
                        </tablecolumnheader>
                        <tablecolumnheader horzjust='center'>
                            Supporting Noise Models
                        </tablecolumnheader>
                    </tableheader>
                    <tablerow>
                        <tablecell>
                            ALM
                        </tablecell>
                        <tablecell>
                            Maximum A-weighted Sound Level for single user-selected flight
                            or static profile.
                        </tablecell>
                        <tablecell>
                            NMap,&nbsp;AAM
                        </tablecell>
                    </tablerow>
                    <tablerow>
                        <tablecell>
                            AMAX
                        </tablecell>
                        <tablecell>
                            Maximum A-weighted Sound Level
                        </tablecell>
                        <tablecell>
                            AAM
                        </tablecell>
                    </tablerow>
                    <tablerow>
                        <tablecell>
                            CDNL
                        </tablecell>
                        <tablecell>
                            C-weighted Day-Night Average Sound Level
                        </tablecell>
                        <tablecell>
                            AGM
                        </tablecell>
                    </tablerow>
                    <tablerow>
                        <tablecell>
                            CNEL
                        </tablecell>
                        <tablecell>
                            Community Noise Equivalent Level
                        </tablecell>
                        <tablecell>
                            all&nbsp;but&nbsp;AGM
                        </tablecell>
                    </tablerow>
                    <tablerow>
                        <tablecell>
                            CNELR
                        </tablecell>
                        <tablecell>
                            Onset-rate-adjusted Community Noise Equivalent Level
                        </tablecell>
                        <tablecell>
                            MRNMap
                        </tablecell>
                    </tablerow>
                    <tablerow>
                        <tablecell>
                            DNL
                        </tablecell>
                        <tablecell>
                            Day-Night Average Sound Level
                        </tablecell>
                        <tablecell>
                            all&nbsp;but&nbsp;AGM
                        </tablecell>
                    </tablerow>
                    <tablerow>
                        <tablecell>
                            LDNMR
                        </tablecell>
                        <tablecell>
                            Onset-rate-adjusted Monthly Day-Night Average A-weighted Sound
                            level. PHA (percent highly annoyed) is also calculated.
                        </tablecell>
                        <tablecell>
                            MRNMap
                        </tablecell>
                    </tablerow>
                    <tablerow>
                        <tablecell>
                            LEQ
                        </tablecell>
                        <tablecell>
                            Equivalent Sound Level (user-selected number of hours).
                        </tablecell>
                        <tablecell>
                            NMap,&nbsp;AAM
                        </tablecell>
                    </tablerow>
                    <tablerow>
                        <tablecell>
                            LEQA
                        </tablecell>
                        <tablecell>
                            Equivalent Sound Level (user-selected number of hours)
                        </tablecell>
                        <tablecell>
                            AAM
                        </tablecell>
                    </tablerow>
                    <tablerow>
                        <tablecell>
                            LEQ24
                        </tablecell>
                        <tablecell>
                            Equivalent Sound Level (24-hour)
                        </tablecell>
                        <tablecell>
                            MRNMap,&nbsp;RNM
                        </tablecell>
                    </tablerow>
                    <tablerow>
                        <tablecell>
                            LMAX
                        </tablecell>
                        <tablecell>
                            Maximum A-weighted Sound Level
                        </tablecell>
                        <tablecell>
                            MRNMap
                        </tablecell>
                    </tablerow>
                    <tablerow>
                        <tablecell>
                            NASEL<linebreak/>
                             NAALM
                        </tablecell>
                        <tablecell>
                            Number of Events Above a user-selected threshold SEL/ALM level
                        </tablecell>
                        <tablecell>
                            NMap,&nbsp;AAM
                        </tablecell>
                    </tablerow>
                    <tablerow>
                        <tablecell>
                            NAPNLT
                        </tablecell>
                        <tablecell>
                            Number of Events Above a user-selected threshold PNLT level
                        </tablecell>
                        <tablecell>
                            AAM
                        </tablecell>
                    </tablerow>
                    <tablerow>
                        <tablecell>
                            NEF
                        </tablecell>
                        <tablecell>
                            Noise Exposure Forecast
                        </tablecell>
                        <tablecell>
                            NMap,&nbsp;AAM,&nbsp;RNM
                        </tablecell>
                    </tablerow>
                    <tablerow>
                        <tablecell>
                            PA
                        </tablecell>
                        <tablecell>
                            Probability of Awakening
                        </tablecell>
                        <tablecell>
                            NMap,&nbsp;AAM
                        </tablecell>
                    </tablerow>
                    <tablerow>
                        <tablecell>
                            PEAK
                        </tablecell>
                        <tablecell>
                            Peak Sound Level
                        </tablecell>
                        <tablecell>
                            AGM
                        </tablecell>
                    </tablerow>
                    <tablerow>
                        <tablecell>
                            SEL
                        </tablecell>
                        <tablecell>
                            Sound Exposure Level for single user-selected flight profile.
                        </tablecell>
                        <tablecell>
                            NMap,&nbsp;AAM
                        </tablecell>
                    </tablerow>
                    <tablerow>
                        <tablecell>
                            SELA
                        </tablecell>
                        <tablecell>
                            Sound Exposure Level for single user-selected flight profile.
                        </tablecell>
                        <tablecell>
                            AAM
                        </tablecell>
                    </tablerow>
                    <tablerow>
                        <tablecell>
                            SEL&nbsp;(all&nbsp;ops)
                        </tablecell>
                        <tablecell>
                            Sound Exposure Level (all operations)
                        </tablecell>
                        <tablecell>
                            MRNMap
                        </tablecell>
                    </tablerow>
                    <tablerow>
                        <tablecell>
                            SELR
                        </tablecell>
                        <tablecell>
                            Onset-rate-adjusted Sound Exposure Level
                        </tablecell>
                        <tablecell>
                            MRNMap
                        </tablecell>
                    </tablerow>
                    <tablerow>
                        <tablecell>
                            SELU
                        </tablecell>
                        <tablecell>
                            Unweighted Sound Exposure Level
                        </tablecell>
                        <tablecell>
                            MRNMap
                        </tablecell>
                    </tablerow>
                    <tablerow>
                        <tablecell>
                            TAALM
                        </tablecell>
                        <tablecell>
                            Time Above (in minutes) a user-selected threshold ALM
                        </tablecell>
                        <tablecell>
                            NMap,&nbsp;AAM
                        </tablecell>
                    </tablerow>
                    <tablerow>
                        <tablecell>
                            WECPNL
                        </tablecell>
                        <tablecell>
                            Weighted Equivalent Continuous Perceived Noise Level
                        </tablecell>
                        <tablecell>
                            NMap,&nbsp;AAM,&nbsp;RNM
                        </tablecell>
                    </tablerow>
                </table>
            </exhibit>
        </section>
        <section id='BaseOps_RunChunk_ComputationsPerformed_id'>
            <title>
                Computations Performed
            </title>
            <exhibit>
                <img src='BaseOps_RunChunk_Computations_ScreenCap.png'/>
            </exhibit>
            <para>
                Each of the noise models supported by BaseOps can calculate noise
                levels (in the <link
                target='#BaseOps_RunChunk_NoiseMetric_id'>selected metric</link>)
                at a two-dimensional grid of locations. All but AGM can also perform
                a detailed noise analysis at each of the case's <link
                target='#BaseOps_PointObjectChunks_id'>points of interest</link>.
            </para>
            <para>
                Select whether you would like to perform grid noise computations,
                points of interest noise computations, or both.
            </para>
            <para>
                If you choose to perform points of interest computations, a points
                of interest report will be created. For each point of interest,
                this report will include a table of the flight and static profiles
                that contribute the most to the noise level at that point. The
                NMap, AAM, and RNM noise models allow you to select the method
                used to rank the profiles. You have two choices.
            </para>
            <unorderedlist>
                <listitem>
                    <para>
                        <italic>Daily</italic> - Profiles are ranked by their contribution
                        to the daily noise level.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        <italic>Event</italic> - Profiles are ranked by their single-event
                        noise levels.
                    </para>
                </listitem>
            </unorderedlist>
        </section>
        <section>
            <title>
                Noise Calculation Cutoff
            </title>
            <exhibit>
                <img
                src='BaseOps_RunChunk_NoiseCalculationCutoff_ScreenCap.png'/>
            </exhibit>
            <para>
                As an optimization, the MRNMap noise model will ignore individual
                noise events with an SEL sound level below a user-defined noise
                calculation cutoff. See the MRNMap documentation for more information.
            </para>
            <para>
                The AGM noise model supports a similar cutoff parameter.
            </para>
        </section>
        <section id='BaseOps_RunChunk_ElevationAndGroundImpedance_id'>
            <title>
                Elevation and Ground Impedance
            </title>
            <exhibit>
                <img
                src='BaseOps_RunChunk_ElevationAndGroundImpedance_ScreenCap.png'/>
            </exhibit>
            <para>
                When computing noise levels, the NMap, AAM, and RNM noise models
                can optionally consider terrain elevation and ground impedance.
                Check the <italic>Use elevation and ground impedance</italic>
                box, then type the names of the elevation and ground impedance
                files. If you used BaseOps to create the elevation and ground
                impedance files, then the correct file names should already be
                set. See <iref
                target='BaseOps_ElevationAndImpedanceChunks_id'/> for more information.
            </para>
            <note type='note'>
                <para>
                    Be aware that the noise models run significantly slower when considering
                    the effects of terrain.
                </para>
            </note>
            <note type='note'>
                <para>
                    The AGM noise model requires that the elevation and ground impedance
                    grids be present.
                </para>
            </note>
        </section>
        <section id='BaseOps_RunChunk_ScenariosToRun_id'>
            <title>
                Scenarios to Run
            </title>
            <exhibit>
                <img src='BaseOps_RunChunk_ScenariosToRun_ScreenCap.png'/>
            </exhibit>
            <para>
                Every <link target='#BaseOps_IntroductionToCases_id'>BaseOps case</link>
                contains one or more <termtext>scenarios</termtext>. See <iref
                target='BaseOps_ScenarioChunk_id'/>. When you run a case, a noise
                analysis is typically performed for each scenario.
            </para>
            <para>
                You may sometimes wish to run only some of the scenarios in the
                case. In this situation, select <italic>Run Only The Following
                Scenarios</italic> from the dropdown list. A list of the scenarios
                in the case is displayed.
            </para>
            <exhibit>
                <img
                src='BaseOps_RunChunk_ScenariosToRun_SomeScenarios_ScreenCap.png'/>
            </exhibit>
            <para>
                Check the box next to each scenario that you wish to run. At least
                one scenario must be checked.
            </para>
            <para>
                If you are running more than one scenario, select how BaseOps
                should respond if an error occurs while running a scenario. You
                have two choices.
            </para>
            <unorderedlist>
                <listitem>
                    <para>
                        <italic>immediately halt the run</italic> - BaseOps immediately
                        terminates and displays the error message.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        <italic>attempt to run other scenarios</italic> - BaseOps halts
                        the current scenario, but attempts to run any remaining scenarios.
                        After all scenarios are attempted, a summary of the error(s) that
                        occurred is displayed. This is useful if you leave BaseOps unattended
                        (for example, overnight) while running a computationally intensive
                        case.
                    </para>
                </listitem>
            </unorderedlist>
        </section>
        <section id='BaseOps_RunChunk_StepsToRun_id'>
            <title>
                Steps to Perform
            </title>
            <exhibit>
                <img src='BaseOps_RunChunk_Steps_ScreenCap.png'/>
            </exhibit>
            <para>
                Running a BaseOps case consists of a number of steps (creating
                the NMap input file, executing the AAM noise model, etc.). Typically,
                you will want to perform all of the steps. However, there may
                be situations where you only want to perform some of them. In
                this situation, select <italic>Perform Only The Following Steps</italic>
                from the dropdown list. A list of the steps is displayed.
            </para>
            <exhibit>
                <img src='BaseOps_RunChunk_Steps_SomeSteps_ScreenCap.png'/>
            </exhibit>
            <para>
                Only those steps that are relevant to the selected noise models
                are shown. See <iref target='BaseOps_NoiseModelsUsed_id'/> for
                more information.
            </para>
            <para>
                Check the box next to each step that you wish to perform. At least
                one step must be checked. The following steps are defined.
            </para>
            <unorderedlist>
                <listitem>
                    <para>
                        <italic>Create Omega 10 and 11 Input Files for NMap Operations</italic>
                        - Omega10 and Omega11 are the United States Department of Defense's
                        computer programs for extrapolating measured noise data. This
                        step creates input files used to run these programs for NMap operations.
                        The input file names will end in the text <filetext>NMap&nbsp;-&nbsp;Omega10.i10</filetext>
                        and <filetext>NMap&nbsp;-&nbsp;Omega11.i11</filetext>. See the
                        NMap documentation for more information.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        <italic>Run Omega 10 and 11 for NMap Operations</italic> - Run
                        the Omega10 and Omega11 programs for NMap operations. The Omega
                        output file names will end in the text <filetext>NMap&nbsp;-&nbsp;Omega10.o10</filetext>
                        and <filetext>NMap&nbsp;-&nbsp;Omega11.o11</filetext>, and the
                        Omega log file names will end in the text <filetext>NMap&nbsp;-&nbsp;Omega10.log</filetext>
                        and <filetext>NMap&nbsp;-&nbsp;Omega11.log</filetext>. See the
                        NMap documentation for more information.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        <italic>Create NMap OPS File</italic> - Create the NMap OPS file.
                        The OPS file name will end in the text <filetext>NMap.ops</filetext>.
                        See the NMap documentation for more information.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        <italic>Create NMap OPX File</italic> - Append the Omega 10 and
                        11 NMap noise profiles to the OPS file to create the NMap OPX
                        input file. The OPX file name will end in the text <filetext>NMap.opx</filetext>.
                        See the NMap documentation for more information.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        <italic>Run NMap</italic> - Run the NMap noise model. The NMap
                        grid, point of interest, and log file names will end in the text
                        <filetext>NMap.grd</filetext>, <filetext>NMap.poi</filetext>,
                        and <filetext>NMap.log</filetext>, respectively. See the NMap
                        documentation for more information.
                    </para>
                    <note type='note'>
                        <para>
                            The grid and point of interest files will only be created if you
                            selected to perform grid and point of interest computations, respectively.
                            See <iref target='BaseOps_RunChunk_ComputationsPerformed_id'/>.
                        </para>
                    </note>
                </listitem>
                <listitem>
                    <para>
                        <italic>Create Omega10R Input Files for MRNMap Operations</italic>
                        - Create input file used to run the Omega10R program for MRNMap
                        operations. The input file name will end in the text <filetext>MRNMap&nbsp;-&nbsp;Omega10.i10</filetext>.
                        See the MRNMap documentation for more information.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        <italic>Run Omega10R for MRNMap Operations</italic> - Run the
                        Omega10R program for MRNMap operations. The Omega10R output and
                        log file names will end in the text <filetext>MRNMap&nbsp;-&nbsp;Omega10.o10</filetext>
                        and <filetext>MRNMap&nbsp;-&nbsp;Omega10.log</filetext>, respectively.
                        See the MRNMap documentation for more information.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        <italic>Create MRNMap INS File</italic> - Create the MRNMap INS
                        file. The INS file name will end in the text <filetext>MRNMap.ins</filetext>.
                        See the MRNMap documentation for more information.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        <italic>Create MRNMap INX File</italic> - Append the Omega10R
                        noise profiles to the INS file to create the MRNMap INX input
                        file. The INX file name will end in the text <filetext>MRNMap.inx</filetext>.
                        See the MRNMap documentation for more information.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        <italic>Run MRNMap</italic> - Run the MRNMap noise model. The
                        MRNMap grid, point of interest, and log file names will end in
                        the text <filetext>MRNMap.grd</filetext>, <filetext>MRNMap.poi</filetext>,
                        and <filetext>MRNMap.log</filetext>, respectively. See the MRNMap
                        documentation for more information.
                    </para>
                    <note type='note'>
                        <para>
                            The grid and point of interest files will only be created if you
                            selected to perform grid and point of interest computations, respectively.
                            See <iref target='BaseOps_RunChunk_ComputationsPerformed_id'/>.
                        </para>
                    </note>
                </listitem>
                <listitem>
                    <para>
                        <italic>Create AAM OPS File</italic> - The AAM OPS input file
                        is created. This file's name will end in the text <filetext>AAM.ops</filetext>.
                        See the AAM documentation for more information.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        <italic>Run AAM</italic> - Run the AAM noise model. The AAM grid,
                        point of interest, and log file names will end in the text <filetext>AAM.grd</filetext>,
                        <filetext>AAM.poi</filetext>, and <filetext>AAM.log</filetext>,
                        respectively. See the AAM documentation for more information.
                    </para>
                    <note type='note'>
                        <para>
                            The grid and point of interest files will only be created if you
                            selected to perform grid and point of interest computations, respectively.
                            See <iref target='BaseOps_RunChunk_ComputationsPerformed_id'/>.
                        </para>
                    </note>
                </listitem>
                <listitem>
                    <para>
                        <italic>Run AGM</italic> - Run the AGM noise model. For each attack
                        run, the DefineRun, AirGunneryModel, and BoomModel programs are
                        executed. Then a combined grid, representing the total summed
                        noise from each attack run, is created. Scaling for munition expenditures
                        and day/evening/night splits happens during the summing stage.
                    </para>
                    <note type='note'>
                        <para>
                            The attack runs processed by the AGM programs can be affected
                            by NoiseMake. See <iref
                            target='BaseOps_RunChunk_NoiseMake_id'/>.
                        </para>
                    </note>
                </listitem>
                <listitem>
                    <para>
                        <italic>Create RNM OPS File</italic> - The RNM OPS input file
                        is created. This file's name will end in the text <filetext>RNM.ops</filetext>.
                        See the RNM documentation for more information.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        <italic>Run RNM</italic> - Run the RNM noise model. The RNM grid,
                        point of interest, and log file names will end in the text <filetext>RNM.grd</filetext>,
                        <filetext>RNM.poi</filetext>, and <filetext>RNM.log</filetext>,
                        respectively. See the RNM documentation for more information.
                    </para>
                    <note type='note'>
                        <para>
                            The grid and point of interest files will only be created if you
                            selected to perform grid and point of interest computations, respectively.
                            See <iref target='BaseOps_RunChunk_ComputationsPerformed_id'/>.
                        </para>
                    </note>
                </listitem>
                <listitem id='BaseOps_RunChunk_Step_CreateGrid_id'>
                    <para>
                        <italic>Create Grid</italic> - Create the final noise grid. The
                        output grids from the other noise models are summed, if necessary,
                        and additional grid metadata (description of the Noisemap case
                        and scenario, details of the scenario's flight tracks, points
                        of interest, etc.) is added to the grid.
                    </para>
                    <para>
                        The final grid will be named <filetext><italic>casename</italic>&nbsp;-&nbsp;<italic>scenarioname</italic>.grd</filetext>,
                        where <italic>casename</italic> is the name of the <link
                        target='#BaseOps_OpeningCase_id'><filetext>.baseops</filetext>
                        case file</link> and <italic>scenarioname</italic> is the <link
                        target='#BaseOps_ScenarioChunk_WorkingWithScenarios_id'>scenario
                        file id name</link>.
                    </para>
                    <para>
                        To view the final noise grid, choose <menutext>Plot</menutext>
                        from the <menutext>Case</menutext> menu. See <iref
                        target='BaseOps_PlottingNoiseContours_id'/>.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        <italic>Export Contours</italic> - Export noise level contours
                        to a file in ARC/INFO Shapefile format. The shapefile will be
                        written to a file that ends in the text <filetext>Contours.shp</filetext>.
                        Shapefile index, shapefile attribute, coordinate system projection,
                        and FGDC metadata files will also be created; these will end in
                        the text <filetext>Contours.shx</filetext>, <filetext>Contours.dbf</filetext>,
                        <filetext>Contours.prj</filetext>, and <filetext>Contours.shp.xml</filetext>,
                        respectively. See <iref target='BaseOps_ContoursChunk_id'/> for
                        more information.
                    </para>
                </listitem>
            </unorderedlist>
            <note type='warning'>
                <para>
                    If you choose to run only some steps, you are responsible for
                    insuring that the proper steps are run at the proper times. For
                    example, if you run the "Create NMap OPX File" step, then make
                    changes to the case, and then run the "Run NMap" step, NMap will
                    run using the previously created OPX file, which doesn't contain
                    the most recent changes made to the case. BaseOps does not check
                    for mistakes of this kind.
                </para>
            </note>
            <note type='note'>
                <para>
                    All of the steps create one or more files. These files will be
                    located in the same directory as the <filetext>.baseops</filetext>
                    case file, and will begin with the name of the case file, followed
                    by the <link
                    target='#BaseOps_ScenarioChunk_WorkingWithScenarios_id'>scenario
                    file id name</link>. For example, if the case file is named <filetext>Wright-Patterson.baseops</filetext>
                    and the scenario file id name is <filetext>Baseline</filetext>,
                    then the Omega 10 input file will be named <filetext>Wright-Patterson&nbsp;-&nbsp;Baseline&nbsp;-&nbsp;Omega10.i10</filetext>.
                </para>
            </note>
            <note type='note'>
                <para>
                    In addition to the primary OPX/OPS input file, some noise models
                    (specifically, NMap, AAM, and RNM) take an additional input file:
                    the RUN file.
                </para>
                <para>
                    BaseOps creates RUN files during the <italic>Run NMap/AAM/RNM</italic>
                    steps. However, these RUN files cannot be used to run the noise
                    models directly. This is because BaseOps supports long file names,
                    but the RUN file format only supports DOS-style 8.3 file names.
                    Therefore, when BaseOps runs a case, it must use temporary 8.3
                    file names for all input and output files. The RUN files BaseOps
                    creates refer to these temporary files.
                </para>
                <para>
                    There are no RUN file options that can't be set using BaseOps.
                    Therefore, as long as the noise models are run from within BaseOps,
                    the fact that the RUN file refers to these temporary files is
                    irrelevant to you. However, if you wish to run the noise models
                    independently of BaseOps, you will need to manually copy all input
                    files to the appropriate temporary files. See the notes at the
                    end of a BaseOps-generated RUN file for more information.
                </para>
            </note>
        </section>
        <section id='BaseOps_RunChunk_NoiseMake_id'>
            <title>
                NoiseMake
            </title>
            <para>
                NoiseMake is a feature of BaseOps that can substantially reduce
                noise model running time when editing a BaseOps case. When NoiseMake
                is active, output from previous noise model runs is reused when
                possible.
            </para>
            <para>
                Currently, NoiseMake has been implemented for only one noise model:
                AGM. When the feature is active, AGM is run on each attack run
                separately, and the output is saved. Subsequently, if the case
                is edited and then rerun, only those attack runs whose data has
                changed are processed; the AGM output for the other attack runs
                is reused.
            </para>
            <para>
                The temporary output are stored in a directory named <filetext><italic>CASENAME</italic>
                - Cache</filetext>, where <filetext><italic>CASENAME</italic></filetext>
                is the name of the BaseOps case file.
            </para>
            <para>
                To turn on NoiseMake, check the <italic>Use NoiseMake</italic>
                box.
            </para>
            <exhibit>
                <img src='BaseOps_RunChunk_NoiseMake_ScreenCap.png'/>
            </exhibit>
            <para>
                Press the <italic>Delete NoiseMake Temporary Files</italic> button
                to delete all the temporary NoiseMake files and reclaim the disk
                space. The next time you run the case, BaseOps will invoke the
                appropriate noise model(s) and recalculate these files on an as-needed
                basis. However, depending on the size of the case, recalculating
                the files may take a considerable amount of time.
            </para>
        </section>
        <section id='BaseOps_RunChunk_ExternalNoiseModelOptions_id'>
            <title>
                External Noise Model Options
            </title>
            <para>
                When running a case, BaseOps executes external noise models such
                as <filetext>NMap.exe</filetext> and <filetext>AAM.exe</filetext>.
                You can select the initial state of the windows in which these
                external noise models run, as well as the process priority at
                which they are run.
            </para>
            <exhibit>
                <img
                src='BaseOps_RunChunk_ExternalNoiseModelWindows_ScreenCap.png'/>
            </exhibit>
            <para>
                You have three choices for the initial window state.
            </para>
            <unorderedlist>
                <listitem>
                    <para>
                        <italic>Normal</italic> - External noise models are run in normal
                        windows. These will appear above the BaseOps window, obscuring
                        it.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        <italic>Minimized</italic> - External noise models are run in
                        minimized windows. The model window will appear on the taskbar.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        <italic>Hidden</italic> - External noise models are run in hidden
                        windows. The only indication that the model is running will be
                        the BaseOps Run Status dialog box.
                    </para>
                </listitem>
            </unorderedlist>
            <para>
                When working with large BaseOps cases that take a long time to
                run, consider choosing either <italic>Minimized</italic> or <italic>Hidden</italic>,
                as these will minimize any interruptions as you use your computer
                for other tasks. Usually, <italic>Minimized</italic> is the recommended
                choice, as that allows you to switch to the model window when
                desired to view any information the model displays as it runs.
            </para>
            <para>
                You have two choices for the process priority.
            </para>
            <unorderedlist>
                <listitem>
                    <para>
                        <italic>Normal</italic> - External noise models are run at the
                        same priority as most other Windows programs.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        <italic>Below Normal</italic> - External noise models are run
                        at a reduced priority.
                    </para>
                </listitem>
            </unorderedlist>
            <para>
                Choosing <italic>Below Normal</italic> can make your computer
                more responsive if you intend to use it for other tasks while
                also running a large BaseOps case.
            </para>
        </section>
    </section>
    <section id='BaseOps_RunStatus_id'>
        <title>
            Monitoring the Status of a Run
        </title>
        <para>
            While BaseOps is running a case, the Run Status dialog box is
            displayed. It presents a summary of the run's progress.
        </para>
        <exhibit>
            <img src='BaseOps_RunStatusDialogBox_ScreenCap.png'/>
        </exhibit>
        <para>
            Press the Minimize button to minimize the BaseOps application
            while the run proceeds. This can be useful if you wish to use
            your computer for other tasks while BaseOps completes a lengthy
            run in the background.
        </para>
        <para>
            Press the Cancel button to terminate the run.
        </para>
    </section>
    <section id='BaseOps_PlottingNoiseContours_id'>
        <title>
            Plotting Noise Contours
        </title>
        <para>
            After a case has been run, you can use the NMPlot plotting application
            to display contours of the <link
            target='#BaseOps_RunChunk_Step_CreateGrid_id'>predicted noise
            levels</link>. To do so, choose <menutext>Plot</menutext> from
            the <menutext>Case</menutext> menu. NMPlot will be started, displaying
            a contour plot of your case's noise level grid file.
        </para>
        <exhibit>
            <img
            src='BaseOps_RunChunk_NMPlotDisplayingContours_ScreenCap.png'/>
        </exhibit>
        <para>
            The first time that a grid file is displayed using NMPlot, an
            NMPlot plot file will be created. This file will have the extension
            <filetext>.nmp</filetext>. If you customize the plot (change the
            contour levels, add background maps, etc.), the changes will be
            stored in this file. You can open and edit this file with NMPlot
            even if BaseOps is not running.
        </para>
        <para>
            If your case has multiple scenarios, then you will have multiple
            noise level grid files. In this situation, when you choose <menutext>Plot</menutext>
            from the <menutext>Case</menutext> menu, a dialog box will appear,
            asking you which scenario's grid file you wish to plot.
        </para>
        <exhibit>
            <img
            src='BaseOps_RunChunk_NMPlotDisplayingContours_SelectGridToPlotDialogBox_ScreenCap.png'/>
        </exhibit>
        <para>
            Select a scenario, then press OK.
        </para>
        <para>
            Select <menutext>Contents</menutext> from NMPlot's <menutext>Help</menutext>
            menu to display the NMPlot User's Guide, which describes NMPlot
            in detail.
        </para>
    </section>
</section>
