
<section id='BaseOps_ScenarioChunk_id'
webfilename='scenariochunk'>
    <title>
        Using Scenarios
    </title>
    <para>
        Every <link target='#BaseOps_IntroductionToCases_id'>BaseOps case</link>
        contains one or more <termtext>scenarios</termtext>. A scenario
        is a set of case modifications, such as scaling the number of
        flight profile operations or deleting static profiles. When you
        run the case, a noise analysis is performed for each scenario:
        see <iref target='BaseOps_RunningCases_id'/>.
    </para>
    <para>
        When a new case is created, it contains a single scenario named
        "Baseline". This baseline scenario does not modify the case. In
        many situations, this is the only scenario required.
    </para>
    <para>
        However, you may sometimes need to perform a noise analysis for
        two or more situations, to compare the noise impact of each alternative.
        For example, when performing an environmental assessment for a
        proposed change to an airfield's operations, it is common to perform
        one noise analysis of the existing noise impact, and another noise
        analysis of the predicted noise impact after the proposed change
        is implemented.
    </para>
    <para>
        Without scenarios, this could only be done by creating separate
        BaseOps cases for each noise analysis. Using scenarios, however,
        you can keep all information in a single case. This brings many
        advantages. Typically, a large fraction of the information is
        common to all of the alternative cases. Keeping all of the information
        in a single BaseOps case reduces the amount of information that
        must be redundantly entered and kept synchronized.
    </para>
    <section id='BaseOps_ScenarioChunk_WorkingWithScenarios_id'>
        <title>
            Working With Scenarios
        </title>
        <para>
            To work with scenarios, choose Scenarios from the <link
            target='#BaseOps_ListPane_id'>object type selector dropdown list</link>.
            Scenarios can be added, duplicated, and deleted as described in
            <iref target='BaseOps_ListPane_id'/>.
        </para>
        <para>
            To edit a scenario, first select it in the <link
            target='#BaseOps_ListPane_id'>object list</link>, then edit its
            properties in the <link
            target='#WCF_ApplicationMainWindow_id'>text pane</link>.
        </para>
        <exhibit>
            <img src='BaseOps_ScenarioChunk_ScreenCap.png'/>
        </exhibit>
        <para>
            Scenarios have the following properties.
        </para>
        <unorderedlist>
            <listitem>
                <para>
                    <italic>Name</italic> - A descriptive name that uniquely and unambiguously
                    identifies the scenario. There is no length restriction on the
                    name.
                </para>
            </listitem>
            <listitem>
                <para>
                    <italic>File Id Name</italic> - A short (40 characters maximum)
                    descriptive name that identifies this scenario. Every scenario
                    in a case must have a unique file id name. All files created while
                    running a scenario will be located in the same directory as the
                    containing <filetext>.baseops</filetext> case file, and will be
                    of the form <filetext>CASENAME - FILEIDNAME - FILETYPE.EXTENSION</filetext>,
                    where CASENAME is the name of the <filetext>.baseops</filetext>
                    case file, FILEIDNAME is the file id name specified here, and
                    FILETYPE and EXTENSION identify the type of the file (NMap input
                    file, RNM log file, etc.).
                </para>
                <para>
                    If desired, the file id name can be empty. This would typically
                    be done in cases that contain only a single scenario.
                </para>
            </listitem>
            [-include "BaseOps_Notes_ListItem.rxl"    ObjectTypeName='scenario'-]
            <listitem>
                <para>
                    <italic>Changes</italic> - The changes to be made to the BaseOps
                    case to create the scenario case.
                </para>
                <para>
                    To add a new change, either press the Add Change button <img
                    src='intres:BaseOps_AddPlusSignSmallButtonBitmap'/>, or press
                    <keytext>Ctrl + A</keytext>. The Select Type of Change dialog
                    box appears.
                </para>
                <exhibit>
                    <img
                    src='BaseOps_ScenarioChunk_SelectTypeOfChangeDialogBox_ScreenCap.png'/>
                </exhibit>
                <para>
                    Select the type of change you would like to make to the case,
                    then press OK. The change is added to the scenario.
                </para>
                <para>
                    To edit a change, press the Edit button <img
                    src='WCF_ThreeDotsButton_Figure.png'/> next to that change. A
                    dialog box appears that allows you to edit the change's options.
                    See <iref
                    target='BaseOps_ScenarioChunk_TypesOfScenarioChange_id'/> for
                    a description of the options associated with each type of change.
                </para>
                <para>
                    To delete a change, either press the Delete Choice button <img
                    src='intres:WCF_DeleteCrossToolbarButtonBitmap'/>, or press <keytext>Ctrl
                    + Del</keytext>.
                </para>
                <para>
                    To move a change 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>. Changes are applied
                    in order, starting from the top of the list and working down.
                </para>
            </listitem>
        </unorderedlist>
    </section>
    <section id='BaseOps_ScenarioChunk_TypesOfScenarioChange_id'>
        <title>
            Types of Scenario Changes
        </title>
        <section
        id='BaseOps_ScenarioChunk_ScaleOperationsScenarioChange_id'>
            <title>
                Scale Operations Scenario Change
            </title>
            <para>
                Use the Scale Operations scenario change to modify the number
                of day, evening (if applicable), and night operations for flight,
                airspace and static profiles. Only flight profile scaling is describe
                here; airspace and static profile scaling is performed in an analogous
                manner.
            </para>
            <para>
                To scale flight profile operations, add a Scale Flight Profile
                Operations change to a scenario, then edit the change's options
                (see <iref
                target='BaseOps_ScenarioChunk_WorkingWithScenarios_id'/>). The
                Scale Flight Profile Operations dialog box appears.
            </para>
            <exhibit>
                <img
                src='BaseOps_ScenarioChunk_ScaleFlightProfilesOperationsDialogBox_ScreenCap.png'/>
            </exhibit>
            <para>
                Enter the factors by which the number of day, evening (if applicable),
                and night operations will be multiplied. A factor of 2 would double
                the number of operations, and 0.5 would halve them. Entering 1
                for the scale factor would leave the number of operations unchanged.
            </para>
            <para>
                Select the flight profiles whose operations will be scaled. This
                is done in a similar manner to selecting the objects to display
                in the object list. See <iref
                target='BaseOps_FilteringListPane_id'/> for more information.
            </para>
        </section>
        <section
        id='BaseOps_ScenarioChunk_DeleteObjectsScenarioChange_id'>
            <title>
                Delete Objects Scenario Change
            </title>
            <para>
                Use the Delete Objects scenario change to delete objects (flight
                tracks, static profiles, etc.). Only flight profile deletion is
                describe here; the deletion of other types of objects is performed
                in an analogous manner.
            </para>
            <para>
                To delete flight profiles, add a Delete Flight Profiles change
                to a scenario, then edit the change's options (see <iref
                target='BaseOps_ScenarioChunk_WorkingWithScenarios_id'/>). The
                Select Flight Profiles to Delete dialog box appears.
            </para>
            <exhibit>
                <img
                src='BaseOps_ScenarioChunk_DeleteFlightProfilesDialogBox_ScreenCap.png'/>
            </exhibit>
            <para>
                Select the flight profiles that will be deleted. This is done
                in a similar manner to selecting the objects to display in the
                object list. See <iref target='BaseOps_FilteringListPane_id'/>
                for more information.
            </para>
        </section>
        <section
        id='BaseOps_ScenarioChunk_ChangeWeatherScenarioChange_id'>
            <title>
                Change Weather Conditions Scenario Change
            </title>
            <para>
                Use the Change Weather Conditions scenario change to modify the
                scenario's weather conditions. You can specify a new temperature,
                relative humidity, and atmospheric pressure to use when running
                the scenario.
            </para>
            <para>
                To change weather conditions, add a Change Weather Conditions
                change to a scenario, then edit the change's options (see <iref
                target='BaseOps_ScenarioChunk_WorkingWithScenarios_id'/>). The
                Select New Weather Conditions dialog box appears.
            </para>
            <exhibit>
                <img
                src='BaseOps_ScenarioChunk_SelectNewWeatherConditionsDialogBox_ScreenCap.png'/>
            </exhibit>
            <para>
                Select the new weather conditions. See <iref
                target='BaseOps_WeatherChunk_id'/> for more information.
            </para>
        </section>
        <section
        id='BaseOps_ScenarioChunk_UseElevationAndImpedanceScenarioChange_id'>
            <title>
                Change Elevation and Ground Impedance Usage
            </title>
            <para>
                Use the Change Elevation and Ground Impedance Usage scenario change to modify whether the elevation and ground impedance files are used when the case is run.
            </para>
            <para>
                To change the usage, add a Change Elevation and Ground Impedance Usage
                change to a scenario, then edit the change's options (see <iref
                target='BaseOps_ScenarioChunk_WorkingWithScenarios_id'/>). The
                Use Elevation and Ground Impedance dialog box appears.
            </para>
            <exhibit>
                <img
                src='BaseOps_ScenarioChunk_ElevationAndGroundImpedanceDialogBox_ScreenCap.png'/>
            </exhibit>
            <para>
                Use the check box to select whether elevation and ground impedance should be used when the case is run.  See <iref
                target='BaseOps_RunChunk_ElevationAndGroundImpedance_id'/> for more information.
            </para>
        </section>
    </section>
    <section>
        <title>
            Saving a Scenario as a New Case
        </title>
        <para>
            If desired, you can save a scenario as a new case file. This is
            rarely necessary, but BaseOps gives you this capability for exceptional
            circumstances.
        </para>
        <para>
            To save a scenario as a new case file, press the Save Modified
            Case to File button. You will be prompted for the name of the
            new <filetext>.baseops</filetext> case file that will be created.
        </para>
        <note type='caution'>
            <para>
                The "save modified case to file" feature should be used sparingly.
                If possible, keep all scenarios in a single BaseOps case. This
                allows you to share those parts of the case that are common between
                multiple scenarios. This makes changes much easier. For example,
                if a flight track used by aircraft from multiple scenarios must
                be modified, the change only needs to be made in one place.
            </para>
        </note>
    </section>
</section>
