Previous Home Site Map Contact Next
Wasmer Consulting BaseOps User's Guide Running Cases
After entering all of the data (runways, flight tracks, weather information, etc.) in a BaseOps case, you can run the case: that is, execute the noise model(s) that compute the predicted noise levels. To run the case, select Run Case from the Case menu.
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.
To check a case for errors and warnings, you can:
Choose Check Case from the Case menu
Press Ctrl + K
The message report is displayed, showing any errors or warnings found.
Errors must be corrected before the case is run. Warnings do not, but you should carefully consider each one.
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.
After following a hyperlink, use the back button to easily return to the message report. See Using the Back and Forward Buttons.
At any time, you can go to the message report and view the results of the last error check by choosing Messages from the object type selector dropdown list.
You can print the message report. See Printing Objects.
The noise models calculate noise levels at a two-dimensional grid of points covering your area of interest. You can set the grid's location, size, and resolution (distance between adjacent points).
The grid is always orientated so that its rows and columns run east-west and north-south.
The grid has the following properties.
Location of Center - The location of the center of the grid, specified with respect to the case reference point. Typically, the reference point is located near the center of the area of interest, so the grid location will usually be close to (0, 0).
The grid location is always specified with respect to the case reference point, regardless of the current case coordinate system.
Point Spacing - The distance between adjacent grid points in the east-west and north-south directions.
Number of Points - 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.
You can select the units used to specify the grid properties. See Setting the Case's Physical Units for more information.
As the final step in running a case, BaseOps exports each scenario's 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.
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 Plotting Noise Contours.
The following contour properties can be set.
Contour Levels - 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 Noise Metric.
Coordinate System - Select the geographic coordinate system of the contour shapefiles. See Coordinate System Control for more information.
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).
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.
Initially, all metadata elements will have default values assigned to them. For example, the Citation/Title 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.
You can edit the information displayed in any of the text boxes. When you do, the Reset Element button will be enabled . 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.
Press the Show Element Definition button to display a metadata element's documentation from the FGDC standard.
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.
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.
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.
There are numerous options that affect the computations performed when you run a BaseOps case. To set these options, first choose Run from the object type selector dropdown list. Then set the options in the text pane.
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 noise metrics.
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 Noise Models
|Name||Description||Supporting Noise Models|
|ALM||Maximum A-weighted Sound Level for single user-selected flight or static profile.||NMap, AAM|
|AMAX||Maximum A-weighted Sound Level||AAM|
|CNEL||Community Noise Equivalent Level||All|
|CNELR||Onset-rate-adjusted Community Noise Equivalent Level||MRNMap|
|DNL||Day-Night Average Sound Level||All|
|LDNMR||Onset-rate-adjusted Monthly Day-Night Average A-weighted Sound level. PHA (percent highly annoyed) is also calculated.||MRNMap|
|LEQ||Equivalent Sound Level (user-selected number of hours). Note that the LEQ noise metric is depreciated. Use LEQA with newer versions of NMap and AAM.||NMap, AAM|
|LEQA||Equivalent Sound Level (user-selected number of hours)||NMap, AAM|
|LEQ24||Equivalent Sound Level (24-hour)||MRNMap, RNM|
|LMAX||Maximum A-weighted Sound Level||MRNMap|
|Number of Events Above a user-selected threshold SEL/ALM level||NMap, AAM|
|NAPNLT||Number of Events Above a user-selected threshold PNLT level||AAM|
|NEF||Noise Exposure Forecast||NMap, AAM, RNM|
|PA||Probability of Awakening||NMap, AAM|
|SEL||Sound Exposure Level for single user-selected flight profile. Note that the SEL noise metric is depreciated. Use SELA with newer versions of NMap and AAM.||NMap, AAM|
|SELA||Sound Exposure Level for single user-selected flight profile.||NMap, AAM|
|SEL (all ops)||Sound Exposure Level (all operations)||MRNMap|
|SELR||Onset-rate-adjusted Sound Exposure Level||MRNMap|
|SELU||Unweighted Sound Exposure Level||MRNMap|
|TAALM||Time Above (in minutes) a user-selected threshold ALM||NMap, AAM|
|WECPNL||Weighted Equivalent Continuous Perceived Noise Level||NMap, AAM, RNM|
Each of the noise models supported by BaseOps can calculate noise levels (in the selected metric) at a two-dimensional grid of locations. They can also perform a detailed noise analysis at each of the case's points of interest.
Select whether you would like to perform grid noise computations, points of interest noise computations, or both.
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.
Daily - Profiles are ranked by their contribution to the daily noise level.
Event - Profiles are ranked by their single-event noise levels.
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.
When computing noise levels, the NMap, AAM, and RNM noise models can optionally consider terrain elevation and ground impedance. Check the Use elevation and ground impedance 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 Editing Elevation and Ground Impedance Data for more information.
Be aware that the noise models run significantly slower when considering the effects of terrain.
You may sometimes wish to run only some of the scenarios in the case. In this situation, select Run Only The Following Scenarios from the dropdown list. A list of the scenarios in the case is displayed.
Check the box next to each scenario that you wish to run. At least one scenario must be checked.
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.
immediately halt the run - BaseOps immediately terminates and displays the error message.
attempt to run other scenarios - 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.
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 Perform Only The Following Steps from the dropdown list. A list of the steps is displayed.
Only those steps that are relevant to the selected noise models are shown. See Noise Models for more information.
Check the box next to each step that you wish to perform. At least one step must be checked. The following steps are defined.
Create Omega 10 and 11 Input Files for NMap Operations - 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 NMap - Omega10.i10 and NMap - Omega11.i11. See the NMap documentation for more information.
Run Omega 10 and 11 for NMap Operations - Run the Omega10 and Omega11 programs for NMap operations. The Omega output file names will end in the text NMap - Omega10.o10 and NMap - Omega11.o11, and the Omega log file names will end in the text NMap - Omega10.log and NMap - Omega11.log. See the NMap documentation for more information.
Create NMap OPS File - Create the NMap OPS file. The OPS file name will end in the text NMap.ops. See the NMap documentation for more information.
Create NMap OPX File - 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 NMap.opx. See the NMap documentation for more information.
Run NMap - Run the NMap noise model. The NMap grid, point of interest, and log file names will end in the text NMap.grd, NMap.poi, and NMap.log, respectively. See the NMap documentation for more information.
Create Omega10R Input Files for MRNMap Operations - Create input file used to run the Omega10R program for MRNMap operations. The input file name will end in the text MRNMap - Omega10.i10. See the MRNMap documentation for more information.
Run Omega10R for MRNMap Operations - Run the Omega10R program for MRNMap operations. The Omega10R output and log file names will end in the text MRNMap - Omega10.o10 and MRNMap - Omega10.log, respectively. See the MRNMap documentation for more information.
Create MRNMap INS File - Create the MRNMap INS file. The INS file name will end in the text MRNMap.ins. See the MRNMap documentation for more information.
Create MRNMap INX File - 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 MRNMap.inx. See the MRNMap documentation for more information.
Run MRNMap - Run the MRNMap noise model. The MRNMap grid, point of interest, and log file names will end in the text MRNMap.grd, MRNMap.poi, and MRNMap.log, respectively. See the MRNMap documentation for more information.
Create AAM OPS File - The AAM OPS input file is created. This file's name will end in the text AAM.ops. See the AAM documentation for more information.
Run AAM - Run the AAM noise model. The AAM grid, point of interest, and log file names will end in the text AAM.grd, AAM.poi, and AAM.log, respectively. See the AAM documentation for more information.
Create RNM OPS File - The RNM OPS input file is created. This file's name will end in the text RNM.ops. See the RNM documentation for more information.
Run RNM - Run the RNM noise model. The RNM grid, point of interest, and log file names will end in the text RNM.grd, RNM.poi, and RNM.log, respectively. See the RNM documentation for more information.
Create Grid - 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.
To view the final noise grid, choose Plot from the Case menu. See Plotting Noise Contours.
Export Contours - 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 Contours.shp. Shapefile index, shapefile attribute, and FGDC metadata files will also be created; these will end in the text Contours.shx, Contours.dbf, and Contours.shp.xml, respectively. See Setting Contour Properties for more information.
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.
All of the steps create one or more files. These files will be located in the same directory as the .baseops case file, and will begin with the name of the case file, followed by the scenario file id name. For example, if the case file is named Wright-Patterson.baseops and the scenario file id name is Baseline, then the Omega 10 input file will be named Wright-Patterson - Baseline - Omega10.i10.
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.
BaseOps creates RUN files during the Run NMap/AAM/RNM 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.
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.
After a case has been run, you can use the NMPlot plotting application to display contours of the predicted noise levels. To do so, choose Plot from the Case menu. NMPlot will be started, displaying a contour plot of your case's noise level grid file.
The first time that a grid file is displayed using NMPlot, an NMPlot plot file will be created. This file will have the extension .nmp. 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.
If your case has multiple scenarios, then you will have multiple noise level grid files. In this situation, when you choose Plot from the Case menu, a dialog box will appear, asking you which scenario's grid file you wish to plot.
Select a scenario, then press OK.
Select Contents from NMPlot's Help menu to display the NMPlot User's Guide, which describes NMPlot in detail.
Previous Home Site Map Contact NextCopyright © 1996-2017, Wasmer Consulting