United States
Environmental
Protection
Agency
Office of Air Quality
Planning and Standards
Research Triangle Park, NC 27711
EPA-450/4-91 -009
April 1991
AIR
E PA GRADED MODEL INFORMATION
SUPPORT SYSTEM (GMISS)
USER'S GUIDE
Volume II: UAM Subsystem
-------
vo
<, ,
"Sa
O
Gridded Model Information Support System (GMISS)
User's Guide
Volume II: UAM Subsystem
Prepared For
Source Receptor Analysis Branch
Technical Support Division
Office of Air Quality Planning And Standards
U.S. Environmental Protection Agency
Research Triangle Park, NC 27711
By
Computer Sciences Corporation
Applied Technology Division
P.O. Box 12767
Research Triangle Park, NC 27709
April 18, 1991 U.S. Environrr ' ' - ,f ,.
Region 5 i;;-,_ iion Agency
West Jack-;, -;.
-------
Notice
The U.S. Environmental Protection Agency funded production of this document under contract
68-01-7365 to Computer Sciences Corporation. The Agency has reviewed the document and approved
it for publication. Mention herein of trade names or commercial products does not constitute
endorsement or recommendation for use.
Acknowledgements
This manual and the software it describes were written for the U.S. Environmental Protection
Agency by employees of Computer Sciences Corporation. Tom Dessent and Phil Gibbs developed the
software, with assistance from Beverly Goodrich and Diane Linderman. Joe Newsom and Susan Gerry
assisted with software testing. Tom Dessent wrote this manual. Jeanne Eichinger edited it and
contributed many helpful suggestions. Ruen-Tai Tang reviewed the manual for technical content.
Richard Wayland supervised the project and provided indispensable technical information, advice, and
encouragement.
Several U.S. Environmental Protection Agency employees reviewed drafts of this document
and made many helpful comments. They included Ellen Baldridge, the project officer, Norman
Possiel, and Edwin Meyer of the Office of Air Quality Planning and Standards; and James Godowitch
of the Atmospheric Research and Exposure Assessment Laboratory. Ellen Baldridge wrote the
Preface. Norman Possiel wrote the Background section of Chapter 1 and the ROMNET scenario
descriptions used in help screens and printed reports. (Norman Possiel and James Godowitch are on
assignment to the U.S. Environmental Protection Agency from the National Oceanic and Atmospheric
Administration, U.S. Department of Commerce.)
-------
Preface
One of the objectives of the Regional Ozone Modeling for Northeast Transport Study was to
provide procedures through which Regional, State, and local agencies could retrieve Regional Oxidant
Model (ROM) data for use in Urban Airshed Model (UAM) applications. The Gridded Model
Information Support System (GMISS) was developed in support of this goal. The UAM Subsystem of
GMISS provides modelers with easy to follow menus which allow them to retrieve ROM data and
create data files specifically formatted for the ROM-UAM Interface Program System. The ROM-
UAM Interface converts the data from the ROM vertical and horizontal gridding resolution to the
UAM resolution. The use of ROM data for initial and boundary conditions to UAM provides
consistent air quality data between UAM applications within a ROM region and relieves Regional,
State and local agencies of costly data preparation and quality assurance tasks.
This volume of the GMISS User's Guide describes the procedures required to retrieve a
temporal (via start and stop times) and spatial (via latitude and longitude) subset of ROM data for use
in a specific UAM application. GMISS retrieval files are specially formatted as input to the ROM-
UAM Interface Program System. Volume V of the UAM User's Guide describes the operations and
procedures for executing the ROM-UAM Interface Program System to create input files to the UAM.
Other volumes of the GMISS User's Guide describe data base management utilities for
loading, quality assuring, and maintaining the ROM database on EPA's IBM computer system at
Research Triangle Park, North Carolina. These parts of the GMISS are currently under development
and testing. Due to the tight schedule set by the Clean Air Act Amendments enacted November 1990,
and in order to give modelers access to these data as soon as possible, the UAM Subsystem was
developed, documented, and made available first.
111
-------
IV
-------
Contents
1. INTRODUCTION 1
1.1 Background 1
1.2 GMISS UAM Subsystem 2
1.3 Organization of This Manual 2
1.4 For More Information 2
2. OVERVIEW 5
2.1 An Introduction to GMISS 5
2.2 The ROM-UAM Interface 7
2.3 Retrieval Files 8
2.4 Selection Criteria 12
2.5 Retrieval Procedures 14
3. PROCEDURES 15
3.1 Authorization 15
3.2 Equipment 15
3.3 Getting Started 16
3.4 Using Menus 18
4. TUTORIAL 23
4.1 Starting GMISS 23
4.2 Choosing a ROM Simulation 25
4.3 Specifying Dates 29
4.4 Selecting Data Categories 33
4.5 Specifying a Subdomain 33
4.6 Selecting Rawin Stations 36
4.7 Retrieval File Names 36
4.8 Batch Job Parameters 38
4.9 Batch Job Submission 40
4.10 Exiting From GMISS 41
4.11 Checking the Data Extraction 42
5. MENU REFERENCE 44
5.1 Menu Outline 44
5.2 Main Menu 46
5.3 Menu 2.1 - Specify Data Selection Criteria 48
5.4 Menus 2.1.1 Through 2.1.4 - Lists of Values 52
5.5 Menu 2.2 - Select From Available Data 56
5.6 Menu 2.3 - Select Data Categories 59
5.7 Menu 2.4 - Specify Subdomain Coordinates 60
5.8 Menu 2.5 - Select Rawin Stations 64
5.9 Menu 2.6 - Specify Retrieval File Names 67
5.10 Menus 2.7 and 1.1 - Specify Batch Job Parameters 70
Contents
-------
Contents
(Continued)
6. FILES 75
6.1 Retrieval File Types 75
6.2 Concentration Data 75
6.3 Processor Data 84
Contents
VI
-------
Figures
Figure 2-1. Overview of GMISS 6
Figure 3-1. SAS Screen That Appears Briefly During GMISS Startup 17
Figure 3-2. GMISS Main Menu 18
Figure 3-3. Sample UAM Subsystem Menu 19
Figure 4-1. Invoking GMISS From TSO 23
Figure 4-2. GMISS Main Menu 24
Figure 4-3. UAM Subsystem Menu for Data Selection Criteria 25
Figure 4-4. Entering a Scenario Name 26
Figure 4-5. Scenario Name Is Incorrect 26
Figure 4-6. Requesting a List of Scenario Names 27
Figure 4-7. First Page of the Scenario "Help" Screen 28
Figure 4-8. Second Page of the Scenario "Help" Screen 28
Figure 4-9. The Selected Scenario Name Is Filled In 29
Figure 4-10. The Dates Available for Scenario BASE85 30
Figure 4-11. Selecting and Altering a Date Range 31
Figure 4-12. An Error Message Indicates a Problem With the Date Range 32
Figure 4-13. Correcting the Date Problem 32
Figure 4-14. The Default Selection Is to Retrieve All Data Categories 33
Figure 4-15. Subdomain Coordinates Are Opposite Corners of a Rectangle 34
Figure 4-16. Specifying Coordinates of a UAM Domain (ROM Subdomain) 35
Figure 4-17. A Message Notes the Exchange of Coordinates to Correct the Error 35
Figure 4-18. First Page of Rawin Selection Menu 37
Figure 4-19. Selecting Rawin Stations After Scrolling the List 37
Figure 4-20. Default Retrieval File Names 38
Figure 4-21. Default Batch Job Parameters 39
Figure 4-22. Supplying the Missing Batch Job Parameters 39
Figure 4-23. TSO Message Confirming Batch Job Submission 40
Figure 4-24. Main Menu Returns When Retrieval Request Is Completed 41
Figure 4-25. The TSO "READY" Prompt That Appears After Exiting From GMISS 41
Figure 4-26. Summary Report of Batch Data Retrieval Processing 43
Figure 5-1. UAM Subsystem Menu Structure 45
Figure 5-2. GMISS Main Menu 47
Figure 5-3, UAM Subsystem Database Contents Report 47
Figure 5-4. Menu 2.1 - Specify Data Selection Criteria 49
Figure 5-5. Appearance of Menu 2.1 When Some Fields Have Only One Possible Value 49
Figure 5-6. Menu 2.1.1 - Select Model 54
Figure 5-7. Menu 2.1.2 - Select Domain 54
Figure 5-8. Menu 2.1.3 - Select Study 55
Figure 5-9. Menu 2.1.4 - Select Scenario 55
Figure 5-10. Menu 2.2 - Select From Available Data 56
Figure 5-11. Menu 2.3 - Select Data Categories 59
v11 Contents
-------
Figures
(Continued)
Figure 5-12. Menu 2.4 - Specify Subdomain Coordinates 61
Figure 5-13. Menu 2.5 - Select Rawin Stations 65
Figure 5-14. Locations of Rawin Stations in Eastern United States and Canada 67
Figure 5-15. Menu 2.6 - Specify Retrieval File Names 69
Figure 5-16. Appearance of Menu 2.6 With an Excluded Data Category 69
Figure 5-17. Menu 2.7 - Specify Batch Job Parameters for Data Retrieval 72
Figure 5-18. Menu 1.1 - Specify Batch Job Parameters for Database Contents Report 72
Figure 5-19. Notification That Batch Job Was Submitted 74
Figure 6-1. Structure Diagram for UAM Retrieval Files of Concentration Data 78
Figure 6-2. Formats of Header Records of UAM Retrieval Files of ROM Processor Data 84
Figure 6-3. Structure Diagram for UAM Retrieval File of Nongridded Data 87
Figure 6-4. Structure Diagram for UAM Retrieval Files of Gridded Data 92
Tables
Table 1-1. EPA Regional Contacts for UAM Ozone Modeling 4
Table 2-1. ROM Chemical Species in UAM Retrieval Files 9
Table 2-2. ROM Processor Data Categories and Data Types in UAM Retrieval Files 11
Table 3-1. PF Key Functions for UAM Subsystem Menus 20
Table 6-1. Types of Data in UAM Retrieval Files 77
Table 6-2. ROM Chemical Species in UAM Retrieval Files 77
Table 6-3. Fields in UAM Retrieval Files of Concentration Data 81
Table 6-4. Fields in Header Records of UAM Retrieval Files of ROM Processor Data 85
Table 6-5. Parameters in the UAM Retrieval File of Hourly Nongridded Data 86
Table 6-6. Fields in UAM Retrieval Files of Nongridded Data 88
Table 6-7. Parameters in UAM Retrieval Files of Time-Invariant Gridded Data 90
Table 6-8. Parameters in UAM Retrieval Files of Hourly Gridded Data 91
Table 6-9. Fields in UAM Retrieval Files of Gridded Data 93
Contents
vin
-------
1. INTRODUCTION
This manual describes the procedures for using the UAM Subsystem ofGMISS to retrieve Regional
Oxidant Model (ROM) data for input to the ROM-UAM Interface Program System. This chapter
summarizes the purpose and features of the GMISS UAM Subsystem and outlines the organization of
the rest of the manual.
1.1 Background
GMISS, the Gridded Model Information Support System, is a computer-based repository of
data produced and used by selected grid-based air pollution models. The U.S. Environmental
Protection Agency (EPA) commissioned the development of GMISS in 1988, and the first implementa-
tion was completed in 1989. Its purpose is to provide a means for States and EPA to readily access
model input and output databases for analysis and interpretation (e.g., evaluating strategies and
assessing model performance). Although GMISS is conceptually designed to handle gridded results of
any air pollution model, all the data stored so far are from simulations using the Regional Oxidant
Model (ROM).
The GMISS UAM Subsystem is designed for retrieval of selected ROM databases which can
be used for specifying input fields to the Urban Airshed Model (UAM). States are required by the
EPA to use UAM to simulate the effectiveness of control strategies to abate the problem of urban
smog in certain high pollution cities. The UAM Subsystem creates data files specifically formatted as
input to the ROM-UAM Interface.1 The ROM-UAM Interface provides a bridge between the two
models, converting ROM data to formats compatible with the UAM. This user's guide describes the
functions of the UAM Subsystem and explains how to use it to obtain ROM databases which drive
UAM via the Interface.
'For a description of the ROM-UAM Interface, see the User's Guide For The Urban Airshed Model, Volume V: Description
and Operation of the ROM-UAM Interface Program System, EPA-450/4-90-007E (June 1990), U.S. Environmental Protection
Agency, Office of Air Quality Planning and Standards, Research Triangle Park. NC 27711.
Introduction
-------
1.2 GMISS UAM Subsystem
Anyone who has access to the IBM computer system at the EPA National Computer Center
can retrieve ROM data with the UAM Subsystem; there are no restrictions on its use. All ROM data
that EPA has reviewed and approved are available for retrieval. This is a continuing process; as
additional ROM runs are made, the new data are released through GMISS following review and
approval.
To use the UAM Subsystem, specify which of the available ROM data to retrieve by entering
choices on a series of menu screens. The menus describe what information is needed. Some menus
display a list of values to choose from, and some have spaces on the screen for entering values. All
the menus check the entries and notify you if a choice is incorrect or inconsistent. You can use the
UAM Subsystem successfully without having extensive knowledge of either the IBM computer system
or the ROM. The UAM Subsystem creates one or more disk files containing the data requested, and a
printed report summarizing the data selection criteria and the computer processing done.
1.3 Organization of This Manual
The following chapters of this manual provide the information required to use the UAM
Subsystem and the data files it creates.
• Chapter 2 describes subsystem features and characteristics.
• Chapter 3 tells what equipment is needed and how to start and use the system.
• Chapter 4 is a tutorial that illustrates typical data retrieval procedures.
• Chapter 5 describes each menu screen and explains how to use it.
• Chapter 6 shows the formats of data files the subsystem generates.
1.4 For More Information
This manual provides complete instructions for using the UAM Subsystem of GMISS, but it
does not attempt to cover other topics. If this manual does not provide required information, contact
the sources listed below.
2
Introduction
-------
For information about using the IBM computer system at the EPA National Computer Center,
or for help with IBM computer-related problems, contact the user support department. Specialists are
on duty weekdays 8:00 a.m. through 7:00 p.m. eastern time to help solve problems and to answer
questions. The user support department mailing address and telephone numbers are:
User Support Department, MD-34
EPA National Computer Center
U.S. Environmental Protection Agency
Research Triangle Park, North Carolina 27711
Telephone: (FTS) 629-7862 or (919) 541-7862 or (800) 334-2405
For any other information not directly related to using the IBM computer system, get in touch
with the meteorology/modeling contact for your EPA Region, listed in Table 1-1. Contact that person
for questions about registering to use EPA's IBM computer system, choosing which ROM simulation
to use as the basis for a UAM simulation, using the ROM-UAM Interface software, or using the UAM
software.
Introduction
-------
Table 1-1. EPA Regional Contacts for UAM Ozone Modeling
Ian Cohen
EPA Region I
J.F.K. Federal Building
Boston, MA 02203-2211
(617) 565-3229
Bob Kelly
EPA Region II
26 Federal Plaza
New York, NY 10278
(212) 264-2551
Brenda Johnson
EPA Region IV
345 Courtland Street, NE
Atlanta, GA 30365
(404) 347-2864
Rebecca Calby
EPA Region V
230 South Dearborn Street
Chicago, IL 60604
(312) 886-6065
Larry Svoboda (acting)
EPA Region VHI
999 18th Street
Denver Place, Suite 500
Denver, CO 80202-2405
(303) 776-5097
Carol Bohnenkamp
EPA Region IX
75 Hawthorne Street
San Francisco, CA 94105
(415) 744-1238
Alan Cimorelli
EPA Region III
841 Chestnut Building
Philadelphia, PA 19107
(215) 597-6563
James Yarbrough
EPA Region VI
First Interstate Bank Tower
1445 Ross Avenue
Dallas, TX 75202-2733
(214) 655-7214
Robert Wilson
EPA Region X
Environmental Services Division
1200 Sixth Avenue
Seattle, WA 98101
(206) 442-1531
Richard Daye
EPA Region VH
726 Minnesota Avenue
Kansas City, KS 66101
(913) 551-7619
Introduction
-------
2. OVERVIEW
The UAM Subsystem lets you access the GMISS database to retrieve regional-scale air pollution model
data for use with the Urban Airshed Model via the ROM-UAM Interface Program System. This
chapter discusses the types of data you can retrieve, the criteria you can use to select data for
retrieval, and the m« chanics of the data retrieval process.
2.1 An Introduction to GMISS
The Gridded Model Information Support System (GMISS) is a database of information
associated with selected grid-based air pollution models, and computer software for maintaining and
accessing that information. Figure 2-1 illustrates the main components of GMISS. The central,
principal component is the database. There are two data-handling components, Model Concentration
Data Subsystem and UAM Subsystem, and two data-handling functions, load and retrieve. The
dashed-line boxes in Figure 2-1 indicate the scope of the data-handling subsystems, and the shaded
boxes indicate the data-handling functions. The shaded arrows in each subsystem signify the flow of
data into and out of the database by the data loading and retrieving functions. The arrow with darker
shading represents the UAM Subsystem data retrieval function described by this manual.
In Figure 2-1, the symbols for input and output files are only partly within the scope of the
data subsystems. This indicates that GMISS does not control the creation of the incoming model data
or the use of retrieved data. GMISS retrieval files are designed and intended for certain uses, as
Figure 2-1 indicates, but the file owners—GMISS users—ultimately determine how the retrieved data
are used. The unshaded arrows in the Use area of Figure 2-1 emphasize that GMISS is not directly
involved with the use of retrieved data.
The Model Concentration Data Subsystem deals primarily with the model predictions—the
computed atmospheric concentrations of pollutants, precursors, and related chemical species. This
subsystem gives EPA access to the vast amounts of data produced by model simulations, and
facilitates data visualization, comparison, and analysis. The load function stores hourly concentration
values in the GMISS database, and the retrieve function extracts selected hourly data and creates either
5 Overview
-------
Gridded Model Information Support System (GMISS)
I Model Concentration Data
tC."."".'I>. Subsystem i
RADM
Cone. File
•'' Model
j Concentration
ROM 1Oafa
Cone. File
PF102
PF108
PF118.
PF119
_PF103_
PF114.
PF115.
_PF11L
PF144—
Model
'Concentration
Data
ROM
Processor
Data
GMISS
Database
ROM
Processor
Files
ROM-UAM
Retrieval
I Files
|MF174|
UAM Subsystem
Analysis
Urban A3r
PQBution
Modeling
Load
Retrieve
Use
Figure 2-1. Overview of GMISS
Overview
-------
sequential or SAS-format retrieval files. Currently the Model Concentration Data Subsystem has data
only from ROM simulations, but in the future it may also include data from the Regional Acid
Deposition Model and the Urban Airshed Model. At present, the Model Concentration Data Subsys-
tem is reserved for internal use by the EPA only.
The UAM Subsystem of GMISS, on the other hand, is available to all users. Its purpose is to
supply ROM data, the results of regional-scale air pollution simulations, for use as initial conditions
and boundary conditions in urban-scale modeling with the Urban Airshed Model. The GMISS
database administrator uses the load function to store ROM data in the GMISS database. With the
retrieve function, GMISS users create retrieval files of ROM concentration data (the results of a
simulation) and ROM processor data (input data for a simulation) that EPA has reviewed and approved
for public use. Anyone having access to the IBM computer system at EPA's National Computer
Center can use the UAM Subsystem to retrieve data from the GMISS database; there are no restric-
tions on its use.
The rest of this chapter explains more about UAM Subsystem retrieval files and the ROM data
they contain, the criteria for specifying which ROM data to retrieve from GMISS, and how the data
retrieval takes place.
2.2 The ROM-UAM Interface
When the UAM Subsystem retrieves data from the GMISS database, it creates one retrieval
file containing data produced by a particular ROM simulation, plus 12 retrieval files that contain some
of the input data used by the ROM in that simulation. (As you will see later, it is possible to suppress
generation of some of the retrieval files if you do not need them.) The content and format of the
retrieval files are compatible with ROM-UAM Interface software that creates the files ultimately used
by the UAM.
Why does GMISS not directly create the files that the UAM needs? Why is there ROM-UAM
Interface software? "Portability" is one reason—-the ability to move data from one computer to
another. The UAM uses unformatted input files, in which numbers are encoded as binary values.
This makes the files compact and easy for the UAM programs to read. But the principal computer
7
Overview
-------
manufacturers each encode binary values differently, and one format is not directly compatible with
another. For example, UAM programs running on a DEC VAX computer could not read a binary file
created on EPA's IBM computer. In order to run the UAM on a computer other than EPA's IBM
computer system, the input files the UAM uses must be compatible with that target computer system.
The ROM-UAM Interface software solves the compatibility problem by converting formatted
data files created by GMISS to the unformatted files the UAM needs. Formatted files represent data
values as characters (digits), as in a printed report. The character-only formatted files can be
exchanged among different computer systems with relative ease. On the target computer system, the
ROM-UAM Interface software reads the formatted (character) files from GMISS and creates unformat-
ted (binary) files for the UAM software. Since the ROM-UAM Interface software and the UAM
software run on the same computer, the unformatted files the Interface creates are compatible with that
computer system and with the UAM.
Of course, the ROM-UAM Interface software does much more than simply translating
formatted files to unformatted ones. It does considerable processing to convert the ROM data to the
forms the UAM needs. But it is the file translation feature that allows data from GMISS to be
"exported" from EPA's IBM computer to other computers.
2.3 Retrieval Files
The UAM Subsystem provides most of the data needed to run the UAM. It automatically
retrieves the appropriate kinds of data from the GMISS database and "packages" the data in retrieval
files compatible with the ROM-UAM Interface software. The UAM Subsystem retrieval files contain
two classes of data: ROM concentration data and ROM processor data. Concentration data are the
results, the output, of ROM simulations; processor data are inputs to ROM simulations.
ROM concentration data are hourly averages of the atmospheric concentrations of about 35
chemical species, mostly pollutants and their precursors, computed during a ROM simulation. The
EPA determined that when these ROM concentration data are used to establish the initial and
boundary conditions for UAM simulations, only the 17 chemical species listed in Table 2-1 signifi-
cantly affect the UAM simulation results. Therefore, the UAM Subsystem creates retrieval files that
Q
Overview
-------
contain concentration data for just those 17 ROM chemical species. The hourly concentration values
in retrieval files are 3-hour moving averages of the hourly values in the GMISS database. The 3-hour
average concentration for a particular hour is the arithmetic mean of the GMISS hourly values for that
hour, the preceding hour, and the following hour. Averaging the ROM data dampens short-term
variations and provides "smoother" boundary conditions for UAM simulations.
Table 2-1. ROM Chemical Species in UAM Retrieval Files
Name
Description
Name
Description
ALD2
CO
ETH
FORM
H202
HNO2
HNO3
ISOP
MTHL
Aldehydes (high mol. wt)
Carbon monoxide
Ethene
Formaldehyde
Hydrogen peroxide
Nitrous acid (HONO)*
Nitric acid
Isoprene
Methanol (MEOH)*
NO
NO2
O3
OLE
PAN
PAR
TOL
XYL
Nitric oxide
Nitrogen dioxide
Ozone
Olefins
Peroxyacetyl nitrate
Paraffins
Toluene
Xylene
Species name in the Urban Airshed Model; all other species names are the same in both models.
The geographic area covered by a ROM simulation is called the domain. A ROM domain is
defined in terms of longitude and latitude, and is a rectangle.2 A grid of imaginary lines parallel with
the domain boundaries divides the domain into rectangular cells that are 15 minutes of longitude
"wide" in the east-west direction and 10 minutes of latitude "high" in the north-south direction. A
ROM cell extends about 18.5 kilometers north-south and, depending on its latitude, about 20-24
kilometers east-west. The ROM also divides the atmosphere vertically into three layers, which have
"thicknesses" that range from about 100 meters to a few thousand meters. The ROM computes the
apparent shape of a ROM domain on a map depends on the type of projection used to represent the nearly-spherical
surface of the Earth. On a map using a cylindrical projection, such as Universal Transverse Mercator, the lines of longitude and
latitude that define domain boundaries are straight and orthogonal, and the ROM domain is a rectangle. On a map using the
more common conic projection system, such as Lambert and Albers projections, the parallels (lines of latitude) are curved and
the meridians (lines of longitude) are straight but not parallel. In the conic projection system, a ROM domain does not look
rectangular, since its top and bottom borders are curved and its left and right sides are not parallel. The plane geometric shape
that best illustrates a ROM domain's dimensions is probably a trapezoid, since the domain's top (northern) edge is shorter than
the bottom (southern) edge due to the convergence of parallels that define the east and west sides. This manual uses the term
"rectangular" to describe the shape of a ROM domain because of the correspondence between right angles in the plane geometry
of the rectangle and the solid geometry of the latitude-longitude coordinate system on the Earth's surface.
" Overview
-------
concentrations of chemical species in every "cube", or cell, of this three-dimensional array. A single
concentration datum is the concentration of a particular chemical species, at a particular date and time
in a particular simulation, for one three-dimensional cell of the domain. That particular cell is
identified by row and column numbers in the domain grid, and by vertical layer3 number. The cell at
the southwest comer of the ROM domain is row 1, column 1. Row numbers increase to the north,
and column numbers increase to the east Layer 1 is at the surface, and each higher layer has a higher
number.
UAM Subsystem retrieval files of ROM concentration data contain data for all three vertical
layers but for only a subset of the ROM grid cells. This ROM subdomain is a rectangular area that
encloses the geographic area to be modeled with the UAM. The subdomain is composed of whole
ROM grid cells, so its boundaries lie on some of the imaginary lines that divide the ROM domain into
a grid, and the longitude-latitude coordinate system specifies its location. Since the urban areas
modeled by the UAM are much smaller than the regional areas of the ROM, the subdomain in a
retrieval file generally contains data for less than 10 percent of the ROM domain. You specify the
size and location of the subdomain when you retrieve the data. The subdomain may be up to 30 grid
cells in the east-west direction (7.5 degrees of longitude), and the size of the ROM domain is the only
limit on its north-south dimension (about 9 degrees of latitude). Thus, the biggest subdomain you can
retrieve is considerably larger than any urban area in North America; for example, the New York City
urban area fits comfortably in a rectangle about 3 degrees of longitude by 2 degrees of latitude.
The second class of data contained in UAM Subsystem retrieval files, ROM processor data, is
more diverse than the concentration data. Table 2-2 lists the 4 data categories, 3 data types, and 12
files. The file names shown are used in the ROM and referred to in the user's guide for the ROM-
UAM Interface software. They are part of the default retrieval file names the UAM Subsystem
constructs. The "PF" prefix denotes a processor file, used by a ROM preprocessor to generate a file
for the ROM or another preprocessor. The "MF" prefix denotes a model file, used directly by the
ROM. In some publications, these are referred to collectively as "PF/MF files". In this manual, we
use "ROM processor files" as a generic term that refers to both processor and model files.
'Sometimes "level" is used instead of "layer"; the terms are synonymous.
Overview 10
-------
Table 2-2. ROM Processor Data Categories and Data Types in UAM Retrieval Files
Data Category
Data Type
File Names and Descriptions
Rawinsonde data
RAWDSf Nongridded,
hourly values
Geographic data
GEO Gridded,
time-invariant
values
Biogenic emissions data
BIOGEN Gridded,
hourly values
Meteorological data
MET Gridded,
hourly values
PF102 Interpolated temperature vertical profiles
derived from rawinsonde data
PF108 Surface roughness
PF118 Land use
PF119 Terrain elevation
PF144 Emissions from biogenic sources
PF103 Surface air temperature
PF114 Layer 2 horizontal wind components
PF115 Layer 1 horizontal wind components
PF117 Sky coverage (cloudiness)
MF165 Elevation of layer 1-layer 2 boundary
MF166 Elevation of layer 2-layer 3 boundary
MF174 Layer 1 water vapor concentration
Each of the four data categories defined by the UAM Subsystem (Table 2-2) consists of one or
more ROM processor files that contain similar types of data and have similar formats. You can
choose which categories to retrieve. The default action is to retrieve all of them, since all are needed
to run the ROM-UAM Interface software.
The RAWIN category is nongridded, hourly air temperature data derived from rawinsonde
vertical profiles. These profiles are measurements of atmospheric conditions recorded by an instru-
mented balloon as it ascends. A ROM preprocessor interpolates the rawinsonde data at regularly-
spaced altitude intervals and at hourly time intervals to produce the vertical profile data stored in
GMISS. The sites where balloons are released and monitored, often at airports, are called rawin
stations. You choose which stations to retrieve based on their proximity to the area to be modeled by
the UAM. The RAWIN retrieval file contains ROM vertical profile data for each station chosen.
11
Overview
-------
The GEO category consists of gridded "geographic" values that remain constant within the
time frame of air pollution modeling, such as land use data. This type of UAM retrieval file has a
single value of each geographic quantity for each grid cell of the ROM subdomain you retrieve.
The BIOGEN and MET categories consist of gridded, hourly data: emissions of key chemical
species from natural sources and meteorological conditions during the time period of a model run.
These types of UAM retrieval files have values for each hour and each grid cell of the ROM
subdomain you retrieve.
Chapter 6 has detailed descriptions of UAM Subsystem retrieval files. It identifies the
particular kinds of data (parameters) in each file, explains how the files are organized, and gives
record formats. You do not need to know this detailed information to use the retrieval files with the
ROM-UAM Interface software, however.
2.4 Selection Criteria
Each ROM simulation of air pollution is based on a set of conditions called a scenario. The
two main components of a scenario are meteorological conditions and emissions from natural
(biogenic) and man-made (anthropogenic) sources. ROM simulations show the effects of various
hypotheses regarding emissions, using meteorological data recorded during the time period being
simulated. The complete description of a scenario identifies the emissions hypotheses and the
meteorological episode used in the simulation.
The GMISS database contains data for many ROM scenarios. You can get descriptions of
these scenarios in the form of a printed report or as "help" information on a UAM Subsystem menu
screen. Knowing the scenario conditions is important because scenario name is the primary criterion
for selecting which data to retrieve from GMISS. To create a particular set of retrieval files, the UAM
Subsystem extracts ROM concentration data and ROM processor data associated with the particular
scenario that you select.
In addition to scenario, there are three other related selection criteria that you need to specify
to retrieve data for a particular ROM simulation: study, domain, and model. Scenarios are grouped
12
Overview
-------
into studies. A study is a series of simulations intended to demonstrate some effect, answer some
general question, or meet some EPA program objective. The definition of a study is flexible. Because
the same scenario name can be used in different studies, you need to specify a study name to identify
a specific simulation. Domain is the geographic area covered by a ROM simulation. Model is the
acronym of the version of the ROM used to perform a simulation. As with study, the same scenario
name may be used for separate simulations that pertain to different domains or ROM versions. To
retrieve data for a particular ROM simulation, therefore, you must qualify the scenario name with the
names of the appropriate study, domain, and model.
Once you have chosen a ROM simulation, you must define what part of the simulation to
retrieve. This involves selection criteria for date range, subdomain, and data categories.
ROM simulations usually have a duration of 15 days, although a few last 12 or 9 days. The
corresponding scenarios in GMISS are 1 or 2 days shorter, because the UAM Subsystem does not use
the first and last dates of a simulation. (Depending on the ROM version, simulations begin and end at
either noon or midnight; the first and last dates may be either half-days or whole days.) Three days is
the shortest time period for which you can retrieve data, and the duration of the scenario is the longest
time period. The UAM Subsystem ensures that data are available for every day in the date range you
specify, so retrieval files always contain data for consecutive days.
Subdomain was discussed in the Retrieval Files section above. A subdomain is a rectangle
within the ROM domain that encloses the urban area to be modeled with the UAM. To define the
subdomain, you specify the longitude and latitude coordinates of two opposite corners of a rectangle.
The UAM Subsystem automatically enlarges your subdomain by adding a border of about two ROM
grid cells on all four sides. The enlarged subdomain provides additional data that the ROM-UAM
Interface software uses to establish boundary conditions at the edges of the area to be modeled with
the UAM (the UAM domain).
The Retrieval Files section also discussed the categories of data defined in the UAM
Subsystem. You choose which of five data categories to retrieve: ROM concentration data and the
four categories of ROM processor data listed in Table 2-2. All five categories of data are needed to
run the ROM-UAM Interface software, so you would retrieve less than the full set only if you have
Overview
-------
already retrieved the same data before, or if you plan to substitute equivalent data obtained from
another source.
2.5 Retrieval Procedures
UAM Subsystem data retrieval occurs in two stages. The first stage is an interactive computer
terminal session, in which you use menus to specify selection criteria for the data to retrieve. The
second stage is a batch job that extracts the requested data from GMISS and creates retrieval files.
The menu software submits the batch job after you have supplied all the necessary information, and
usually the job begins executing very soon thereafter. It may be delayed if many other batch jobs are
running (or waiting to run), or if your job control specifications force it into a low-priority category.
Chapter 5, Menu Reference, describes the items that affect batch job priority. Since the batch job
creates the retrieval files, you cannot access them until the batch job finishes.
If you are running the ROM-UAM Interface and the UAM on a computer other than the IBM
computer system at EPA's National Computer Center, you will have to "export" the retrieval files the
UAM Subsystem creates. You probably will copy the files to magnetic tape and have the tape sent to
your computer site. (An "average" set of 13 retrieval files is about 14 megabytes of data, so
downloading to a PC by modem is not really feasible.) If you need assistance, get in touch with the
user support department of the EPA National Computer Center, or with the modeling contact for your
EPA Region. See the For More Information section of Chapter 1 for telephone numbers.
14
Overview
-------
3. PROCEDURES
The UAM Subsystem runs on the IBM computer system at EPA's National Computer Center. This
chapter explains what authorization and equipment you need to use the UAM Subsystem, how to use
subsystem menus, and how to start the subsystem.
3.1 Authorization
There are no restrictions on the use of the UAM Subsystem except that you must be a
registered user of the IBM computer system at the EPA National Computer Center. You need access
only to standard facilities of the IBM computer system: the ability to use TSO and to submit batch
jobs. TSO, or Time Sharing Option, is the interactive part of the IBM computer operating system; it
is the environment in which UAM Subsystem menus operate. Batch jobs, submitted by the menus,
execute under control of the MVS operating system. Job Control Language (JCL) statements created
by the menus define the tasks performed and the resources used by the batch job.
If you are not a registered user of EPA's IBM computer system, get information about
registration procedures from the modeling contact for your EPA Region. See the For More Informa-
tion section of Chapter 1 for the telephone number.
3.2 Equipment
The UAM Subsystem uses full-screen menus. This means the computer system and the
terminal exchange data in screen-sized segments, rather than a line at a time or character by character.
You must use a terminal that supports this full-screen protocol, or use equipment that emulates such a
terminal.
Full-screen IBM terminals have model numbers such as 3270, 3278, and 3179. Other
manufacturers market functionally equivalent terminals. These terminals display 80 characters per line
and 24 or 32 lines per screen. Some terminals have color displays, but monochrome displays are more
common. The UAM Subsystem menus work on either terminal type.
15 Procedures
-------
If you do not have a full-screen terminal, you can emulate one using an asynchronous terminal
or its equivalent, such as a personal computer equipped with a modem and appropriate communica-
tions software. The EPA National Computer Center has a protocol converter, equipment that converts
the character-by-character communications protocol of an asynchronous terminal to the full-screen
protocol required for the UAM Subsystem menus. For a PC/modem emulation to work acceptably, the
PC communications software must provide a way to make some keys on the PC keyboard equivalent
to the program function (PF) keys on full-screen terminals. You will not be able to use UAM
Subsystem menus if your terminal cannot emulate PF keys.
If you need more information about terminals or terminal emulations, get in touch with the
modeling contact for your EPA Region or with the user support department of the EPA National
Computer Center. See the For More Information section in Chapter 1 for telephone numbers.
3.3 Getting Started
GMISS and its UAM Subsystem run in the TSO environment on the IBM computer system of
EPA's National Computer Center. Before you can use the UAM Subsystem, you need to log on to
TSO in full-screen mode. If you need help doing this, read the "Getting Started" chapter of the Guide
to NCC Services. The Guide is distributed to new users of the National Computer Center when they
register, and current users can request a copy from the user support department (see For More
Information in Chapter 1 for telephone numbers). Unfortunately, the Guide to NCC Services is not
very clear about the procedure for connecting to the IBM computer system in the full-screen emulation
mode if you are using an asynchronous terminal or a personal computer and a modem. If you need
help, get in touch with the modeling contact for your EPA Region, or call the user support department
of the EPA National Computer Center. See For More Information in Chapter 1 for telephone
numbers.
When you have completed the log-on and TSO has displayed its "READY" prompt, you are
ready to invoke the UAM Subsystem. Type the following command exactly as shown (you can use
either lower case or upper case):
EX rGAME.GMISS.CLIST(GMISS)'
Procedures
-------
Press the ENTER key to transmit the command to the computer and start the UAM Subsystem. There
will be a short pause while the software is loaded and initialized. During that process, the SAS screen
shown in Figure 3-1 may appear briefly. When the main menu emerges (Figure 3-2), GMISS is
active.
You will find instructions for using GMISS menus later in this manual. The next section of
this chapter describes the general procedures for using UAM Subsystem menus. Chapter 4, Tutorial,
uses an example to illustrate those procedures and the menus you might use for a typical data retrieval
request. Chapter 5, Menu Reference, describes the sequence of menus and explains the details of each
one.
+LOG
Command ===>
Welcome to the new SAS System, Release 6.06.
Changes and enhancements available in SAS Release 6.06 are documented
in the "SAS Companion for the MVS Environment."
+PROGRAM EDITOR-
Command ===>
00001
00002
00003
00004
00005
00006
Figure 3-1. SAS Screen That Appears Briefly During GMISS Startup
17
Procedures
-------
Griddttd Modal Information Support System (GMXSS)
Main Manu
What do you want to do? _
1 - List Database Contents
2 - Retrieve Data for Urban Airshed Model (UAM)
(Press PF3/PF15 to exit from GMISS.)
Figure 3-2. GMISS Main Menu
3.4 Using Menus
UAM Subsystem menus make it easy for you to retrieve data from GMISS. The procedure is
simple:
1. A menu appears on your terminal screen and prompts you for certain informatioa
2. You supply the requested information and press the ENTER key. This is the basic
operating procedure; pressing the ENTER key tells the menu program, "I'm done here. Go on to the
next operation." You can alter the basic procedure using PF keys, as explained later in this sectioa
3. The menu program checks the information for errors or inconsistencies and reports any
problems it finds. You fix the problems, press ENTER, and the next menu appears.
4. Steps 1 through 3 are reputed for each menu needed to define your retrieval. When all
the specifications are assembled, the last menu program submits a batch job to perform the retrieval.
This section explains common features of UAM Subsystem menus and general procedures for
using them. Figure 3-3 is a menu that illustrates many of the features. The paragraphs following the
figure describe the features and how to use them.
Procedures
-------
+2.2-
GMISS: Retrieve Data for UAM
Select From Available Data
The data available in GMISS that match your initial selection criteria are
listed below, one scenario and continuous date range per line. Enter "S"
to select one entry from the list. Change the date range to select fewer
days, if you wish. Press ENTER to accept the marked selection.
(PF8/PF20=scroll forward, PF7/PF19=scroll backward, PF3/PF15=prev. menu)
You may select only one entry from the list.
SELECT Dates Available Scenario Study Domain Model
S
S
—
06/10/83
07/04/88
07/09/85
08/09/85
07/04/88
07/04/88
07/04/88
07/04/88
07/04/88
07/04/88
- 06/20/83
- 07/17/88
- 07/22/85
- 08/16/85
- 07/17/88
- 07/17/88
- 07/17/88
- 07/17/88
- 07/17/88
- 07/17/88
BASE05
BASE 05
BASES 5
BASE 8 5
BASE85
CS01
CS02
CS03
CS05
CS06
ROMNET
ROMNET
ROMNET
ROMNET
ROMNET
ROMNET
ROMNET
ROMNET
ROMNET
ROMNET
ROMNET 1
ROMNET 1
ROMNET 1
ROMNET 1
ROMNET 1
ROMNET 1
ROMNET 1
ROMNET 1
ROMNET 1
ROMNET 1
ROM21
ROM21
ROM21
ROM21
ROM21
ROM21
ROM21
ROM21
ROM21
ROM21
Figure 3-3. Sample UAM Subsystem Menu
Identification
Every UAM Subsystem menu has a number in the top left comer that uniquely identifies it,
and two title lines at the top of the screen summarize the menu's purpose or function. In
Figure 3-3, the identifying number is 2.2. The first title line identifies the general function
(data retrieval) and the second line states the specific purpose (choose which of the available
data you want to retrieve).
Instructions
The lines of text below the menu title explain what you are expected to do. The specific
instructions vary from one menu to another, but there are two general types of actions: select
from a list and fill in a blank. In Figure 3-3, the four lines of instructions describe both types
of action.
PF Keys
Below the instructions in Figure 3-3 is one line that indicates the functions assigned to PF
keys; on some menus, this information is located at the bottom of the screen. Table 3-1 lists
the standard PF key functions. The cancel function, PF3 or PF15, is available on every menu.
19
Procedures
-------
Table 3-1. PF Key Functions for UAM Subsystem Menus
PF Key Assigned Function
PF3 or PF 15 CANCEL - Tenninate the current menu without taking any action
and return to the previous menu.
PF4 or PF16 ABORT - Terminate the current menu without taking any action
and return to the GMISS main menu.
PF7 or PF19 BACKWARD - Scroll toward the beginning of a list of items.
PF8 or PF20 FORWARD - Scroll toward the end of a list of items.
PF10 or PF22 TOP - Scroll to the beginning of a list This is equivalent to
using PF7 or PF19 repeatedly.
PF11 or PF23 BOTTOM - Scroll to the end of a list This is equivalent to
using PF8 or PF20 repeatedly.
It lets you return to a previous menu or exit from the UAM Subsystem without retrieving data.
The abort function, PF4 or PF16, is available on every menu except the main menu. It is a
quick way to abandon a data retrieval request and return to the GMISS main menu, but your
menu choices are not saved (see below), and some warning messages may occur when you
end a GMISS terminal session in which you use abort. The scrolling functions listed in
Table 3-1 are meaningful only on menus that display an item list that does not all fit on one
screen. On other menus the PF keys for scrolling have the same effect as the ENTER key.
Error Messages
All UAM Subsystem menus have a message area that is used to notify you when something is
wrong. If you never make a mistake when using UAM Subsystem menus, the message area
will always be a blank line. Generally, it is located just below the instructions and list of PF
keys. When a menu program detects something wrong, it describes the problem in a one-line
message that appears after you press the ENTER key of your terminal. The message is
highlighted (red on color terminals) to make it stand out. In Figure 3-3, the message "You
may select only one entry from the list" appeared because two lines are selected, contrary to
the instructions to select only one.
20
Procedures
-------
Error Correction
Fill-in-the-blank fields associated with an error are highlighted (red on color terminals). If
there are multiple errors, the error message describes only the first one, but the fields involved
with all errors are highlighted to alert you that additional errors exist The cursor is positioned
at the first field involved with an error. You should change that field to eliminate the error. If
you can determine what is wrong with other highlighted fields just by looking at them, the
most efficient procedure is to change them also, before you press the ENTER key. If you are
not sure what is wrong with the other fields, just correct the field to which the error message
applies and press the ENTER key. An error message applicable to the next highlighted field
will then appear, and you can correct it. In some instances an error condition involves two or
more fields, and you may need to decide which of them is the real "culprit", the one causing
the error.
Selection and Specification Fields
The middle or bottom of a menu displays a list of values for you to choose from or has spaces
(fields) for you to enter values. The menu in Figure 3-3 has both. The fields under the
heading "SELECT" are for choosing which line (scenario) to retrieve. The fields under the
heading "Dates Available" will accept values you enter to replace their initial values. Both
selection fields and specification fields may have initial values. Pressing the terminal's TAB
key moves the cursor from one selection or specification field to the next. If your terminal
has a reverse-tab or back-tab key, pressing it moves the cursor to the previous selection or
specification field. You can also use the terminal's cursor-movement keys to move the cursor
to a field, but using the TAB key is quicker.
Protected Fields
Sections of the screen skipped over when you press TAB are protected; you cannot alter them.
If you move the cursor with cursor-movement keys to a protected part of the screen and try to
alter it, the terminal keyboard locks and you must press the RESET key to regain use of it.
Menu titles, instructions, "white space", and so on are protected areas. Sometimes an area of a
menu that looks like a fill-in-ti.c-blank field with an initial value is instead a protected field.
This happens when the menu program determines that only one value is valid for the field,
"fills in" that value for you, and makes the field protected. If you can tab the cursor to a field,
it has an initial value that can be changed. If you cannot tab to it, the field is protected.
91
Procedures
-------
Scrolling
Some menus have a list of items to choose from. In Figure 3-3, each item is one line, but
some menus have multiline items. If the entire list does not fit on the screen, you can scroll
to see more items. Imagine that part of the menu is a window through which you see the list
of items. Scrolling forward is like sliding the window down, toward the end of the list.
Scrolling backward is like sliding the window up, toward the beginning of the list. The
window scrolls by the number of lines visible, until it reaches the end or beginning of the list.
Scrolling backward when the beginning of a list is displayed has no effect, nor does scrolling
forward at the end of a list; "end of file" or "at bottom" or "at top" may appear in the message
area, however.
Field Values Saved and Recalled
The first time you use a menu, the fields in which you can enter values are blank or they have
default values chosen by the menu program, such as the dates in Figure 3-3. Underlines
indicate the locations and sizes of blank fields. When you leave a particular menu, the UAM
Subsystem saves the values of all fill-in-the-blank fields, but not the selections you make from
a scrollable list The next time you use the same menu, the values you entered (or the defaults
you accepted) are displayed as the initial values. If you want to use the same values again,
you do not have to re-enter them.
22
Procedures
-------
4. TUTORIAL
This chapter illustrates a typical data retrieval session. It shows how the menus will look when you
use the UAM Subsystem, and how they respond to common mistakes. You can run this example on
your own terminal, if you wish, by entering the values and commands given in the text.
4.1 Starting GMISS
Suppose you want to simulate ozone pollution in the Washington, DC-Baltimore, MD,
metropolitan area using the Urban Airshed Model. To get started on the project, you will retrieve
ROM data from GMISS to use in the UAM simulations. Having completed the log-on to EPA's IBM
computer system, you are ready to begin data retrieval. Follow the instructions for invoking GMISS,
given in the Getting Started section of Chapter 3, and type ex ' game. gmiss . clist (gmiss)'
after the TSO READY prompt. Your terminal screen at this point looks like Figure 4-1.
90/11/07
90/11/07
90/11/05
90/10/30
90/10/26
90/10/23
90/10/17
90/09/27
90/09/04
90/08/06
READY
ex ' game .
: IBM SYSTEMS UNAVAILABLE SUNDAY NOV 11TH
: NEW PRINT OUTPUT STANDARDS (UPDATED)
: VETERANS DAY HOLIDAY SCHEDULE
: APPLICATION MENU SYSTEM (APMS)
: NATURAL 2.1.5 IMPLEMENTATION (UPDATED)
: UPGRADE TO DF/HSM RELEASE 2.5
: CLASS K INITIATORS REINSTATED
: FOCUS RELEASE 6.0.6 IMPLEMENTATION
: FILE-AID/SPF V6.4.0 AVAILABILITY
: SAS REL 6.06 AVAILABLE FOR USER TESTING
gmiss . clist (gmiss) '
- SEE
- SEE
- SEE
- SEE
- SEE
- SEE
- SEE
- SEE
- SEE
- SEE
NEWS
NEWS
NEWS
NEWS
NEWS
NEWS
NEWS
NEWS
NEWS
NEWS
ALERTS
ALERT 11
ALERTS
ALERT 1
ALERT 6
ALERT 9
ALERT 8
ALERT 4
ALERT2
ALERT 10
Figure 4-1. Invoking GMISS From TSO
23
Tutorial
-------
Shortly after you press the ENTER key, the GMISS main menu appears. As you can see in
Figure 4-2, the main menu has two options. You should use option 1 to get a printed report listing the
names, dates, and descriptions of the ROM simulations available in GMISS before you begin using
option 2 to retrieve data. Figure 5-3 in Chapter 5 shows what the report looks like.
For this example, let us assume that the modeling contact for your EPA Region has advised
you to retrieve base case data for 1988, and has given you the GMISS scenario name for that data,
"BASE85". Choose option 2 of the GMISS main menu, Retrieve Data for UAM. Type 2 in the blank
after What do you want to do? and press the ENTER key. This selects the data retrieval function of
the UAM Subsystem of GMISS.
Gridded Model Information Support System (GMISS)
Main Menu
What do you want to do? _
1 - List Database Contents
2 - Retrieve Data for Urban Airshed Model (UAM)
(Press PF3/PF15 to exit from GMISS.)
Figure 4-2. GMISS Main Menu
24
Tutorial
-------
4.2 Choosing a ROM Simulation
Menu 2.1 (Figure 4-3), the first UAM Subsystem retrieval menu, appears in response to
choosing option 2 of the main menu. With menu 2.1, you can enter values for model, domain, study,
and scenario to specify which ROM simulation to retrieve. You can also specify the dates to retrieve
by entering values for first date and last date. Notice that the model, domain, and study fields already
have values. This is because all the ROM simulations in the GMISS database (at the time of this
example) are associated with the model, domain, and study shown on the menu. Since there is only
one possible value for those fields, the program has filled in the blanks and made the fields unchange-
able; they are protected fields. The second sentence of the instructions on the menu explains this
feature.
+2.1-
GMISS: Retrieve Data For UAM
Specify Data Selection Criteria
Enter selection criteria to define the data you want to retrieve.
If you cannot tab to a field, the value shown is the only one available.
You may enter "?" in a field (except dates) to see a list of values. If
you leave a field blank, the next screen will show the available values.
Model: ROM21
Domain: ROMNET1
Study: ROMNET
Scenario:
First Date to Retrieve: (mm/dd/yy)
Last Date to Retrieve: (mm/dd/yy)
(Press PF3/PF15 to return to the main menu.)
Figure 4-3. UAM Subsystem Menu for Data Selection Criteria
Scenario is the only selection you need to make to choose a ROM simulation, in this case.
Recall that we assumed your Regional modeling contact advised you to retrieve the ROM base case
simulation having scenario name "BASE85". In order to illustrate some features of GMISS menus, do
not enter that name. Instead, type "base88" in the scenario field, as shown in Figure 4-4, and press
the ENTER key. Figure 4-5 shows the result. The scenario field is highlighted and an error message
has appeared under the instructions. It says GMISS does not have a scenario named "BASE88".
25 Tutorial
-------
+2.1-
GMISS: Retrieve Data For UAM
Specify Data Selection Criteria
Enter selection criteria to define the data you want to retrieve.
If you cannot tab to a field, the value shown is the only one available.
You may enter "?" in a field (except dates) to see a list of values. If
you leave a field blank, the next screen will show the available values.
Model: ROM21
Domain: ROMNET1
Study: ROMNET
Scenario: base88
First Date to Retrieve: (mm/dd/yy)
Last Date to Retrieve: (mm/dd/yy)
(Press PF3/PF15 to return to the main menu.)
Figure 4-4. Entering a Scenario Name
+2.1-
GMISS: Retrieve Data For UAM
Specify Data Selection Criteria
Enter selection criteria to define the data you want to retrieve.
If you cannot tab to a field, the value shown is the only one available.
You may enter "?" in a field (except dates) to see a list of values. If
you leave a field blank, the next screen will show the available values.
That is not a valid SCENARIO.
Model: ROM21
Domain: ROMNET1
Study: ROMNET
Scenario: BASE88
First Date to Retrieve: (mm/dd/yy)
Last Date to Retrieve: (mm/dd/yy)
(Press PF3/PF15 to return to the main menu.)
Figure 4-5. Scenario Name Is Incorrect
Tutorial
26
-------
Notice that the instructions on the menu say you can get a list of the valid scenario names by
entering a question marie in the first position of the scenario field, (You could get lists of studies,
domains, and models in the same way, if there were more than one possible value for those fields.)
Type a question mark, as Figure 4-6 shows, and press the ENTER key. Notice that you did not have
to erase the rest of the scenario field, after the question mark.
+2.1-
GMISS: Retrieve Data For UAM
Specify Data Selection Criteria
Enter selection criteria to define the data you want to retrieve.
If you cannot tab to a field, the value shown is the only one available.
You may enter "?" in a field (except dates) to see a list of values. If
you leave a field blank, the next screen will show the available values.
That is not a valid SCENARIO.
Model: ROM21
Domain: ROMNET1
Study: ROMNET
Scenario: 7ASB88
First Date to Retrieve: (mm/dd/yy)
Last Date to Retrieve: (mm/dd/yy)
(Press PF3/PF15 to return to the main menu.)
Figure 4-6. Requesting a List of Scenario Names
Figure 4-7 is the "help" screen that appears after you press the ENTER key. The bottom half
of the screen lists the names of two scenarios and describes the conditions of the corresponding ROM
simulations. Note that BASE85, the scenario we want, is one of those listed. What if the scenario
you are looking for is not listed on the screen? You can scroll the list to see more scenarios. Press
the PF8 (or PF20) key of your terminal, and Figure 4-8 shows the result. Two more scenarios are
described. The scenario names are listed in alphabetical order. You can press the PF8 key again to
see more scenario names and descriptions, if you wish. Then scroll the list back to the BASE85
scenario by pressing the PF7 (or PF19) key as many times as you pressed the PF8 key, or by pressing
the PF10 (or PF22) key once. Your screen should look like Figure 4-7 again.
27 Tutorial
-------
+2.1.4
GMISS: Retrieve Data For UAM
Select Scenario
Move (tab) the cursor to the scenario you want to select and press ENTER.
Press PF8/PF20 to scroll the list forward, PF7/PF19 to scroll it backward.
Press PF3/PF15 to exit without selecting a scenario.
Scenario
BASE05
-Description-
ROMNET 2005 Baseline: Derived from the 1985 Base Case.
Includes projected emissions due to growth between 1985 and
2005 and the effects of existing control programs.
BASE85 ROMNET 1985 Base Case: Anthropogenic emissions derived from
1985 NAPAP inventories. Mobile emissions computed by
MOBILE4 and adjusted for temperature effects. Biogenic
emissions computed by BEIS. ROM 2.1 used for simulations.
Figure 4-7. First Page of the Scenario "Help" Screen
+2.1.4-
GMISS: Retrieve Data For UAM
Select Scenario
Move (tab) the cursor to the scenario you want to select and press ENTER.
Press PF8/PF20 to scroll the list forward, PF7/PF19 to scroll it backward.
Press PF3/PF15 to exit without selecting a scenario.
Scenario
CS01
CS02
-Description-
ROMNET Strategy 1: Maximum technology VOC controls applied
to the 2005 Baseline region-wide. NOx, CO, and Canadian
emissions are at the 2005 Baseline. MOBILE 3.9 used for
mobile emissions.
ROMNET Strategy 2: Maximum technology VOC controls applied
to the 2005 Baseline in the NE Corridor. VOC elsewhere and
NOx and CO emissions region-wide are at the 2005 Baseline.
MOBILE 3.9 used for mobile emissions.
Figure 4-8. Second Page of the Scenario "Help" Screen
Tutorial
28
-------
Select the BASE85 scenario, following the directions given on the menu. Press the TAB key
to position the cursor on "BASE85" and then press the ENTER key. Figure 4-9 shows the result.
You are back to the original selection criteria menu, and the name of the scenario you chose has been
filled in.
+2.1-
GMISS: Retrieve Data For UAM
Specify Data Selection Criteria
Enter selection criteria to define the data you want to retrieve.
If you cannot tab to a field, the value shown is the only one available.
You may enter "?" in a field (except dates) to see a list of values. If
you leave a field blank, the next screen will show the available values.
Model: ROM21
Domain: ROMNET1
Study: ROMNET
Scenario: BASE85
First Date to Retrieve: (mm/dd/yy)
Last Date to Retrieve: (mm/dd/yy)
(Press PF3/PF15 to return to the main menu.)
Figure 4-9. The Selected Scenario Name Is Filled In
4.3 Specifying Dates
Now you need to specify for which days of the BASE85 simulation to retrieve data. The
GMISS database contents report that you can obtain using option 1 of the main menu lists the dates
available for every scenario, but there is another way to find out. Notice the last line of the instruc-
tions on menu 2.1: If you leave afield blank, the next screen will show the available values. Try that;
leave the screen just as it appears in Figure 4-9, with nothing in the date fields, and press the ENTER
key. The "select from available data" menu (Figure 4-10) appears on your terminal screen.
29 Tutorial
-------
+2.2-
GMISS: Retrieve Data For UAM
Select From Available Data
The data available in GMISS that match your initial selection criteria are
listed below, one scenario and continuous date range per line. Enter "S"
to select one entry from the list. Change the date range to select fewer
days, if you wish. Press ENTER to accept the marked selection.
(PF8/PF20-scroll forward, PF7/PF19-scroll backward, PF3/PF15-prev. menu)
SELECT Dates Available
07/09/85 - 07/22/85
08/09/85 - 08/16/85
07/04/88 - 07/17/88
Scenario Study Domain Model
BASES5 ROMNET ROMNET1 ROM21
BASE85 ROMNET ROMNET1 ROM21
BASE85 ROMNET ROMNET1 ROM21
Figure 4-10. The Dates Available for Scenario BASE85
Although it is similar in function to the scenario help screen you used earlier (Figure 4-7), this
screen is different. It does not explain any of the fields, it simply lists the available values. It shows
the combinations of field values in the GMISS database that meet the criteria listed in menu 2.1
(Figure 4-9), rather than the allowed values for just one field. The lines under the column headings
show time periods when data are available for the BASE85 simulation you selected on the previous
menu. Each entry in the list (each line) represents a series of consecutive days, with no interruptions.
(If you had left the scenario field blank on the previous menu, this menu would have listed the dates
available for the BASE05 scenario, then for BASE85, and for the other scenarios in order.
Figure 5-10 shows how your terminal screen would have looked. You could have scrolled the list and
chosen both the scenario and the date range with this menu.)
Only the last entry in the list on menu 2.2 has dates in 1988, the year for which you want to
retrieve data. The menu instructions say to select an entry from the list by entering an S. Use the
TAB key to position the cursor on the select field beside the last entry of the list, and type s. (Do not
press the ENTER key yet) The instructions also say that you can change the date range of the entry.
Since this is just a "test run" to gain experience with the menus, let us retrieve data for a shorter time
Tutorial
30
-------
span. Try specifying just one day—July 4, 1988. Move the cursor over and change the second date
to July 4. Your screen should look like Figure 4-11.
+2.2-
GMISS: Retrieve Data For UAM
Select From Available Data
The data availa jle in GMISS that match your initial selection criteria are
listed below, o.ie scenario and continuous date range per line. Enter "S"
to select one entry from the list. Change the date range to select fewer
days, if you wish. Press ENTER to accept the marked selection.
(PF8/PF20=scroll forward, PF7/PF19=scroll backward, PF3/PF15=prev. menu)
SELECT Dates Available
07/09/85 - 07/22/85
08/09/85 - 08/16/85
s 07/04/88 - 07/04/88
Scenario Study Domain Model
BASE85 ROMNET ROMNET1 ROM21
BASE85 ROMNET ROMNET1 ROM21
BASE85 ROMNET ROMNET1 ROM21
Figure 4-11. Selecting and Altering a Date Range
Now press the ENTER key. An error message appears on the menu, and the dates are
highlighted in the line you selected. Figure 4-12 shows how the screen looks. The error message
explains what is wrong: 3 days is the shortest time period for which you can retrieve data. (Some of
the processing that the ROM-UAM Interface software performs requires data for at least 3 days.)
Change the highlighted end date to July 6, as shown in Figure 4-13, and press the ENTER key. The
3-day date range is accepted.
31
Tutorial
-------
+2.2-
GMISS: Retrieve Data For UAM
Select From Available Data
The data available in GMISS that match your initial selection criteria are
listed below, one scenario and continuous date range per line. Enter "S"
to select one entry from the list. Change the date range to select fewer
days, if you wish. Press ENTER to accept the marked selection.
(PF8/PF20-scroll forward, PF7/PF19-scroll backward, PF3/PF15=prev. menu)
The date range must be at least 3 days long.
SELECT Dates Available Scenario Study Domain Model
_ 07/09/85 - 07/22/85 BASE85 ROMNET
_ 08/09/85 - 08/16/85 BASE85 ROMNET
S 07/04/88 - 07/04/88 BASE85 ROMNET
ROMNET1 ROM21
ROMNET1 ROM21
ROMNET1 ROM21
Figure 4-12. An Error Message Indicates a Problem With the Date Range
+2.2-
GMISS: Retrieve Data For UAM
Select From Available Data
The data available in GMISS that match your initial selection criteria are
listed below, one scenario and continuous date range per line. Enter "S"
to select one entry from the list. Change the date range to select fewer
days, if you wish. Press ENTER to accept the marked selection.
(PF8/PF20=scroll forward, PF7/PF19=scroll backward, PF3/PF15=prev. menu)
The date range must be at least 3 days long.
SELECT Dates Available Scenario Study Domain Model
_ 07/09/85 - 07/22/85 BASE85 ROMNET
_ 08/09/85 - 08/16/85 BASE85 ROMNET
S 07/04/88 - 07/06/88 BASE85 ROMNET
ROMNET1 ROM21
ROMNET1 ROM21
ROMNET1 ROM21
Figure 4-13. Correcting the Date Problem
Tutorial
32
-------
4.4 Selecting Data Categories
The next menu to appear on your terminal asks you to choose which categories of data to
retrieve. Figure 4-14 shows how it looks. By default, all five data categories are selected (notice the
S's in the select fields) because all five are needed to use the ROM-UAM Interface software. Press
the ENTER key to accept the default selections.
+2.3
GMISS: Retrieve Data For UAM
Select Data Categories
Select data categories to retrieve by entering "S" or exclude categories
by erasing the "S", then press ENTER. Select at least one data category.
SELECT Category Description of Data
S CONC Hourly gridded concentrations of ROM chemical species
S RAWIN Hourly nongridded temperature vertical profiles
derived from rawinsonde upper-air data
S GEO Time-invariant gridded geographic features: land use,
terrain elevation, and surface roughness
S BIOGEN Hourly gridded biogenic emissions
S MET Hourly gridded surface meteorological conditions, cloud
cover, wind vectors, and layer boundary heights
(Press PF3/PF15 to return to the previous menu.)
Figure 4-14. The Default Selection Is to Retrieve All Data Categories
4.5 Specifying a Subdomain
Menu 2.4, shown in Figure 4-15, appears next. It asks you to define the ROM subdomain, the
geographic "window", of the ROM data to be retrieved. For this example, assume that your UAM
simulations will cover an area 200 kilometers on a side, approximately centered on Washington, DC,
and Baltimore, MD. You have fixed the position of the proposed UAM domain on a U.S. Geological
Survey map, and determined the Universal Transverse Mercator (UTM) coordinates of its boundaries.
Then you converted the UTM coordinates of the southwest and northeast comers of the proposed
33 Tutorial
-------
UAM domain to longitude-latitude coordinates, using the procedure your Regional modeling contact
suggested. Enter the longitude-latitude coordinates as degrees, minutes, and seconds in the fields of
menu 2.4, as shown in Figure 4-16. Notice that the coordinates of the proposed UAM domain are
within the boundaries of the ROM domain of the simulation (ROMNET1), which are given on the right
side of the menu.
+2.4 +
GMISS: Retrieve Data For UAM
Specify Subdomaln Coordinates
Define the geographic extent of the ROM data you are retrieving to match
the size and location of the area you will model with the UAM. Supply
coordinates for opposite corners of your UAM domain as degrees, minutes,
and seconds of longitude and latitude, then press ENTER. The range of
coordinates allowed in the ROM domain are listed below. GMISS enlarges
the subdomain you define by about two ROM grid cells in each direction.
Coordinates of UAM Domain ROMNET1 Domain
(X) (Y) (X) (Y)
Longitude Latitude Longitude Latitude
(ddd mm ss) (dd mm ss) (ddd mm ss) (dd mm ss)
SW Corner: 84 37 30 36 35 00
NE Corner: 69 22 30 44 45 00
(Press PF3/PF15 to return to the previous menu.)
Figure 4-15. Subdomain Coordinates Are Opposite Corners of a Rectangle
After you press the ENTER key, a message appears on menu 2.4, and the longitude coordi-
nates are highlighted. Figure 4-17 shows the screen. If you entered the coordinates as shown in
Figure 4-16, the east and west coordinates of the subdomain were swapped. The menu program has
exchanged the longitude coordinates and is asking for confirmation. Notice that the minutes and
seconds fields left blank in Figure 4-16 have been converted to zeros, and that all the values entered in
the left side of fields have been shifted to the right side. The exchanged coordinates now correctly
represent the proposed UAM domain (and the ROM subdomain), so press the ENTER key to accept
them.
Tutorial 34
-------
+2.4-
GMISS: Retrieve Data For UAM
Specify Subdomain Coordinates
Define the geographic extent of the ROM data you are retrieving to match
the size and location of the area you will model with the UAM. Supply
coordinates for opposite corners of your UAM domain as degrees, minutes,
and seconds of longitude and latitude, then press ENTER. The range of
coordinates allowed in the ROM domain are listed below. GMISS enlarges
the subdomain you define by about two ROM grid cells in each direction.
SW Corner:
NE Corner:
Coordinates
(X)
Longitude
(ddd mm ss)
75_ 52 40
78
of UAM Domain
(Y)
Latitude
(dd mm ss)
38 5 16
39 55 43
ROMNET1 Domain
(X)
Longitude
(ddd mm ss)
84 37 30
69 22 30
(Y)
Latitude
(dd mm ss)
36 35 00
44 45 00
(Press PF3/PF15 to return to the previous menu.)
Figure 4-16. Specifying Coordinates of a UAM Domain (ROM Subdomain)
+2.4-
GMISS: Retrieve Data For UAM
Specify Subdomain Coordinates
Define the geographic extent of the ROM data you are retrieving to match
the size and location of the area you will model with the UAM. Supply
coordinates for opposite corners of your UAM domain as degrees, minutes,
and seconds of longitude and latitude, then press ENTER. The range of
coordinates allowed in the ROM domain are listed below. GMISS enlarges
the subdomain you define by about two ROM grid cells in each direction.
Coordinates of SW and NE corners exchanged.
Coordinates of UAM Domain
SW Corner:
NE Corner:
(X)
Longitude
(ddd mm ss)
78 00 00
75 52 40
(Y)
Latitude
(dd mm ss)
38 05 16
39 55 43
Press ENTER to accept.
ROMNET1 Domain
(X) (Y)
Longitude Latitude
(ddd mm ss) (dd mm ss)
84 37 30 36 35 00
69 22 30 44 45 00
(Press PF3/PF15 to return to the previous menu.)
Figure 4-17. A Message Notes the Exchange of Coordinates to Correct the Error
35
Tutorial
-------
4.6 Selecting Rawin Stations
The next menu to appear asks you to choose the rawin stations for which GMISS will retrieve
data. Figure 4-18 shows the screen, which has a list of the available stations. The list includes the
station-id, the station elevation and coordinates, and the city in which the station is located. The
coordinates of the ROM subdomain defined on the previous menu are listed here for reference. Note
that the coordinates are not the same as the ones you entered, however. The menu program has added
a border of about 2 ROM grid cells around the subdomain you defined, enlarging it by about 30
minutes of longitude east and west, and by about 15 minutes of latitude north and south. The
coordinates of the enlarged subdomain are shown on the rawin selection menu.
You should to get data for two or more rawin stations, but none of the stations listed on the
screen is within or near the subdomain. (The longitude and latitude columns give the locations of the
stations.) Follow the menu instructions and press the PF8 key of your terminal to scroll the list.
Select two rawin stations in Virginia that are within the subdomain (or very nearly so), and press the
ENTER key. Figure 4-19 shows the s's entered to select them.
4.7 Retrieval File Names
Figure 4-20 shows the next menu to appear. It lists the default names of the retrieval files that
will be created. Since you elected to retrieve all five categories of data, there are file names for all of
them. Had you decided not to retrieve, say, the MET category, the menu would have blanks instead
of the seven file names for that category. Press the ENTER key to accept the default retrieval file
names. Had you decided to change the file names, you would have typed over the default names,
being careful to specify valid IBM dataset names.
Tutorial 36
-------
+2.5-
GMISS: Retrieve Data for UAM
Select Rawin Stations
Type "S" beside each rawin station you wish to select, then press ENTER.
Press PF3/PF15 to return to the previous menu without selecting stations,
Scroll the list forward with PF8/PF20, backward with PF7/PF19.
The longitude and latitude coordinates (ddd mm ss) of the subdomain
to be retrieved are: SW corner lon= 78 30 00 lat= 37 50 00
NE corner lon= 75 30 00 lat= 40 20 00
Station Elevation Longitude Latitude
SELECT ID (meters) (ddd mm) (dd mm) Station Description
03860
03879
03881
13601
13723
13840
13873
13880
255
167
139
6
276
250
244
14
82
88
87
64
79
84
83
80
33
57
15
41
57
03
19
02
38
38
32
32
36
39
33
32
22
38
54
22
05
49
57
54
Huntington, WV
Salem, IL
Centreville, AL
St. George, Bermuda
Greensboro/High Pt.,
Wright Patterson AFB,
Athens, GA
Charleston, SC
NC
OH
Figure 4-18. First Page of Rawin Selection Menu
+2.5-
GMISS: Retrieve Data for UAM
Select Rawin Stations
Type "S" beside each rawin station you wish to select, then press ENTER.
Press PF3/PF15 to return to the previous menu without selecting stations,
Scroll the list forward with PF8/PF20, backward with PF7/PF19.
The longitude and latitude coordinates (ddd mm ss) of the subdomain
to be retrieved are: SW corner lon= 78 30 00 lat= 37 50 00
NE corner lon= 75 30 00 lat= 40 20 00
Station Elevation Longitude Latitude
SELECT ID (meters) (ddd mm) (dd mm) Station Description
14826
14842
148'47
14898
54719
93729
a 93734
8 93739
234
205
220
211
170
7
85
4
83
89
84
88
75
75
77
75
45
41
21
08
58
33
28
29
42
40
46
44
46
35
38
37
58
40
28
29
23
16
59
51
Flint, MI
Peoria, IL
Sault Ste. Marie
Green Bay, WI
Maniwaki, Quebec
, MI
Cape Hatteras, NC
Sterling, VA
Wallops Island,
VA
Figure 4-19. Selecting Rawin Stations After Scrolling the List
37
Tutorial
-------
+2.6-
GMISS: Retrieve Data For UAM
Specify Retrieval File Names
You may specify your own retrieval file names by typing over the default
names listed below. Press ENTER to accept your choices for file names.
Category Description
CONG ROM species cone.:
RAWIN Vert air profiles:
GEO Surface roughness:
Landuse fractions:
Terrain elevation:
BIOGEN Biogenic emiss'ns:
MET Surface met'ology:
Layer 2 wind fids:
Layer 1 wind fids:
Cloudiness fractn:
Layer 1-2 intface:
Layer 2-3 intface:
Layer 1 water vap:
(Press PF3/PF15
File Name
JLUX1HK.D910117.
JLUX1HK.D910117.
JLUX1HK.D910117.
JLUX1HK.D910117.
JLUX1HK.D910117.
JLUX1HK.D910117.
JLUX1HK.D910117.
JLUX1HK.D910117.
JLUX1HK.D910117.
JLUX1HK.D910117.
JLUX1HK.D910117.
JLUX1HK.D910117.
JLUX1HK.D910117.
to return to the
T123527.ROM21.ROMNET1.U
T123527.PF102.ROMNET1.U
T123527.PF108.ROMNET1.U
T123527.PF118.ROMNET1.U
T123527.PF119.ROMNET1.U
T123527.PF144.ROMNET1.U
T123527.PF103.ROMNET1.U
T123527.PF114.ROMNET1.U
T123527.PF115.ROMNET1.U
T123527.PF117.ROMNET1.U
T123527.MF165.ROMNET1.U
T123527.MF166.ROMNET1.U
T123527.MF174.ROMNET1.U
previous menu.)
Figure 4-20. Default Retrieval File Names
4.8 Batch Job Parameters
The next menu, shown in Figure 4-21, solicits batch job parameters. These items are used to
construct the control statements (JCL) for the batch job that will extract the data you have requested
from the GMISS database and create the retrieval files. Most of the fields have default values. You
could change them if you want to, but you must choose valid values or the batch job probably will not
run. (Section 5.10 in the next chapter explains what the fields mean and describes valid values.) You
must fill in values for two fields that don't have defaults, FIMAS ID and NCC bin. For FIMAS ID (a
type of accounting code required by the EPA computer center management), enter the code supplied
by your Regional modeling contact. For NCC bin, enter the letter M followed by your EPA computer
system user-id. This code "tells" the computer center to mail printed output to you. rigure 4-22
shows terminal screen at this point, for a person with user-id "JLU".
Tutorial
38
-------
+2.7
GMISS: Retrieve Data For UAM
Specify Batch Job Parameters
Enter the information needed to submit a batch job, then press ENTER.
Job Name: JLU UAMR
Job Time: 5,0 (Min,Sec)
Job Priority: 2
Account: X1HK
FIMAS ID:
NCC Bin:
Destination: LOCAL
NCC Form:
(Press PF3/PF15 to return to the previous menu without submitting a job.)
Figure 4-21. Default Batch Job Parameters
+2.7
GMISS: Retrieve Data For UAM
Specify Batch Job Parameters
Enter the information needed to submit a batch job, then press ENTER.
Job Name: JLU UAMR
Job Time: 5,0 (Min,Sec)
Job Priority: 2
Account: X1HK
FIMAS ID: aqmap
NCC Bin: mjlu
Destination: LOCAL
NCC Form:
(Press PF3/PF15 to return to the previous menu without submitting a job.)
Figure 4-22. Supplying the Missing Batch Job Parameters
39 Tutorial
-------
4.9 Batch Job Submission
When you press the ENTER key, the menu program submits a batch job using the parameters
and the data selection criteria you entered during the session. The computer system issues a TSO
message to confirm that the batch job has been submitted and to list the job name and job number.
Figure 4-23 shows how the terminal screen looks when the message appears. The three asterisks
under the message mean that the computer system is waiting for you to press the ENTER key in order
to continue. You should write down the job name and number in case you need to know them later to
check the status of the batch job.
IKJ56250I JOB JLUUAMR(JOB24290) SUBMITTED
***
Figure 4-23. TSO Message Confirming Batch Job Submission
When you press ENTER, the GMISS main menu appears again, as shown in Figure 4-24.
Notice that it has retained the 2 you entered t-dier as the choice for What do you want to do? If you
wanted to start another retrieval request, you could simply press ENTER.
Tutorial
-------
Gridded Model Information Support System (GMISS)
Main Menu
What do you want to do? 2
I - List Database Contents
2 - Retrieve Data for Urban Airshed Model (UAM)
(Press PF3/PF15 to exit from GMISS.)
Figure 4-24. Main Menu Returns When Retrieval Request Is Completed
4.10 Exiting From GMISS
One retrieval job is enough for this example, and it is time to get out of the GMISS menus.
Following the instructions displayed on the GMISS main menu (Figure 4-24), press the PF3 (or PF15)
key to exit. After a brief pause, the screen clears, and TSO gives its "READY" prompt as shown in
Figure 4-25.
READY
Figure 4-25. The TSO "READY" Prompt That Appears After Exiting From GMISS
41 Tutorial
-------
4.11 Checking the Data Extraction
The next day, you should receive the printed output generated by the batch job that extracted
the data you requested. At the end of the printout, after the JCL listing and accounting information, is
a short report that lists the data selection criteria you specified and summarizes the "progress" of the
data extraction. Figure 4-26 shows the report. It indicates that the batch job extracted all the data you
selected and created retrieval files.
The first line of the report states when the batch job began executing. Next is a listing of all
the specifications you entered on the UAM Subsystem menus, plus some additional information. For
example, the report gives the date range of the retrieved data in the Gregorian format (04JUL88) you
used in the menu, and also in the Julian format (88186) used in the ROM-UAM Interface. The
following line gives the size of the ROM subdomain in terms of ROM grid cells, and lists the row and
column numbers in the overall ROM domain. The list of retrieval file names ends the first part of the
report, the summary of data retrieval specifications. The rest is a "progress report". When the batch
job finishes creating each of the retrieval files, it writes a line in the report that identifies the file and
states the date and time. (If you had re-used existing retrieval files to hold the retrieved data, the
report would have an additional line for each re-used file, noting that the data retrieved in this job
replaced the previous contents of the file.) The last line of the report tells when the batch job finished
executing.
By examining this report, you can verify that the batch job finished successfully. If the batch
job had not completed the data extraction due to a problem, some of the "progress" messages would
be missing. If Finished GMISS UAM Subsystem data retrieval... is not the last message in the report,
the batch job did not complete all the data retrieval processing. In that case you should look carefully
at the JCL listing and IBM system messages to determine what went wrong. Your Regional modeling
contact and the user support department of the EPA National Computer Center can help to resolve this
kind of problem.
42
Tutorial
-------
Began GMISE UAM Subsystem data retrieval at 12:37:23 on THURSDAY, JANUARY 17, 1991.
Summary of retrieval specifications:
Model: ROM21 Domain: ROMNET1 Study: ROMNET Scenario: BASE85
Dates: 04JUL68-06JUL88 (88186-88188)
Data Types: CONC RAW IN GEO BIOGEN MET
Subdomain Size: 12 columns (27-38) by 15 rows (10-24)
Subdomain Location:
Southwest Corner
Northeast Corner
Rawin Stations: ID
1: 93734
2: 93739
Retrieval Files:
CONC CONC
RAWIN PF102
GEO PF108
GEO PF118
GEO PF119
BIOGEN PF144
MET PF103
MET PF114
MET PF115
MET PF117
MET MF165
MET MF166
MET MF174
Longitude
78 30 00
75 30 00
Longitude
77 28 00
75 29 00
Latitude
37 50 00
40 20 00
Latitude
38 59 00
37 51 00
Elevation
85 m
4 m
JLUX1HK.D910117.T123527.ROM21.ROMNET1.U
JLUX1HK.D910117.T123527.PF102.ROMNET1.U
JLUX1HK.D910117.T123527.PF108.ROMNET1.U
JLUX1HK.D910117.T123527.PF118.ROMNET1.U
JLUX1HK.D910117.T123527.PF119.ROMNET1.U
JLUX1HK.D910117.T123527.PF144.ROMNET1.U
JLUXlHK.D910117.il23527.PF103.ROMNET1.U
JLUX1HK.D910117.T123527.PF114.ROMNET1.U
JLUX1HK.D910117.T123527.PF115.ROMNET1.U
JLUX1HK.D910117.T123527.PF117.ROMNET1.U
JLUX1HK.D910117.T123527.MF165.ROMNET1.U
JLUX1HK.D910117.T123527.MF166.ROMNET1.U
JLUX1HK.D910117.T123527.MF174.ROMNET1.U
Retrieval of CONC data completed at 12:41:29 on 17JAN91.
Retrieval of RAWIN data, file PF102, completed at 12:42:42 on 17JAN91.
Retrieval of GEO data, file PF108, completed at 12:42:45 on 17JAN91.
Retrieval of GEO data, file PF118, completed at 12:42:49 on 17JAN91.
Retrieval of GEO data, file PF119, completed at 12:42:52 on 17JAN91.
Retrieval of BIOGEN data, file PF144, completed at 12:43:00 on 17JAN91.
Retrieval of MET data, file PF103, completed at 12:43:05 on 17JAN91.
Retrieval of MET data, file PF114, completed at 12:43:11 on 17JAN91.
Retrieval of MET data, file PF115, completed at 12:43:16 on 17JAN91.
Retrieval of MET data, file PF117, completed at 12:43:21 on 17JAN91.
Retrieval of MET data, file MF165, completed at 12:43:25 on 17JAN91.
Retrieval of MET data, file MF166, completed at 12:43:30 on 17JAN91.
Retrieval of MET data, file MF174, completed at 12:43:35 on 17JAN91.
Finished GMISS UAM Subsystem data retrieval at 12:43:35 on THURSDAY, JANUARY 17, 1991.
Figure 4-26. Summary Report of Batch Data Retrieval Processing
43
Tutorial
-------
5. MENU REFERENCE
This chapter describes the UAM Subsystem menus. It begins with an outline of the menu structure,
illustrating how menus are related to each other and the order in which they occur as you use the
UAM Subsystem. The rest of the chapter gives detailed descriptions of the menus. Each description
explains a menu's purpose, tells how to use it, and lists error messages and tells what causes them.
5.1 Menu Outline
The UAM Subsystem menus allow you to specify what information you want to retrieve from
GMISS. Figure 5-1 illustrates how the menus are related to each other and the order in which they
appear on your terminal screen.
The GMISS main menu is the starting point for any type of information retrieval. Two paths
branch out from the main menu, corresponding to the two choices available: generate a database
contents report, and retrieve data for the UAM. The first choice has a very simple menu structure.
There is only one menu, with which you specify items needed to submit a batch job. When the job
has been submitted, control returns to the main menu.
The second main menu choice, retrieve data for the UAM, has more menus and more options.
The contents of the GMISS database and the specifications you enter affect what menus appear on
your terminal. In Figure 5-1, the shaded boxes designate optional or conditional menus that appear
only under some circumstances. The data retrieval function always begins with menu 2.1, with which
you can enter data selection criteria. If you request a list of values that you may enter as a selection
criterion, optional menu 2.1.1, 2.1.2, 2.1.3, or 2.1.4 appears and provides the information. If you enter
partial selection criteria in menu 2.1—by leaving one or more fields blank—or if your criteria select
more than one time period of a particular ROM simulation, then menu 2.2 appears with a list of
available data that meet the criteria. If your menu 2.1 criteria uniquely define the data to retrieve,
menu 2.2 is not necessary and does not appear. Similarly, menu 2.5 is not necessary if you choose
not to retrieve the RAWIN data category.
44
Reference
-------
The rest of this chapter describes in detail each of the data retrieval menus. The single menu
for generating a report of database contents is very similar to the last menu for data retrieval, and both
of them are described in Section 5.10.
GMISS UAM Subsystem Menus
Option 1
Database Contents
1.1
Specify Batch Job Farms.
I
Submit Batch Job
GMISS Main Menu
Option 2 1 Retrieve Data
1
2.1
Specify Data Selection Criteria
I
22
Select from Available Data
I
2.3
Select Data Categories
2.4
Specify Subdomain Coords.
2.5
Select Rawin Stations
2.6
Specify Retrieval File Names
2.7
Specify Batch Job Farms.
I
Submit Batch Job
2.1.1 Select Model
2.1.2 Select Domain
2.1.3 Select Study
2.1.4 Select Scenario
Shaded boxes
indicate menus
that are optional
or conditional
Figure 5-1. UAM Subsystem Menu Structure
45
Reference
-------
5.2 Main Menu
The GMISS main menu (Figure 5-2) allows you to choose which function to execute. The
first function, list database contents, produces a printed report that lists the data available for retrieval
with the UAM Subsystem. Figure 5-3 shows part of the report. The second function on the main
menu, retrieve data for UAM, extracts data from the GMISS database and creates retrieval files as
described in Chapter 2.
Instructions
To perform a function listed on the main menu, enter the number of the function in the blank
after the question What do you want to do? and press the ENTER key of your terminal. The available
functions and associated numbers are listed under the question.
To exit from the main menu without performing a function and return to TSO, press the PF3
or PF15 key of your terminal.
Error Messages
That is not a valid choice.
The value you entered is not one of the choices listed on the main menu. Enter one of the
available choices and press the ENTER key, or exit from the menu by pressing the PF3 or
PF15 key.
Reference
-------
Gridded Model Information Support System (GMISS)
Main Menu
What do you want to do? _
1 - List Database Contents
2 - Retrieve Data for Urban Airshed Model (UAM)
(Press PF3/PF15 to exit from GMISS.)
Figure 5-2. GMISS Main Menu
11/02/90 GMISS: UAM Subsystem Database Contents Report
Model: ROM21 Regional Oxidant Model, version 2.1
Domain: ROMNET1 Northeast region for oxidant studies (primarily ROM 2.1)
Study: ROMNET Regional Oxidant Modeling for NorthEast Transport
Page 1
Scenario Description
BASE05 ROMNET 2005 Baseline: Derived from the 1985 Base Case.
Includes projected emissions due to growth between 1985 and
2005 and the effects of existing control programs.
Dates Available
06/10/83 - 06/20/83
07/04/88 - 07/17/88
BASE85 ROMNET 1985 Base Case: Anthropogenic emissions derived from
1985 NAPAP inventories. Mobile emissions computed by
MOBILE4 and adjusted for temperature effects. Biogenic
emissions computed by BEIS. ROM 2.1 used for simulations.
07/09/85 - 07/22/85
08/09/85 - 08/16/85
07/04/88 - 07/17/88
CS01 ROMNET Strategy 1: Maximum technology VOC controls applied
to the 2005 Baseline region-wide. NOx, CO, and Canadian
emissions are at the 2005 Baseline. MOBILE 3.9 used for
mobile emissions.
07/04/88 - 07/17/88
CS02 ROMNET Strategy 2: Maximum technology VOC controls applied
to the 2005 Baseline in the NE Corridor. VOC elsewhere and
NOx and CO emissions region-wide are at the 2005 Baseline.
MOBILE 3.9 used for mobile emissions.
07/04/88 - 07/17/88
Figure 5-3. UAM Subsystem Database Contents Report
47
Reference
-------
5.3 Menu 2.1 - Specify Data Selection Criteria
UAM Subsystem menu 2.1, Figure 5-4, is the primary menu for specifying data retrieval
selection criteria. The menu has six fields:
Model Version of the ROM used for simulation of air pollution
Domain Geographic area of the ROM simulation
Study Group of ROM simulations having the same purpose, funding, etc.
Scenario A specific ROM simulation, designed to show a particular effect
First date First date in the ROM simulation to retrieve data for
Last date Last date in the ROM simulation to retrieve data for
The values entered in these fields must match values of ROM data in the GMISS database. If all the
available data have a single value for one of these fields, that value is automatically filled in by the
menu program and you cannot alter the value. Otherwise, you can enter a new value or change an
existing value. For example, suppose all the available data are derived from simulations using ROM
version 2.1 in the ROMNET1 domain. The model field would contain "ROM21" and the domain field
would contain "ROMNET1". Both fields would be protected and you would not be able to alter those
values. Figure 5-5 shows how menu 2.1 would look under these conditions.
You have the option of leaving blank any of the unprotected fields of menu 2.1. Leaving a
field blank means "Don't apply any selection criteria with respect to this field. On the next menu,
show me all the possible values of this field for data that match the selection criteria in other fields."
You do not have to precede a blank field with filled-in fields. For example, if you specified a value
for scenario but left the model, domain, and study fields blank, the menu program would find all the
combinations of model, domain, and study in the database that have the scenario you entered.
Entering a value for first date but leaving last date blank means "find all available dates on or after
first date"; entering a value for last date but leaving first date blank means "find all available dates on
or before last date".
Reference
-------
+2.1-
GMISS: Retrieve Data For UAM
Specify Data Selection Criteria
Enter selection criteria to define the data you want to retrieve.
If you cannot tab to a field, the value shown is the only one available.
You may enter "?" in a field (except dates) to see a list of values. If
you leave a field blank, the next screen will show the available values.
Model:
Domain:
Study:
Scenario:
First Date to Retrieve: (mm/dd/yy)
Last Date to Retrieve: (mm/dd/yy)
(Press PF3/PF15 to return to the main menu.)
Figure 5-4. Menu 2.1 - Specify Data Selection Criteria
+2.1-
GMISS: Retrieve Data For UAM
Specify Data Selection Criteria
Enter selection criteria to define the data you want to retrieve.
If you cannot tab to a field, the value shown is the only one available.
You may enter "?" in a field (except dates) to see a list of values. If
you leave a field blank, the next screen will show the available values.
Model: ROM21
Domain: ROMNET1
Study:
Scenario:
First Date to Retrieve: (mm/dd/yy)
Last Date to Retrieve: (mm/dd/yy)
(Press PF3/PF15 to return to the main menu.)
Figure 5-5. Appearance of Menu 2.1 When Some Fields Have Only One Possible Value
49
Reference
-------
If you do not know what value to enter in the model, domain, study, or scenario field, you can
see a list of valid values by typing a question mark in the first position of the field and pressing the
ENTER key. This invokes one of the "help" screens, described in the next section, that lists the values
you can enter in menu 2.1 and gives a brief explanation of what each value means.
The values you enter on menu 2.1 are saved. Each time you use the UAM Subsystem data
retrieval function, the initial values of menu 2.1 fields are the values you specified the previous time.
Instructions
Enter values in unprotected fields to define the ROM simulation and date range you want to
retrieve. (An unprotected field is one at which the cursor stops when you use the terminal's TAB key.
The cursor skips over protected fields.) If you wish, you may leave any or all unprotected fields
blank, or erase their initial values. In that case, menu 2.2 will show you the combinations of model,
domain, study, scenario, and date values in the GMISS database that match the menu 2.1 fields that do
have values.
To see a list of the available values for an unprotected model, domain, study, or scenario field,
type a question mark in the first position of the field (you need not erase any value already in the
field), and press the ENTER key. Another menu will appear that lists and describes the values you
can specify, and lets you choose one. The next section of this chapter describes the list-of-values
menus for these four fields.
If you specify dates, they must define a time period of at least 3 days. Menu 2.1 does not
provide a way to list the available dates, since menu 2.2 does that. You have to know what dates are
available to enter valid selection criteria. (A database contents report, option 1 of the GMISS main
menu, lists the dates available for each scenario.) You can specify both the beginning and end of the
date range, only the beginning, only the end, or not specify a date range at all.
To return to the main menu without specifying selection criteria, press the PF3 or PF15 key of
your terminal.
Reference 50
-------
Error Messages
That is not a valid MODEL.
That is not a valid DOMAIN.
That is not a valid STUDY.
That is not a valid SCENARIO.
The value you entered for the field named in the message does not match any of the values
available in the GMISS database. To correct the error, enter a different value, enter a question
mark and pick a valid value from the list displayed by menu 2.1 jc, or erase the field and
choose one of the values that appears in menu 2.2 after you press the ENTER key.
Invalid combination of MODEL, DOMAIN, STUDY, and SCENARIO values.
Although the four fields individually have valid values, the combination of values is not
correct. That is, no data in the GMISS database have the combination of values you specified.
Only non-blank fields are significant in this comparison. Enter a different value, enter a
question mark to get a list of available values, or erase a value. The value you entered for
scenario is most likely to cause this error. You might try erasing that field and choosing a
scenario from the list displayed by menu 2.2.
Invalid date. Use the format mm/dd/yy.
The value you entered for first date or last date is not a valid date. You must specify all
three parts of the date as numbers in the order month, day, and year. You may separate the
three parts with slashes (/), dashes (-), or spaces. Month can be 1 through 12. Day can be 1
through the number of days in the month. Year values of 50 through 99 represent the years
1950 through 1999, and values of 0 through 49 represent the years 2000 through 2049. You
do not have to use a leading zero in a value less than ten. Leading and trailing blanks in the
values are ignored.
First date must precede last date (by at least 2 days).
The value of first date is later than the value of last date. Change the dates so that first date
precedes last date, or erase one of the values. If you specify both dates, they must define a
time period of at least 3 days.
^ Reference
-------
The date range must be at least 3 days long.
First date and last date must define a time period of at least 3 days. (The ROM-UAM
Interface software requires at least 3 days of data.) Change one or both date fields so thai first
date precedes last date by 2 days or more.
The available dates are mmlddlyy through mmlddlyy.
The date you specified for first date or last date does not fall within the valid range of dates,
listed in the error message, for any ROM simulation selected by the model, domain, study, and
scenario values. Change the faulty date to be within the time period listed in the error
message. Be sure the new date range is at least 3 days long.
Press PF3/15 to return to the previous menu
This message occurs only if some unusual condition prevents the menu from working as it
should. Some information about the error condition may appear on the menu where the
second title line normally is. Record the information, press the PF3 or PF15 key of your
terminal until you have exited from GMISS, and contact the EPA office in charge of GMISS,
listed in the For More Information section of Chapter 1.
5.4 Menus 2.1.1 Through 2.1.4 - Lists of Values
Four similar menus, 2.1.1 through 2.1.4, provide lists of valid values for the model, domain,
study, and scenario fields on menu 2.1. A list-of-values menu appears when you enter a question
mark in the corresponding field of menu 2.1. The four menus, shown in Figure 5-6 through
Figure 5-9, have essentially the same format. The bottom half of the screen shows the list of values.
The name or code that you could enter on menu 2.1 is at the left side of the screen. Beside the name
is a description of what it means. If the list has more entries than will fit on the screen, you can scroll
the list to see all the values. The Using Menus section of Chapter 3 describes scrolling and tells what
terminal keys to use.
52
Reference
-------
The values listed by these four menus take into account the values entered in other fields on
menu 2.1. For example, if there are values for model and domain, the list-of-values menu for study
shows only the study names valid for that model and domain.
The four list-of-values menus do more than just list the valid values; they also let you select a
value from the list The value you select appears in the appropriate field of menu 2.1, so you do not
have to remember a value and enter it yourself.
Instructions
Examine the list of values displayed, scrolling the list if necessary, until you find the value
you want to select. Press the TAB key of your terminal until the cursor is at that value, then press the
ENTER key. This selects the value and returns you to menu 2.1, with the selected value entered in
the appropriate field.
If you do not want to select a value from the list, press the PF3 or PF15 key. Menu 2.1
reappears, and the field corresponding to the list-of-values menu has the same value it did before you
invoked the list-of-values menu.
Error Messages
Press PF3/15 to return to the previous menu
This message occurs only if some unusual condition prevents the menu from working as it
should. Some information about the error condition may appear on the menu where the
second title line normally is. Record the information, press the PF3 or PF15 key of your
terminal until you have exited from GMISS, and contact the EPA office in charge of GMISS,
listed in the For More Information section of Chapter 1.
53 Reference
-------
+2.1.1-
GMISS: Retrieve Data for UAM
Select Model
Move (tab) the cursor to the model you want to select and press ENTER.
Press PF8/PF20 to scroll the list forward, PF7/PF19 to scroll it backward.
Press PF3/PF15 to exit without selecting a model.
Model
ROM20
ROM21
ROM22
-Description-
Regional Oxidant Model, version 2.0
Regional Oxidant Model, version 2.1
Regional Oxidant Model, version 2.2
Figure 5-6. Menu 2.1.1 - Select Model
+2.1.2-
GMISS: Retrieve Data for UAM
Select Domain
Move (tab) the cursor to the domain you want to select and press ENTER.
Press PF8/PF20 to scroll the list forward, PF7/PF19 to scroll" it backward.
Press PF3/PF15 to exit without selecting a domain.
Domain
MIDROXA
NEROS1
NEROXA
ROMNET1
-Description-
Midwest region for oxidant studies
76 Cols 71 Rows SW corner Ion: 97.00
lat: 35.00 degrees
Northeast region for ozone studies (primarily ROM 2.0)
60 Cols 42 Rows SW corner Ion: 84.00 lat: 38.00 degrees
Northeast region for oxidant studies
68 Cols 52 Rows SW corner Ion: 85.00
lat: 36.33 degrees
Northeast region for oxidant studies (primarily ROM 2.1)
64 Cols 52 Rows SW corner Ion: 85.00 lat: 36.33 degrees
Figure 5-7. Menu 2.1.2 - Select Domain
Reference
54
-------
+2.1.3
GMISS: Retrieve Data for UAM
Select Study
Move (tab) the cursor to the study you want to select and press ENTER.
Press PF8/PF20 to scroll the list forward, PF7/PF19 to scroll it backward.
Press PF3/PF15 to exit without selecting a study.
Study Description
ROMNET Regional Oxidant Modeling of NorthEast Transport
Figure 5-8. Menu 2.1.3 - Select Study
+2.1.4-
GMISS: Retrieve Data for UAM
Select Scenario
Move (tab) the cursor to the scenario you want to select and press ENTER.
Press PF8/PF20 to scroll the list forward, PF7/PF19 to scroll it backward.
Press PF3/PF15 to exit without selecting a scenario.
Scenario Description-
BASE05 ROMNET 2005 Baseline: Derived from the 1985 Base Case.
Includes projected emissions due to growth between 1985 and
2005 and the effects of existing control programs.
BASE85 ROMNET 1985 Base Case: Anthropogenic emissions derived from
1985 NAPAP inventories. Mobile emissions computed by
MOBILE4 and adjusted for temperature effects. Biogenic
emissions computed by BEIS. ROM 2.1 used for simulations.
Figure 5-9. Menu 2.1.4 - Select Scenario
55 Reference
-------
5.5 Menu 2.2 - Select From Available Data
Menu 2.2 is a conditional menu; it appears if any field of menu 2.1 is left blank. The purpose
of this menu is to show you which ROM simulations and date ranges meet the selection criteria you
specified on menu 2.1, and to let you choose one of them. In addition, you may alter the date range.
Figure 5-10 shows the format of menu 2.2. The bottom portion of the screen lists available
ROM simulations. Each line of the list is a contiguous series of days of a simulation. The simula-
tions are listed in alphabetical order by model, domain, study, and scenario names. If a particular
simulation was run for several different time periods, there is a line in the list for each one;
Figure 5-10 illustrates this for the BASE05 and BASE85 scenarios. If the list has more entries than
will fit on the screen, you can scroll the list to see all the lines. The Using Menus section of Chapter
3 describes scrolling and tells what terminal keys to use.
+2.2-
GMISS: Retrieve Data for UAM
Select From Available Data
The data available in GMISS that match your initial selection criteria are
listed below, one scenario and continuous date range per line. Enter "S"
to select one entry from the list. Change the date range to select fewer
days, if you wish. Press ENTER to accept the marked selection.
(PF8/PF20=scroll forward, PF7/PF19=scroll backward, PF3/PF15=prev. menu)
SELECT Dates Available
Scenario Study
Domain
Model
—
06/10/83
07/04/88
07/09/85
08/09/85
07/04/88
07/04/88
07/04/88
07/04/88
07/04/88
07/04/88
- 06/20/83
- 07/17/88
- 07/22/85
- 08/16/85
- 07/17/88
- 07/17/88
- 07/17/88
- 07/17/88
- 07/17/88
- 07/17/88
BASE 05
BASE 05
BASE 8 5
BASE 8 5
BASE 8 5
CS01
CS02
CS03
CS05
CS06
ROMNET
ROMNET
ROMNET
ROMNET
ROMNET
ROMNET
ROMNET
ROMNET
ROMNET
ROMNET
ROMNET 1
ROMNET 1
ROMNET 1
ROMNET 1
ROMNET 1
ROMNET 1
ROMNET 1
ROMNET 1
ROMNET 1
ROMNET 1
ROM21
ROM21
ROM21
ROM21
ROM21
ROM21
ROM21
ROM21
ROM21
ROM21
Figure 5-10. Menu 2.2 - Select From Available Data
There are three fields in each line of the list of ROM simulations that you can change. Use
the first one, labeled "SELECT", to select an entry from the list. Use the next two fields, labeled
Reference
56
-------
"Dates Available", to specify the first and last dates for which you want to retrieve data. For each
entry in the list of ROM simulations, the beginning date is the later of the first date value you entered
on menu 2.1 or the first available date of the simulation. The ending date for each entry is the earlier
of the last date value you entered on menu 2.1 or the last date of the simulatioa You can change the
beginning date, the ending date, or both of them. You must specify a time period of at least 3 days
that is within the time period of the simulation.
Instructions
Examine the list of simulations and dates displayed, scrolling the list if necessary, until you
find the one you want to select. Press the TAB key of your terminal until the cursor is at the select
field of the line containing the simulation and date range you have chosen to retrieve. Type an 5 in
the select field to indicate your choice. (You may use any character except blank or underline to
indicate selection; is does not have to be 5.) If you want to change the beginning date of the data to
be retrieved, type over the value listed on the screen. Follow the same procedure for the ending date.
The rules for specifying dates are the same as for menu 2.1: enter month, day, and year as numbers
separated by slashes (/), dashes (-), or spaces. Press the ENTER key to confirm the selection you have
made and to proceed to the next menu.
If you do not want to select an entry from the list, press the PF3 or PF15 key. Menu 2.1
reappears with the selection criteria you specified. You may then change the criteria and press
ENTER to proceed again to menu 2.2, or press the PF3 or PF15 key again to return to the GMISS
main menu.
Error Messages
You may select only one entry from the list.
You cannot select more than one ROM simulation and date range in a particular data retrieval
session. If you accidentally entered a character in the select column, erase it and press the
ENTER key. If you purposely selected more than one entry, decide which one to retrieve in
this session and erase all other select fields, then press the ENTER key.
57 Reference
-------
Invalid date. Use the format mm/dd/yy.
The value you entered for beginning or ending date is not valid. You must specify all three
parts of the date as numbers in the order month, day, and year. You may separate the three
parts with slashes (/), dashes (-), or spaces. Month can be 1 through 12. Day can be 1
through the number of days in the month. Year values of 50 through 99 represent the years
1950 through 1999, and values of 0 through 49 represent the years 2000 through 2049. You
do not have to use a leading zero in a value less than ten. Leading and trailing blanks in a
value are ignored.
First date must precede last date (by at least 2 days).
The beginning date is later than the ending date. Change the dates so that the beginning date
precedes the ending date and they define a time period of at least 3 days.
The date range must be at least 3 days long.
The beginning and ending dates must define a time period of at least 3 days. (The ROM-
UAM Interface software requires at least 3 days of data.) Change one or both date fields so
that the beginning date precedes the ending date by 2 days or more.
The available dates are mm/dd/yy through mm/dd/yy.
A date you specified does not fall within the valid range of dates, listed in the error message,
for the beginning or ending date of the selected ROM simulation. Change the faulty date so it
is within the time period listed in the error message. Be sure the new date range is at least 3
days long.
Press PF3/15 to return to the previous menu
This message occurs only if some unusual condition prevents the menu from working as it
should. Some information about the error condition may appear on the menu where the
second title line normally is. Record the information, press the PF3 or PF15 key of your
terminal until you have exited from GMISS, and contact the EPA office in charge of GMISS,
listed in the For More Information section of Chapter 1.
58
Reference
-------
5.6 Menu 2.3 - Select Data Categories
With menu 2.3, you specify which categories of ROM data you want to retrieve. Refer to the
Retrieval Files section of Chapter 2 for a discussion of the data categories, and to Chapter 6 for a
description of the files in each category.
I igure 5-11 shows the format of menu 2.3, which lists the five data categories you may
choose. All five categories are needed to run the ROM-UAM Interface, so the default is to retrieve
them all. The first time you use this menu, there will be an S in the select field beside the name of
every data category, as in Figure 5-11. Thereafter, the initial values in the select fields will reflect the
categories you selected the previous time, because menu 2.3 saves and "remembers" your selection
criteria.
+2.3 +
GMISS: Retrieve Data For UAM I
Select Data Categories I
Select data categories to retrieve by entering "S" or exclude categories
by erasing the "S", then press ENTER. Select at least one data category.
SELECT Category Description of Data
S CONG Hourly gridded concentrations of ROM chemical species
S RAWIN Hourly nongridded temperature vertical profiles
derived from rawinsonde upper-air data
S GEO Time-invariant gridded geographic features: land use,
terrain elevation, and surface roughness
S BIOGEN Hourly gridded biogenic emissions
S MET Hourly gridded surface meteorological conditions, cloud
cover, wind vectors, and layer boundary heights
(Press PF3/PF15 to return to the previous menu.)
Figure 5-11. Menu 2.3 - Select Data Categories
59 Reference
-------
Instructions
Type an 5 (or any other character but blank or underline) in the select field beside each
category of data you wish to retrieve from the GMISS database. Leave blank or erase the select field
beside each category of data you do not want to retrieve. You must select at least one category. Press
the ENTER key to accept the category selections you have made and to proceed to the next menu in
the data retrieval function.
To return to the previous menu without selecting data categories, press the PF3 or PF15 key of
your terminal.
Error Messages
You must select at least one category.
If you select none of the data categories, there would be no retrieval files to create, and no
point in executing the UAM Subsystem data retrieval function. Therefore you must select at
least one of the categories. If you do not retrieve a particular category of data from GMISS,
you will have to supply equivalent data from some other source to be able to run the ROM-
UAM Interface software.
5.7 Menu 2.4 - Specify Subdomain Coordinates
The purpose of menu 2.4 is to define the geographic area, the ROM subdomain, for which you
will retrieve ROM data. Since any urban area you might model with the UAM is much smaller than
the regional area modeled by the ROM, you need to retrieve only a small part of the data of a ROM
simulation. Menu 2.4 lets you specify which part of the ROM's regional domain corresponds with the
geographic area you plan to model with the UAM. You define a "rectangle" within the ROM domain
that encloses the urban area you are interested in. (Since the ROM subdomain boundaries are parallel
to lines of longitude and latitude, its shape is more trapezoidal than rectangular. See the Retrieval
Files section of Chapter 2 for a discussion of subdomain shape.)
Reference 60
-------
Figure 5-12 shows the format of menu 2.4. The instructions near the top of the screen explain
that you need to supply map coordinates, longitude and latitude, of two opposing comers of the
geographic area you intend to model with the UAM—your UAM domain. Below the instructions, at
the left side of the screen, are fields for specifying the map coordinates. You must enter two
coordinates for each comer: the east-west position (longitude) and the north-south position (latitude).
Thus, to specify the locations of two corners of the UAM domain, you have to enter four coordinates.
Each coordinate has three fields: degrees, minutes, and seconds of longitude or latitude.
+2.4-
GMISS: Retrieve Data For UAM
Specify Subdomain Coordinates
Define the geographic extent of the ROM data you are retrieving to match
the size and location of the area you will model with the UAM. Supply
coordinates for opposite corners of your UAM domain as degrees, minutes,
and seconds of longitude and latitude, then press ENTER. The range of
coordinates allowed in the ROM domain are listed below. GMISS enlarges
the subdomain you define by about two ROM grid cells in each direction.
Coordinates of UAM Domain ROMNET1 Domain
(X) (Y) (X) (Y)
Longitude Latitude Longitude Latitude
(ddd mm ss) (dd mm ss) (ddd mm ss) (dd mm ss)
SW Corner: 84 37 30 36 35 00
NE Corner: 69 22 30 44 45 00
(Press PF3/PF15 to return to the previous menu.)
Figure 5-12. Menu 2.4 - Specify Subdomain Coordinates
Beside the fields for entering the UAM domain coordinates, at the right side of the screen, are
the coordinates of the ROM domain of the simulation you selected to retrieve. These are the
maximum and minimum values you can specify for any coordinate of the UAM domain.
The UAM Subsystem retrieves data for whole ROM grid cells, so the ROM subdomain is
defined in terms of ROM grid cells, too. Menu 2.4 determines the smallest rectangle composed of
whole ROM grid cells that completely encloses your UAM domain, plus a border of about two cells.
The border is added to provide additional ROM data that the ROM-UAM Interface uses to obtain a
61 Reference
-------
better estimate of ROM data values at the boundaries of your UAM domain. The border around the
UAM domain must contain the centers of at least two ROM grid cells. To determine the smallest
rectangle of ROM cells that meets these requirements, menu 2.4 first expands your UAM domain
outward in all four directions (north, south, east, and west) by 1.5 times the north-south or east-west
dimension of a ROM cell, as appropriate. Then, menu 2.4 determines the coordinates of the southwest
and northeast comers of the ROM grid cells containing the southwest and northeast comers, respec-
tively, of the expanded rectangle. These are the coordinates of the ROM subdomain. On average, the
ROM subdomain is two ROM cells bigger in each direction than your UAM domain, since the
minimum amount of expansion is 1.5 times the cell dimension, and the maximum amount is 2.5 times.
When you enter coordinates on menu 2.4, do not consider the two-cell border or the locations
of ROM cells. Enter the exact coordinates of the UAM domain—the geographic area you intend to
use in UAM simulations.
Menu 2.4 saves the coordinates you enter, and it "remembers" them the next time you use it.
The coordinates you entered the previous time are the initial values on the menu. If you want to use
the same coordinates again, you do not have to re-enter them.
Instructions
Enter the longitude and latitude coordinates of opposite comers of the UAM domain for which
you want to retrieve ROM data. Although the screen requests coordinates of the southwest and
northeast comers, you can specify coordinates in any arrangement that you prefer. Menu 2.4 will
rearrange your values to fit the southwest-northeast convention. If you find it easier to think in terms
of sides of the UAM domain, do not worry about comers at all. Simply enter the minimum and
maximum longitudes of the UAM domain in the longitude column, and enter the minimum and
maximum latitudes in the latitude column. Menu 2.4 will rearrange your values as needed to define
the southwest and northeast corners.
You must specify four coordinates in order to define the ROM subdomain. You do not have
to enter values for minutes or seconds of longitude or latitude, but there must be a value in all four
fields for degrees. Leaving blank a minutes or seconds field is equivalent to specifying zero.
£f\
Reference
-------
The ROM-UAM Interface software, which converts your retrieval files to UAM input data, can
handle subdomains no larger than 30 ROM grid cells in the east-west direction. Since the two-cell-
wide border added to the ROM subdomain accounts for four cells of the total, the maximum east-west
dimension you can specify is 26 ROM grid cells, or 6.5 degrees of longitude. The largest urban areas
are about half that size, so the 30-cell maximum subdomain width should not limit any reasonable
retrieval you would want to do. The north-south dimension of the subdomain may be as large as the
ROM domain. The minimum subdomain size is a single ROM grid cell. (Of course, a'ter a two-cell-
wide border is added, the smallest possible subdomain is five ROM grid cells in each dimension.)
To return to the previous menu without specifying subdomain coordinates, press the PF3 or
PF15 key of your terminal.
Error Messages
Invalid value. Coordinates must be numeric.
You entered a non-numeric value in the field at which the cursor is positioned. Enter a
numeric value for degrees, minutes, or seconds, and press the ENTER key.
You must specify all coordinates of the subdomain
Four coordinates are required to define the subdomain "rectangle". You must specify a value
in the degrees field of each coordinate. Enter a value for degrees and press the ENTER key.
Minutes of longitude must be 0 - 59
Minutes of latitude must be 0 - 59
Seconds of longitude must be 0 - 59
Seconds of latitude must be 0 - 59
There are 60 minutes of longitude or latitude per degree, and 60 seconds per minute.
Therefore, the minutes and seconds fields can have values 0 through 59. (A value of 60
minutes would be equivalent to the next higher degree and zero minutes, and 60 seconds
would be equivalent to the next higher minute and zero seconds.) Change the minutes or
seconds value and press the ENTER key.
63 Reference
-------
Allowed longitudes are dd:mm:ss • dd:mm:ss (deg:min:sec).
Allowed latitudes are dd:mm:ss - dd:mm:ss (deg:min:sec).
A subdomain coordinate has a value outside the bounds of the ROM domain you selected.
Change the coordinate to be within the bounds listed in the error message, and press the
ENTER key.
Longitude range of dd:mm:ss (d:m:s) exceeds the maximum dd:mm:ss allowed.
The east-west dimension of the subdomain you have defined exceeds the maximum allowed.
Change the longitude coordinates to select a smaller subdomain, and press the ENTER key.
Coordinates of SW and NE corners exchanged. Press ENTER to accept.
The coordinates as entered did not define southwest and northeast corners of the subdomain.
Menu 2.4 has rearranged the coordinates to do that, and is asking you to confirm that the
rearranged coordinates correctly define the subdomain. If the coordinates are correct, press the
ENTER key to accept them. Otherwise, change the coordinates and then press the ENTER
key. Menu 2.4 always forces the coordinates to define the southwest and northeast corners of
the subdomain, so if you change them to represent other comers, menu 2.4 will change them
back and ask for confirmation again.
5.8 Menu 2.5 - Select Rawin Stations
Menu 2.5 is conditional; it appears if you choose on menu 2.3 to retrieve the RAWIN data
category. The purpose of menu 2.5 is to allow you to select which rawin stations to retrieve data for.
EPA guidelines for using the UAM include advice for choosing rawin stations. You should consult
that document1 before using the GMISS UAM Subsystem to retrieve RAWIN data. Your Regional
modeling contact can tell you how to obtain a copy of the publication. See For More Information in
Chapter 1 for the telephone number.
1Guideline for Regulatory Application of the Urban Airshed Model, Office of Air Quality Planning and Standards,
U.S. Environmental Protection Agency, Research Triangle Park, North Carolina 27711 (in preparation)
64
Reference
-------
Figure 5-13 shows the format of menu 2.5. The bottom portion of the screen is a list of rawin
stations, one station per line. At the left side of each line, under the heading "SELECT", is a field
where you type an S (or any other character except blank or underline) to select the rawin station
described in that line. The station description includes the WBAN2 station identifier, the station
elevation, longitude, and latitude, and the name of the place where the station is located. Use the
place name and the longitude-latitude of a station to determine its proximity to the ROM subdomain
you defined with the previous menu. Menu 2.5 displays the boundaries of the ROM subdomain above
the list of rawin stations. Note that the subdomain coordinates reflect the two-cell-wide border added
to the subdomain as described in the preceding section.
+2.5-
GMISS: Retrieve Data for UAM
Select Rawin Stations
Type "S" beside each rawin station you wish to select, then press ENTER.
Press PF3/PF15 to return to the previous menu without selecting stations,
Scroll the list forward with PF8/PF20, backward with PF7/PF19.
The longitude and latitude coordinates (ddd mm ss) of the subdomain
to be retrieved are: SW corner lon= 78 30 00 lat= 37 50 00
NE corner lon= 75 30 00 lat= 40 20 00
Station Elevation Longitude Latitude
SELECT ID (meters) (ddd mm) (dd mm) Station Description
03860
03879
03881
13601
13723
13840
13873
13880
255
167
139
6
276
250
244
14
82
88
87
64
79
84
83
80
33
57
15
41
57
03
19
02
38
38
32
32
36
39
33
32
22
38
54
22
05
49
57
54
Huntington, WV
Salem, IL
Centreville, AL
St. George, Bermuda
Greensboro/High Pt . ,
Wright Patterson AFB,
Athens, GA
Charleston, SC
NC
OH
Figure 5-13. Menu 2.5 - Select Rawin Stations
Usually there are more stations than menu 2.5 can list on one screea For example, a typical
KOM simulation in the ROMNET1 domain has data for about 25 rawin stations. You can scroll the
list to see all of them. The Using Menus section of Chapter 3 describes scrolling and tells what
terminal keys to use.
WBAN stands for Weather Bureau, Army, Navy—the organizations that established the original network of rawin stations.
65
Reference
-------
Instructions
Examine the list of rawin stations and select at least one by typing an 5 in the select field at
the left of the screen. Figure 5-14 shows the approximate locations of rawin stations in central and
eastern United States and Canada. Not all of the stations shown on the map are available for a
particular ROM simulation, however. Follow EPA guidelines for choosing rawin stations (see the
reference on page 64). To be sure you are making the best choices, scroll the list to see all of the
available stations. Press the ENTER key to confirm your selections and to proceed to the next menu.
To return to the previous menu without selecting rawin stations, press the PF3 or PF15 key of
your terminal.
Error Messages
You must select at least one rawin station.
If you have chosen to retrieve the RAWIN data category, you must select at least one rawin
station to retrieve data for. Examine the list and select at least one station by typing an S in
the select field beside it, then press the ENTER key.
Press PF3/15 to return to the previous menu
This message occurs only if some unusual condition prevents the menu from working as it
should. Some information about the error condition may appear on the menu where the
second title line normally is. Record the information, press the PF3 or PF15 key of your
terminal until you have exited from GMISS, and contact the EPA office in charge of GMISS,
listed in the For More Information section of Chapter 1.
Reference
-------
104 102 100 98 96 94 92 90 88 86 84 82 80 78 76 74 72 70 68 66 64 62 60
24
104 102 100 96 96 94 92 90 38 86 84 82 80 78 76 74 72 70 68 66 64 62 60
Figure 5-14. Locations of Rawin Stations in Eastern United States and Canada
5.9 Menu 2.6 - Specify Retrieval File Names
Menu 2.6 has a utilitarian function: specifying the names of the files that will hold the ROM
data retrieved according to the selection criteria you entered on preceding menus. The Retrieval Files
section of Chapter 2 summarizes the properties of the data files the UAM Subsystem creates, and
Chapter 6 gives detailed information about them.
Figure 5-15 shows the format of menu 2.6. The bottom portion of the screen lists the five
categories of data, an abbreviated description of the files in each category, and the default file names
menu 2.6 has assigned. If you elected not to retrieve data for a particular category, the area of the
67
Reference
-------
screen reserved for that category's file names is blank. Figure 5-16 shows how menu 2.6 looks when
the GEO data category is not being retrieved.
Menu 2.6 assigns default file names based on the date and time when you use the menu. The
name of the file of ROM concentration data includes the ROM version name (such as "ROM21")
instead of the data category name ("CONC"). The names of the files of ROM processor data include
the "PF" or "MF" file designation referenced in Chapter 6 of this manual and in the user's guide for
the ROM-UAM Interface software. If you change the default names, be sure to record them so you
will know the contents of the files. Also make sure that the new file names are valid for EPA's IBM
computer system; menu 2.6 does not check the names to determine their validity. If you are unsure of
the file naming conventions, get in touch with the user support department of the EPA National
Computer Center. See the For More Information section of Chapter 1 for telephone numbers.
The blank places on menu 2.6 that result from not selecting a data category, as Figure 5-16
shows, are protected fields, and you cannot enter file names there. If you decide you want to retrieve
a data category that you excluded, you must return to menu 2.3 and select it. Similarly, you cannot
exclude a data category selected on menu 2.3 by erasing the retrieval file names on menu 2.6. Every
retrieval file in every selected data category must have a file name.
Instructions
If you want to change a default file name listed on menu 2.6, move the cursor to it and type
the name you wish to use. Be sure the new name is valid for EPA's IBM computer system. If you
specify an invalid name, the batch job that retrieves data will not run. It is not necessary to type
upper-case characters in the name; menu 2.6 converts entries to upper case automatically. Press the
ENTER key to accept the file names and to proceed to the next menu.
To return to the previous menu without specifying retrieval file names, press the PF3 or PF15
key of your terminal.
Reference 68
-------
+2.6-
GMISS: Retrieve Data for UAM
Specify Retrieval File Names
You may specify your own retrieval file names by typing over the default
names listed below. Press ENTER to accept your choices for file name.
Category Description
CONG ROM species cone.:
RAWIN Vert air profiles:
GEO Surface roughi ess:
Landuse fract:ons:
Terrain elevation:
BIOGEN Biogenic emiss'ns:
MET Surface met'ology:
Layer 2 wind fids:
Layer 1 wind fids:
Cloudiness fractn:
Layer 1-2 intface:
Layer 2-3 intface:
Layer 1 water vap:
(Press PF3/PF15
File Name
TADRMFP.D901123.
TADRMFP.D901123.
TADRMFP.D901123.
TADRMFP.D901123.
TADRMFP.D901123.
TADRMFP.D901123.
TADRMFP.D901123.
TADRMFP.D901123.
TADRMFP.D901123.
TADRMFP.D901123.
TADRMFP.D901123.
TADRMFP.D901123.
TADRMFP.D901123.
to return to the
T131401.ROM21.ROMNET1.U
T131401.PF102.ROMNET1.U
T131401.PF108.ROMNET1.U
T131401.PF118.ROMNET1.U
T131401.PF119.ROMNET1.U
T131401.PF144.ROMNET1.U
T131401.PF103.ROMNET1.U
T131401.PF114.ROMNET1.U
T131401.PF115.ROMNET1.U
T131401.PF117.ROMNET1.U
T131401.MF165.ROMNET1.U
T131401.MF166.ROMNET1.U
T131401.MF174.ROMNET1.U
previous menu.)
Figure 5-15. Menu 2.6 - Specify Retrieval File Names
+2.6-
GMISS: Retrieve Data for UAM
Specify Retrieval File Names
You may specify your own retrieval file names by typing over the default
names listed below. Press ENTER to accept your choices for file name.
Category Description
CONC ROM species cone.:
RAWIN Vert air profiles:
GEO Surface roughness:
Landuse fractions:
Terrain elevation:
BIOGEN Biogenic emiss'ns:
MET Surface met'ology:
Layer 2 wind fids:
Layer 1 wind fids:
Cloudiness fractn:
Layer 1-2 intface:
Layer 2-3 intface:
Layer 1 water vap:
(Press PF3/PF15
File Name
KWBOAQP.D901123.T131546.ROM21.ROMNET1.U
KWBOAQP.D901123.T131546.PF102.ROMNET1.U
KWBOAQP.D901123.T131546.PF144.ROMNET1.U
KWBOAQP.D901123.T131546.PF103.ROMNET1.U
KWBOAQP.D901123.T131546.PF114.ROMNET1.U
KWBOAQP.D901123.T131546.PF11J.ROMNET1.U
KWBOAQP.D901123.T131546.PF117.ROMNET1.U
KWBOAQP.D901123.T131546.MF165.ROMNET1.U
KWBOAQP.D901123.T131546.MF166.ROMNET1.U
KWBOAQP.D901123.T131546.MF174.ROMNET1.U
to return to the previous menu.)
Figure 5-16. Appearance of Menu 2.6 With an Excluded Data Category
69
Reference
-------
Error Messages
Required filename(s) must be entered
A file name is blank in a data category you chose to retrieve. All retrieval files that you have
instructed the UAM Subsystem to create must have names. Enter a valid IBM file name in
the field at the cursor (and in any other blank field in the same data category), and press the
ENTER key.
5.10 Menus 2.7 and 1.1 - Specify Batch Job Parameters
Menu 2.7 (Figure 5-17) is the last menu in the UAM Subsystem data retrieval function. Menu
1.1 (Figure 5-18) is the only menu of the List Database Contents function, option 1 on the GMISS
main menu. Both menus are identical in appearance (except for the function title), and they serve the
same purpose: they get the information needed to submit a batch job that will retrieve data or generate
a database contents report. The menu programs use the values you enter (or the default values they
supply) to generate job control language (JCL) statements that control the execution priority of the
batch job and the disposition of its printed output. The batch job information on the two menus
consists of these fields:
Job name Identifier of the batch job
Job time Maximum amount of computer processing time the job may use
Job priority Processing priority the batch job receives
Account Source of funds to pay for the computer resources the job uses
FIMAS ID General project or activity the batch job supports
NCC bin Where to send printed job output
Destination Where to print job output
NCC form The type of paper on which to print job output
Job name is an eight-character field that identifies the batch job to the IBM computer system.
The first three characters must be your EPA National Computer Center user-id. Since that part of the
job name is required, menus 2.7 and 1.1 put your user-id there for you, and you cannot alter that part
70
Reference
-------
of the job name. The rest of the job name has the default value "UAMR" on menu 2.7 and "UAMD"
on menu 1.1. You can change that part of the job name to any five letters or numbers you wish.
Job time is the maximum amount of CPU time the batch job may consume. It is specified as
two numbers, minutes and seconds, separated by a comma. The default job times, 5 minutes for data
retrieval (menu 2.7) and 2 minutes for database contents report (menu 1.1), are sufficient. Depending
on your selection criteria, your batch job may take less time. However, if /ou do not specify enough
time, the batch job will not complete the data retrieval or the report.
Job priority determines when your batch job is considered for execution. There are two
possible values. Priority value "2", the default on both menus, makes your job immediately available
for execution. Usually your job will begin executing within a few minutes after being submitted.
Priority value "1" puts your batch job in an "overnight" category that is not considered for execution
until after 5:00 p.m. eastern time. Priority "1" jobs cost only half as much per CPU minute as priority
"2" jobs, however.
The account field is the EPA National Computer Center account code that will be charged for
the cost of the batch job. The account code is supplied to you when you register as a user of the
computer center. Menus 2.7 and 1.1 obtain the account code you are using for your terminal session
and display that as the initial value of the account field. If you have multiple account codes, you can
enter another one, if you wish.
FIMAS ID is another accounting code that identifies the project or general type of work that
the batch job is supporting. Your Regional modeling contact can tell you what FIMAS code to use.
(See the For More Information section in Chapter 1 for telephone numbers.) The menus do not have
an initial value for this field.
NCC bin designates where the computer center puts the printed output of the batch job. A
value like "B123" identifies a physical bin at the computer center from which you are authorized to
remove job listings. A value like "Muid" tells the computer center staff to mail the printed output to
the address on file for user-id uid. The menus do not have an initial value for this field.
Reference
-------
+2.7
GMISS: Retrieve Data For UAM
Specify Batch Job Parameters
Enter the information needed to submit a batch job, then press ENTER.
Job Name: uid UAMR
Job Time: 5,0 (Min,Sec)
Job Priority: 2
Account: acct
FIMAS ID:
NCC Bin:
Destination: LOCAL
NCC Form:
(Press PF3/PF15 to return to the previous menu without submitting a job.)
Figure 5-17. Menu 2.7 - Specify Batch Job Parameters for Data Retrieval
+1.1
GMISS: List Database Contents
Specify Batch Job Parameters
Enter the information needed to submit a batch job, then press ENTER.
Job Name: uid UAMD
Job Time: 2,0 (Min,Sec)
Job Priority: 2
Account: acct
FIMAS ID:
NCC Bin:
Destination: LOCAL
NCC Form:
(Press PF3/PF15 to return to the previous menu without submitting a job.)
Figure 5-18. Menu 1.1 - Specify Batch Job Parameters for Database Contents Report
72
Reference
-------
Destination specifies where to print the job listing. The value "LOCAL" means print it at the
EPA National Computer Center. This is the default destination on both menus. Values like
"RMT321" mean print the job at a remote printer, presumably located where you are. The value
"HOLD" means do not print the output, but retain it on the computer system where it can be viewed
using a terminal. UAM Subsystem batch jobs automatically retain the job output, in addition to
printing it, so it is not necessary to use destination "HOLD" to be able to view job output with a
terminal.
NCC form specifies the kind of paper on which to print the job listing. You may leave this
field blank (the initial value on both menus) to indicate that the printer's default form should be used.
The EPA National Computer Center default form is "8381", which is fanfold paper approximately 12
inches wide and 8.5 inches high. If you specify a destination other than "LOCAL", it is best to leave
NCC form blank, thus using the remote printer's default form. Some remote printers cannot handle a
forms request, and "stall" if they encounter one in job output. Then the IBM computer operator must
take special action to remove the job output from the print queue and restart the printer.
Menus 2.7 and 1.1 save the values you specify for the batch job parameters, and "remember"
those values the next time you use the menu. Since you probably will use the same values each time,
you have to type them in the fields only the first time you use the menu.
Instructions
Enter values in any fields that are blank, and alter the initial values of fields if you wish.
Every field except NCC form must have a value. Press the ENTER key to accept the values and
submit the batch job. The computer system confirms that the batch job has been submitted by
displaying a message like the one shown in Figure 5-19. Press the ENTER key to clear the message
from your terminal, and the GMISS main menu appears. At this point you can initiate another
function, or press the PF3 key or PF15 key to exit from the GMISS menu system.
To return to the previous menu without submitting a batch job, press the PF3 key or PF15 key
of your terminal.
T\
10 Reference
-------
IKJ56250I JOB UIDUAMR(JOB12345) SUBMITTED
***
Figure 5-19. Notification That Batch Job Was Submitted
Error Messages
All fields must be filled in
You must enter a value in every field of menus 2.7 and 1.1 except NCC form. Type a value
in the field where the cursor is positioned (and in any other blank field except NCC form), and
press the ENTER key.
JOBTIME must be of the form MIN,SEC
A value for the job time field must consist of two numbers, minutes and seconds of CPU time,
separated by a comma. Enter a value with that format and press the ENTER key.
Only 0123456789 and , allowed in JOBTIME
The value of job time is not numeric. Enter two numbers, minutes and seconds of CPU time,
separated by a comma, and press the ENTER key.
First character of Bin must be B or M
Only two kinds of values are acceptable for NCC bin: B followed by three digits, or M
followed by a three-character user-id. Enter a value with one of those formats and press the
ENTER key.
Priority must be 1 or 2
The valid values tor job priority are "1" and "2". Enter one of those values and press the
ENTER key.
Reference 74
-------
6. FILES
This chapter describes the formats and contents ofUAM Subsystem retrieval flies.
6.1 Retrieval File Types
The UAM Subsystem creates 13 separate retrieval files. Table 6-1 lists the generic names of
the files and the kinds of data they contain. As the table indicates, there are four types of data:
• Gridded, layered, hourly values (ROM concentration data)
• Nongridded, hourly values (ROM processor data, RAWIN category)
• Gridded, time-invariant values (ROM processor data, GEO category)
• Gridded, hourly values (ROM processor data, BIOGEN and MET categories)
There are three retrieval file formats: one for concentration data, one for nongridded processor data,
and one for gridded processor data. The rest of this chapter describes the file formats and the kinds of
data in each retrieval file.
6.2 Concentration Data
The UAM Subsystem retrieval file of ROM concentration data has a logical structure identical
to that of the concentration file produced by a ROM simulation. It has a group of header records that
identify the contents of the file, followed by sets of records that give the concentrations of chemical
species at each hour of each day, at three levels, and for each grid cell of the subdomain. A time-step
header record introduces the set of records for each hour. Figure 6-1 illustrates the file structure.
Although their logical structures are identical, the ROM concentration file and the UAM
Subsystem retrieval file differ in several respects. One difference is the number of chemical species in
the file. A ROM 2.1 concentration file includes 35, while a UAM Subsystem retrieval file has only
the 17 species listed in Table 6-2.
75 Files
-------
Another difference is the content of physical records. In the ROM concentration file, a
physical record contains three logical records: the values for a particular species and row at three
levels. In the UAM retrieval file, logical and physical records correspond exactly. Each record holds
the values for one row of the grid; there is a separate record for each combination of hour, row,
species, and level.
Another difference is in the way numeric fields are represented. In a ROM concentration file,
values are encoded as binary integers or floating-point numbers. In a UAM retrieval file, all numeric
values are in formatted fields; the values are expressed as digits (characters) in the fields. Table 6-3
gives the names, formats, and descriptions of the fields.
The other differences between the files pertain to the content and meaning of the header
records. The first header record in ROM concentration files has the creation date and time of several
files (BMAT, BTRK, BCON, and ICON) that the model uses. These values are not significant to
GMISS, so they are not retained in the database. Since the dates and times are not available, and
since UAM does not need them, the UAM Subsystem writes zeros in these fields of the retrieval file.
The same conditions apply to text records in the ROM concentration file header, which
describe how the file was created. GMISS does not retain these text records when the data are loaded
into the database, and therefore cannot reproduce them in a retrieval file. However, the retrieval file
has the same number of text records (ten) that a ROM concentration file usually has, and the first text
record identifies the model ("ROM2.1"). Subsequent records note how the file was created (by
GMISS) and when (date and time), and give the formulation of the first day's data. (Formulation is a
code that people who run the ROM use to identify a particular simulation and computer run.) The rest
of the text records are blank. The retrieval file has ten text records, even though not all of them are
used, because the ROM-UAM Interface software requires that number of records.
Finally, the fields for scenario start date and time, in the first header record, have different
meanings in the UAM retrieval file than in the ROM concentration file. These fields contain the first
date and hour of data in the retrieval file rather than the start date and time of the ROM scenario.
Consequently, the retrieval file header always has zero in the field for elapsed time between the
beginning of the scenario and the first hour in the file.
Rles 76
-------
Table 6-1. Types of Data in UAM Retrieval Files
Data Category
Data Type
File Names and Descriptions
Concentration data
CONC
Rawinsonde data
RAWIN
Geographic data
GEO
Gridded, layered, ROMxx Results of a ROM simulation (xx is the
hourly values ROM version number, such as 27)
Nongridded,
hourly values
Gridded,
time-invariant
values
Biogenic emissions data
BIOGEN Gridded,
hourly values
Meteorological data
MET Gridded,
hourly values
PF102 Interpolated temperature vertical profiles
derived from rawinsonde data
PF108 Surface roughness
PF118 Land use
PF119 Terrain elevation
PF144 Emissions from biogenic sources
PF103 Surface air temperature
PF114 Layer 2 horizontal wind components
PF115 Layer 1 horizontal wind components
PF117 Sky coverage (cloudiness)
MF165 Elevation of layer 1-layer 2 boundary
MF166 Elevation of layer 2-layer 3 boundary
MF174 Layer 1 water vapor concentration
Table 6-2. ROM Chemical Species in UAM Retrieval Files
Name
Description
Name
Description
ALD2
CO
ETH
FORM
H2O2
HNO2
HNO3
ISOP
MTHL
Aldehydes (high. mol. wL)
Carbon monoxide
Ethene
Formaldehyde
Hydrogen peroxide
Nitrous acid (HONO)*
Nitric acid
Isoprene
Methanol (MEOH)*
NO
NO2
O3
OLE
PAN
PAR
TOL
XYL
Nitric oxide
Nitrogen dioxide
Ozone
Olefins
Peroxyacetyl nitrate
Paraffins
Toluene
Xylene
Species name in the Urban Airshed Model; all other species names are the same in both models.
77
Files
-------
UAM
Retrieval
File
(Cone. Data)
Record
(toon)
Record
Files
Figure 6-1. Structure Diagram for UAM Retrieval Files of Concentration Data (1 of 3)
78
-------
File "
Create
Date
File '8
Create
Time
Scenario
Start
Date
Y
Scenario
Start
Time
18
Time
Step
Duration
18
Time To
First
Step
A8
Grid
Name
F8.3
Southwest
Longitude
F8.3
Southwest
Latitude
F8.3
Northeast
Longitude
F8.3
Northeast
Latitude
F8.5
Longitude
Increment
F8.5
Latitude
Increment
14
No. of
Columns
14
No. of
Rows
14
No. of
Levels
M
No. of
Species
18
BMAT File
Create Date
18
BMAT File
Create Time
18
BTRK File
Dreate Date
18
BTRK File
Create Time
»
BCON File
Create Date
18
BCON File
Create Time
18
ICON File
Create Date
18
ICON File
Create Time
14
No. of
Text Recs.
Figure 6-1. Structure Diagram for UAM Retrieval Files of Concentration Data (2 of 3)
79
Files
-------
Ftaowd
Fteord
Files
Figure 6-1. Structure Diagram for UAM Retrieval Files of Concentration Data (3 of 3)
80
-------
Table 6-3. Fields in UAM Retrieval Files of Concentration Data (1 of 3)
Field
File Create Date
File Create Time
Scenario Start Date
Scenario Start Hour
Time Step Duration
First Time Step
Grid Name
SW Longitude
SW Latitude
NE Longitude
NE Latitude
Longitude Increment
Latitude Increment
Number of Columns
Number of Rows
Type
Num (18)
Num(I8)
Num (18)
Num (18)
Num (18)
Num (18)
Char
Num (F8.3)
Num (F8.3)
Num (F8.3)
Num (F8.3)
Num (F8.5)
Num (F8.5)
Num (14)
Num (14)
Length
First Header
8
8
8
8
8
8
8
8
8
8
8
8
8
4
4
Description
Record
Date of file creation (MMDDYY)
Time of file creation (HHMMSS)
Earliest date of data in retrieval file (Julian
date: YYDDD)
First hour present in file for Scenario Start
Date (HH); always zero (midnight) in retrieval
file
Length of a time step (in seconds); always
3600 (1 hour) in retrieval file
Time (in seconds) from start of scenario to first
time step in file; always zero in retrieval file
Name of the model domain
Longitude and latitude (in degrees) of the
southwest corner of the retrieval subdomain
Longitude and latitude (in degrees) of the
northeast corner of the retrieval subdomain
West-to-east size of a ROM grid cell (decimal
degrees)
South-to-north size of a ROM grid cell (deci-
mal degrees)
Number of grid columns in the retrieval
subdomain
Number of grid rows in the retrieval sub-
domain
81
Files
-------
Table 6-3. Fields in UAM Retrieval Files of Concentration Data (2 of 3)
Field
Type Length Description
Number of Levels
Number of Species
BMAT Create Date
BMAT Create Time
BTRK Create Date
BTRK Create Time
BCON Create Date
BCON Create Time
ICON Create Date
ICON Create Time
Number of Text Recs.
Species Name
Level Name
Descriptive Text
First Header Record (continued)
Num (14)
Num(I4)
Num (18)
Num (18)
Num (18)
Num (18)
Num (18)
Num (18)
Num (18)
Num (18)
4
4
8
8
8
8
8
8
8
8
Num (14)
Char
Char
Number of levels (layers) in the retrieved data;
always 3 for ROM 2.1
Number of chemical species in the retrieved data;
always 17 for ROM 2.1
Creation date (MMDDYY) and time (HHMMSS)
of the B -matrix, backtrack, boundary conditions,
and initial conditions files used for the ROM
scenario. These fields are undefined in the UAM
retrieval file; they all have zero values.
4 Number of text records in the retrieval file header,
always 10 for ROM 2.1
Second Header Record
4*17 Names of the 17 chemical species in the retrieved
data (e.g., "O3" for ozone). The order of the
names indicates the order of species in the file
body.
Third Header Record
4*3 Names of the 3 levels (layers) in the retrieved data
("1", "2", "3")
Fourth through Thirteenth Header Records
Char 160 Lines of text that describe how and when the re-
trieval file was created. Only the first 80 charac-
ters of each line are used. (The lines are 160
characters long for compatibility with ROM-UAM
Interface software. ROM versions 2.1 and 2.2 use
80-byte text records.)
Files
82
-------
Table 6-3. Fields in UAM Retrieval Files of Concentration Data (3 of 3)
Field
Type Length
Description
Step Date
Step Time
Num (15)
Num (16)
Time
5
6
Step Header Record
Julian date (YYDDD) of the following concen-
tration values
Time (HHMMSS) at the beginning of the time
Elapsed Time
Step Number
Num (18) 8
Num (16)
step for the following concentration values;
hour has values 0-23; minutes and seconds are
always zero
Number of seconds from Scenario Start Date
and Scenario Start Hour to the date and time
of this time step
Ordinal number of this time step (1, 2, 3,...)
Time Step Body Records1
Species Concentrations Num (E12.6) I2*cols
Concentration of a chemical species in each
grid cell of a row of the retrieval subdomain.
The Number of Columns field in the file header
specifies how many of the values are in each
record.
The time step body has a record for each combination of row in the retrieval subdomain, species (17), and level (3).
83
Files
-------
6.3 Processor Data
The UAM Subsystem of GMISS creates retrieval files of ROM processor data that have
logical structures similar to those of the ROM processor files used in a ROM simulation. There are
two file formats: one for nongridded data and one for gridded data. The two categories of gridded
data, time-invariant and time-varying (hourly), use the same file structure. The retrieval files for both
nongridded and gridded data begin with a header, which has the same format in both file types. Data
records, constituting the file body, follow the header records.
The following subsections describe the common file header, the structure and format of the
data records in each file type, and the kinds of data values (parameters) in each retrieval file.
6.3.1 File Header
The header of retrieval files of ROM processor data consists of six records plus one additional
record for each parameter in the file. Figure 6-2 shows the formats of the header records, and
Table 6-4 lists and describes the fields in them. Each underlined area in Figure 6-2 indicates the
position of a field in the header records. The letters in the underlined areas refer to the field
description in Table 6-4.
+ 1 +
FILE: a
SOUTHWEST ROM
SOUTHWEST ROM
CREATE DATE: m
WRITE DATE: o
PARAMETER NAME
2
q
+ 1 +
2 + 3 + 4 + 5 + 6 + 7.... + {
REGION: b TYPE: c COLS: d ROWS: e PARAMETERS: f
CELL (LAT) : % h_ i
CELL (LON) : J k_ 1
CREATE TIME: n
WRITE TIME: £
: UNITS: DESCRIPTION:
r s
r s
2 + 3 + 4 +• 5 + 6 + 7 '
3
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(etc.)
3
Figure 6-2. Formats of Header Records of UAM Retrieval Files of ROM Processor Data
Files 84
-------
Table 6-4. Fields in Header Records of UAM Retrieval Files of ROM Processor Data
ID1
a
b
c
d
e
f
g
h
i
j
k
1
m
n
0
P
q
r
s
Field
File Name
Grid Name
File Type
No. of Columns
No. of Rows
No. of Parameters
SW Latitude Deg.
SW Latitude Min.
SW Latitude Sec.
SW Longitude Deg.
SW Longitude Min.
SW Longitude Sec.
File Create Date
File Create Time
File Write Date
File Write Time
Parameter Name
Units of Measure
Description
Type
Char
Char
Num(Il)
Num (12)
Num (12)
Num (12)
Num (14)
Num (12)
Num (F5.2)
Num (14)
Num (12)
Num (F5.2)
Num (16)
Num (16)
Num (16)
Num (16)
Char
Char
Char
Length
12
8
1
2
2
2
4
2
5
4
2
5
6
6
6
6
10
12
40
Description
Internal name of file ("PFnnn")
Name of model grid (domain)
Type of file (l=nongridded, 4=gridded time-
invariant, or 5=gridded hourly)
Number of columns and rows in the ROM sub-
domain in this file. In a file of nongridded data,
these fields contain zeros.
Number of parameters in this file
Latitude (degrees, minutes, seconds) of the
southwest corner of the ROM subdomain in this
file2
Longitude (degrees, minutes, seconds) of the
southwest corner of the ROM subdomain in this
file2
Date (MMDDYY) and time (HHMMSS) this file
was created
Date (MMDDYY) and time (HHMMSS) this file
was last updated (same as file creation date and
time)
Name, units, and description of each parameter
in the file
The 'ID" column refers to Figure 6-2, which shows the location of each field.
The latitude and longitude of the ROM subdomain have no meaning in a retrieval file of nongridded data,
but the ROM-UAM Interface software requires that the coordinates be in the header.
85
Files
-------
6.3.2 File Body: Nongridded Data
The UAM Subsystem has only one retrieval file of nongridded hourly data. This type of
retrieval file has a group of records in the file body for each hour of each day selected for retrieval.
In each hour group there is a group of records for each parameter. A parameter group begins with a
header record that specifies the number of rawin stations reporting data for that hour and parameter.
The parameter group body, which follows the parameter header record, has a group of records for each
station. Each station group begins with two header records that identify the date and time, the
parameter, and the station. The rest of the station group is data records that contain values of the
parameter at each height (altitude) in the vertical profile for the station.
Table 6-5 identifies the nongridded retrieval file and describes the parameters in it. Figure 6-3
illustrates the file structure and Table 6-6 lists and describes the fields in each of the file's record
types.
Table 6-5. Parameters in the UAM Retrieval File of Hourly Nongridded Data
Parameter Units Description
PF102 : Upper-air vertical temperature profiles, interpolated to every hour and to every 50
meters from rawinsonde data (3 parameters)
Zm m above MSL Height where parameters were interpolated
Tvm(z) K Virtual temperature
qm(z) (none) Mixing ratio fraction
Files 86
-------
UAM
Retrieval
File
(Non-Grklded Data)
No.
13
of
Stations
Record
Station
Header
I5.1X
Step
Date
I5.1X
Station
ID
12,1 X
Step
Time
1X.A10
Parameter
Name
Record
F5.2.1X
Station
Latitude
F5.2.1X
Station
Longitude
14
No. of
Altitudes
F8.2
Station
Elevation
Record
Record
Figure 6-3. Structure Diagram for UAM Retrieval File of Nongridded Data
87
Files
-------
Table 6-6. Fields in UAM Retrieval Files of Nongridded Data
Field
No. of Stations
Date
Hour
Parameter
Station ID
Latitude
Longitude
Number of values
Elevation
Parameter value
Type
Length
Description
Parameter Header Record
Num (13) 3 Number of stations reporting data for this hour
Station Header Record 1
Num (15,IX) 6 Julian date (YYDDD) for the following data
Num (12, IX) 3 Hour of the day (00-23) for the following data
Char (1X.A10) 11 Name of the parameter for the following data
Station Header Record 2
Num (I5.1X) 6
Num (F5.2.1X) 6
Num (F5.2.1X) 6
Num (14) 4
Num (F8.2)
8
Station ID number for the following data
Station latitude (degrees)
Station longitude (degrees)
Number of altitudes (data records) in the vertical
profile for this station
Station elevation (meters above mean sea level)
Data Records
Num (1X.E12.6) 13
Value of the parameter at each altitude of the
vertical profile; one record for each altitude
Files
88
-------
6.33 File Body: Gridded Data
Except for rawin data discussed in the preceding section, all UAM Subsystem retrieval files
contain gridded data. There are two varieties of gridded data, time-invariant and hourly. A retrieval
file of gridded, hourly data has a group of records in the file body for each hour of each day selected
for retrieval. A gridded, time-invariant retrieval file has just one group of records in the file body,
equivalent to a single hour. An hour-group has an hour-parameter header record, foliowxl by data
records that contain values of each parameter at that hour in each grid cell of the subdomain selected
for retrieval. Each data record holds the parameter values for one row of the subdomain.
Table 6-7 identifies each retrieval file of time-invariant, gridded data and the parameters in it.
Table 6-8 does the same for retrieval files of hourly, gridded data. Figure 6-4 illustrates the retrieval
file structure, and Table 6-9 lists and describes the fields of each type of record in the file.
89 Files
-------
Table 6-7. Parameters in UAM Retrieval Files of Time-Invariant Gridded Data
Parameter Units Description
PF108 : Gridded effective surface roughness (1 parameter)
ZO m Effective surface roughness length
PF118 : Gridded land use fractions (11 parameters)
URBAN (none) Urban
AGRI (none) Agricultural
RANGE (none) Rangeland
DF (none) Deciduous forest
CF (none) Coniferous forest
MF (none) Mixed forest types including wetlands
WATER (none) Water
BARREN (none) Barren
NFW (none) Nonforested wetland
MAR (none) Mixed agricultural and rangeland
ROCKY (none) Rocky open with shrubs and lichens
PF119 : Gridded smoothed terrain elevation (1 parameter)
Zt m above MSL Terrain elevation
Files 90
-------
Table 6-8. Parameters in UAM Retrieval Files of Hourly Gridded Data
Parameter Units Description
PF103 : Hourly gridded surface air temperature (1 parameter)
SURTMP K Absolute surface temperature
PF114 : Hourly gridded horizontal wind components for layer 2 (2 parameters)
2 m/s West-to-east wind component
2 m/s South-to-north wind component
PF115 : Hourly gridded horizontal wind components for layer 1 (2 parameters)
l m/s West-to-east wind component
l m/s South-to-north wind component
PF117 : Hourly gridded fractional sky coverage total of all opaque cloud types (1 parameter)
SIGMAct (none) Fractional cloud coverage
PF144 : Hourly gridded emissions from biogenic sources (S parameters)
OLE mol/h Olefins
PAR mol/h Paraffins
ISOP mol/h Isoprenes
ALD2 mol/h Aldehydes (high mol. wt.)
NO mol/h Nitric oxide
MF165 : Hourly gridded elevation of top surface of layer 1 (1 parameter)
Zl m above MSL Interface surface elevation
MF166 : Hourly gridded elevation of top surface of layer 2(1 parameter)
72 m above MSL Interface surface elevation
MF174 : Hourly gridded water vapor concentration in layer 1 (1 parameter)
l ppm Layer 1 water vapor concentration
91 Files
-------
UAM
Retrieval
File
(Griddrt Data)
ftecbrd
Files
Figure 6-4. Structure Diagram for UAM Retrieval Files of Gridded Data
92
-------
Table 6-9. Fields in UAM Retrieval Files of Gridded Data
Field
Type
Length
Description
Hour-Parameter Header Record
Num (I5.1X) 6 Julian date (YYDDD) of the Mowing data
Num (12, IX) 3 Hour of the day (0-23) of the following data
Date
Hour
Parameter names
Char (1X.A10) ll*(#parms) Names of the parameters whose values are
recorded in the following data records
Parameter values
Data Records^
Num (E12.6) \2*colwnns Value of a parameter in each grid cell of a row
of the retrieval subdomain. The Number of
Columns field in the file header specifies how
many of the values are in each record.
Each data record holds the values of one parameter for one row of the subdomain. Thus, the number of
data records per hour-group is the product of the number of parameters in the file and the number of rows in
the subdomain.
93
Files
-------
TECHNICAL REPORT DATA
(Please read Instructions on the reverse before completing)
1. REPORT NO.
EPA-450/4-91-009
2.
3. RECIPIENT'S ACCESSION NO.
4. TITLE AND SUBTITLE
Gridded Model Information Support System
(GMISS) UAM Subsystem User's Guide
5. REPORT DATE
February 25, 1991
6. PERFORMING ORGANIZATION CODE
7. AUTHOR(S)
Thomas A. Dessent
8. PERFORMING ORGANIZATION REPORT NO.
9. PERFORMING ORGANIZATION NAME AND ADDRESS
Computer Sciences Corporation
Applied Technology Division
P.O. Box 12767
Research Triangle Park, NC 27709
10. PROGRAM ELEMENT NO.
11. CONTRACT/GRANT NO.
12. SPONSORING AGENCY NAME AND ADDRESS
U.S. Environmental Protection Agency
Technical Support Division (MD-14)
Office of Air Quality Planning and Standards
Research Triangle Park, NC 27711
13. TYPE OF REPORT AND PERIOD COVERED
14. SPONSORING AGENCY CODE
15. SUPPLEMENTARY NOTES
16. ABSTRACT
The Gridded Model Information Support System (GMISS) is a data base
management system for selected Regional Oxidant Model (ROM) input
data and species concentrations produced by gridded photochemical
air pollution models. The UAM Subsystem allows state and local
agencies to use these data to set initial and boundary conditions
for the Urban Airshed Model. Selected data may be retrieved and
used to build input files to the ROM/UAM Interface System which
converts the data from ROM grid cell and vertical layer dimensions
to UAM grid cell and vertical dimensions. This document describes
how to invoke and execute the UAM Subsystem using the full screen
menus.
17.
KEY WORDS AND DOCUMENT ANALYSIS
DESCRIPTORS
b.IDENTIFIERS/OPEN ENDED TERMS C. COSATI Field/Group
Urban Airshed Model (UAM)
Regional Oxidant Model (ROM)
ROM/UAM Interface System
species, domain, scenario,
rawin station, biogenic
emissions
18. DISTRIBUTION STATEMENT
Release Unlimited
19. SECURITY CLASS (This Report)
21. NO. OF PAGES
20. SECURITY CLASS {Tins pagef
22. PRICE
93
EPA Form 2220-1 (Rev. 4-77) PREVIOUS EDITION is OBSOLETE
------- |