EPA-454/B-96-002
Replaces: EPA-454/B-94-020
METEOROLOGICAL PROCESSOR FOR
REGULATORY MODELS
(MPRM)
USER'S GUIDE
U.S. Environmental Protection Agency
Office of Air Quality Planning and Standards
Emissions, Monitoring, and Analysis Division
Research Triangle Park, NC 27711
August 1996
-------
EPA-454/B-96-002
Replaces: EPA-454/B-94-020
DISCLAIMER
The information in this guide has been reviewed by the U.S. Environmental
Protection Agency (EPA), and approved for publication as an EPA document. Mention of
trade names or commercial products does not constitute endorsement or recommendation for
use.
The following trademarks appear in this guide:
F77L is a registered trademark of Lahey Computer Systems. Inc.
IBM is a registered trademark of International Business Machines
Microsoft is a registered trademark of Microsoft Corp.
UNTVAC is a registered ^trademark of Unisys Corp.
VAX/VMS is a registered trademark of Digital Equipment Corp.
WordPerfect is a registered trademark of WordPerfect Corp.
11
-------
EPA-454/B-96-002
Replaces: EPA-454/B-94-020
PREFACE
This document revises and replaces the October 1994 MPRM User's Guide. The
revisions reflect necessary changes associated with the August 1995 revision of Appendix W
to 40 CFR Part 51; these changes are implemented in the revised MPRM (dated 96225).
This guide as well as the source code, executable, and test case files for MPRM are available
for downloading from the EPA Technology Transfer Network (TTN), Support Center for
Regulatory Air Models (SCRAM) electronic bulletin board.
The modular design of MPRM facilitates the ready adaptation of the processor to
changes in technology. Consequently, it is anticipated that MPRM will be updated as
necessary to accommodate new input/output formats for meteorological data, new dispersion
models, and new processing techniques.
This guide was prepared using WordPerfect 5.1 word processing software and, as
such, is available in both hard copy and soft (electronic) copy. Hard copies of the user's
guide are available from the National Technical Information Services (NTTS), Springfield,
VA 22161 (phone (703) 487-4650); ask for NTTS document No. PB96-180518. Copies of
the user's guide in WordPerfect 5.1 format may be obtained from the TTN SCRAM bulletin
board; phone (919) 541-5742.
111
-------
EPA-454/B-96-002
Replaces: EPA-454/B-94-020
ABSTRACT
The Meteorological Processor for Regulatory Models (MPRM) is a general purpose
program used to process meteorological data for use in EPA recommended air quality
dispersion models. Capabilities include quality assessment of meteorological data, detailed
report generation, and the ability to process a variety of meteorological data bases including
both on-site (user collected) and National Weather Service (NWS) meteorological data.
MPRM is comprised of three processing stages. Stage 1 (extraction and quality
assessment) retrieves meteorological data from various storage media provided by the user
(e g magnetic tape, floppy disk, and CD-ROM) and conducts the quality assessment of
these data. The stage 1 report files provide listings of missing, suspect, and invalid data.
These reports provide necessary information allowing users to correct problem data prior to
its use in modeling. Stage 2 merges, the corrected stage 1 data from the various MPRM
pathways - upper air (UA), surface (SF) and on-site (OS). The third and final stage
performs the necessary processing to create a meteorological data file for use in a dispersion
model selected by the user.
MPRM supports the following air quality dispersion models which are recommended
by EPA for use in regulatory applications (Appendix W to 40 CFR Part 51): BLP,
CAIINE-3, CDM 2.0, COMPLEX1, ISCST, ISCLT, RAM, RTDM, and VAULEY.
IV
-------
EPA-454/B-96-002
Replaces: EPA-454/B-94-020
TABLE OF CONTENTS
Disclaimer . . ii
Preface iii
Abstract iv
List of Figures viii
List of Tables ix
Revision History x
Acknowledgments . . . xi
1 Introduction 1-1
1.1 Relationship to Modeling Guidance . . 1-1
1.2 Sources of Meteorological Data . . . 1-2
1.3 Importance of Quality Assessment . . 1-2
1.4 Missing Data . . . 1-2
1.5 Support for ISC3 Deposition Estimates . . 1-3
1.6 MPRM Syntax . . 1-3
1.7 Stages of Processing 1-4
1.8 Getting Started . . . . . . 1-4
1.9 Document Overview 1-5
2 Processing - Stage 1 and 2 2-1
2.1 Stage 1 - Extraction and Quality Assessment 2-1
2.1.1 Upper Air Data 2-1
2.1.2 Surface Data . . 2-4
2.1.3 On-Site Data 2-5
2.1.4 Contents of the General Report File 2-8
2.1.5 Contents of the Error/Message File 2-10
2.1.6 Summary of Stage 1 Output 2-10
2.2 Stage 2 Merge . . 2-11
3 Processing - Stage 3 3-1
3.1 Example Test Case . 3-1
3.1.1 OS Pathway Input 3-1
v
-------
EPA-454/B-96-002
Replaces: EPA-454/B-94-020
3.1.2 MP Pathway Input -, 3'2
3.2 Processing Options 3"4
3.3 Surface Characteristics 3-4
3.4 Stage 3 General Report File 3'6
3.5 Stage 3 Error/Message File 3'8
4 Scientific Notes « . 4-1
4.1 Stage 1
4.1.1 Averaging sub-hourly values
4.1.2 Quality Assessment
4.2 Stage 3 ..................................... ........ 4'6
4.2.1 Wind ...................................... 4'6
4.2.2 Temperature ................................. 4'7
4.2.3 Stability .............. ........... • • • ........ 4'8
4.2.4 Mixing height ............................ • • •
4.2.5 Surface Characteristics ..........................
4.3 Boundary Layer Parameters ............................... 4-11
4.3.1 Unstable Boundary Layer Parameters ................. 4-12
4.3.2 Stable boundary Layer Parameters ................... 4-15
4.3.3 Parameters at the Application Site ................... 4-17
5 Notes for Programers
5.1 Introduction .............................. ............ 5-1
5.2 Fortran Compatibility and Extensions ........................... 5-1
5.2.1 INCLUDE Statements ............... ............ 5-1
5.2.2 OPEN Statements .............................. 5-2
5.2.3 Character Conversion ............................ 5-3
5.2.4 System Date and Time ........................... 5-3
5.2.5 Extended Error Handling ......................... 5-3
VI
-------
EPA-454/B-96-002
Replaces: EPA-454/B-94-020
5.3 Compiling for Extended Memory 5-3
5.3.1 Lahey F77L-EM/32 Compiler 5-3
5.3.2 Lahey Fortran 90 Compiler 5-5
6 Trouble Shooting . 6-1
6.1 Abnormal Job Termination 6-1
6.2 Interpreting Runtime Error and Warning Messages . 6-1
6.3 Other Runtime Problems 6-2
6.3.1 SF W43 SFLEVS:OVRPNCH 11 6-2
6.3.2 Missing Records 6-3
6.3.3 UA Processing not Always Needed 6-3
6.3.4 Hourly Label for On-site Data 6-3
6.3.5 Hourly Labels - On-site versus NWS Data 6-3
6.3.6 Floating Point Errors in Stage 3 6-4
7 References 7-1
Appendices
A. Summary of Keywords
B. Input Syntax
C. Variable Names and Default Range Checks
D. Example Test Cases
E. Error and Warning Messages
F. Data File Formats
G. Glossary
vu
-------
EPA-454/B-96-002
Replaces: EPA-454/B-94-020
TJST OF FIGURES
1-1 Overview of processing stages within MPRM 1-6
2-1 Report file for extraction and QA of surface data 2-15
2-2 Summary of Stage 1 audit results for UA, SF, and OS pathways 2-17
2-3 Extract from Stage 1 error/message file for the SF pathway 2-18
2-4 Extract from the Stage 2 (MERGE) report file 2-20
3-1 Report file for Stage 3 processing 3"18
3-2 Partial listing of the error/message file for example with trace option enabled . 3-20
4-1 Example Stage 1 Error/Message Report Tracking Modifications to UA File ... 4-5
6-1 Example report file for extraction and QA of mixing heights 6-5
6-2 Example error/message file for extraction and QA of mixing heights ....... 6-6
viu
-------
EPA-454/B-96-002
Replaces: EPA-454/B-94-020
LIST OF TABLES
2-1 Runstream for the extraction and QA of upper air data 2-12
2-2 Runstream for the extraction and QA of NWS surface data 2-13
2-3 Runstream for the extraction and QA of on-site data 2-14
2-4 Runstream for merging of NWS mixing height and surface data with on-site data 2-19
3-1 Runstream for processing of data for use in wet deposition modeling 3-10
3-2 Dispersion models supported by MPRM 3-11
3-3 Information for selecting processing options on the MP VBL input image . . . 3-12
3-4 Albedo of natural ground covers by land use and season 3-13
3-5 Daytime Bowen ratio by land use and season 3-14
3-6 Surface roughness length by land use and season 3-15
3-7 Average anthropogenic heat flux and net radiation for several urban areas . . . 3-15
3-8 Surface characteristics used in example test case 3-16
3-9 Subroutines associated with Stage 3 processing options . 3-17
4-1 Stability classification methods implemented in MPRM 4-9
5-1 MPRM source code files 5-7
rx
-------
EPA-454/B-96-002
Replaces: EPA-454/B-94-020
REVISION HISTORY
Version 1.1, MPRM (dated 89142), was released and made available on the SCRAM
Bulletin Board in May 1989.
Version 1.2, MPRM (dated 90045), was released in February 1990. This release
corrects a problem in the STAGES processing of calm conditions. Details are provided in
MPRM Model Change Bulletin #2 (MCB#2) on the SCRAM Bulletin Board.
Version 1.3, MPRM (dated 93140), was released in May 1993. This release
corrected 'bugs' in all three stages of MPRM processing and incorporated revisions to
enhance user-friendliness. Details are provided in MPRM MCB#3 on the SCRAM Bulletin
Board.
MPRM (dated 96225), was released in August 1996. This release implemented
changes to MPRM associated with the August 1995 revision of Appendix W to 40 CFR Part
51. Details are provided in MCB#4 on the SCRAM Bulletin Board.
-------
EPA-454/B-96-002
Replaces: EPA-454/B-94-020
ACKNOWLEDGMENTS
Roger W. Erode, John S. Irwin, and James O. Paumier coauthored the first release of
the user's guide in July 1988. Other contributors to the July 1988 release included: Carol
Brown; Dr. P.M. Barlow; Phil Boone; and Russell F. J^ee. The user's guide was revised,
converted to Wordperfect, and re-released in October 1994; Desmond T. Bailey was the
project officer for these activities. Dr. Bailey also served as editor for the August 1996
revisions to the user's guide. Peer review for the August 1996 document was provided by
Roger W. Erode (PES), Tom Coulter (U.S. EPA, OAQPS), and Jerry Crescenti (U.S. EPA,
NERL).
XI
-------
-------
SECTION 1
INTRODUCTION
The Meteorological Processor for Regulatory Models (MPRM) is a general purpose
program used to process meteorological data for use in EPA recommended air quality
dispersion models. Capabilities include quality assessment of meteorological data, detailed
report generation, and procedures for processing a variety of meteorological data bases
including both on-site (user collected) data and National Weather Service (NWS)
meteorological data.
1.1 Relationship to Modeling Guidance
MPRM supports most of the refined air quality dispersion models preferred by EPA
for use in regulatory applications. These models are described in Appendix W to 40 CFR
Part 51. A list of the models supported by MPRM is provided in Section 3.2.
MPRM includes enhancements which support requirements promulgated in the August
1995 revision of Appendix W to 40 CFR Part 51. These enhancements are: 1) coding to
implement the Solar Radiation Delta-T (SRDT) method of stability classification and 2)
algorithms to calculate boundary layer parameters which are used in the revised Industrial
Source Complex (ISC) model to estimate deposition velocity and plume depletion. A related
enhancement, not part of the August 1995 revisions, involves the processing of hourly
precipitation data for use in wet deposition calculations.
The data processing methods incorporated in MPRM implement the recommendations
of the "On-Site Meteorological Program Guidance for Regulatory Modeling Applications"
(U.S. EPA, 1987). These recommendations include methods for estimating Pasquill-Gifford
(P-G) stability categories from on-site measurements, and procedures for processing wind
data to obtain the scalar averaged wind direction and the standard deviation of the wind
direction. Guideline recommendations for processing wind, temperature, stability category
and mixing height are implemented as default procedures in MPRM; these are identical to
the default procedures employed in RAMMET and PCRAMMET.
The MPRM user's guide provides necessary information related to the QA and
processing of meteorological data for use in dispersion modeling - it is not intended to
provide guidance on the regulatory aspects of dispersion modeling - for such guidance, user's
are referred to Appendix W to 40 CFR Part 51. Users should refer to the appropriate model
user's guide for information related to specific models, to the on-site guidance (U.S. EPA,
1987) for information on meteorological monitoring, and to the "Quality Assurance
Handbook for Air Pollution Measurement Systems, Volume IV Meteorological
Measurements" (U.S. EPA, 1995) for guidance on the quality assurance of meteorological
measurements.
1-1
-------
1.2 Sources of Meteorological Data
National Weather Service (NWS) meteorological data are available from the National
Climatic Data Center (NCDC) in Ashville, NC (http://www.ncdc.noaa.gov). These data are
available on a variety of storage media (magnetic tape, floppy diskette, and CD ROM).
MPRM will process data from a selected subset of NCDC formats as follows: TD-5600
(upper air data); TD-9689 (estimated mixing heights); TD-3240 (hourly precipitation); CD-
144 (surface data).
Selected NCDC data are also available on the EPA Technology Transfer Network .
(TTN) SCRAM Bulletin Board. These include NCDC estimated mixing height data and
NWS surface data. The SCRAM formats for both of these data types differ from the NCDC
formats; e.g., the SCRAM surface data are stored in a compressed format which includes
only those variables that are necessary for dispersion modeling. The NCDC and SCRAM
formats applicable to MPRM are described in Appendix F.
Use of site specific (on-site) meteorological data has always been encouraged for
applications of dispersion modeling and is required for some regulatory applications; e.g.,
complex terrain (Appendix W to 40 CFR Part 51). On-site meteorological monitoring
programs conducted in support of such requirements result in data files with varying formats.
The formats for these files can be included in the input runstream to MPRM. This provides
flexibility within MPRM for processing these generic format data files. This capability is
discussed in Section 3.
1.3 Importance of Quality Assessment
MPRM was designed with built in procedures to quality assess meteorological data
prior to its use in modeling. The QA process flags suspect and/or invalid data and facilitates
the correction of such data. In many instances this may be the only QA performed on the
meteorological data used in modeling. Given the types of decisions that may be based on
modeling estimates, one should not wait until after the fact (i.e., after the modeling is
completed) to QA the meteorological data - it is better to be informed as to the quality of the
data before hand. In some instances, a particular data set may be rejected for failure to meet
QA criteria.
1.4 Missing Data
Short-term dispersion models require hourly meteorological data and in many cases
will not accept missing data; i.e., there must be a valid record for every hour in the analysis
period. Users should always check to see that the meteorological data set they intend to use
is complete (does not contain missing data). If the data are not complete, and the model they
intend to use does not allow missing data then procedures to complete the data base will need
to be implemented. Such procedures are often case specific and may require prior approval
by the permit granting authority. For regulatory applications, substitutions, to fill hi missing
1-2
-------
data, may not exceed 10 percent. Users are referred to the section on 'Completeness
Requirements' in (U.S. EPA, 1987) for more detailed guidance on handling missing data (see
also Sections 6.3.2 and 6.3.6).
Note, in preparing to process data with MPKM, one needs to review the values used
(in the raw input data file) to identify missing (null) data to ensure correspondence with the
MPKM missing value indicators listed in Appendix C. If the values do not agree, the default
missing value indicator(s) should be changed to correspond with the values used in the data
file (see Section 2.1). Failing this, MPRM may interpret missing data as being out of range.
1.5 Support for ISC Deposition Estimates
MPRM includes the following enhancements in support of ISC deposition estimates:
Algorithms for Boundary Layer Parameters - Estimates of two boundary layer
parameters (the friction velocity and Monin-Obukhov length) are required in the revised ISC
short-term model (ISCST) for use in deposition and plume depletion calculations. MPRM
includes the necessary algorithms for estimating these parameters. The friction velocity (u*)
is a measure of the stress due to wind shear at the earth's surface. The Monin-Obukhov
length (L) is a stability parameter that relates the friction velocity to the transfer of heat.
The computations require user specified surface characteristics including albedo, Bowen
ratio, and roughness length. The surface characteristics are allowed to vary with time of
year and/or wind direction (sector).
Processing of Hourly Precipitation Data - Hourly precipitation data are required in
ISCST for use in estimating wet deposition. To support wet deposition estimates, MPRM
has been enhanced to accommodate processing precipitation data available on SAMSON
CD_ROM and TD-3240 precipitation data files both of which are available from the National
Climatic Data Center (NCDC).
1.6 MPRM Syntax
We refer to the input necessary to run the MPRM processor as the input run stream
or simply run stream. The run stream consists of several 80-character images, each of which
begins with a 2-character group, called a pathway; this is followed by a 3-character group,
called a keyword.
Each input run stream can be thought of as a sequence of 80-character images. Each
image consists of two or more fields. The fields presented within the 80-character
image are considered FREE format; that is, proper interpretation of afield is not
dependent on column position. However, the fields must be separated by commas or
spaces.
1-3
-------
Pathways - The logic, and hence the input to the processor, is divided into six
functional areas called pathways. These are identified by two-letter acronyms as follows:
• JB - processes that affect or pertain to the entire job
• UA - processes related to NWS upper air data and NCDC mixing height estimates
• SF - processes related to NWS hourly surface data
• OS - processes related to site specific (on-site) meteorological data
• MR - processes related to the merging of meteorological data
• MP - processes related to creating meteorological data files for use in dispersion
modeling
The structure of the input is such that, with some experience, one should be able to
interpret an input run stream with minimal effort. The keywords associated with each of the
pathways are summarized in Appendix A; note that some keywords may be used with
several pathways and that some keywords are mandatory while others are optional. The
keywords and associated input syntax are described in Appendix B. Together these two
appendices should enable the user to construct customized run streams.
1.7 Stages of Processing
MPRM is packaged in two separate executable programs (STAGE1N2.EXE and
STAGE3.EXE) comprising three processing stages (see Figure 1-1). The three stages
implement the following processes:
1. Extract and quality assurance
2. Merge
3. Process and create files for use in dispersion modeling
1.8 Getting Started
Example input ninstreams, meteorological data files, and MPRM output and report
files have been packaged with the test cases for MPRM and are available, along with the
executables for MPRM, for downloading from the EPA Technology Transfer Network
(TTN) Support Center for Regulatory Air Modeling (SCRAM) electronic bulletin board. If
you have not already done so, these files should downloaded and copied to a working
directory. The instructions in Sections 2 and 3 refer to the example test cases which should
1-4
-------
be especially helpful to new users in negotiating the learning curve for MPJRM. Experienced
users may wish simply to exercise the test cases and refer to Sections 2 and 3 for reference.
It should be noted that the input run streams are sufficiently long and complex to
preclude direct input from the keyboard. Instead, a text editor should be used to create the
necessary input files. These files should consist of standard ASCII characters only. Note,
some text editors differentiate between document files, which contain special non-ASCII
control characters, and non-document files, which are composed of ASCII characters only.
For such editors, be sure to select the non-document mode of editing.
1.9 Document Overview
Section 2 provides instructions and examples for Stage 1 (Extraction and Quality
Assessment) and Stage 2 (Merge). Section 3 provides instructions and examples for Stage 3
(Creating files for use in modeling). Section 4 provides information on the scientific basis
for the processing algorithms in Stage 3. Section 5 provides instructions for compiling the
source code and other information of interest to programmers. Section 6 provides
information on the interpretation of error messages.
There are seven appendices as follows: Appendix A presents a summary of the
keywords used in defining the input to the processor and denotes those that are mandatory
and those that are optional. Appendix E describes usage, limitations, and syntax of each
keyword. Appendix C provides information on the meteorological variables processed on
each of the pathways giving the variable name, a brief description, units, missing value
indicator, and default upper and lower bounds. Appendix D describes the test cases for
MPRM (dated 96030) and provides selected examples. Appendix E describes various types
of messages that are generated by the processor. Appendix F describes the computer file
formats used for the storage of the extracted data. Appendix G is a glossary of commonly
used terms associated with processing of meteorological data.
1-5
-------
METEOROLOGICAL PROCESSOR
FOR
"REGULATORY MODELS
STAGE1N2.EXE
STAGE 1
PROCESSING
Extract and Quality
Assess Data
STAGE 2
PROCESSING
Combine (Merge)
Data Files
STAGE3.EXE
STAGE 3
PROCESSING
Create Data
File for Modeling
Figure 1-1. Overview of processing stages within MPRM.
1-6
-------
SECTION 2
PROCESSING - STAGES 1 AND 2
2.1 STAGE 1 PROCESSING - EXTRACTION AND QUALITY ASSESSMENT
Example input runstreams and report files have been packaged with the test cases for
MPRM and are available, along with the executables for MPRM, for downloading from
SCRAM. If you have not already done so, these files should downloaded and copied to a
working directory; see the instructions on 'Getting Started' in Section 1.8.
Selected example test cases provide the basis for the instructions which follow.
Additional information on all of the example test cases is provided in Appendix D. It is
hoped that review of these materials will be an effective means of completing the learning
curve for MPRM. In addition, the following additional material should be useful: Appendix
A, which provides a listing of the keywords available to each pathway and Appendix B,
which provides definitions and the input syntax for the keywords.
Note, in preparing to process data with MPRM, one needs to review the values used
(in the raw input data file) to identify missing (null) data to ensure correspondence with the
MPRM missing value indicators listed in Appendix C. If the values do not agree, the default
missing value indicators) should be changed to correspond with the values used in the data
file (see text on use of the CHK keyword in Sections 2.1.1, 2.1.2, and 2.1.3). Failing this,
MPRM may interpret missing data as being out of range. There are no fixed standards for
missing (null) value indicators for meteorological data; consequently, this check should be
made for all data regardless of the pathway.
2.1.1 Extraction and QA of Upper Air Data
An example runstream illustrating the extraction and QA of upper air data is
presented in Table 2-1. As necessary (e.g., to illustrate an option not employed in a test
case) additional images have been added to the input runstreams. These additional images
are identified by italics. In addition, keywords are highlighted in bold when they are first
introduced. This is done to alert the reader that material related to a new keyword is being
presented. The same keyword may appear multiple times later on in the text, but these later
occurrences will normally not be highlighted unless new information pertaining to the
keyword is presented.
The input images to the processor have a structure, which when understood, facilitates
construction of customized runstreams. The three-character keywords are, for the most part,
abbreviations of the actions that this input should invoke.
2-1
-------
Consider the first three input images shown in Table 2-1.
! 2-character pathway
| |— 3-character keyword
I I
JBSTA
JB OUT DISK TEST121.RPT
JB ERR DISK TEST121.ERR
The first image JB STA indicates the start of the input images for the JB pathway.
The STA keyword, although optional, helps to structure the input and therefore, is retained
for purposes of instruction. The second image is also optional; the keyword OUT in this
image defines the name for the general report file. By default, if the general report file is
not defined, all print is routed to logical unit 6. On a mainframe computer, this is the
default printer for batch processing; on a PC, the default for unit 6 is the screen. To ensure
that the report file is retained it should always be defined following the OUT keyword. The
third image contains the mandatory keyword ERR and provides the name of the
error/message file. The contents of this file are described in Section 2.1.5.
The JB RUN image is optional and is used for checking syntax. When this image is
present, the MPRM processor checks the entire runstream for syntax and then stops. This is
a quick way to check the runstream for syntax errors. To actually process data, simply
remove this image from the runstream. The fifth image contains the mandatory keyword
EIN and signals the end of the input data for the JB pathway.
Instructions to MPRM for processing of upper air data begin with the UA STA input
image. This is followed by images providing necessary information for accessing these data.
The UA INI image provides information related to rawinsonde data files; these files contain
data for twice per day vertical profiles of pressure, temperature, humidity, wind speed, and
wind direction. These data are contained on a magnetic tape identified by the logical name
'TAPE10'. The format field '5600VB' indicates that the data are written using the NWS
TD-5600 format with a variable blocked structure. The 'ASCII' field identifies the character
set, in this case, American Standard Code for Information Interchange. The '24157' field is
the station identification number. Procedures for accessing tape files and assigning logical
tape names, etc. are system dependent.
The UA TOP image applies to the profile data defined in the UA INI image. It
instructs the processor to extract and process upper air data at or below 7000 meters. This is
referred to as the clipping height; all data above 7000 meters are "clipped," i.e., disregarded.
The default value for the clipping height is 5000 meters.
2-2
-------
The UA IN2 image provides necessary information for accessing twice per day
estimated mixing height data. The 'USER' field indicates that the data are contained in a
user disk file having the filename 24157-94.MDL The character string following the file
name, '(A5,3I2,1X,I5,13X,I5)' is the Fortran format statement which will be used by
MPRM to read the mixing heights. The last item in the UA IN2 input, the '24157' field, is
the station number for the NWS upper air site.
The UA LOG image provides the station identification number, the latitude and
longitude (in decimal degrees), and the number of hours to be subtracted to convert the times
given in the data file to Local Standard Time (LST). The latter adjustment depends on the
location and the type of data being extracted. For an east coast location, the conversion to
LST requires an adjustment of 5 hours (i.e., EST = GMT - 5); for a west coast location the
adjustment is 8. The LOC keyword is also used on the SF and OS pathways.
The UA EXT image, defines the starting and ending times for the extraction. The
sequence year, month, and day must be observed in specifying extraction dates. The year
may be defined by all four digits or "by the last two digits only. In the example, an extra day
has been added to the beginning and end of the extraction to facilitate subsequent processing
of the mixing heights. This is necessary because MPRM (Stage 3) uses an interpolation
scheme to estimate hourly mixing heights based on the twice daily values for the preceding
and following days. The EXT keyword is also used on the SF, OS, MR, and MP pathways.
The UA IQA and UA OQA images define the input and output files for the QA
processing. The contents of these two files are identical in the current version of MPRM
(see Appendix F, page F-16). The additional (redundant) file is included in MPRM to
facilitate the possible incorporation of automatic substitution procedures at some point in the
future. The additional file would then be used to store the modified data.
The UA CHK image provides a means for redefining (overriding) the default settings
used during QA. The information following the CHK keyword provides the variable name,
range check switch, missing value flag, and the upper and lower bounds for the QA.
Variable names are unique four-character strings. Default settings for the variables
associated with the UA-pathway are given in Table C-l in Appendix C. The units for the
upper and lower bounds must be the same as those employed within the processor and
defined in Appendix C. An example input runstream image follows.
UACHKUAPR 1 -9999 4000 10999
I j I I . _ . .
I | | ' Upper bound of range
\ I . I
I | ' Lower bound of range
• Missing value indicator
Range check switch
Name of variable
2-3
-------
In the example given, UAPR is the variable name for the upper air atmospheric
pressure. The upper and lower bounds for this variable are in tenths of millibars. Hence,
the lower bound of 4000 translates to 400 mb; the upper bound translates to 1099.9 nib. The
range check switch tells the processor how to'perform the range" check. A value of 1
excludes the upper and lower bounds while a value of 2 includes them. In the example, the
range check switch is set to 1. Hence, a value of 400 mb would be considered out of
bounds, and a warning message would be listed to the error/message file.
The CHK keyword is unique in that the information provided following the keyword is
remembered by MPRM and is available to subsequent stages of processing. This information
is written to header records associated with the quality assessment input, and output files.
Tlie processor incorporates the range check information into the header record that is written
to the OQAfile. In subsequent quality assessment checks, MPRM will use the range check
information provided in the header records. The Stage 1 QA is often an iterative process
and, consequently, the range checks can be overridden as necessary; this is especially
important \vith on-site data where the default range checks may not always be applicable.
For example, an initial QA pass of on-site data (using the default range checks) will often
flag values which upon further investigation are determined to be valid for the particular site.
In such cases, one or more follow-up QA passes using revised range checks may be
necessary to clearly segregate valid and invalid data.
The last image in Table 2-1, the JB END image, is an alternate means for identifying
the end of the input runstream. The processor assumes that the end of the input data occurs
whenever it encounters an end-of-file (EOF) or the JB END input image.
2.1.2 Extraction and QA of Surface Data
An example runstream illustrating the extraction and QA of NWS surface and
precipitation data is presented in Table 2-2. New keywords illustrated in this example and
discussed in the following include: INS, ADD, and TRA.
The SFIN2 image in this example provides necessary information for extracting the
surface data: the file name (24155-94.DAT), the file format (CD144FB), and the station
identifier (24155). The character string for the file format 'CD144FB' indicates that this is
an NCDC CD-144, fixed block (FB) data file. Other data formats recognized by the surface
pathway are SCRAMFB and SAMSON. These formats are described in Appendix F.
The SF INS image provides necessary information for extracting the precipitation
data: the file name (24155-94.PPP), the file format (TD3240FB), and the station identifier
(992415). The station identifier in the INS image is a six-digit number and should not be
confused with the WBAN number provided in the IN2 input image. The station identifier is
recorded in columns 4-9 in each TD-3240 record and includes a two-digit state code ('99' is
a dummy) and a four-digit number assigned by NCDC ('2415' is also a dummy).
2-4
_
-------
The SF AUD image adds the variable for present weather (PWTH) to the list of
default variables appearing in the audit report. Present weather might be useful in a
dispersion analysis if one anticipated that a pollutant might be "washed out" of the
atmosphere during a precipitation event, like a ram shower, and therefore it would no longer
be available for transport further downwind. Such information would be relevant in
attempting to compare values of gaseous concentrations observed versus concentration values
estimated by a dispersion model which makes no provision for pollutant washout.
The default audit variables for the SF-pathway are: sea-level pressure, station
pressure, ceiling height, sky cover, horizontal visibility, dry bulb temperature, wind
direction, and wind speed. The optional AUD input image need only be included when audits
are desired for one or more non-default variables. Several variables can appear on one AUD
input image, so long as the image does not exceed 80 characters. The AUD input image can
be repeated as often as necessary. The AUD image differs from the CHK image in that it is
not remembered by the MPRM processor; i.e., the AUD image must be repeated each time
QA is performed.
The SF TRA image turns the trace option on for the variables indicated: present
weather (PWTH), pressure (PRES), ceiling height (CLTH), total and opaque sky cover
(TSKC), temperature (TMPT), wind direction (WD16) and wind speed (WIND). The trace
option writes a record to the error/message file indicating each occurrence of a
missing value.
The TRA keyword should be used with caution especially if one is not familiar with
the data being processed. SCRAM surface data, for example, do not include present weather
or pressure. Consequently, if the example SF TRA image were used with a SCRAM surface
file, it would result in at least two missing data messages (records) for each hour.
2.1.3 Extraction and QA of On-site Data
Site specific, user collected meteorological data do not have a standard format; in
fact, the variety of measurements possible preclude development of such a standard. This
being the case, MPRM has been designed such that the formats for these files can be
included in the input runstream to MPRM. This provides flexibility within MPRM for
processing generic format meteorological data files. The following rules apply:
• Observations (records) must be ordered sequentially
• There must be no missing records
• Each record must contain data for the same variables and in the same order
• The data must be in a form such that it can be read using a Fortran Format Statement
2-5
-------
An example runstream illustrating the extraction and assessment of on-site
meteorological data is presented in Table 2-3. New keywords illustrated in this example and
discussed in the following include: AVG, HGT, DTI, MAP, and IMT.
The OS AVG image defines the maximum number of data records expected for each
hour; The default is 1. In the example, the value '4' following the AVG keyword indicates
that up to four data records may be provided for each hour. This would be the case for a
data file created by a data logger using 15-minute averaging. MPRM will read on-site data
records until a new hour is encountered. Hourly averages are computed if at least 50 percent
of the sub-hourly data are present, otherwise the hour is flagged as missing. The AVG input
image is only needed for the initial processing of on-site data. Thereafter, only hourly
averaged data are available for processing. Users should note that MPRM assumes that the
label assigned to an hourly observation or hourly average is the integer value for the hour
beginning; e.g., an hourly average for the period 01:00 to 02:00 should be assigned a time
label of 01.
The OS HGT image provides the measurement heights for multi-level variables, if
any. This information would be necessary if the on-site data base included measurements
from a meteorological tower instrumented at several levels. The image provided in the
example indicates that measurements are available for 2 levels, 20 m and 100 m.
The OS DTI image provides the measurement heights for vertical temperature
difference (Delta-T) data, if any. In this example, Delta-T would have been measured
between 2 and 20 m. MPRM will handle up to three temperature difference measurements
(DTI, DT2, and DT3). The measurement heights for each are entered as per the example
for DTI. In MPRM the measurement heights defining the vertical temperature difference are
independent of the measurement heights for the multilevel variables.
The OS MAP image lists the names of the on-site variables to be extracted and may
be repeated depending on the structure of the data file. MPRM allows considerable
flexibility in the structure of on-site data files; however, the following restrictions on file
organization apply:
• The first two fields in the first record for each time period should contain the date and
time (the order is not important). The tune must, at the very least, define the hour to
be associated with the observation. All date and time data must be capable of being
read using INTEGER format.
• The meteorological data should follow the date and time; these data may be continued
on additional records, as necessary up to a maximum of 20 records per time period.
No more than 40 values can be given in any one record.
2-6
-------
The OS MAP DAT01 image in the example indicates that the first record contains
data for the following variables: year (OSYR), month (OSMO), day (OSDY), hour (OSHR),
wind speed (WS01), temperature (TT01), vertical temperature difference (DT01), wind
direction (WD01), sigma rheta (SA01), and insolation (INSO). The OS MAP DAT02 image
indicates that the second record contains data for WD02, WS02, SA02, and TT02. The
complete list of variables available for the OS pathway is given in Table C-3 in Appendix C.
The OS EMT images provide the Fortran formats to be employed in reading each
record. The OS FMT DAT01 image shown in the example uses a '4X, 412.2' format to
read the first four fields: year, month, day, and hour. The formats given in the FMT image
are used by the processor in listing the data values to the file specified in the OQA image.
By using 412.2 rather than 412 in our format specification, the date/time group, '94110101'
in the first record would be written to the OQA file as '94110101'. Using 412 in the format
specification, the first record would be written as '9411 11'; i.e., the leading zeros are lost
with the 412 format. It is easier to read with the leading zeros; therefore, use of 12.2 style
format is recommended hi specifying the format for date and time in the FMT image.
Not all variables appearing in the input data file have to be mapped. Only those
variables the user believes will be useful in the final application are required, whether it be
dispersion modeling or other analyses. With proper usage of the X or T format specifier,
variables can be skipped; with careful usage of the / format specifier, entire records can be
skipped. The format statements defined by the FMT input images are used in all processing
involving reading or writing of the on-site data from data files. Hence, if X, T or / format
specifiers have been employed, the information skipped in the original raw data file will
appear as blanks in subsequent files.
The format statements defined by the FMT input images are used in all
processing involving reading or -writing of the on-site data from data files.
If in the course of quality assessment it is found necessary to edit the on-site
data file, be sure not to alter the data format, or read errors mil occur in
subsequent attempts to process the data.
The OS CHK images redefine the missing value flag and/or the default upper and
lower bounds for the QA of the indicated variables: insolation (INSO), vertical temperature
difference (DT01), and sigma theta (SA).
The OS CHK DT01 image resets the default upper and lower bounds for the QA of
vertical temperature difference from -200 (lower) and 500 (upper) to -10 (lower) and 5
(upper). Note, the units for the upper and lower bounds are (°C). The magnitude of the
vertical temperature difference depends, among other things, on the elevation and depth of
the layer being monitored. Consequently, the QA of vertical temperature difference data mil
almost always require a change in the default upper and lower bounds; this may involve
2-7
-------
some experimentation. Note, the QA ofDTOl involves comparisons of temperature
differences; this is different than the QA procedures for upper air data which involves
comparisons of lapse rates.
The OS AUD image adds the variables for insolation (TNSO) and vertical temperature
difference (DT01) to the list of default variables appearing in the audit report. The default
variables for the OS pathway are: mixing height, wind speed, wind direction, aA, 0%, sea
level pressure, station pressure, ceiling height, and sky cover. The optional AUD input
image need only be included when audits are desired for one or more non-default variables.
2.1.4 Contents of the General Report File
The general report lists the input and output files, provides a summary of the kinds
and frequency of messages, and a table summarizing the results of the quality assessment of
the data. The general report files for Stage 1 processing for the three pathways UA, SF, and
OS will all have similar information; An example from the Stage 1 extraction and QA for
the SF pathway is shown in Figure 2-1.
The first page of the general report provides information on the status of the
processing environment prior to actual processing. The first item is the MPRM heading; this
includes the MPRM version date and the date and time of the processing. This heading is
standard and appears at the top of all output pages. Following the heading are the names of
files to be used and the status of the pathway data files (OPEN or NOT OPEN). Other
information provided includes: extraction dates, site identifier, and the latitude and longitude.
The remainder of the report provides: the MPRM message summary table; warning
messages, if any; error messages, if any; and a summary of the audit results. The message
summary table, in this example, indicates that 11 informational messages were generated (7
on the JB pathway and 4 on the SF pathway). There were no warning or error messages.
The audit for the surface data indicates that 720 observations for 11 variables were
extracted. All 720 observations (100 percent) were accepted as valid for 5 of the variables.
Audit results for the other surface variables indicate that one or more records were found
with missing data; the number of 'bad' records (hours) ranges from 1 record (hour) for total
sky cover (TS) to 10 records (hours) for ceiling height (CLHT). The total number of bad
records is 26; this is a worst case since some records may have multiple counts (more than
one missing value). Bad records are traced in the error/message file providing the variable is
specified following the TRA keyword in the input runstream.
There are two 'double duty' SF variables included in the audit report, TSKC and
PWTH. The four-character variable TSKC contains information on total and opaque sky
cover. During processing, MPRM splits this double duty variable into its two component
parts, TS (total sky cover) and KS (opaque sky cover). The two parts are listed on separate
2-8
-------
lines in the audit report. The variable PWTH is another example where two fields of
information are stored together. PWTH contains information on prevailing (PW) and
secondary weather (TH) occurring during the observation. All 'double duty' variables are
two integer variables which have been combined to form a single integer variable (see Table
C-2 for a list of these variables). These combined variables are separated prior to QA and
any subsequent processing.
The footnotes to the audit report for the surface data indicate the number of calms
(30) and provide results for audits involving comparisons of two variables. These
comparisons check for invalid combinations of two variables; e.g., the dew point temperature
should never exceed the dry bulb temperature. The following results are noted:
Zero wind speed with non-zero wind direction 0
Dew point greater than dry bulb temperature 0
Precipitation and weather mismatch 6
A summary of the Stage 1 audit results for the UA, SF, and OS pathways is presented
in Figure 2-2. The audit provides information on the quality of the data as extracted -
mixing heights on the UA pathway, surface data on the SF pathway, and site sealers and site
vectors on the OS pathway. Information is provided for all default variables and any
variables specified in an input runstream following the AUD keyword. Missing value flags
and the upper and lower bounds used for checking the data are also indicated for each of the
variables. These will normally be default values unless overridden in an input runstream
following the CHK keyword.
On the UA pathway, only the twice-daily mixing height values (NCDC TD-9689 data)
are audited by default. However, other audit variables can always be added with the AUD
keyword (the syntax of the AUD input image is given in Appendix B). The audit report in
this example shows that 32 values of morning (UAM1) and afternoon (UAM2) mixing
heights were extracted and that all were accepted.
The audit information for the SF pathway (see violation summary for surface data in
Figure 2-2) is the same as that given in Figure 2-1 and discussed above.
The audit information for the OS pathway indicates that there are at least one (i.e.,
the four missing values occurred in the same hour/record) and possibly as many as four 'bad'
records (i.e., the four missing values occurred in four different hours/records. More than
likely, the four missing-value flags all occurred hi the same hour (record). However, this
would have to be verified by examining the error/message file. In addition to the missing
records, the audit also indicates that the SA site vector (i.e., Sigma Theta) exceeded the
upper bound (50 degrees) on 15 occasions.
2-9
-------
2.1.5 Contents of the Error/Message File
An extract from the error/message file from the Stage 1 extraction of the surface data
is provided in Figure 2-3., The first ten records provide information about the job and what
data were extracted. Seven of these messages are associated with the JB pathway and three
are associated with the SF pathway. The latter have to do with accessing the data files for
the surface observations and reporting how many observations were processed. The fourth
informational message associated with the SF pathway is an 'end-of-file' message and
appears at the bottom of the file.
The information related to 'bad records' begins with the llth record as follows:
30502 SF SFQASM: CIHT MISSING ON 94/11/01/02
This record indicates that ceiling height (CLHT) was missing for 02:00 on November 1,
1994. Other records are translated similarly. With the exception of a missing value reported
for surface pressure on 94/11/02/02,' all of the bad records occur on 94/11/01. This is
because the first 12 records in the surface file were deliberately altered for the purpose of
testing the QA procedures for missing data. Normally, one would expect that bad records
would be more randomly distributed throughout the data file. In any case, the bad records
should be corrected before proceeding to Stage 2. As this is an extract from a larger file, we
do not see all of the records that have been flagged in the QA. The full file, reproduced in
Appendix D (Figure D-16) contains the following:
Type of Message Number
Informational JB 7
Informational SF 4
Missing Data 26
Calms 30
Precipitation/Wx Mismatch 6
Total 73
2.1.6 Summary of Stage 1 Output
Stage 1 of MPRM produces three types of output files: a general report file, an
error/message file, and data files.
The general report summarizes the processing results and is typically only several
pages long. The contents of the general report file are discussed in Section 2.1.4.
The error/message file contains all the messages generated during processing and can
be quite large depending on the data file. Appendix E provides a listing of the various
messages associated with all stages of MPRM processing; there are nearly 100 different
messages possible. As the error/message file may be rather long, it may not always be
2-10
-------
practical or advisable to try to print it. The user should view the contents using a general
purpose text editor. A discussion of the structure and content of the error messages written
to the error/message file is provided in Section 6. Also within Section 6 is a discussion of
how the general report is altered when errors are encountered.
Two data files are created during the Stage 1 extraction and QA for the UA and SF
pathways. These are the raw extracted data file, defined by the IQA keyword, and the
quality assessed data file, defined by the OQA keyword. The contents of these two files in
the current version of MPRM is identical (see Appendix F, page F-16 for discription and
format of the IQA/OQA files for the UA pathway and pages F-17 and F-18 for the
description and format of the IQA/OQA files for the SF pathway). The Stage 1 QA for the
OS pathway creates only one data file containing the quality assessed data and defined by the
OS OQA input image.
2.2 STAGE 2 PROCESSING
The goal of the Stage 2 processing is to combine (merge) the quality assessed data
from two or more pathways for subsequent use in Stage 3 processing. The output from
Stage 2 is stored in an unformatted (binary) data file.
An example runstream for a Stage 2 merge of UA, SF, and OS data is presented in
Table 2-4. The MR OUT image in this example provides the file name for the merge
output. Other keywords in this example have been discussed in preceding examples.
The MR EXT image is optional. Specifying start and stop dates to be associated with
Stage 2 processing, this input provides a means for selecting the data to be included in the
merged data file. This might be useful if one wanted to create a merged data file for a
specific few days or months. If the MR EXT image is omitted, MPRM searches the OQA
files on each pathway for the earliest date. This date becomes the first day of merged data.
The last day of merged data acceptable is then defined as the first day plus 367. In other
words, omission of the MR EXT input allows up to 368 days of data to be merged, starting
from the earliest date encountered on all the input files.
2-11
-------
Table 2-1
Runstream for the Extraction and Quality Assessment of Upper Air Data.
JB STA
IB OUT DISK TEST121.RPT
JB ERR DISK TEST121.ERR
JB RUN
JB BIN
Start JB input
Defines name for general report file
Defines name for error/message file
Check for syntax only
Finish JB input
UA STA
UA INI TAPE TAPEIO S600VB ASCII 24157
UA TOP 7000
UA IN2 USER 24157-94.MK(A5,3I2,2X,I4,14X,I4) 24157
UA LOG 24157 117.53W 47.63N +8
UA EXT 941031 941201
UA IQA DISK IQAUA.121
UA CHK UAPR 1 -9999 4000 10999
UA OQA DISK OQAUA.121
UA FIN
JB END
Start UA input
Provides information for extracting
upper air data
Define clipping height
Provides information for extracting
mixing heights
Defines location of mixing height data
Defines time period for extraction of
mixing heights
Defines name for QA input file
(extracted data file)
Redefine default bounds for QA of
pressure (UAPR)
Defines name for QA output file
Finish UA input
End of runstream
2-12
-------
Table 2-2
Runstream for the Extraction and Quality Assessment of NWS Surface Data
JB STA
JB OUT DISK TEST122.RPT
JB ERR DISK TEST122.ERR
JB FIN
Start JB input
Defines name for general report file
Defines name for error/message file
Finish JB input
SF STA
SF IN2 DISK 24155-94.DAT CD144FB 24155
SF INS DISK 24155-94.PPP TD3240FB 992415
SF LOG 24157 118.85W 45.67N 0
SF EXT 94 11 01 94 11 30
SF IQA DISK IQASF.122
SF OQA DISK OQASF.122
SF ADD PWTH
SF TRA PWTH PRES CLHT TSKC TMPT WD16 WIND
SF FIN
Start SF input
Provides information for extracting
NWS surface data
Provides information for extracting
precipitation data
Defines location of NWS surface data
Defines time period for extraction of
surface data
Defines name for QA input file
(extracted data file)
Defines name for QA output file
Adds present weather (PWTH) to the
audit report
Adds specified variables to trace report
Finish SF input
2-13
-------
Table 2-3
Runstream for the Extraction and Quality Assessment of On-site Data
JB STA
JB OUT DISK TEST123.RFT
JB ERR DISK TEST123.ERR
JB FIN
Start JB input
Defines name for general report file
Defines name for error/message file
Finish JB input
OS STA
OS IQA DISK LAF-OS.MET
OS LOG LAFAYE 122.60W 45.SON 0
OS EXT 9411 01 9411 30
OS AVG 4
OS HOT 2 20 100
OS DTI 2 20
OS MAP DAT01 OSYR OSMO OSDY OSHR WS01 TT01 DT01 WD01 SA01 INSO
OS MAP DAT02 WD02 WS02 SA02 TT02
OS FMT DAT01 (4X, 412.2, F9.1, 9X, 5F9.1)
OS FMT DAT02 (4F6.2)
OS CHK INSO 2 9999 0 700
OS CHK DT01 1 -999 -10 5
OS CHK SA 1 99 0 50
OS AUD INSO DT01
OS OQA DISK OQAOS.123
OS FIN
Start OS input
Defines name of on-site data file
Defines location of in-site data
Defines time period for extraction of
on-site data
Defines maximum number of values
per hour
Defines heights for multi-level
variables
Defines heights for temperature
difference
Defines list of on-site variables
Defines list of on-site variables
Defines format for on-site data
Defines format for on-site data
Redefines default upper and lower
bounds for QA of insolation
Redefines default bounds for QA of
Delta-T
Redefines default bounds for QA of
Sigma-Theta
Adds insolation and Delta-T to the QA
audit report
Defines name for QA output file
Finish OS input
2-14
-------
1.
2.
3.
4.
METEOROLOGICAL PROCESSOR FOR REGULATORY MODELS [MPRM (dated
30-JAN-96 10:19:28
STAGE 1 EXTRACTION AND QA OF METEOROLOGICAL DATA
*** JOB TERMINATED NORMALLY ***
********************************************************
STATUS REPORT PRIOR TO BEGINNING PROCESSOR RUN
REPORT FILE NAMES
ERROR MESSAGES: TEST122.ERR
SUMMARY OF RUN: TEST122.RPT
UPPER AIR DATA
THE PROCESS(ES) MPRM ANTICIPATES TO PERFORM ARE:
NONE - NO DATA TO BE PROCESSED ON THIS PATH
NWS SURFACE DATA
SITE ID LATITUDE(DEG.) LONGITUDE(DEG-)
24155 45.67N 118.85W
THE PROCESS(ES) MPRM ANTICIPATES TO PERFORM ARE:
EXTRACT AND QUALITY ASSESSMENT
EXTRACT INPUT - OPEN: 24155-94.DAT
EXTRACT OUTPUT- OPEN: IQASF.122
QA OUTPUT - OPEN: OQASF.122
THE EXTRACT DATES ARE: STARTING: 1-NOV-94
ENDING: 30-NOV-94
ON-SITE DATA
THE PROCESS(ES) MPRM ANTICIPATES TO PERFORM ARE:
NONE - NO DATA TO BE PROCESSED ON THIS PATH
**** MPRM MESSAGE SUMMARY TABLE ****
0- 9 10-19 20-29 30-39 40-49 50-59 60-69 70-79
JB
EO 0 0 000 0 0
WO 00 0 00 0 0
I 0 7 0 0 0 0 0 0
SF
EO 000 0 0 00
WO 0 0 0 0 00 0
10 0 0 04 00 0
Q 0 0 0 00 0 0 0
0 7 0 04 00 0
96030)]
TOTAL
0
0
7
0
0
4
0
11
Figure 2-la Report Hie for extraction and QA of surface data (1 of 2).
2-15
-------
METEOROLOGICAL PROCESSOR FOR REGULATORY MODELS [MPRM (dated 96030)]
30-JAN-96 10:19:28
STAGE 1 EXTRACTION AND QA OF METEOROLOGICAL DATA
**** WARNING MESSAGES ****
— NONE —
**** ERROR MESSAGES ****
— NONE —
********************************************************
*** JOB TERMINATED NORMALLY ***
********************************************************
**** SUMMARY OF THE QA AUDIT ****
SURFACE DATA
SLVP
PRES
CLHT
TS
KC
PW
TH
HZVS
TMPD
WD16
WIND
TOTAL
# DBS
720
720
720
720
720
720
720
720
720
720
720
MISSING
0
4
10
2
1
0
0
0
0
5
4
-VIOLATION SUMMARY-
LOWER
BOUND
0
0
0
0
0
0
0
0
0
0
0
UPPER
BOUND
0
0
0
0
0
0
0
0
0
0
0
ACCEPTED
100.00
99.44
98.61
99.72
99.86
100.00
100.00
100.00
100.00
99.31
99.44
j TEST VALUES \
MISSING LOWER UPPER
FLAG BOUND BOUND
-9999.0, 9000.0,10999.0
-9999.0, 9000.0,10999.0
0.0, 300.0
0.0, 10.0
0.0, 10.0
0.0, 92.0
0.0, 92.0
0.0, 1640.0
350.0
0.0, 36.0
0.0, 500.0
-9999.0,
99.0,
99.0,
99.0,
99.0,
-9999.0,
-9999.0, -300.0,
-9999.0,
-9999.0,
NOTE: TEST VALUES MATCH INTERNAL SCALING APPLIED TO VARIABLES
(SEE APPENDIX C OF THE USER'S GUIDE)
THE FOLLOWING CHECKS WERE ALSO PERFORMED FOR THE SURFACE QA
OF 720 REPORTS, THERE WERE
30 CALM WIND CONDITIONS (WS=0, WD=0)
0 ZERO WIND SPEEDS WITH NONZERO WIND DIRECTIONS
0 DEW-POINT GREATER THAN DRY BULB TEMPERATURES
6 PRECIPITATION & WEATHER MISMATCH
THE TIMES OF THESE OCCURRENCES CAN BE FOUND IN THE MESSAGE FILE
WITH QUALIFIERS CLM, ZNZ, DTT & PPT (RESP.)
THIS CONCLUDES THE AUDIT TRAIL
Figure 2-lb Report file for extraction and QA of surface data (2 of 2).
2-16
-------
METEOROLOGICAL PROCESSOR FOR REGULATORY MODELS [MPRM (dated 96030)]
30-JAN-96 10:19:19
STAGE 1 EXTRACTION AND QA OF METEOROLOGICAL DATA
**** SUMMARY OF THE QA AUDIT ****
SF
MIXING HTS
UAM1
UAH2
SURFACE DATA
SLVP
PRES
CLHT
TS
KC
PW
TH
HZVS
TMPD
UD16
WIND
TOTAL
# DBS
32
32
TOTAL
# OBS
720
720
720
720
720
720
720
720
720
720
720
j- VIOLATION SUMMARY j
# LOWER UPPER %
MISSING BOUND BOUND ACCEPTED
0 0 0 100.00
000 100.00
| TEST VALUES |
MISSING LOWER UPPER
FLAG BOUND BOUND
-9999.0, 50.0, 2500.0
-9999.0, 50.0, 4500.0
#
MISSING
0
4
10
2
1
0
0
0
0
5
4
VIOLATION SUMMARY-
LOWER UPPER
•-j j TEST VALUES |
MISSING LOWER UPPER
BOUND BOUND ACCEPTED FLAG BOUND BOUND
0 0 100.00 -9999.0, 9000.0,10999.0
0 0 99.44 -9999.0, 9000.0,10999.0
0 0 98.61 -9999.0, 0.0, 300.0
0 0 99.72 99.0, 0.0, 10.0
0 0 99.86 99.0, 0.0, 10.0
0 0 100.00 99.0, 0.0, 92.0
0 0 100.00 99.0, 0.0, 92.0
0 0 100.00 -9999.0, 0.0, 1640.0
0 0 100.00 -9999.0, -300.0, 350.0
0 0 99.31 -9999.0, 0.0, 36.0
0 0 99.44 -9999.0, 0.0, 500.0
OS
OS
SITE SCALARS
INSO
DT01
SITE VECTORS
SA
TT
WD
WS
TOTAL
# OBS
720
720
TOTAL
# OBS
720
720
720
720
| VIOLATION SUMMARY |
# LOWER UPPER %
MISSING BOUND BOUND ACCEPTED
000 100.00
0 8 20 96.11
| TEST VALUES j
MISSING LOWER UPPER
FLAG BOUND BOUND
9999.0, 0.0, 700.0
-999.0, -10.0, 5.0
#
MISSING
1
1
1
1
•VIOLATION SUMMARY
LOWER UPPER
BOUND BOUND
"i
0
0
0
0
ACCEPTED
20.00 M
15
0
97.78
99.86
99.86
99.86
MISSING
FLAG
99.0,
99.0,
999.0,
999.0,
-TEST VALUES-
LOWER
BOUND
0.0,
-30.0,
0.0,
0.0,
UPPER
BOUND
50.0
35.0
360.0
50.0
THE FOLLOWING CHECKS WERE ALSO PERFORMED FOR THE SURFACE QA
OF 720 REPORTS, THERE WERE
30 CALM WIND CONDITIONS (WS=0, WD=0)
0 ZERO WIND SPEEDS WITH NONZERO WIND DIRECTIONS
0 DEW-POINT GREATER THAN DRY BULB TEMPERATURES
6 PRECIPITATION & WEATHER MISMATCH
THE TIMES OF THESE OCCURRENCES CAN BE FOUND IN THE MESSAGE FILE
WITH QUALIFIERS CLM, ZNZ, DTT & PPT (RESP,)
THIS CONCLUDES THE AUDIT TRAIL
Figure 2-2 Summary of Stage 1 audit results for UA, SF, and OS pathways.
2-17
-------
15 JB 119 SETUP: FOUND "END OF FILE" ON DEVICE DEVIN 5
0 JB 110 TEST: SUMMARY: NO UA-EXT CARD, NULL EXTRACT
0 JB 111 TEST: SUMMARY: NO UA-IQA CARD, NULL QA
0 JB 112 TEST: SUMMARY: NO UA-OQA CARD, NULL MERGE
0 JB 110 TEST: SUMMARY: NO OS-EXT CARD, NULL EXTRACT
0 JB 111 TEST: SUMMARY: NO OS-IQA CARD, NULL QA
0 JB 112 TEST: SUMMARY: NO OS-OQA CARD, NULL MERGE
0 SF 140 SFEXT: *** HLY SFC OBS & PRECIP EXTRACTION ***
720 SF 149 RD144D: END-OF DATA WINDOW AFTER RECORD 721
0 SF 149 SFEXT: 720 HLY WX & 720 PRECIP OBS EXTRACTED
30502 SF
30502 SF
30503 SF
30504 SF
30504 SF
30505 SF
30505 SF
30506 SF
30507 SF
30507 SF
30508 SF
30508 SF
30508 SF
30508 SF
30509 SF
30509 SF
30509 SF
30509 SF
30509 SF
30510 SF
30510 SF
30510 SF
30510 SF
30510 SF
30510 SF
30511 SF
30511 SF
30511
30511
30511
30511
30602 SF
30905 SF
30906 SF
30907 SF
SF
SF
SF
SF
SFQASM: CLHT MISSING ON 94/11/01/02
PPT SFQASM: WEATHER WITHOUT PRECIP ON 94/11/01/02
SFQASM: CLHT MISSING ON 94/11/01/03
SFQASM: CLHT MISSING ON 94/11/01/04
PPT SFQASM: PRECIP WITHOUT WEATHER ON 94/11/01/04
SFQASM: CLHT MISSING ON 94/11/01/05
PPT SFQASM: PRECIP WITHOUT WEATHER ON 94/11/01/05
SFQASM: CLHT MISSING ON 94/11/01/06
SFQASM: CLHT MISSING ON 94/11/01/07
SFQASM: WD16 MISSING ON 94/11/01/07
SFQASM: CLHT MISSING ON 94/11/01/08
SFQASM: WD16 MISSING ON 94/11/01/08
SFQASM: WIND MISSING ON 94/11/01/08
PPT SFQASM: PRECIP WITHOUT WEATHER ON 94/11/01/08
SFQASM: PRES MISSING ON 94/11/01/09
SFQASM: CLHT MISSING ON 94/11/01/09
SFQASM: WD16 MISSING ON 94/11/01/09
SFQASM: WIND MISSING ON 94/11/01/09
PPT SFQASM: PRECIP WITHOUT WEATHER ON 94/11/01/09
SFQASM: PRES MISSING ON 94/11/01/10
SFQASM: CLHT MISSING ON 94/11/01/10
SFQASM: TSKC MISSING ON 94/11/01/10
SFQASM: WD16 MISSING ON 94/11/01/10
SFQASM: WIND MISSING ON 94/11/01/10
PPT SFQASM: PRECIP WITHOUT WEATHER ON 94/11/01/10
SFQASM: PRES MISSING ON 94/11/01/11
SFQASM: CLHT MISSING ON 94/11/01/11
SFQASM: TSKC MISSING ON 94/11/01/11
SFQASM: TSKC MISSING ON 94/11/01/11
SFQASM: WD16 MISSING ON 94/11/01/11
SFQASM: WIND MISSING ON 94/11/01/11
SFQASM: PRES MISSING ON 94/11/02/02
CLM SFQASM: CALM WINDS ON 94/11/05/05
CLM SFQASM: CALM WINDS ON 94/11/05/06
CLM SFQASM: CALM WINDS ON 94/11/05/07
721 SF 149 SFQASM: END OF FILE AFTER OBS # 720
Figure 2-3 Extract from the Stage 1 error/message file for the SF pathway.
2-18
-------
Table 2-4
Runstream for Merging of NWS Mixing Height and Surface Data with On-site Data
JB STA
JB OUT DISK TEST223.RPT
JB ERR DISK TEST223.ERR
JB FIN
Start JB input
Defines name for general report file
Defines name for error/message file
Finish JB input
UA STA
UA OQA DISK OQAUA.121
UA FIN
Start UA input
Provides name of upper air output file
to merge
Finish UA input
SF STA
SF OQA DISK OQASF.122
SF FIN
Start SF input
Provides name of surface output file to
merge
Finish SF input
OS STA
OS OQA DISK OQAOS.123
OS FIN
Start OS input
Provide name of on-site output file to
merge
Finish OS input
MR STA
MR EXT 941101 9411 30
MR OUT DISK MERGE.223
MR FIN
Start MR input
Define time period of data to merge
Define name of merge output file
Finish MR input
An extract from the Stage 2 (merge) report file is presented in Figure 2-4. The report
shows that upper air, surface, and on-site data for a one month (30 day) period were merged.
The data include 24 records per day of surface and on-site data, and 6 records per day of
mixing heights. The latter is necessary because in Stage 3 hourly mixing heights will be
interpolated based on twice daily mixing heights for the preceding and following days.
2-19
-------
METEOROLOGICAL PROCESSOR FOR REGULATORY MODELS [MPRM (dated 96030)]
30-JAN-96 10:24:56
STAGE 2 MERGE METEOROLOGICAL DATA
***** DAI|_Y OUTPUT STATISTICS *****
MO/DA 117 1 117 2 117 3 117 4 117 5 117 6
NWS UPPER AIR SDGS 000000
NCDC MIXING HEIGHTS 666666
NWS SFC OBSERVATIONS 24 24 24 24 24 24
ON-SITE OBSERVATIONS 24 24 24 24 24 24
117 7 117 8 117 9 11/10
0000
6666
24 24 24 24
24 24 24 24
MO/DA 11/11 11/12 11/13 11/14 11/15 11/16 11/17 11/18 11/19 11/20
NWS UPPER AIR SDGS 0000000000
NCDC MIXING HEIGHTS 6 6 6 66 6 6 6 6 6
NWS SFC OBSERVATIONS 24 24 24 24 24 24 24 24 24 24
ON-SITE OBSERVATIONS 24 24 24 24 24 24 24 24 24 24
MO/DA 11/21 11/22 11/23 11/24 11/25 11/26 11/27 11/28 11/29 11/30
NWS UPPER AIR SDGS 000000
NCDC MIXING HEIGHTS 666666
NWS SFC OBSERVATIONS 24 24 24 24 24 24
ON-SITE OBSERVATIONS 24 24 24 24 24 24
0
6
24
24
0
6
24
24
0
6
24
24
0
6
24
24
UPPER AIR DBS. READ: 32
SURFACE OBS. READ: 720
ON-SITE OBS. READ: 720
***** MERGE PROCESS COMPLETED *****
Figure 2-4 Extract from the Stage 2 (MERGE) report file.
2-20
-------
SECTION 3
PROCESSING - STAGE 3
The goal of Stage 3 processing is to construct a meteorological data file for use with a
user selected dispersion model. As a minimum, the input runstream for Stage 3 needs to
provide the names for the input file (i.e., the merge output file from Stage 2), the output file,
and the dispersion model. General instructions on preparing the input runstream for Stage 3
processing are provided using an example test case in Section 3.1. Subsequent sections
provide more specific instructions on: selection of processing options (Section 3.2); and
selection of surface characteristics (Section 3.3). Information on the Stage 3 general report
and error/message files is provided in Sections 3.4 and 3.5, respectively.
3.1 Example Test Case
An example run stream for processing a merged data file for use in wet deposition
modeling is presented in Table 3-1. 'New keywords introduced in this example are: SFC on
the OS pathway and MET, MMP, and VBL on the MP pathway. The OS and MP pathway
input images are described in Sections 3.1.1 and 3.1.2 respectively.
3.1.1 OS Pathway Input
The OS SFC images provide necessary information on surface characteristics for use
in estimating boundary layer parameters. The first such record indicates that surface
characteristics will be specified by season for 2 sectors; the next two records provide the
beginning and ending azimuth (degrees) for these sectors. Records containing the
'VALUES' character string provide the surface characteristics.
The syntax of the OS SEC SETUP image is:
OS SFC SETUP parml parm2
The parml field is a place holder for frequency which must be one of the following character
strings: ANN[UAL], SEA[SONAL], or MON[THLY]; the frequency indicates that the
surface characteristics are constant over an annual cycle, or vary by season or calendar
month. The brackets indicate that only the first three letters of the character string are
required. The parm2 field is a place holder for the number of sectors (maximum 12). The
sectors should be contiguous and should cover 360°. To define a single value for each of the
site characteristics, the frequency should be specified as ANNUAL and the number of sectors
should be 1.
The syntax of the OS SFC SECTORS image is:
OS SFC SECTORS parml parml parm3
3-1
-------
Parml is the sector number; parm2 is the beginning azimuth (included in the sector), and
parmS is the ending azimuth (excluded from the sector). The azimuth is defined in a
clockwise sense; a sector definition may pass through north (360°) without having to
terminate at north. The number of 'OS SFC SECTORS' images must correspond to the
number of sectors.
The syntax of the OS SFC VALUES image is:
OS SFC VALUES parml parm2 parmS ... parm9
The VALUES character string indicates that information on surface characteristics
follows. Parml is the frequency index (1 for annual, 1-4 for season, or 1-12 for monthly)
and parm2 is the sector index. Seasons are defined in MPRM as follows: Winter =
December, January and February (parml = 1); Spring = March, April, and May (parml =
2); Summer = June, July, and August (parml = 3); Fall = September, October, and
November (parml = 4). The order and defaults for the surface characteristics (parmS ...
parm9) are:
Albedo 0.25
Bowen Ratio 0.70
Roughness Length (measurement site) 0.15 m
Roughness Length (application site) 0.15 m
Minimum Monin-Obukhov Length 2.00 m
Surface Heat Flux (fraction of net) 0.15
Anthropogenic Heat Flux 0.00 WnT2
Information on specifying surface characteristics is provided in Section 3.3.
3.1.2 MP Pathway Input
The MP MET image identifies the merge data file to be processed (MERGE. 223) and
provides the number of integer hours to be subtracted from the Greenwich Mean Time
(GMT) to convert to local standard time (LST). For a west coast location, the conversion is
8 hours.
The MP MMP image defines the name for the processed meteorological data file
(TEST324.OUT) and selects a dispersion model (ISCSTWET). The default, if no model is
specified, is the ISCST3 model; the output in this case is an ASCH file formatted for use in
ISCST3. Detailed information on file formats for the dispersion models supported by
MPRM is provided in Appendix F.
The syntax for the MMP keyword is:
MP MMP DISK filename model
3-2
-------
where filename is the name of the output file and model specifies the dispersion model. The
filename should not exceed 48 characters and must conform to the file naming conventions
appropriate to the computing platform. The dispersion models supported by MPRM are
listed hi Table 3-2.
The MP VBL images specify processing options to be employed for the indicated
meteorological variables. The syntax of the MP VBL image is:
MP VBL item action parml parm2
Information for completing the item, action, and parameter fields is given in Table 3-3. The
item field refers to the meteorological variable: wind speed and direction (WIND);
temperature (TEMP); mixing height (MHGT) and stability (STAB). The action field refers
to type of data to be used; the choices are NWSWXX for NWS airport data (the default) and
ONSITE for user collected, site specific data. For stability, the action field additionally
indicates the method employed to estimate stability. The parml field is a place holder for
the measurement height for the WIND, TEMP, and STAB items. The parm2 field has
meaning only for user specified stability (see Section 3.2 for details). In the Table 3-1
example, onsite data are specified for wind and temperature, and rruib* processing is
specified for stability. There is no MP VBL image for mixing heights; therefore, by default,
mixing heights are based on NWS airport data. Selection of processing options for
meteorological variables is discussed in Section 3.2. The scientific basis for these options
are discussed in Section 4.
The MP TRA image activates tracing and currently has meaning only with the
determination of the Pasquill stability category. As is described hi Section 4, there are six
different methodologies available for specifying the stability category: one is equivalent to
the RAMMET processor and employs only NWS data, the other five employ on-site data.
Since all of the on-site data methods are acceptable, MPRM searches for an alternate on-site
method if the primary method is incapable of working for a given hour due to lack of data.
The TRA option reports the results of such searches whenever they occur. If these searches
were to occur frequently, the error/message file might well become quite large. Therefore,
uidiscriminate use of the trace option is not recommended. A better use of the TRA option
would be to process short periods of record that are known to contain frequent periods of
missing data. The MP EXT input can be used to control the dates processed. In this
manner, the search results can be reviewed in a manageable fashion. Obviously, if an
alternate method for specifying the stability category is employed too often, it may invalidate
the use of the data for certain regulatory actions.
The MP LST image activates the listing of the generated meteorological data to the
general report file and, like the MP TRA image, enhances the detail provided hi the Stage 3
processing messages. The extra output produced by these two options are of little concern if
only several days of data are being processed. If a longer record is involved, e.g., a 1-year
3-3
-------
period, one might question the wisdom of employing these options. The MP LST image
will generate one full page of output for each 2 to 3 days of data depending on the dispersion
model.
3.2 Processing Options
Default selections for processing wind, temperature, stability category, and mixing
height employ the NWS hourly surface weather observations and twice-daily estimated
mixing heights. The default selections duplicate the procedures employed by the RAMMET
meteorological processor. In MPRM, the defaults can be overridden using the MP VBL
input image. The syntax for this image is:
HP VBL ITEM ACTION XXXX X
'— Input needed only with
Item "STAB" and Action
"USERIN"
Additional input,
as required
6-character keyword
instructing processor
on how ITEM is to be
accomplished
4-character keyword
defining process
(methodology)
Table 3-3 describes the allowable character strings for ITEM and ACTION and provides
other necessary information for completing the MP VBL image.
3.3 Surface Characteristics
MPRM provides the means to specify direction-dependent surface characteristics for
use in estimating boundary layer parameters. If none are specified, the default values given
in Section 3.1 are used. The default values are typical for cultivated land with average
moisture and, consequently, will not apply to all modeling situations. Information on
specifying site specific values for surface characteristics is provided in the following.
Albedo - The albedo is the fraction of the incoming solar radiation that is reflected
from the ground when the sun is directly overhead. Adjustments are made automatically
within MPRM for the variation in the albedo with solar elevation angle. Typical values
range from 0.1 for thick deciduous forests to 0.65 for fresh snow. A range of values is
given in Table 3-4 as a function of several land-use types and season. The default value in
MPRM is 0.25.
Bowen Ratio - The Bowen ratio is an indicator of the amount of moisture at the
surface and is defined by H/LE, where H is the upward sensible heat flux and LE is the
latent heat flux used in evaporation. The presence of moisture at the earth's surface alters
3-4
-------
the energy balance, which in turn alters the sensible heat flux and Monin-Obukhov length.
The Bowen ratio varies from 0.1 over water to 10.0 in desert. A range of values is given hi
Table 3-5 as a function of land-use type, season and moisture condition. The default value
for Bowen ratio is 0.75. ,
Roughness Length - The surface roughness length (ZQ) is, hi principle, the height at
which the wind speed vanishes; it is generally proportional to the physical dimensions of the
roughness elements. Roughness length values range from less than 1 cm over a calm water
surface to 1 m or more over a forest. Typical values for a range of land-use types as a
function of season are listed in Table 3-6. MPRM expects surface roughness information to
be provided for two types of sites: the measurement site, and the application site.
Measurement Site - The surface roughness at the measurement site is used internally
in MPRM for scaling meteorological variables within the surface layer based on a
single surface layer measurement (nominally the 10 m level). The measurement site
refers to the site of the meteorological measurements. If the meteorological data have
been collected in accordance with recommendations in (U.S. EPA, 1987), this should
not be a problem since the site characteristics will have been fully documented. If
such documentation is not available, one should assess surface characteristics within a
one kilometer radius of the measurement site and use the information in Table 3-6 to
determine the appropriate roughness length. For NWS data, a default value of
0.15 m should be used.
Application Site - The surface roughness at the application (receptor) site is needed
for modeling applications involving estimates of dry deposition and depletion; the
surface roughness at the application site is not used internally Within MPRM, but is
passed along directly to the meteorological input file for the model selected. One
should not expect that the surface characteristics of the measurement site will
necessarily be representative of the application site; in fact, often this will not be the
case. The surface roughness length at the application site is used to obtain estimates
of the surface friction velocity (u*) and Monin-Obukhov length (L) at the application
site.
Monin-Obukhov Length - The Monin-Obukhov length is a measure of atmospheric
stability. It is negative during the day when surface heating results in an unstable
atmosphere and positive at night when the surface cools (stable atmosphere). Values near
zero indicate very unstable or stable conditions (depending on the sign). In urban areas
during stable conditions, the estimated value of L may not adequately reflect the less stable
boundary layer. Hanna and Chang (1991) point out that mechanical turbulence generated by
obstacles (buildings) in urban areas will tend to produce a "more neutral" surface layer than
that over an unobstructed site. They suggest that a minimum value of L be set for stable
hours in order to simulate this effect. Using an approximate relation between obstacle height
3-5
-------
and the zone of flow affected by an obstacle, they suggest the following minimum values for
several urban land use classifications:
agriculture (open) " 2m
residential 25 m
compact residential/industrial 50 m
commercial (19-40 story buildings) 100 m
(> 40 story buildings) 150 m
Surface Heat Flux - The flux of heat into the ground during the daytime is
parameterized as a fraction of the net radiation. Values suggested by Oke (1982) are:
rural 0.15
suburban 0.22
urban 0.27
Anthropogenic Heat Flux - The anthropogenic heat flux can usually be neglected (set
equal to zero) in areas outside highly urbanized locations. However, in areas with high
population densities or high energy use, this flux may not always be negligible. Oke (1978)
presents estimates of population density and per capita energy use for 10 cities and obtains a
heat flux for each. Summertime values are typically 50% of the mean, while wintertime
values are about 150% of the mean in the colder climates. Table 3-7 provides values for
several urban areas.
The surface characteristics used in the example test case are based on an assumed
modeling scenario involving a source located on the boundary separating an urban area from
a deciduous forest. The two land use types are assumed to occupy contiguous 180 degree
sectors. Table 3-8 provides a summary the surface characteristics by season for these two
land use types.
3.4 Stage 3 General Report File
The Stage 3 general report is structured somewhat differently than that generated
during Stages 1 and 2. If the LST keyword has been activated, then the first page of the
general report will echo the header information that was written to the output file (i.e., the
file defined following the MMP keyword). This would be followed by the listing of the
generated meteorological data. The listing would continue for as many pages as necessary.
The rest of the Stage 3 general report is standard; an example is shown in Figure 3-1. The
general report documents Stage 3 processing under 11 headings as follows:
1. Filenames as determined in setup
2. Dispersion model defined in setup
3. Processing options selected
4. Stability methods used
3-6
-------
5. Processing assumptions
6. Locations specified in setup
7. Output file names
8. Summary of data processing results
9. Distribution of wind speeds
10. Rural stability category results
11. Surface characteristics used
The information contained under the first two headings is self-explanatory. Notes related to
the information contained under the remaining headings is provided in the following:
Processing options selected - This item documents the processing options as selected
during setup (see Table 3-3 and discussion in Section 3.2). The example documented in
Figure 3-1 indicates that on-site data were specified for wind and temperature, and TTDIFF
processing was specified for stability. By default, NWS airport data were used for mixing
heights.
Stability methods used - Six methods for estimating the P-G stability category are
provided in MPRM. The six methods are considered to be equivalent; consequently, if data
for the method specified in the MP VBL STAB image are not available, MPRM will attempt
to process stability using one or more of the remaining alternative methods. If all of the
methods are exhausted, MPRM will write a message to the error/message file indicating that
stability processing could not be completed for the indicated hour. The example documented
in Figure 3-1 indicates that the ITUIFF method was employed successfully in estimating
stability for 719 records (hours).
Processing assumptions - Item 5 of the general report documents the measurement
heights for the meteorological variables used in creating the meteorological data file. This
information is especially important when on-site data are being processed because multiple
measurement levels may be involved. As discussed in Section 3.2, when data for multiple
levels are available, MPRM will select the level closest to the value provided in the
associated MP VBL image. The example documented in Figure 3-1 indicates that wind
speed data, used for stability category estimates, are based on 10-m measurements; wind
speed and direction data, for use in transport, are based on 10-m measurements; and
temperature data, for use in plume rise calculations etc., are based on measurements made at
2m.
Locations specified in setup - Item 6 of the general report documents the location
information (station identifier, latitude, and longitude) associated with each of the sources of
meteorological data in the merged file. The latitude and longitude for the NWS surface and
upper air data are provided for information only, since Stage 3 processing assumes that the
location information provided for the on-site data are to be used in processing. The latitude
and longitude are used in MPRM to calculate the elevation of the sun with respect to the
3-7
-------
horizon and, in turn, the time of sunrise and sunset. The latter are important in processing
routines for estimating the P-G stability category.
Output file names. - The seventh item in the general report provides documentation
related to the output from Stage 3. This includes the file names for the error/message file
and the output meteorological data file for use in modeling. The header record on the output
file is also listed. This normally contains the station identifiers and year for the surface and
upper air data; some models use this information to verify that the meteorological data file
being used is consistent with that which was requested in the model input.
Summary of data processing results - The eighth item in the general report lists the
number of valid and invalid (missing) records for each meteorological variable in a standard
output file. The example in Figure 3-1 shows that 720 records (hours) were processed and
that there were 719 valid data values for each of the six variables (stability, wind speed,
wind direction, rural mixing height, urban mixing height, and temperature); note, calms are
regarded as valid wind speeds. Normally, invalid (missing) records should be resolved
following the completion of Stage 1 processing; thus, one would normally not expect to find
missing data showing up in Stage 3. In this case, at least one and perhaps as many as six
bad records slipped through the cracks. These records should be corrected prior to the use
of these data in regulatory dispersion modeling.
Distribution of wind speeds - The ninth item in the general report provides
information on the distribution of wind speeds in the data base. The information provided is
the frequency of occurrence (number of hours) and the harmonic average wind speed (ms"1)
for six wind speed ranges (0-3, 4-6, 7-10, 11-16, 17-21, and > 21 kts).
Stability category results - Item ten in the general report provides information on the
distribution of P-G stability category estimates.
Surface characteristics used - Item eleven in the general report documents the
surface characteristics used in stage 3 processing. As indicated in Table 3-8, the surface
characteristics used in the example vary with season of the year and direction sector (land
use type).
3.5 Stage 3 Error/Message File
The user has two means to amplify the information provided in the general report.
First, the meteorological data stored in the output file for the dispersion model can be listed
to the general report file. This is accomplished by use of the JB LST input. Second, more
detailed messages can be obtained in the error/message file. This is accomplished using the
UA TRA, SF TRA, OS TRA, or MP TRA input image.
3-8
-------
Figure 3-2 presents a partial listing of an error/message file associated with the
following Stage 3 input image: ;
MP TRA STAB
The following images from the error/message file indicate that there was insufficient data to
compute a stability category for hour 23 on Julian day 365:
365 MP T75 OS1PGT: ISPD MISSING, HR 23 PGSTAB .EQ. 0
365 MP T75 OSSEPG: ISPD MISSING, HR 23 PGSTAB .EQ. 0
365 MP T75 OSSAPG: ISPD MISSING, HR 23 PGSTAB .EQ. 0
365 MP T75 OS2NWS: ISPD MISSING, HR 23 PGSTAB .EQ. 0
365 MP T75 SFSTAB: HOUR 23 NO PG CATEGORY POSSIBLE
In the first image, 365 is the record number in the output file, MP is the pathway, T75 is the
message number (see Appendix E), and OS1PGT is the name of the subroutine which
senerated the message. The subroutine identifies the stability processing method: these are
listed for reference in Table 3-9. Translated the message reads 'wind speed (ISPD) was
missing for hour 23 and thus, the P-G stability category was set to zero (i.e., missing)'.
The next three images are translated similarly, only the subroutine is changed. Taken
together the first four images show that four different subroutines were called in an attempt
to determine a stability category and all failed due to a missing value for wind speed. The
last (fifth) image indicates that all acceptable techniques for estimating the P-G stability have
been exhausted.
Note, for hour 24 (see Figure 3-2), the search ended in subroutine OSSAPG, where it was
determined that sufficient data were present to employ the SASITE option for computing
stability category.
3-9
-------
Table 3-1
Runstream for Processing NWS and On-site Data for use in Wet Deposition Modeling
JB STA
JB OUT DISK TEST324.RPT
JB ERR DISK TEST32A.ERR
JB FIN
Start JB input
Defines name for general
report file
Defines name for error report
file
Finish JB input
OS STA
OS LOC LAFAYE 122.60U 45.SON 0
OS SFC SETUP SEASON 2
OS SFC SECTORS 1 0 180
OS SFC SECTORS 2 180 360
OS SFC VALUES 1 1 0.50 1.50 0.15 0.50
OS SFC VALUES 2 1 0.12 0.70 0.15 1.00
OS SFC VALUES 3 1 0.12 0.30 0.15 1.30
OS SFC VALUES 4 1 0.12 1.00 0.15 0.80
OS SFC VALUES 1 2 0.35 1.50 0.15 1.00 50.00 0.27 0.0
OS SFC VALUES 2 2 0.14 1.00 0.15 1.00 50.00 0.27 0.0
OS SFC VALUES 3 2 0.16 2.00 0.15 1.00 50.00 0.27 0.0
OS SFC VALUES 4 2 0.18 2.00 0.15 1.00 50.00 0.27 0.0
OS FIN
2.00 0.15 0.0
2.00 0.15 0.0
2.00 0.15 0.0
2.00 0.15 0.0
Start OS input
Defines on-site location
Specifies seasonal surface
characteristics for 2 sectors
Defines bounds for sector 1
Defines bounds for sector 2
Data for season 1, sector 1
Data for season 2, sector 1
Data for season 3, sector 1
Data for season 4, sector 1
Data for season 1, sector 2
Data for season 2, sector 2
Data for season 3, sector 2
Data for season 4, sector 2
Finish OS input
HP STA
HP MET DISK HERGE.223 8
HP HHP DISK TEST324.0UT ISCSTWET
HP VBL WIND ONS1TE 10
HP VBL TEHP ONSITE 2
HP VBL STAB TTDIFF 10
HP TRA
HP LST
HP FIN
Start MP input
Provides name of merge file to
process
Defines output file name and
dispersion model
Defines processing options for
wind speed and direction
Defines processing options for
temperature
Defines processing options for
stability
Activates trace procedures
Activates listing of data to
general report file
Fin.ish MP input
3-10
-------
Table 3-2
Dispersion Models Supported by MPRM
MMP Model
Option
Dispersion
Model Name
Description
ISCST
ISCSTDRY
1SCSTWET
ISCST
ISCST
ISCST
BLP
COMPLEX 1
RAM
CALJNE-3
RTDM
VALLEY
1SCLT
COM 16*
CDM36"
BLP
COMPLEX 1
RAM
CALJNE-3
RTDM
VALLEY
ISCLT
COM 2.0*
CDM 2.0
The ISCST model option results in an ASCII file for use in ISCST;
this is the default. The default output consists of ten fields ending
with the mixing heights (see Appendix F).
ISCSTDRY produces an ASCII file for use in modeling dry
deposition with ISCST. Each record includes three additional fields
following the mixing height: surface friction velocity, Monin-
Obukhov length and surface roughness length at the application site.
ISCSTWET produces an ASCII file for use in wet deposition
modeling with ISCST. Each record includes five additional fields
following the mixing height: surface friction velocity, Monin-
Obukhov length, surface roughness length at the application site.
precipitation type and precipitation amount.
Selection of these models results in a RAMMET binary output file
with 24 hours of data per record. The same file also supports the
unformatted (binary) option of ISCST.
This selection results in an ASCII file for use in CALJNE-3. This
format has 1 hour of data in each record.
This selection results in an ASCII file for use in RTDM. This
format has 1 hour of data in each record.
This selection results in an ASCII file containing data describing the
joint frequency distribution of wind direction and wind speed by
stability class. Sixteen wind direction sectors are used in developing
the frequency distribution, with the first 22.5° sector centered on
winds from the North.
This selection results in an ASCII file containing data describing the
joint frequency distribution of wind direction and wind speed by
stability class. Thirty-six wind direction sectors are used in
developing the frequency distribution, with the first 10° sector
centered on winds from the North.
The CDM 2.0 dispersion model can process meteorological frequency function data (often referred to
as STability ARray data, STAR), constructed using either 16 or 36 wind direction sectors. To provide
this flexibility, we'have used CDM16 and CDM36 to identify whether 16 or 36 wind direction sectors
are desired in constructing the STAR data. STAR output for CDM use the six stability categories A,
B. C. D-da>. D-night. E-F. STAR output for the ISCLT and VALLEY models use the six stability
categories: A. B. C. D. E. F.
3-11
-------
Table 3-3
Information for Selecting Processing Options on the MP VBL Input Image
Item
Action
Description
WIND
NHSUXX
ONSITE
Default] The wind direction and speed are determined using the wind direction
and speed given in the hourly NWS weather observation. As the observations are
reported to the nearest 10°, a standard set of random numbers is used, as in
RAHHET, for randomizing the wind directions.
Additional input is a value for STKHGT. Wind direction and speed are determined
from on-site observations. Values selected are from on-site tower level nearest
to value given for STKHGT.
TEMP
NUSWXX
ONSITE
[Default] The temperature is determined using the values given in the hourly
NWS weather observation.
Additional input is a value for THPHGT. Temperature is determined from on-site
observations. Values selected are from on-site tower level nearest to value
given for THPHGT.
MHGT
NWSVXX
ONSITE
[Default] The mixing height is determined using the NCDC twice-daily mixing
height values and the stability category for the hour. The procedure is that
employed in RAMHET.
The mixing height given in the hourly on-site observation is used.
STAB
NWSVXX
ONSITE
SESfTE
SAS:TE
USERIN
HNDWXX
TTDIFF
[Default] The stability category is determined using the cloud cover, ceiling
height, and wind speed (from NWS weather observations) coupled with sun's
position. The procedure is that employed in RAMMET. An optional additional
input is a value for ANEHGT (the default is 1C m).
Additional input is a value for ANEHGT. The stability category is determined
using the same procedure as NWSWXX, with all data taken from the on-site
observation. Wind Speed values are from on-site tower level nearest to value
given for ANEHGT.
Additional input is a value for ANEHGT. The stability category is determined
using standard deviation of vertical wind direction fluctuations at tower level
nearest to value given for ANEHGT.
Additional input is a value for ANEHGT. The stability category is determined
using standard deviation of horizontal wind direction fluctuations at tower
level nearest to value given for ANEHGT.
Additional input is a value for ANEHGT and [ISCVAR = 1, 2, or 3]. This action
indicates that the user is providing the stability directly in the variable US01
(when ISCVAR =1).
Additional input is a value given for ANEHGT. The stability category is
determined using on-site wind speed from tower level nearest to ANEHGT, and NWS
observations of cloud amount and ceiling height.
TTDIFF Additional input is a value for ANEHGT. The stability category is
determined using the solar radiation temperature difference method.
3-12
-------
Table 3-4
Albedo1 of Natural Ground Covers by Land Use and Season (from Iqbal, 1983)
Autumn
WaleTSurfece. OO12 67To014
2 Deciduous Forest 0.50 0.12 0.12 0.12
3 Coniferous Forest 0.35 0.12 0.12 0.12
4 Swamp 0.30 0.12 0.14 0.16
5 Cultivated Land 0.60 ,0.14 0.20 0.18
6*. Grassland 0.60 0.18 0.18 0.20
7 Urban 0.35 0.14 0.16 0.18
8. Desert Shnibland 0.45 0.30 0.28 0.28
Definitions of Seasons:
Winter- Periods when surfaces were covered by snow, and when temperatures
are sub-freezing (defined as December, January, and February in
MPRM).
s - periods when vegetation is emerging or partially green. This is a
&' transitional situation that applies for 1-2 months after the last killing
frost in spring (defined as March. April, and May in MPRM).
Summer Periods when vegetation is lush and healthy, typical of mid-summer,
but also of other seasons where frost is less common (defined as
June. July, and August in MPRM).
Autumn- Periods when freezing conditions are common, deciduous trees are
leafless crops are not yet planted or are already harvested (bare soil
exposed), grass surfaces are brown, and no snow is present (defined
as September, October, and November in MPRM).
i See also Iqbal (1983) for specific crops or ground covers.
2 Winter albedo depends upon whether a snow cover is present continuously,
intermittently, or seldom. Albedo ranges from about 0.30 for fresh snow
cover to about 0.65 for continuous cover.
3-13
-------
Table 3-5
Daytime Bowen Ratio by Land Use and Season (from Paine, 1987)
Dry Conditions
Land-Use
Water (fresh and sea)
Deciduous Forest
Coniferous Forest
S\v»inp
Cultivated Land
Grttsstttnd
U*rhnn
Desert Slmihland
Winter Spring Summer
2.0 0.1 0.1
2.0 1.5 0.6
2.0 1.5 0.6
2.0 0.2 0.2
2.0 1.0 1.5
2.0 1.0 2.0
2.0 2.0 4.0
10.0 5.0 6.0
Autumn
0.1
2.0
1.5
0.2
2.0
2.0
4.0
'10.0
Average Conditions
Land-Use
Water Oresh and sea)
Deciduous Forest
Coniferous Forest
Swamp
Cultivated Lund
Grasslmu!
Urliitn
Desert ShruhlHiid
Winter Spring Summer
1.5 0.1 0.1
1.5 0.7 0.3
1.5 0.7 0.3
1.5 0.1 0.1
1.5 0.3 05
1.5 0.4 0.8
1.5 1.0 2.0
6.0 3.0 4.0
Autumn
0.)
1.0
0.8
O.i
0.7
1.0
2.0
6.0
Wet Conditions
Lund-Use
Water ifre.sli and sett)
Deciduous Forest
Coniferous Forest
Swamp
Cultivated Land
Grassland
Urban
Desen Shruhland
Winter Spring Summer
0.3 0.1 0.1
0.5 0.3 0.2
0.3 0.3 0.2
0.5 0.1 0.1
0.5 0.2 0.3
0.5 0.3 0.4
0.5 0.5 1.0
2.0 1.0 5.0
Autumn
0.1
0.4
0.3
0.1
0.4
0.5
1.0
2.0
3-14
-------
Table 3-6
Surface Roughness Length (m) by Land Use Type and Season (from Sheih et al., 1979)
Land-Use Type
1. Water Surface
2. Deciduous Forest
3. . Coniferous Forest
4. Swamp
5. Cultivated Land
6. Grassland
7. Urban
8. Desert Shrubland
Table 3-7
Average Anthropogenic Heat Flu. (Qf) and Net Radiation (Q.) for Several Urban Areas (from Oke, 1978)
Winter
0.0001
0.50
1.30
0.05
0.01
0.001
1.00
0.15
Spring
0.0001
1.00
1.30
0.20
0.03
0.05
1.00
0.30
_^_—— — ^-^— .^—
Summer
0.0001
1.30
1.30
0.20
0.20
0.10
1.00
0.30
. i — —
Autumn
0.0001
0.80
1.30
0.20
0.05
0.01
1 .00
0.30
i " •• '"
Urban area/
latitude/period
Manhattan (40=N)
annual
summer
winter
Montreal (45CN)
annual
summer
winter
Budapest (47=N)
annual
summer
winter
Sheffield (53CN)
annua I
West Berlin (52°N)
annual
Vancouver (49°hO
annual
summer
winter
Hong Kong (22°N)
annual
Singapore (1°N)
! annual
Los Angeles (34°N)
annual
Fairbanks (64CN)
annual
Population
Population density
(x 10 ) (persons/km )
1.7 28,810
1.1 14,102
1.3 11,500
0.5 10,420
2.3 9,830
0.6 5,360
3.9 3,730
2.1 3,700
7.0 2,000
0.03 810
Per capita
energy usage
(MJxIO /yr)
128
221
118
58
67
112
34
25
331
740
Qf,
(W./nT)
.117
40
198
99
57
153
43
32
51
19
21
19
15
23
4
3
21
19
Q.
(W/n/}
93
52
92
13
46
100
-8
56
57
57
107
6
-110
'110
108
18
3-15
-------
Table 3-8
Surface Characteristics Used in Example Test Case
Season
Winter
Spring
Summer
Fall
Winter
Spring
Summer
Fall
Sector/
Land Use Type
Deciduous
Deciduous
Deciduous
Deciduous
Urban
Urban
Urban
Urban
Albedo3
0.50
0.12
0.12
0.12
0.35
0.14
0.16
0,18
Bowen Ratioh
1.50
0.70
0.30
1.00
1.50
1.00
2.00
2.00
Z0 (application)0
0.50
1.00
1.30
0.80
1.00
1.00
1.00
1.00
" From Table 3-4
h From Table 3-5 (Average Conditions)
c From Table 3-6
3-16
-------
Table 3-9
Subroutines Associated with Stage 3 Processing Options
ITEM
WIND
TEMP
MHGT
STAB
ACTION
NWSWXX
ONSITE
NWSWXX
ONSITE
NWSWXX
ONSITE
NWSWXX
ONSITE
SESITE
SASITE
WNDWXX
TTDIFF
USERIN
Subroutine
WS1NWS
WS1OS
TT]NWS
TT1OS
Z1NWS
Z1OS
PGTNWS
OS1PGT
OSSEPG
OSSAPG
OS2PGT
OSSRPG
OSINPG
3-17
-------
METEOROLOGICAL PROCESSOR FOR REGULATORY MODELS [MPRM (dated 96030)]
30-JAN-96 10:27:33
STAGE-3 PROCESSING OF MERGED METEOROLOGICAL DATA
********************************
*** JOB TERMINATED NORMALLY ***
********************************
1. FILENAMES AS DETERMINED DURING SETUP
TEST324.RPT
TEST324.ERR
MERGE.223
TEST324.0UT
2. DISPERSION MODEL DEFINED DURING SETUP:
OPENED SUCCESSFULLY
OPENED SUCCESSFULLY
OPENED SUCCESSFULLY
OPENED SUCCESSFULLY
ISCSTWET
3. PROCESSING OPTIONS SELECTED DURING SETUP
PROCESS SCHEME
WIND ONSITE
TEMPERATURE ONSITE
MIXING HEIGHTS NWSWXX
STABILITY TTDIFF
4. STABILITY METHODS USED
NWSWXX
ONSITE
SESITE
SASITE
WNDWXX
TTDIFF
USERIN
0
0
0
0
0
719
0
5. PROCESSING ASSUMPTIONS
WIND SPEED/TURB. MEASUREMENT HEIGHT (M):
STACK HEIGHT (M)
TEMPERATURE HEIGHT (M)
10.00
10.00
2.00
6. LOCATIONS SPECIFIED IN SETUP
DATA
PATHWAY
UA
SF
OS
SITE
ID
24157
24155
LAFAYE
LONGITUDE
(DEGREES)
117.53W
118.85W
122.60W
LATITUDE
(DEGREES)
47.63N
45.67N
45.SON
*****************************************
* LONGITUDE AND LATITUDE FOR PROCESSING *
* 122.60 45.50 *
*****************************************
Figure 3-la Report file for Stage 3 processing (1 of 2)
3-18
-------
METEOROLOGICAL PROCESSOR FOR REGULATORY MODELS [MPRM (dated 96030)]
30-JAN-96 10:27:33
STAGE-3 PROCESSING OF MERGED METEOROLOGICAL DATA
7. OUTPUT FILE NAMES.
ERROR REPORT FILE:
MET DATA FOR MODELING:
HEADER ON OUTPUT FILE:
TEST324.ERR
TEST324.0UT
24157
94
24155
94
8. SUMMARY OF DATA PROCESSING RESULTS
VARIABLE # VALID # MISSING
STABILITY 719 1
WIND SPEED 673 1
WIND DIRECTION 719 1
RURAL MIXING HEIGHT 719 1
URBAN MIXING HEIGHT 719 1
TEMPERATURE 719 1
9. DISTRIBUTION OF WIND SPEEDS
46 (Calms)
5.16 (Average)
WS CLASS 12345
# HOURS 235. 265. 138. 31.
AVERAGE 1.38 2.42 4.07 6.38 9.
10. RURAL STABILITY CATEGORY RESULTS (# HOURS)
A B C DD DN
0 20 41 213 205
4.
05
EF
240
6
0.
0.00
11. SURFACE CHARACTERISTICS USED
Month Sector Albedo Bowen zO(meas) zO(appl) Min. L
Cg
Anth Heat
1
2
3
4
5
6
7
8
9
10
11
12
1
2
3
4
5
6
7
8
9
10
ir
12
1
1
1
1
1
1
1
1
1
1
1
1
2
2
2
2
2
2
2
2
2
2
2
2
0.5000
0.5000
0.1200
0.1200
0.1200
0.1200
0.1200
0.1200
0.1200
0.1200
0.1200
0.5000
0.3500
0.3500
0.1400
0.1400
0.1400
0.1600
0.1600
0.1600
0.1800
0.1800
0.1800
0.3500
1.5000
1.5000
0.7000
0.7000
0.7000
0.3000
0.3000
0.3000
1.0000
1 .0000
1 .0000
1.5000
1.5000
1.5000
1.0000
1.0000
1.0000
2.0000
2.0000
2.0000
2.0000
2.0000
2.0000
1.5000
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.5000
0.5000
.0000
.0000
.0000
.3000
.3000
.3000
0.8000
0.8000
0.8000
0.5000
1.0000
1.0000
1.0000
1 .0000
1.0000
1.0000
1.0000
1.0000
1.0000
1.0000
1.0000
1.0000
2.0000
2.0000
2.0000
2.0000
2.0000
2.0000
2.0000
2.0000
2.0000
2.0000
2.0000
2.0000
50.0000
50.0000
50.0000
50.0000
50.0000
50.0000
50.0000
50.0000
50.0000
50.0000
50.0000
50.0000
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.1500
0.2700
0.2700
0.2700
0.2700
0.2700
0.2700
0.2700
0.2700
0.2700
0.2700
0.2700
0.2700
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
Figure 3-lb Report file for Stage 3 processing (2 of 2)
3-19
-------
30 JB 103 HPPROC:
8 JB 119 HPSTUP:
0 OS W15 AUTCHK:
0 OS W15 AUTCHK:
0 OS W15 AUTCHK:
365 JB W06 HTKEY :
365 HP
365 HP
365 HP
365 HP
365 HP
365 HP
365 HP
365 HP
365 HP
365 HP
365 HP
365 HP
365 HP
T75 OS1PGT:
T76 ROUGH:
T75 OSSEPG:
T75 OSSEPG:
T76 ROUGH:
T75 OSSAPG:
T75 OSSAPG:
T75 OS2NWS:
T75 SFSTAB:
T75 OS1PGT:
T75 OSSEPG:
140 SFSTAB:
W75 SFSTAB:
IOSTAT= 3047 REACHED END OF HEADERS
FOUND "END OF FILE" ON DEVICE DEVIN 5
HHGT NOT IN INPUT LIST: AUDIT DISABLED
NRAD NOT IN INPUT LIST: AUDIT DISABLED
SE NOT IN INPUT LIST: AUDIT DISABLED
NO TT AT LVL01. TMPHGT IS: 2.0
ISPD HISSING, HR 23 PGSTAB .EQ. 0
NO WD FOR ZO, HOUR 23
ZO HISSING FOR HOUR: 23
ISPD MISSING, HR 23 PGSTAB .EQ. 0
NO WD FOR ZO, HOUR 23
ZO MISSING FOR HOUR: 23
ISPD MISSING, HR 23 PGSTAB .EQ. 0
ISPD MISSING, HR 23 PGSTAB .EQ. 0
HOUR 23 NO PG CATEGORY POSSIBLE
OSTSKY HISSING, HR 24 PGSTAB .EQ.
SE & SW MISSING, HR 24 PGSTAB .EQ.
HOUR 24 USED STAB. SCHEME SASITE
23 HOURS HAVE 0 FOR PG CATEGORY
Figure 3-2 Partial listing of the error/message file, for example with trace option
enabled.
3-20
-------
SECTION 4
SCIENTIFIC NOTES
This section provides a brief technical description of the methods employed by
MPRM during processing. All of the methods are documented in the indicated references to
which the reader is referred for details. The methods employed during Stage 1 (Extraction
and Quality Assessment) are described first, followed by descriptions of the methods
employed in Stage 3 processing.
4.1 Stage 1
4.1.1 Averaging Sub-hourly Values
Hourly averaging is standard for most regulatory dispersion modeling and for the
meteorological monitoring conducted in support of such modeling. Nevertheless, many on-
site meteorological monitoring programs are designed for multiple purposes and
consequently, employ sub-hourly averaging ranging anywhere from seconds to 30 minutes.
The MPRM Stage 1 processor will accept sub-hourly averaged data ranging from 5 to 30
minutes. The number of observations per hour is specified using the optional run stream
input image OS AVG. The default value is one observation per hour; the maximum value is
12 (5-minute averaging).
The sub-hourly values are averaged producing hourly values during the extraction
process. For most variables the hourly value is computed as the arithmetic mean. Wind
speed and direction, however, are treated differently in order to properly differentiate
between cases when values are missing and cases when values are present but below
instrument threshold. The threshold wind speed by default is 1.0 ms"1: this can be redefined
using the OS CLM input image. Wind speeds less than the threshold are given a value of
one-half the threshold wind speed and -the wind direction is treated as missing (this procedure
for computing an hourly average should not be confused with the procedure for treatment of
calms discussed in Section 4.2.1.2). The hourly wind speed is computed as an arithmetic
mean. The hourly wind direction is computed according to the method given in (U.S. EPA,
1987) to properly account for the 0-360 degree crossover.
Hourly values of the standard deviation of the wind direction are computed as the
root-mean-square of the sub-hourly values, in accordance with the recommendations in (U.S.
EPA, 1987).
4.1.2 Quality Assessment
In Stage 1 processing. QA is performed on each pathway by comparing data values to
the upper and lower bounds defined for each variable. Default QA bounds are defined in
Appendix C. but these values can be overridden by the user with the CHK input image. The
4-1
-------
endpoints of the interval, i.e., the boundary values, are either included as acceptable data or
excluded as questionable data according to the Range Check Switch field. This parameter
can also be changed with the CHK input image. The default value of the Range Check
Switch for each variable is also defined in Appendix C.
4.1.2.1 QA of Upper Air Data
Prior to performing the quality assessment on upper air soundings, the processor
recomputes the heights reported in the soundings using the hypsometric formula. If the
surface height is missing, the heights are not recomputed.
Because the upper air soundings contain multiple levels of data, vertical gradients of
several variables can also be checked. This poses a question of how to report the audit
results as there are a variable number of levels in a sounding and the heights of the levels
differ from soundine to sounding. The MPRM solution is to stratify the data into ten height
categories as follows: surface, 0 to 500 m, 500 to 1000 m, ... 3500 to 4000 m, and greater
than 4000 m.
Lapse Rate - The gradient of temperature, or lapse rate, between two levels in the
upper air data is checked against an upper and lower bound. The default maximum value is
5 °C/100 m and the default minimum is -2 °C/100 in. Note that these values are in units of
"C/100 m; changes to the default values, using the UA CHK UALR input image, must be
entered in the same units.
Wind Shear - Wind velocity has two components: speed and direction. The vertical
gradient of the wind, or shear, can be expressed either as a vector shear in which both speed
and direction are combined to yield one shear value, or speed and direction separately. The
wind speed and direction shear are expressed separately in MPRM. The default maximum
wind speed shear is 5 (ms-l)/100 m. Because the absolute difference of the speed is
considered, i.e. the computation is independent of which level has the higher wind speed, the
default minimum speed shear is 0 (ms'^/lOO m. The variable name for use with CHK to
alter the range check parameters for the wind speed shear is UASS. The default maximum
wind direction shear is 90 degrees/100 m and the minimum is 0 degrees/100 m. The
directional shear is independent of which way the wind changes with height (i.e., clockwise
or counterclockwise). The variable name for use with CHK to alter the range check
parameters for the wind direction shear is UADS.
Dew-Point Temperature Gradient - The vertical gradient of dew-point temperature
is treated a little differently than the lapse rate and wind shear. Three consecutive values are
required for this evaluation. An estimate from the line drawn between the upper and lower
points is made at the height of the middle point. The absolute difference between the
estimate and the actual dew-point is divided by the height difference between the upper and
lower points. This value is compared to the upper and lower bounds defined by UADD.
The default upper and lower bounds are 2 °C/100 m and 0 °C/100 m, respectively.
4-2
-------
The violations for the lapse rate and shear are tallied into the height category
containing the upper height, whereas the dew-point violations are tallied into the height
category containing the middle point. Therefore, if none of the data required to perform the
gradient calculations are missing, then there are (N-l) checks on lapse rate and shear and
(N-2) checks on dew-point, where N represents the number of levels in a sounding.
4.1.2.2 Upper Air Data Modification
By default, some cleanup is performed on the upper air data during the extraction
process. This housekeeping involves the following QA procedures:
• Temperature above 1000 m
• Lapse rate
• Redundant level
• Calm conditions
• Missing dry bulb and/or dew-point
• Height of sounding.
The above QA procedures may be deactivated through the use of the optional input
image UA OFF. The UA OFF image deactivates all of the above actions; there is no way to
deactivate individual actions.
Temperature above 1000 m - For heights above 1000 m above ground level (AGL),
temperatures greater than 10 °C are checked to insure they have the correct sign. The sign
of the temperature immediately below the level in question is checked. If the sign is
negative, then the sign of the temperature at the level in question is changed to negative; if
the sign is positive or if the temperature is missing, then no action is taken. This action was
introduced to reduce the number of sign errors that occur in the TD-5600 format data. The
primary emphasis is on levels away from the surface where it is obvious that the signs were
in error. No attempt is made here to correct the data near the surface. Checks of
temperatures fluctuating around 0 °C are also avoided, where the temperature can switch
signs from one level to the next, by only considering temperatures greater than 10 °C.
Lapse rate - If the temperature lapse rate between two levels is superadiabatic, i.e.,
less than -0.0098 "Cm'1, and the lower level temperature is greater than 0 °C, the sign of
the lower level temperature is changed. This sign change is not performed if it would create
a temperature inversion greater than the maximum defined with the keyword UALR, i.e., the
lapse rate upper bound for quality assessment (see Appendix C for default value).
Redundant level - If a mandatory sounding level is within 1 percent of a significant
level (with respect to pressure) then the mandatory level is deleted. Because the mandatory
levels were originally computed from the data at the significant levels, there is no loss of
information in the sounding.
4-3
-------
Deleting mandatory levels occurs after the data are retrieved from tape, which results
in reducing the number of levels in a sounding. If the maximum number of levels is
retrieved, then this process will produce a sounding with fewer than the maximum number of
levels, i.e., the processor does not return to the tape to retrieve-additional levels. The
maximum number of levels that can be retrieved is 20.
Calm conditions - The wind speed and direction at each level are checked to insure
that there are no levels with a zero wind speed and a non-zero wind direction. If one is
found, the wind direction is set to zero to represent calm conditions.
Missing dry bulb and/or dew-point - If temperature or dew-point at a level is
represented by a missing value indicator, then an estimate for the missing observation is
made by linearly interpolating to the level in question. The data from the level immediately
below and the nearest valid data from above the level in question are used. If data that are
required for the interpolation are also missing, then no interpolation is performed.
Sounding heights - The sounding heights on magnetic tape are stored as meters above
mean sea level. With the sounding modification actions enabled, the heights are converted to
meters above ground level. The first level in a sounding is for the surface. The height at
this level is subtracted from all levels including the surface, so that the heights start at 0 m.
If the height is missing at the surface, then a value of zero is assumed in performing the
subtractions.
Modifications to an upper air data file are tracked in the Stage 1 error/message file;
an example is provided in Figure 4-1. The warning messages that are written if the data are
modified include the date and time. The format is YYMMDD/HH where YY = 2-digit
year, MM = month (1-12), DD = day (1-31) and HH = hour (1-24). The example
error/message report shown in Figure 4-1 indicates that 13 mandatory levels were determined
to be redundent and were deleted. In addition, the sign on two temperature values was
corrected.
4-4
-------
12 JB 119
0 JBW12
0 JBI10
JBI11
JBI12
JB 110
JB 111
JBI12
UAI30
UA 136
UAI37
UAI37
UAI37
UAI37
UAI37
UAI37
UAI37
UAI37
UAI37
UAI37
UAI37
UAI37
UAI37
UAI37
UA 137
UAI39
UAI30
0
0
0
0
0
0
0
0
1
1
2
1
2
3
2
1
1
3
1
1
6
0
SETUP: ENCOUNTERED END OF "JOB/RUN CARD"
UAQAST: SUMMARY: MISSING/ERRORS IN UA-OQA CARD
TEST: SUMMARY: NO SF-EXT CARD, NULL EXTRACT
TEST: SUMMARY: NO SF-IQA CARD, NULL QA
TEST: SUMMARY: NO SF-OQA CARD, NULL MERGE
TEST: SUMMARY: NO OS-EXT CARD, NULL EXTRACT
TEST: SUMMARY: NO OS-EXT CARD, NULL QA
TEST: SUMMARY: NO OS-EXT CARD, NULL MERGE
UAEXT: **** UPPER AIR EXTRACTION ****
UAEXT: * *** AUTOMATIC SDG, CHECKS ARE ON
UAAUTO: 64 1 II 7; LVL 6 -TEMP. SIGN CHANGE
UAAUTO: 64 1 1/19; 450.MB -MAND. LVL DELETED
UAAUTO: 64 1 21 7; 90Q.MB -MAND. LVL DELETED
UAAUTO: 6412/7; 850.MB-MAND. LVL DELETED
UAAUTO: 6412/19; 950.MB-MAND.
UAAUTO: 64 1 2/19; 900.MB -MAND.
UAAUTO: 64 1 2/19; 600.MB -MAND.
UAAUTO: 64 1 2/19: LVL 8 -TEMP. SIGN CHANGE
UAAUTO: 64 1 3/ 7; 700.MB -MAND. LVL DELETED
UAAUTO: 64 1 3/19; 900.MB -MAND. LVL DELETED
UAAUTO: 64 1 4/ 7; 850.MB -MAND. LVL DELETED
UAAUTO: 64 1 4/ 7; 500.MB -MAND. LVL DELETED
UAAUTO: 64 1 4/ 7; 450.MB -MAND. LVL DELETED
UAAUTO: 64 1 5/ 7; 950.MB -MAND. LVL DELETED
UAAUTO: 64 1 5/19: 900.MB -MAND. LVL DELETED
GETMIX: END-OF-FILE, END-OF-DATA
UAEXT: 11 SDGS AND 6 MIXING HTS EXTRACTED
LVL DELETED
LVL DELETED
LVL DELETED
Figure 4-1 Example Stage 1 Error/Message Report Tracking Modifications to an
Upper Air Data File
4-5
-------
4.2 Stage 3 Processing
4.2.1 Wind
4.2.1.1 Default Processing
The default method for handling wind data by MPRM is to use NWS surface
observations. The data are hourly and result from observations made at a single level. No
input is required for implementation. If the data are missing, then a missing value indicator
is written to the output file, and a message is inserted in the error/message file to warn the
user that this has occurred.
4.2.1.2 Treatment of Calms
Calm winds are handled somewhat differently for dispersion models requiring hourly
meteorological data versus those requiring STAR output. The following calms procedures
are used for those models which require unformatted (binary) hourly meteorological data:
NWS Data - For NWS data, if the wind speed is less than 1 ms'1, then the
speed is reset to 1 ms"1 and the wind direction is set to the last valid, non-
randomized wind direction value.
Cm-site Data - For on-site data, if the wind speed is less than the threshold
(OSCALM). then the speed is reset to 1 ms"1 and the wind direction is set to the last
valid wind direction value. If the on-site wind speed is less than 1 ms"1 but greater
than or equal to the threshold, the speed is reset to 1 ms"1 and the wind direction is
accepted as valid. This procedure should not be confused with the procedure for
obtaining an hourly averaged wind speed described in Section 4.1.1.
For the formatted (ASCII) output option available with ISCST, the procedures for
identifying calms are the same: however, when a calm is detected both the wind speed and
wind direction are reset to 'zero'.
For those models requiring STAR output, the occurrences of calm winds are
distributed within the lowest wind speed classes in accordance with the directional
distribution of non-calm observations within these classes.
4.2.1.3 Measurement Height
As discussed in Section 4, the OS MAP image provides the list of variables available
in the on-site data base. The OS MAP image may have include several levels of wind data.
In such cases, MPRM needs to be told which level to use in processing the data for use in a
dispersion model. This is accomplished using the following input image:
MP VBL WIND ONSITE stkhgt
4-6
-------
where stkhgt is a place holder for the measurement height.
The dispersion models supported by MPRM require only one level of wind data for
use in calculating plume rise, and for estimating plume transport and dilution. Applicable
guidance (Appendix W to 40 CFR Part 51) recommends that wind measurements
representative of stack-top height be used for these estimates. MPRM has been designed to
use wind data from the level closest to the value for stkhgt. This measurement level is then
used in all further processing of wind data. In defining the measurement level, MPRM
interrogates the OS MAP input images to insure that wind data are available at this level;
processing is stopped if it is determined that no wind data are available. Since any value
greater than zero for stkhgt is allowed, the user can specify the level that is best for the
given dispersion analysis. This may or may not be the level nearest to the actual height of
the stack being modeled, as the data may not be representative for one reason or another, or
more likely, the data may not be sufficiently complete at all levels (see guidance on
completeness requirements hi U.S. EPA, 1987).
Consider the case of on-site wind data being available at 10, 60 and 100 m on a
meteorological mast, and the stack height to be modeled is 300 m. The user could include as
input during Stage 3 processing:
MP VBL WIND ONSITE 300
MPRM would then process the 100 m wind data, the level closest to 300 m, for generating
the modeling output file. What would happen if the 100 m data were only available during a
small portion of the period to be analyzed? Perhaps, the instruments at 100 m were damaged
and replacement was delayed. Then the input could be modified to force MPRM to select
the wind data at a lower level where the observation record is more complete; e.g.:
MP VBL WIND ONSITE 60.
For regulatory applications, such procedures should be cleared with the appropriate authority.
4.2.2 Temperature
4.2.2.1 Default Processing
The default method for processing temperature data is to use NWS surface
observations. The data are hourly and result from observations made at a single level. No
input is required for implementation. If the data are missing, then a missing value indicator
is written to the output file, and a message is inserted in the error/message file to warn the
user that this has occurred.
4-7
-------
4.2.2.2 Measurement Height
As discussed in Section 4, the OS MAP image provides the list of variables available
in the on-site data base. The OS MAP image may include several levels of temperature data.
In such cases, MPRM needs to be told which level to use in processing the data for use in a
dispersion model. This is accomplished using the following input image:
MP VBL TEMP ONSITE tmphgt
where tmphgt is a place holder for the measurement height.
Temperature data for use in regulatory dispersion modeling is normally measured at a
level representative of the surface layer (nominally 2 m), [U.S. EPA, 1987]. However.
depending on the specific applicaton, other levels may be more apropriate. As with multiple
levels of wind data, MPRM will use temperature data from the level closest to the value for
tmphgt.
For example, consider a case involving temperature data at two levels (10 and 100
m). The following input image could be used to specify use of the surface layer
temperature:
MP VBL TEMP ONSITE 2
MPRM would then process the 10 m temperature data, the level closest to 2 m, for
generating the modeling output file.
4.2.3 Stability
Stability processing in MPRM supports those dispersion models which employ the
Gaussian plume algorithm with Pasquill-Gifford (P-G) plume dimensions and stability
categories; these models employ P-G stability categories which originally were based on
insolation, cloud cover, and 10 m wind speed (Pasquill, 1961). Turner (1964) provided an
objective method for estimating P-G stability based on wind speed, cloud cover and ceiling
height - data which are routinely available for many airports.
MPRM provides three choices for implementing Turner's method depending on the
source of the meteorological data: 1) all airport data; 2) all site specific data; and 3) a
mixture of airport and site specific data. Alternative methods for use when representative
cloud cover and ceiling observations are not available are also supported. These include a
radiation-based method which uses on-site measurements of solar radiation and delta-T
(SRDT) and two turbulence-based methods which use on-site wind fluctuation statistics
(Sigma-A and Sigma-E).
4-8
-------
Detailed guidance on estimating P-G stability is provided in (U.S. EPA, 1987).
Turner's (1964) method with site-specific wind speed measurements at or near 10 m and
representative cloud cover and ceiling height is preferred for regulatory applications. There
is no order of preference for the alternative methods.
A summary of the stability classification methods implemented in MPRM is presented
m Table 4-1,
Table 4-1 Stability Classification Methods Implemented in MPRM
Method
Turner (1964) .
SRDT
Sigma-E
Sigma-A
MPRM Action
NWSWXX
ONSITE
WNDWXX
TTDIFF
SESITE
SASITE
USERIN
Description
Uses NWS wind speed, ceiling height, and
cloud cover (opaque or total)
Uses on-site wind speed, ceiling height, and
cloud cover (opaque or total)
Uses on-site wind speed with NWS ceiling
height and cloud cover (opaque or total)
Uses on-site wind speed in combination with
solar radiation during the day and vertical
temperature difference at night
Uses the standard deviation of the elevation
angle of the wind vector
Uses the standard deviation of the azimuth
angle of the wind vector
Stability category is provided as input
Turner's (1964) method - Turner presented a method for determining Pasquill
stability categories from data that are routinely collected at National Weather Sendee (NWS)
stations. The method estimates the effects of net radiation on stability from solar altitude (a
function of time of day and time of year), cloud cover (opaque is preferred, otherwise total if
opaque is missing), and ceiling height.
Solar radiation/delta-T (SRDT) method - The solar radiation/delta-T (SRDT)
method retains the basic structure and rationale of Turner's method while obviating the need
for observations of cloud cover and ceiling. The method uses the surface layer wind speed
(measured at or near 10 m) in combination with measurements of total solar radiation during
the day and a low-level vertical temperature difference (AT) at night. The method is based
4-9
-------
on Bowen et al. (1983) with modifications as necessary to retain as much as possible of the
structure of Turner's method. The classification algorithm is empirically based on evaluation
results from three different geographic locations (U.S. EPA, 1993).
Sigma-E method - The Sigma-E (
-------
4.2.4 Mixing Height
The default method for processing mixing height is to use the interpolation scheme
employed in the RAMMET meteorological processor, which uses the twice-daily mixing
heights from the nearest NWS upper air observation site, coupled with the stability category
determined for the hour. This method is described hi more detail hi the RAM model user's
guide (Catalano et al., 1987). The user may also designate the on-site mixing height to be
employed. In this case MPRM will use the value for the hour given hi the on-site
observation.
4.2.5 Surface Characteristics
MPRM provides the means to specify direction-dependent surface characteristics for
use hi estimating boundary layer parameters (see Section 4.3). The surface characteristics
are: albedo, Bowen ratio, surface roughness length (at the measurement site and at the
application site), minimum Monin-Obukhov length for stable conditions, fraction of the net
radiation absorbed at the ground, and anthropogenic heat flux. Information on specifying
these surface characteristics is provided hi Section 3.3. The following defaults apply if
values are not specified:
Albedo 0.25
Bowen Ratio 0.70
Roughness (measurement site) 0.15 m
Roughness (application site) 0.15 m
Minimum M-O Length 2.00 m
Surface Heat Flux (fraction of net) 0.15
Anthropogenic Heat Flux 0.00 Wm2
The default values are typical for cultivated land with average moisture and will not
apply to all modeling situations.
The roughness length is used hi Stage 3 processing to adjust the aE and
-------
velocity (u*) is a characteristic velocity based on (wind) shear stresses at the earth's surface.
The Monin-Obukhov length (L) is a stability parameter that relates this velocity to the
transport of heat. This section presents the technical aspects of the computations hi MPRM.
Stull (1988) provides a good introduction to the theoretical basis for estimating these
parameters.
The day is divided into two regimes: unstable and stable. The atmosphere is unstable
if the time of day is between sunrise and sunset and the transfer of heat is away from the
surface. The atmosphere is considered stable if the time of day is between sunset and sunrise
(of the next day) and the transfer of heat is toward the earth's surface. The estimation of
these parameters for the unstable and stable boundary layer are discussed in the following.
Section 4.3.3 discusses the adjustment of these parameters for the application (receptor) site.
4.3.1 Unstable Boundary Layer Parameters
During daytime convective conditions (L < 0), the surface of the earth is heated,
resulting in an upward transfer of heat. Hourly estimates of this heat flux are required to
estimate u* and L. The estimates for the heat flux here follow the development of Holtslag
and van Ulden (1983). The heat flux is estimated directly from measurements of net
radiation (if such measurements are available) using equation 4.2. Alternatively, the net
radiation is estimated from measurements of solar insolation (if available) and cloud cover
using equation 4.6. If such radiation measurements are not available, then the heat flux is
estimated from cloud cover, surface temperature, Bowen ratio and albedo as described
below.
Once the heat flux is computed, u* and L are determined through an iterative
procedure using surface layer similarity. While u* and L change with each iteration, the
hourly heat flux remains fixed.
A simple equation that expresses the energy balance at the earth's surface is:
R+ = H + \E + G (4.1)
where RN is the net radiation, Qf is the anthropogenic heat flux, H is the sensible heat flux,
XE is the latent heat flux, and G is the flux of heat into the ground. Each term is expressed
as W m"2. The value of G is assumed to be proportional to the left side of Eq. 4.1, i.e., G
= cg(RN + Qj), where cg is the fraction of the net radiation absorbed at the ground, and is
specified by the user. Using this estimate for G and the definition of the Bowen ratio, B0 =
HIXE, which was specified by the user, the following expression for the sensible heat flux,
H, is obtained
4-12
-------
H - (L° « (4.2,
where KA* = RN + Qf.
The net radiation RN is estimated from the total incoming solar radiation. R, as
(4-3)
where r is the user-specified noon-time albedo (dimensionless), and IN is the net long- wave
radiation at the earth's surface as given by Holtslag and van Ulden (1983). The
anthropogenic heat flux specified by the user is then added to the net radiation to obtain RN .
In the general case in which clouds are present. R is computed using the following
formula proposed by Kasten and Czeplak (1980)
where R0 (W m"2) is the incoming solar radiation at ground level for clear skies, and N is the
fractional opaque cloud cover. The empirical coefficients b1 and b2 are assigned the values
of -0.75 and 3.4. respectively. If cloud cover is missing for a particular hour, then MPRM
assumes overcast conditions (i.e.. 10/10 cloud cover) and proceeds with the calculations. A
warning message is written to the log file to indicate such an occurrence.
The incoming solar radiation for clear skies R0 is given by
where g> is the elevation of the sun above the horizon (degrees), a1 = 990 W m"2 and
a-, = -30 W m"2. The constants a} and a2 account for attenuation of the short wave radiation
by water vapor and dust in the atmosphere. The values used in MPRM are appropriate for
mid-latitudes (Holtslag and van Ulden. 1983).
Substituting Eqs. 4.4 and 4.5 into Eq. 4.3 and parameterizing the net long-wave
radiation as a function of temperature and cloud cover, Holtslag and van Ulden (1983)
estimate the net radiation as
4-13
-------
- aSBT4
(4.6)
1 + c,
where aSB = 5.67 X 10"s W m"2 K"4 is the Stefan-Boltzmann constant, and the other
empirical constants are as follows:
Cj = 5.31 x 10'13 W m'2 K'6,
C2 = 60 W m'2,
c3 = 0.12.
by:
An empirical expression for the albedo as a function of solar elevation angle is given
r = r' + (1 -r')eaw*
/\ -av f b
(4.7)
where r' is the surface albedo (dimensionless) for the sun on the meridian specified by the
user, v is the solar elevation angle in degrees, a = —0.1, and b = —0.5 (1 — r')2.
MPRM next computes the surface friction velocity H* and the Monin-Obukhov length
L for the unstable atmosphere through an iterative procedure that is similar to the technique
used in the METPRO processor (Paine, 1987). The two equations for w* and L used in the
iteration algorithm are:
" =
kU
In
(4.8)
and
kgH
where:
(4.9)
H is the sensible heat flux at the surface (W m"2),
k is the von Karman constant,
U is the wind speed (m s"1),
zri,fis the anemometer height (m),
Z0 is the surface roughness at the measurement site (m) specified by the user,
p is the density of dry air (kg m~3),
cp is the specific heat capacity of air (1004 J kg"1 K"1),
4-14
-------
T is temperature (K), and
g is the acceleration due to gravity (9.81 m s~2).
The values for ¥ and ^0 (Lumley and Panofsky, 1964; Businger, 1973) are:
= 2 In
i V
In
(4.10)
= 21n
+ In
-i/
- 2tan-JGO -
(4.11)
where
- 16zr,f/L)1/4
, = ( 1 - 16z0 / L )
1/4
(4.12)
(4.13)
This procedure requires an initial guess for w*. which is found by initially setting %
and SI^,'to.zero. The iteration continues until consecutive values of L differ by 1 % or less.
4.3.2 Stable Boundary Layer Parameters
The calculations of u* and L for the stable atmosphere (L > 0) are based on an
approach outlined by Venkatram (1980). The approach does not require an iterative
procedure as used for the unstable atmosphere. Estimates of w* and 0* (a temperature scale)
are made from cloud cover, wind speed and temperature. This, in turn, provides an estimate
of the heat flux, and L is computed directly from Eq. 4.9.
The method begins with the following estimate for 0*:
B* ='0.09(1-0.5N2)
where N is the fraction of opaque cloud cover. The neutral drag coefficient, CD
(dimensionless). is calculated as
(4.14)
ln(z
(4.15)
ref
4-15
-------
The friction velocity is determined from
«. = CDU/2 (!+(!-( 2u0 I
where
and (3m = 4.7 is a dimensionless constant.
To obtain real-valued solutions for w*, the following must hold
(4.16)
(4.17)
(4.18)
If this condition holds, then u* is computed from Eq. 4.16; if this condition does not
hold (under very stable conditions), then the solution to the quadratic equation is imaginary,
and a slightly different approach is taken.
Equality in the above condition corresponds to a critical (minimum) wind speed. Ucr,
for which a real-valued solution to Eq. 4.16 is
TCT
(4,19)
For this value, there is a corresponding friction velocity, «*C7., such that
(4.20)
For wind speeds less than this critical value, Eq. 4.16 no longer yields a real-valued
solution, and it is desirable to have w* -> 0 as U -» 0. Therefore, for U < Ucr, u*cr is scaled
by the ratio U / Ucr. and w* is calculated as
4-16
-------
" "
1L (4.21)
For U < Ucr, van Ulden and Holtslag (1985) showed that there is a nearly linear variation
of 0* with H*. Therefore, 0* is similarly scaled as
e = e _^L <4-22>
*-' * w */•»•
With the u* from Eq. 4.16 or 4.21 and the 0* from Eq. 4.14 or 4.22, the heat flux H is
computed as
H = -pcpu,6f . (4-23>
Finally, usins these estimates of w* and H. L is computed from Eq. 4.9.
J *—•
In the case of strong winds, # may become unrealistically large. Therefore, a limit
of -64 W m'2 is placed on the heat flux, which forces a limit on the product «*0*. This
yields a cubic equation in «*, which is solved to obtain a new u*. With this new value for H,
and H = -64 W m'2. L is recomputed from Eqs. 4.9 and 4.23 as:
L = T u* / (k g 0*)'.
If the value of the Monin-Obukhov length is less than the minimum value specified by
the user, then L is reset to this minimum value and a new value for u* is computed.
4.3.3 Parameters at the Application Site
The discussion above focused on the estimates at the measurement site. Typically,
the measurement site is not the location where the output meteorological data from MPRM
are to be applied. Dry deposition estimates are sensitive to the value of the friction velocity.
Therefore, the friction velocity and Monin-Obukhov length estimated for the measurement
site are adjusted to represent the site where the output is to be applied. With the surface
roughness length entered by the user for the application site and the estimates of u* and L at
the "measurement site, u* and L representative of the application site are estimated and
written to the output file.
4-17
-------
Walcek et al. (1986) suggest that near the surface
«i«.i B "2 ".2
for changes in the underlying surface roughness, where the subscripts 1 and 2 represent the
previous and current estimates. MPRM incorporates this approach to estimate u* and L at
the application site.
With the roughness length representative of surface conditions at the application site,
a new estimate for u* is obtained through an iterative process using surface layer similarity.
The Monin-Obukhov length is obtained from
Lo = Lj (u*2/u*])3
(on the first iteration, the subscript 1 represents the value at the measurement site). When
two consecutive estimates of u» are within 1 %, then the process stops.
4-18
-------
SECTIONS
NOTES FOR PROGRAMMERS
5.1 Introduction
The original MPRM processor was designed and coded to run on most operating
systems of the day. In 1988 when MPRM was first released these included VAX and IBM
mainframes, and the IBM PC-XT and compatible personal computers. Since then personal
computing power has advanced considerably, whereas mainframe computing has remained
relatively static. The changes to MPRM over the years reflect these trends; i.e., no new
features have been added and few changes have been made to routines that are mainframe
oriented. As this trend continues, it is expected that there will be a diminishing need to
maintain a mainframe compatible code.
The advances in personal computing which most affect MPRM are the increase in
processing speed, the increase in memory, and the introduction of CD-ROM memory. The
IBM PC-XT, which was state-of-the-art in 1988, was limited to 640K of main memory. The
original MPRM processor was designed with this memory limitation in mind; a modular
design was necessary in order to make use of overlays during execution.
Advances in PC memory structure over the years have essentially done away with the
640K limitation such that overlays are fast becoming a thing of the past. Some of the recent
additions to MPRM (e.g., the incorporation of the random number file in the source code)
have more-or-less assumed that the processor would be run on a PC with extended memory.
The following topics are covered in the remainder of Section 5: Fortran
Compatibility and Extensions (Section 5.2), Compiling for Extended Memory (Section 5.3).
5.2 Fortran Compatibility and Extensions
To retain portability, the MPRM processor was coded using American National
Standards Institute (ANSI) Fortran X3.9-1978 or, as it is more commonly known,
Fortran-77. Extensions to Fortran-77 were avoided with the following exceptions:
INCLUDE statements, OPEN statements, character conversion, system date and time, and
extended error handling. These are described in the following. The filenames of the MPRM
Fortran source code files are listed in Table 5-1.
5.2.1 INCLUDE Statements
Nearly all the subroutines in the MPRM processor contain statements to include
named COMMON blocks. The method for incorporating these statements into the source
5-1
-------
code varies according to the compiler in use, but all use some form of the nonstandard
INCLUDE statement. These statements appear as extensions to VAX-11 FORTRAN
(version 3 0), IBM VS FORTRAN (version 2), RM/FORTRAN (version 2.10), Microsoft
FORTRAN (version 4.1),,and Lahey FORTRAN (version 5.2).' The syntax for each of these
is shown below. The punctuation is required where shown except for the left and right
bracket which indicates an optional parameter. In the accompanying examples, the
assumption is made that the INCLUDE files are in the same subdirectory or partitioned data
set as the main programs and subroutines that use them.
VAX-11 FORTRAN
INCLUDE 'filename[/LIST]', where filename is any valid VAX file specification and
/LIST, which is optional, indicates that the statements are to be listed in the
compilation source listing. If /LIST is omitted then no listing of the included files
appears in the compilation listing.
Example: INCLUDE'MAIN1.INC/LIST'
IBM VS FORTRAN
INCLUDE (name) [n], where name is the member name hi the partitioned data set
and n is a value used to decide whether or not. to include the file during compilation.
This parameter can be omitted, in which case the file is included, or can take on a
value from 1 to 255. If the value of n appears in the CI compile option, then the file
is included, otherwise it is omitted. This is not the simple list or no list option, rather
it includes or excludes the named member in the compilation.
Example: INCLUDE (MAIN1)
RM/Fortran, version 2.10
Microsoft Fortran, Version 5.1
Lahey Fortran, Version 5.2
INCLUDE 'filename', where filename is any valid DOS file specification.
Example: INCLUDE'MAIN1.INC'
5.2.2 OPEN Statements
The subroutines that use OPEN statements for disk files and magnetic tapes have been
placed in separate files to expedite the transfer of source code between systems. These files
are SETUPVX.FOR for VAX applications, SETUPPC.FOR for PC applications and
SETUPIBM.FOR for IBM mainframe applications. The subroutines in these files control the
5-2
-------
opening of disk files (subroutine ELOPEN) and magnetic tapes (subroutine TPOPEN) and
perform operations on ASCII and EBCDIC positional codes.
5.2.3 Character Conversion
Subroutines for character conversion are contained in LIBVX. FOR (for VAX),
LIBPC.FOR (for PC) and LEBIBM.FOR (for IBM). The character conversion subroutine
(CHCONV) is used in converting EBCDIC characters on magnetic tape to ASCII characters.
It uses the VAX octal representation of characters. This conversion is only required on the
VAX. Because magnetic tape drives are not normally available on personal computers and
because the IBM operates with EBCDIC, a dummy subroutine has been provided for these
systems.
5.2.4 System Date and Time
Subroutines to return the system data and time are contained hi the same files as the
subroutines for character conversion: LIBVX.FOR (for VAX), LIBPC.FOR (for PC) and
LffiffiM.FOR (for IBM).
5.2.5 Extended Error Handling
An extended error handling subroutine for use on IBM mainframes is included in
IIBIBM.for. This routine allows uninterrupted processing of data files typically available
from NCDC. Dummy subroutines are provided for VAX and PC applications.
5.3 Compiling for Extended Memory
Due to the large memory requirements, a compiler which makes use of extended
memory is recommended. The MPRM source code has been compiled and tested using two
extended memory compilers: the Lahey F77L-EM/32 Fortran compiler and the Lahey
Fortran 90 compiler. Instructions for compiling and linking with these compilers are
provided hi Sections 5.3.1 and 5.3.2.
5.3.1 Lahey F77L-EM/32 Compiler
The commands to compile and link MPRM using the Lahey F77L-EM/32 Fortran
extended memory compiler (version 5.2) are presented in the following:
f7713 COMPLETE.FOR /b /i /I /no /nw
f7713 HEADER.FOR /b /i /I /no /nw
f7713 LIBFILE.FOR /b /i II /no /nw
f7713 LIBPC.FOR /b /i /I /no /nw
f7713 MERGE.FOR /b /i II /no /nw
f7713 MP2XFOR.FOR /b /i II /no /nw
5-3
-------
JF7713 MP3XFOR.FOR /b /i /I /no /nw
f7713 MP4XFOR.FOR /b /i /I /no /nw
£7713 DEPMET1.FOR /b /i /I /no /nw
f7713 DEPMET2.FOR ' /b /i /I /no /nw
f7713 OSEELE.FOR /b /i /I /no /nw
f7713 OSSETUP.FOR /b /i /I /no /nw
f7713 OSSRPG.FOR /b /i /I /no /nw
f7713 SETUP.FOR /b /i /I /no /nw
f7713 SETUPPC.FOR /b /i /I /no /nw
f7713 SFFILE.FOR /b /i /I /no /nw
f77I3 STAGE1N2.FOR /b /i II /no /nw
f77D STAGES.FOR /b /i /I /no /nw
f7713 UAFILE.FOR /b /i /I /no /nw
where the switches after the filename provide the following control:
/b checks array subscripts and character substring bounds;
/i interface checking between subprograms;
/I lists line numbers in the event the executable program terminates abnormally;
/no compiler options are not displayed when a file is compiled;
/nw warning messages are not displayed when a file is compiled.
MPRM generates many warning messages as a result of the variables in the
INCLUDE (.INC) files, hence, the /nw switch. If changes to the code are more extensive
than the simple changes to array limits, then this switch should be removed to list the
warning messages and identify potential problems.
After the Fortran source files have been compiled, they can be linked to create an
executable program. To create the executable STAGE1N2.EXE, the following statement is
used:
386LINK STAGE1N2,COMPLETE,HEADER,SETUP1,SETUP2,
SETUPPC,SETUP,LffiFILE,LIBPC,
SFFILE,UAFILE, OSFTLE,MERGE
-stub runb -exe STAGE1N2.EXE -pack
The switches after the filenames have the following effect:
-stub runb binds the Lahey/Phar Lap 3861 DOS-Extender to the (protected-mode)
executable,
-exe STAGE1N2 defines the name of the executable program, in this case,
STAGE1N2.EXE, and
5-4
-------
-pack performs data compression on the executable file.
The final step is optional and simply disables the 3 86 j DOS-Extender banner that is
shown whenever the executable program is run:
CFIG386 STAGE1N2.EXE -nosignon.
To create the executable STAGE3.EXE, the following statement is used:
386IINK STAGE3,COMPI^TE,HEADER,SETUP1,SETUP2,SETUPPC,
OSSETUP,IJBFILE,IJBPC,
MP2XFOR,MP3XFOR,MP4XFOR,OSSRPG,DEPMET1,DEPMET2
-stubrunb -exeSTAGE3.EXE -pack
The switches after the filenames have the same effect as for STAGE1N2.EXE. As before,
the final step is to disable the 386 j DOS-Extender banner with
CFIG386 STAGE3.EXE -nosignon.
Note that a math coprocessor is required to use the Lahey-compiled executables. The
minimum memory requirements to load STAGE1N2 is 807 Kb and 746 Kb to load STAGES.
5.3.2 Lahey Fortran 90 Compiler
The commands to compile and link MPRM using the Lahey Fortran 90 compiler are
presented in the following:
LF90 COMPLETE.FOR -c-chk
LF90 DEPMET1.FOR -c-chk
LF90 DEPMET2.FOR -c-chk
LF90 HEADER.FOR -c-chk
LF90 IIBFILE.FOR -c-chk
LF90 LEBPC.FOR -c-chk
LF90 MERGE.FOR -c -chk
LF90 MP2XFOR.FOR -c-chk
LF90 MP3XFOR.FOR -c-chk
LF90 MP4XFOR.FOR -c-chk
LF90 DEPMET1.FOR -c-chk
LF90 DEPMET2.FOR -c-chk
LF90 OSFILE.FOR -c-chk
LF90 OSSETUP.FOR -c-chk
5-5
-------
LF90 OSSEPG.FOR -c -chk
LF90 SETUP.FOR -c -chk
LF90 SETUPPC.FOR -c -chk
LF90 SFFILE.FOR -c -chk
LF90 STAGE1N2.FOR -c -chk
LF90 STAGES .FOR -c-chk
LF90 UAFJJLE.FOR -c-chk
The link and link response files for Stage 1 are:
LF90 @UNK1N2.LRF -out STAGE1N2.EXE -pack -bind
CFIG386 STAGE1N2 -nosignon
STAGE1N2.OBJ COMPLETE.OBJ HEADER.OBJ SETUP1.OBJ
SETUP2.OBJ SETUPPC.OBJ OSSETUP.OBJ LIBFELE.OBJ LIBPC.OBJ
SFFILE.OBJ UAFELROBJ OSFILE.OBJ MERGE. OBJ
The link and link response files for Stage 3 are:
LF90 @IINK3.LRF -out STAGE3.EXE -pack -bind
CFIG386 STAGES -nosignon
STAGES.OBJ COMPLETE.OBJ HEADER.OBJ SETUP1.OBJ
SETUP2.OBJ SETUPPC.OBJ OSSETUP.OBJ LIBFILE.OBJ
LIBPC.OBJ MP2XFOR.OBJ MP3XFOR.OBJ DEPMET1.OBJ
DEPMET2.OBJ MP4XFOR.OBJ OSSRPG.OBJ
5-6
-------
Table 5-1
MPRM Source Code Files
Filename
BLOCK1 INC
BLOCK2 INC
HAIN1 INC
MAIN2 INC
HP1 INC
OS1 INC
OS2 ' INC
SF1 INC
SF2 INC
UA1 INC
UA2 INC
WORK1 INC
COMPLETE FOR
DEPHET1 FOR
DEPHET2 FOR
HEADER FOR
LIBFILE FOR
LIBPC FOR
MERGE FOR
HP2XFOR FOR
HP3XFOR FOR
HP4XFOR FOR
OSFILE FOR
OSSETUP FOR
OSSRPG FOR
SETUP1 FOR
SETUP2 FOR
SETUPPC FOR
SFFILE FOR
STAGE1N2 FOR
STAGES FOR
UAFILE FOR
LIBIBM FOR
LIBVX FOR
SETUP IBM FOR
SETUPVX FOR
Size
12781
42312
2582
2292
14200
2871
4904
1765
4323
1395
6826
2035
37371
26077
15059
15313
76550
3541
34641
44318
18961
77730
31637
61921
6905
56494
39813
10163
107762
40469
43239
83947
3258
7157
11508
11019
Date
08-12-96
08-10-95
04-02-95
02-02-95
08-09-96
10-20-95
08-09-96
08-06-95
02-15-95
08-31-94
08-09-92
02-14-95
11-13-95
08-09-96
"08-09-96
08-16-92
01-25-96
08-14-96
01-25-96
07-24-96
05-14-96
05-14-96
07-22-96
08-09-96
01-23-96
10-17-95
11-30-95
02-09-95
08-09-96
01-25-96
08-09-96
12-04-95
09-14-88
09-14-88
09-20-92
04-16-92
5-7
-------
-------
SECTION 6
TROUBLESHOOTING
6.1 Abnormal Job Termination
The developers of MPRM anticipated that users of the software would occasionally
make mistakes and, consequently, have built in capability for error detection and reporting.
These error tracking procedures include such things as checks for correct use of MPRM
syntax, presence/omission of mandatory keywords, parameters, etc., and the availability of
specified files. The more serious/fatal errors result in an 'Abnormal Job Termination'.
If a fatal error is detected, a message indicating an abnormal job termination will be
written to the file defined in the JB OUT input image, if provided, or to the screen if a
report file has not been specified. In the latter case, one would not necessarily be aware of
the abnormal job termination. As this could lead to problems in subsequent processing, one
should always check the report file for the job status at the completion of each processing
stage. A successful run is indicate by a 'Job Terminated Normally' message.
An example report file from a job with a fatal error in the input run stream is shown
in Figure 6-1. The example is based on the Stage 1 example (extraction and QA of upper air
data) discussed in Section 2.1.1. Recall that the IQA input image is used in Stage 1 to
specify the file name for the output of the extraction process and is mandatory for Stage 1
processing of surface and upper air data. A fatal error results if, as in the example, this
input image is missing; a message indicating the error is written to the Stage 1 error/message
file and to the report file. The interpretation of these messages is discussed in Section 6.2.
6.2 Interpreting Run-time Error and Warning Messages
The messages generated by this example are shown in Figure 6-2. The fourth record
is the message resulting from the omission of the UA IQA image. The message is
deciphered as follows:
0 JB W12 UAEXST: SUMMARY: MISSIMG/ERRORS IN UA-IQA CARD
I I
1— Message (up to 40 characters)
— Subroutine where message was generated
L— Message code (Appendix E)
!— Pathway identification
!— Counter
The structure of all messages is identical. In the first field of the message is a
counter, which in this particular case has no significance. The second field indicates that the
6-1
-------
The structure of all messages is identical. In the first field of the message is a
counter which in this particular case has no significance. The second field indicates that the
message was generated at the JB level of logic within the processor. The conditions for the
generation of messages are:
• JB messages - most often when problems are encountered in deciphering the input run
stream or when the processor detects incomplete run stream information.
• UA, SF, OS, and MR messages - when problems are encountered in deciphering an
input run stream for the respective pathway, when data cannot be properly read, or
when suspect data are encountered during a quality assessment check.
The third field is a three-character message code. The first character indicates the type of
message: informational (I), warning (W), error (E), quality assessment (Q), trace (T). In
the example, the W indicates that this message is a warning. Warnings do not necessarily
prohibit data processing, error messages do. The two numbers following the first character
are used to provide additional information concerning this message. This additional
information is provided in Appendix E. In general, messages concerning input run stream
have message numbers from 0 to 20. Message numbers greater than 20 are generated while
reading data files or during quality assessment checks. The information provided in
Appendix E for message W12 is: "Missing/errors on an input image - may or may not be
fatal depending on the processing requested."
All messages generated during processing can be found in the error/message file,
defined in the JB ERR input image. This file can be very long if there are a substantial
number of messages; therefore, the file should be reviewed prior to printing to determine if
printing of the entire file is appropriate.
6.3 Other Run-time Problems
6.3.1 SF W43 SFLEVS-.OVRPNCH 11
The following warning message may appear during Stage 1 processing of NWS
surface data:
OSF W43 SFUEVS:OVRPNCH 11, IMPROPER DECODE ON 3362271
The warning is caused by the presence of a "K" hi column 58, used to denote "cloud
type". It turns out that characters such as "K", "M", "N", "O", and "R" normally occur in
this field as necessary to indicate certain cloud types. The warning may be disregarded.
6-2
-------
6.3.2 Missing Records
MPRM expects the data files provided for processing to be complete; i.e., there
should be a record for each hour in the period defined hi the EXT (extraction) input image.
Missing records can be detected indirectly in the report files for Stages 1 and 2. If one or
more records are missing, the number of records extracted, as indicated in the Stage 1
report, will be less than expected based on the extraction period. In such cases, the Stage 2
report'should be checked to determine when the missing records occurred; missing records
are indicated by a mismatch in the number of hours merged for a 24-hour period. Files with
missing records will not normally cause a fatal error in Stage 1 or 2. However, such files
should not be passed on to Stage 3 processing as unexpected results may be obtained. See
also discussion of missing data in Section 1.4 and discussion of floating point errors in
Section 6.3.6.
6.3.3 UA Processing not always needed -
Users should note that upper air data are not required for some of the models
supported by MPRM. The models that do not require upper air data are: VALLEY, ISCLT,
and CDM 2.0. Stage 1 and Stage 2 processing in support of these models need not include
data for the upper air (UA) pathway.
6.3.4 Hourly Label for On-site Data
Users should note that MPRM assumes that the label assigned to an hourly
observation or hourly average is the integer value for the hour beginning; e.g., an hourly
average for the period 01:00 to 02:00 should be assigned a time label of 01.
6.3.5 Hourly Labels - On-site versus NWS Data
Users should note that MPRM expects on-site data to be reported using a 01-24 hour
clock, the same clock that MPRM uses internally for processing. In preparing to merge
NWS data, which are reported using a 00-23 hour clock, MPRM reassigns the first record in
each day (i.e., the record with the hourly label: '00') to the previous day (relabeled as hour
'24'). This hi effect results in a mismatch at the end of a merge file of OS and SF data as
the last record would not normally include data for the SF pathway. To avoid this mismatch,
users should always extract an extra record from SF files. If necessary, the extra record
should be appended to the end of the SF file.
6-3
-------
6.3.6 Floating Point Error in Stage 3
If a floating point error occurs during Stage 3 processing and no obvious cause
presents itself, users should check to ensure that the meteorological data file is complete;
i.e., there should be no missing records (see discussion of missing records in Section 6.3.2).
One instance in which such errors have occurred is in the processing of NWS surface data to
determine P-G stabilities using the WNDWXX procedure (Table 4-1). A suggested solution,
if missing records are causing problems, is to insert necessary dummy records in the NWS
surface data file and reprocess the data beginning with Stage 1. The dummy records should
contain the station and date/time identifiers in columns 1-13; other fields should be filled as
per the guidance provided on SCRAM (see also discussion of missing data in Section 1.4).
6-4
-------
METEOROLOGICAL PROCESSOR FOR REGULATORY MODELS [MPRM (dated 96030)]
26-APR-96 15:32:43
STAGE 1 EXTRACTION AND QA OF METEOROLOGICAL DATA
********************************************************
*** ABNORMAL JOB TERMINATION ***
********************************************************
STATUS REPORT PRIOR TO BEGINNING PROCESSOR RUN
1. REPORT FILE NAMES
ERROR MESSAGES: TEST121.ERR
SUMMARY OF RUN: TEST121.RPT
2. UPPER AIR DATA
SITE ID LATITUDE(DEC.) LONGITUDE(DEC.)
24157 47.63N 117.53W
THE PROCESS(ES) MPRM ANTICIPATES TO PERFORM ARE:
NONE- ERROR(S) ON INPUT IMAGES FOR THIS PATH
EXTRACT INPUT - OPEN: 24157-94.MIX
QA OUTPUT - OPEN: OQAUA.121
THE EXTRACT DATES ARE: STARTING: 31-OCT-94
ENDING: 1-DEC-94
3. NWS SURFACE DATA
THE PROCESS(ES) MPRM ANTICIPATES TO PERFORM ARE:
NONE - NO DATA TO BE PROCESSED ON THIS PATH
4. ON-SITE DATA
THE PROCESS(ES) MPRM ANTICIPATES TO PERFORM ARE:
NONE - NO DATA TO BE PROCESSED ON THIS PATH
**** MPRM MESSAGE SUMMARY TABLE ****
0- 9 10-19 20-29 30-39 40-49 50-59 60-69 70-79 TOTAL
JB
EOOOOOOOOO
U010000001
12 7 0 00 0 0 0 9
2 8 0 00 0 0 010
WARNING MESSAGES ****
0 JB W12 UAEXST: SUMMARY: MISSING/ERRORS IN UA-IQA CARD
*** ERROR MESSAGES ****
--- NONE ---
Figure 6-1 Example report file for extraction and QA of mixing heights
6-5
-------
5 JB 100 DEFINE: BLANK CARD FOUND, SKIP TO NEXT IMAGE
8 JB 100 DEFINE: BLANK CARD FOUND, SKIP TO NEXT IMAGE
13 JB 119 SETUP: FOUND "END OF FILE" ON DEVICE DEVIN 5
0 JB W12 UAEXST: SUMMARY: MISSING/ERRORS IN UA-IQA CARD
0 JB 110 TEST: SUMMARY: NO SF-EXT CARD, NULL EXTRACT
0 JB 111 TEST: SUMMARY: NO SF-IQA CARD, NULL QA
0 JB 112 TEST: SUMMARY: NO SF-OQA CARD, NULL MERGE
0 JB 110 TEST: SUMMARY: NO OS-EXT CARD, NULL EXTRACT
0 JB 111 TEST: SUMMARY: NO OS-IQA CARD, NULL QA
0 JB 112 TEST: SUMMARY: NO OS-OQA CARD, NULL MERGE
Figure 6-2 Example error/message file for extraction and QA of mixing heights.
6-6
-------
SECTION 7
REFERENCES
Appendix W to 40 CFR Part 51
Bowen, B.M.. J.M. Dewart, and A.I. Chen, 1983: Stability Class Determination: a
Comparison for One Site. Proceedings Sixth Sysposium on Turbulence and
Diffusion, Amer. Meteor. Soc., pp. 211-214
Businger, J.A., 1973: Turbulent Transfer in the Atmospheric Surface Layer. Workshop- on
Micrometeorology. D. Haugen, Ed., Amer. Meteor. Soc., 67-100
Catalano. J.A., D.B. Turner, and J.H. Novak, 1987: User's Guide for RAM-Second
Edition. EPA-600/8-87-046, U.S. Environmental Protection Agency. Research
Triangle Park. NC. 200 pp.
Hanna. S.R.. and J.C. Chang. 1991: Modification of the Hybrid Plume Dispersion Model
CHPDM) for Urban Conditions and Its Evaluation Using the Indianapolis Data Set.
Vol. I. User's Guide for HPDM-Urban. Sigma Research Corporation, Concord, MA.
Holtslag, A.A.M.. and A.P. van Ulden, 1983: A Simple Scheme for Daytime Estimates of
the Surface Fluxes from Routine Weather Data. J. Climate Aool. Meteor., 22: 517-
529.
Iqbal. M. 1983: An Introduction to Solar Radiation. Academic Press, New York, NY.
Kasten. F., and G. Czeplak, 1980: Solar and Terrestrial Radiation Dependent on the
Amount and Type of Cloud. Solar Energy. 24: 177-189.
Lumley, J.L.. and H.A. Panofsky, 1964: The Structure of Atmospheric Turbulence.
Intel-science Publ., New York. NY, 239 pp.
Oke, T.R., 1978: Boundary Laver Climates/John Wiley & Sons, New York, NY.
Oke. T.R.. 1982: The Energetic Basis of the Urban Heat Island. Quart. J. Roval Meteor.
Soc.. 108: 1-24.
Paine, R.J., 1987: User's Guide to the CTDM Meteorological Preprocessor (METPROI
Program. EPA-600/8-88-004, Research Triangle Park, NC.
Pasquill. F., 1961: The Estimation of the Dispersion of Windborne Material. Meteor.
^. 90, 33-49.
7-1
-------
Sheih. C.M.. M.L. Wesley, and B.B. Hicks 1979: Estimated Dry Deposition Velocities of
Sulfur Over the Eastern U.S. and Surrounding Regions. Atmos. Environ.. 13: 361-
368.
Stull. R.B., 1988: An Introduction to Boundary Layer Meteorology. Kluwer Academic
Publishers, Dordrecht, The Netherlands. 666 pp.
Turner. D.B.. 1964: A Diffusion Model for an Urban Area. J. Appl. Meteor.. 3:83-91.
U.S. EPA, 1987: On-Site Meteorological Program Guidance for Regulatory Modeling
Applications. EPA-450/4-87-013, U.S. Environmental Protection Agency, Research
Triangle Park, NC, 187 pp.
U.S. EPA. 1993: An Evaluation of a Solar Radiation/Delta-T (SRDT) Method for
Estimating Pasquill-Gifford (P-G) Stability Categories, EPA-454/R-93-055. U.S.
Environmental Protection Agency, Research Triangle Park, NC.
U.S. EPA, 1995: Quality Assurance Handbook for Air Pollution Measuremnet Systems.
Volume IV: Meteorological Measurements, EPA-600/R-94/038d. U.S. Environmental
Protection Agency, Research Triangle Park. NC.
van Ulden. A. P., and A. A. M. Holtslag. 1985: Estimation of Atmospheric Boundary
Layer Parameters for Diffusion Applications. J. Climate Appl. Meteor.. 24: 1196-
1207.
Venkatram. A., 1980: Estimating the Monin-Obukhov Length in the Stable Boundary Layer
for Dispersion Calculations. Bound.-Layer Meteor.. 19: 481-485.
Walcek. C. J.. R. A. Brost. J. S. Chang, and M. L. Wesley, 1986: SO2. Sulfate and HNO3
Deposition Velocities Computed Using Regional Land Use and Meteorological Data.
Atmos. Environ.. 20, 949-964.
7-2
-------
APPENDIX A
SUMMARY OF INPUT KEYWORDS
This appendix provides summary information for the keywords used in the MPRM
processor. The summaries are functionally divided into six areas called pathways. Separate
tables are presented summarizing the keywords applicable to each pathway. The pathways
are identified by two-letter acronyms as follows:
• JB processes that affect or pertain to the entire job (see Table A-l for a summary
of the keywords associated with this pathway)
• UA processes related to NWS upper air data and NCDC mixing height estimates
(see Table A-2 for a summary of the keywords associated with this pathway)
• SF processes related to NWS hourly surface data (see Table A-3 for a summary of
the keywords associated with this pathway)
• OS processes related to site specific (on-site) meteorological data (see Table A-4
for a summary of the keywords associated with this pathway)
• MR processes related to the merging of meteorological data (see Table A-5 for a
summary of the keywords associated with this pathway)
• MP processes related to creating meteorological data files for use in dispersion
modeling (see Table A-6 for a summary of the keywords associated with this
pathway)
There are four processing tasks that might be involved in any given application.
These tasks has been assigned the following two-letter acronyms:
• EX Extraction and storing of data
• QA Quality Assessment
• MR Merge
• MP Process data for use with a specific dispersion model.
The information provided in the columns headed by these two-letter acronyms
indicates whether a given keyword is mandatory (M) or optional (O) for the indicated task.
If a particular keyword is not relevant or not used for a task then the column is blank.
A-l
-------
Appendices A and B are designed to be used together. Appendix A is consulted with
a specific task in mind to determine which keyword is needed to specify the task. Appendix
B is consulted for syntax and the information needed to employ the keyword.
Table A-l
Summary of Keywords Associated with the JB Pathway
1 JB keywords
I FIN
I
; ERR
STA
EX
M
M
0
QA
M
H
o
MR
H
H
0
HP
H
, M,
0
Description and usage
Signals the completion of input data
for this pathway.
Defines disk file name for processor
;* geheralecJ warning and error messages.
Defines the beginning of input data
OUT
RUN
END
0 I
0
for pathway.
Defines disk file name for the general
report.
If present, processing STOPS following
completion of processing input images.
Useful for checking input images.
Alternate method for signaling the end
of theinput data. Default is
'encountering an End-bf-File (EOF) in
"reaSfhg the input data.
A-2
-------
Table A-2
Summary of Keywords Associated with the UA Pathway
UA keywords
FIN
STA
LOC
i
IQA
OQA
EXT
IN1
'
IN2
.
' TOP
'
OFF
\
i
j CHK
i
AUD
TRA
EX
M
0
M
M
M
Defines disk file name for storage of
QA processed data and input data for
MERGE.
Defines EXTRACT start and stop dates.
Defines tape name, format, and
characteristics for upper air data.
Defines tape name and characteristics, [
' or disk file name and format for ,
.morning and afternoon mixing height
'data.
' ' ' ' • • " '-••.'-'•
Upper air data for altitudes above
ground greater than UATOP are ignored.
: Default value of UATOP is 5000 m.
Turns off automatic data modifications
i during EXTRACT of upper air soundings.
By default adjustments are made to.
correct suspect temperatures, redefine
directions associated with calm winds, !
.delete '(when possible) data given for
mandatory pressure levels, fill in
missing' dew-point temperatures, and ;
adjust heights to AGL.
Redefines QA range checks and missing
value flag for a variable.
Adds variable to general AUDIT report.
Default variables are UAM1 and UAM2,
morning and evening mixing heights.
Turns on trace for missing data during.
QA processing.
CM) One or both of IN-1 and IN2 must be present, if EXT is present.
A-3
-------
Table A-3
Summary of Keywords Associated with the SF Pathway
_^^^^^^^^__
" SF keywords
FIN
STA
IOC
;
1CA
OCA
EXT
1H2
INS
CHK
AUO
1
j
!
i
i
• TRA
EX
H
0
H
H
H
M
0
OA
H
0
H
M
H
0
0
0
MR
H
0
M
H
HP
Description and usage
Signals the completion of keyword input for this pathway.
Defines the beginning of keyword input for this pathway.
Defines station ID, station longitude and latitude,
and number of hours to convert times in the data to 1ST.
Defines disk file name for storage of extracted data and
input data for QA processing.
Defines disk file name for storage of QA processed data and
input data for MERGE.
Defines EXTRACT start and stop dates.
Defines tape name and characteristics, or
disk file name and format of hourly weather observation data.
Defines the filename and format of the precipitation data file.
Redefines QA range checks and missing value flag for a variable.
Adds variable to general AUDIT report.
Default variables are:
SLVP Station pressure (adjusted to sea level)
PRES Station pressure (unadjusted)
CLHT Ceiling height
TSKC Total and Opaque sky cover
HZVS Horizontal visibility
THPD Dry-bulb temperature
WD16 Wind direction
WIND Wind speed.
Turns on trace for missing data during QA processing.
A-4
-------
Table A-4
Summary of Keywords Associated with the OS Pathway
OS keywords |
FIN
STA
LOC
IQA
OQA
EXT
MAP
FMT
AVG
i DT1
DT2
DT3
EX
M
. 0
M
M
0
M
M
0
0
0
0
QA
M
0
M
M
M
M
M
0
0
0
0
MR
M
0
M
M
...
M
M
MP
Description and usage
Signals the completion of input data
for this pathway.
Defines the beginning of input data
for pathway.
Defines site ID, site longitude
and "latitude, and number of hours to
convert times given in data to 1ST.
Defines disk file name for storage of
input data for QA processing. May
have more than one observation
per hour.
Defines disk file name for storage of
QA processed data and input data for
MERGE. Always hourly averages. j
, Defines EXTRACT start and stop dates."
Defines order of OS input variables as
they appear within IQA 'file.
Defines FORTRAN format statements for
'. reading IQA f i le.
Defines maximum number of observations
to be expected per hour for input data
provided within IQA file.
Defines lower and upper measurement
heights associated with first
temperature difference.
Defines lower and upper measurement
heights associated with second
temperature difference.
Defines lower and upper measurement
heights associated with third
temperature difference.
A-5
-------
Table A-4 (continued)
Summary of Keywords Associated with the OS Pathway
HOT
CLH
CHK
. AUD
TRA
SFC
I
0
0
Defines meteorological mast
configuration, number of levels, and
height associated with each.
Redefines valid minimum wind speed
for use in definition of a calm;
default = 1 ms"1 I
Redefines QA range checks and missing
value flag for a variable.
Adds variable to general AUDIT report.
Default variables are:
HHcf' "Mixing height
SA SD of horizontal wind direction
SE SD of vertical wind direction
TT Dry-bulb temperature
WD Horizontal mean wind direction
WS Horizontal mean wind speed.
Turns on trace for missing data during
QA processing.
Defines surface characteristics.
Default values are albedo, 0.25; Bowen
ratio, 0.75; and surface roughness
length, 0.15 m.
Table A-5
Summary of Keywords Associated with the MR Pathway
MR keywords
i
1 OUT
i
FIN
EXT
STA
EX
QA
MR
M
H
0
0
HP
Description and usage j
Defines disk file name for storage
of combined (merged) data.
Signals the completion of input data
for this pathway.
Defines start and stop dates for
MERGED data.
Defines the beginning of input data
for pathway.
A-6
-------
Table A-6
Summary of Keywords Associated with the MP Pathway
MP keywords
FIN
STA
MET
EX
MMP
.
QA
j
| '
I
j EXT . !
!
i
VBL 1
MR
MP
M
0
M
" M
0""
0
Description and usage
Signals the completion of input data I
for this pathway.'
Defines the beginning of input data |
for pathway.
Defines disK file name associated with
combined (merged) meteorological data
.file.
- ? , , ''i ".
Defines disk file name associated with
output meteorological file created by 1
this run. Included as an option is ',
the ability to define the dispersion 1
model that will be accessing this
file. ' '" " '
Defines start and stop dates for
meteorological data file to be
^created by this run.
Redefines (override default)
nrni-pssina methodoloav to be employed
TRA
1ST
in generating output meteorological
data file. Currently there are
selection options available for
processing wind, temperature,
stability category, and mixing
"height, choice is largely whether to
.use NWS or on-site meteorological
data.
Turns on more detailed trace of errors .
"encountered during processing. !
Default is to provide daily summaries.
Turns on listing of generated
meteorology to general report file.
A-7
-------
-------
APPENDIX B
SUMMARY OF INPUT SYNTAX
Appendices A and B are designed to be used together. Appendix A is consulted with
a specific task in mind to determine which keyword is needed to specify the task. Appendix
B is consulted for syntax and the information needed to employ the keyword.
In the following tables, the keywords used in the input to the MPRM processor are
presented in more detail. Table B-l provides information on keywords which are used in
specifying files associated with Stage 1 processing. Table B-2 provides information and
syntax for the keywords which are used in defining these files (the INI, IN2, and INS
keywords). These keywords are presented first, as they are likely to be consulted most
often. Table B-3 provides the syntax for the remaining keywords, arranged in alphabetical
order by keyword.
Table B-l
Keywords and files associated with Stage 1
JB
UA, SF
& OS
UA
UA
ERR
OUT
IQA
OQA
INI
IN2
Text
Text
Pathway Keyword Device Form or Format Description
Error/message file
General report file
Unprocessed data before QA
Unprocessed data after QA
Unprocessed upper air data
Unprocessed upper air data
NCDC estimated mixing heights
NCDC estimated mixing heights
NCDC estimated mixing heights
DISK
DISK
DISK
DISK
TAPE
TAPE
DISK
USER
TD5600FB
TD5600VB
TD9689FB
TD9689FB
User Specified
SF
SF
IN2 TAPE CD144FB
IN2 DISK CD144FB
SCRAMFB
SAMSON
NWS surface data
NWS surface data
NWS surface data
NWS surface data
SF
INS DISK TD3240FB
TD3240VB
NWS hourly precipitation
NWS hourly precipitation
B-l
-------
Table B-2
Syntax for Keywords Used in Defining Files for Stage 1
Keyword:
Purpose:
Syntax:
Parml:
Pann2:
Parm3:
Pann4:
PannS:
Example:
INI used on pathway UA
Define input tape file for upper air data
Pathway INI Pannl Parm2
Parml is always TAPE
Parm2 is the name of the tape
Pann3 is the tape file format:
Pann4 is the character set:
PannS Pann4 PannS
file
5600FB for fixed block or
5600VB for variable block
ASCII or
EBCDIC
Parm5 is the WBAN number of the observation station
UA INI TAPE filename 5600FB ASCII 13840
Keyword:
Purpose:
Syntax:
Pann 1 :
Pann2:
PannS:
Pan«4:
PannS:
Example:
IN2 used on pathway UA
Define input tape file for mixing height data
Pathway IN2 Pannl Parm2
Pannl is always TAPE
Pann2 is the name of the tape
PannS is the tape file format:
Parm4 is the character set:
PannS Parm4 PannS
file
9689FB
ASCH or
EBCDIC
PannS is the WBAN number of the observation station
UA IN2 TAPE filename 9689FB ASCH 13840
B-2
-------
Table B-2 (continued)
Syntax for Keywords Used in Defining Files for Stage 1
Keyword:
Purpose:
IN2 used on pathway UA
Define input disk file for mixing height data
Syntax:
Parml:
Parm2:
ParmS:
Parm4:
Example:
Pathway IN2 Parml Parm2 ParmS Parm4
Parml is always DISK
Parm2 is the name of the tape file
ParmS is the disk file format: 9689FB
Parm4 is the WBAN number of the observation station
UA IN2 DISK filename 5600FB 13840
Keyword:
Purpose:
IN2 used on pathway UA
Define input user disk file for mixing height data
Syntax:
Parml:
Parm2:
ParaiS:
Parm4:
Example:
Pathway IN2 Parml Parm2 ParmS Parm4
Parml is always USER
Parm2 is the name of the disk file
ParmS is a user specified format for the mixing height data. Must be
a valid Fortran format. The input list is of the form:
AAAAA, YEAR, MONTH, DAY, UAM1, UAM2. Where
AAAAA is a 5-character station ID. YEAR, MONTH, and
DAY are 2-digit integer variables . UAM1 and UAM2 are
morning and afternoon mixing heights (read as 4-digit integer
variables).
Parm4 is the WBAN number of the observation station
UA IN2 USER filename (A5, 312, 2X, 14, 14X, 14) 24157
B-3
-------
Table B-2 (continued)
Syntax for Keywords Used in Defining Files for Stage 1
Keyword:
Purpose:
Syntax:
Parml:
Parm2:
ParmS:
Parm4:
ParmS:
Example:
IN2 used on pathway SF
Define input tape file for NWS surface data
Pathway IN2 Parml Parm2 ParmS Parm4 ParmS
Parml is always TAPE
Parm2 is the name of the tape file
ParmS is the tape file format: CD144FB
Parm4 is the character set: ASCII or
EBCDID
ParmS is the WBAN number of the observation station
SF IN2 TAPE filename CD144FB ASCH 13840
Keyword:
Purpose:
Syntax:
Parml:
Parm2:
ParmS:
Parm4:
Example:
IN2 used on pathway SF
Define input disk file for NWS surface data
Pathway IN2 Parml Parm2 ParmS Parm4
Parml is always DISK
Parm2 is the name of the disk file
ParmS is the disk file format: CD144FB
SCRAMFB
SAMSON
Parm4 is the WBAN number of the observation station
SF IN2 DISK filename SCRAMFB 13840
B-4
-------
Table B-2 (continued)
Syntax for Keywords Used in Defining Files for Stage 1
Keyword:
Purpose:
INS used on pathway SF
Define input disk file for NWS hourly precipitation data
Syntax:
Parml:
Parm2:
ParmS:
Parm4:
Example:
Pathway INS Parml Parm2 ParmS Parm4
Parml is always DISK
Parm2 is the name of the disk file
ParmS is the disk file format:
TD3240FB
TD3240VB
Parm4 is the six-digit station identifier recorded in columns 4-9 in each
TD-3240 record. The station identifier includes a two-digit state code and a
four-digit number assigned by NCDC.
SF INS DISK filename TD3240FB 992415
B-5
-------
Table B-3
Syntax for Keywords: AUD - VBL
Keyword:
Purpose:
Syntax:
Parml:
Examples:
AUD used on pathway UA, SF, and OS
Add variables to the audit summary report
Pathway AUD Parml, Parm2, ...
Parml, Parm2, ... are the 4-character variable names listed in Appendix C.
The AUD input can be repeated as often as needed in order to list all the
variables to be added to the audit summary.
The default list of audit variables on the UA-pathway are the twice-daily
mixing height values.
The default list of audit variables on the SF-pathway are: wind direction,
wind speed, ceiling height, sky cover, temperature, sea-level pressure, station
pressure, and visibility.
The default list of audit variables on the OS-pathway are: mixing height,
wind direction, wind speed, ceiling height, sky cover, temperature, sea-level
pressure, station pressure,
-------
Keyword:
Purpose:
HK used on pathway UA; SF, and OS
Redefine quality assessment range check parameters
Syntax:
Parml
Parm2
PamiS
Pami4
Parm5
Examples
Pathway CHK Pannl Parm2 Pann3 Pann4 PannS
Pannl is the 4-character variable name (2-character for multi-level on-site
variables) given in Appendix C.
Parm2 is the range check switch (integer 1 or 2).
1 = exclude upper and lower bounds
2 = include upper and lower bounds
Parm3 is the missing value indicator (flag), an integer variable.
Parm4 is the lower bound for the range check (an integer).
Parm5 is the upper bound for the range check (an integer).
OS CHK INSO 2 9999 0 700
OS CHK DT01 1 -999 -10 5
OS CHK SA 1 99 0 50
Keyword:
Purpose:
Syntax:
Farm 1 :
Example:
CLM used only on pathway OS
Define threshold for wind speed and wind direction
Pathway CLM Parml
Pannl is the threshold wind speed (ms"1) for valid wind
(default = 1 ms"1. The threshold wind speed is used in
OS CLM 0.5
measurements
defining calms
Keyword:
Purpose:
Syntax:
Parm 1 :
Parm2
Example:
DTI, DT2. and DT3 used only on pathway OS
Define heights for vertical temperature difference measurements.
Pathway DTn Parml Parm2
Pannl is the height (m) of the lower temperature measurement.
Pann2 is the height (m) of the upper temperature measurement.
OS DTI 2 20
B-7
-------
Keyword:
Purpose:
Syntax:
Pannl:
Example:
END used only on
Signals end of input
Pathway END
pathway JB
run stream for
entire job
This keyword has no parameters
JB END
Keyword:
Purpose:
Syntax:
Parm 1 :
Example:
EXT used on pathway UA, SF, OS, MR, and MP
Define start and stop dates for processing
Pathway EXT Pannl Parm2 Parm3 Parm4 Parm5 Parm6
Pannl. Parm2, and Parm3 define the starting year, month, and day of the
data to be processed. Parm4. PannS, and Pann6 define the ending year.
month, and day of the data to be processed. The dates are inclusive (I.e.,
data for day "ParmS" will be included. All values must be entered as
integers. Pannl and Parm4 may be expressed fully (e.g., 1987) or
abbreviated by the last two digits (e.g., 87).
UA EXT 94 10 31 94 12 01
Keyword:
Purpose:
Syntax:
Pannl:
Example:
FIN used on all pathways
Signifies end of input run stream
Pathway KEY
This keyword has no parameters
SF FIN
for pathway
B-8
-------
keyword:
Purpose:
FMT used only on Pathway OS
Define FORTRAN formats for reading input data
Syntax:
Parrnl:
Parm2
Examples:
Pathway FMT Parml Pann2
Parml is always DATxx where xx is an integer (i.e., 01, 02, etc.).
DATxx - the xx refers to sequence number. For instance, if there are
three READs (in the FORTRAN sense) needed for reading the data,
then there would be DAT01, DAT02 and DAT03 definitions within
the OS MAP input and there would likewise be DAT01, DAT02 and
DAT03 definitions within the OS FMT input.
Parm2 must be a valid Fortran format statement, the format must include
the right and left parentheses.
OS MAP DAT02 INSO TSKC CLHT
OS FMT DAT02 (5X,F4.2,2X,2F5.2)
Note the specification of the number of decimal places. This is not
necessary for proper input of the value, but since we use this format
in writing to the OQA-file, we NEED the decimal specification.
Keyword:
Purpose:
HGT used only on Pathway OS
Define heights associated with multilevel input data.
Syntax:
Farm 1:
Parm2
Example:
Pathway HGT Parml Parm2 Parm3 ... ParmN
Parml is the number of heights to be read in as input (Maximum: 10).
Parm2 ... ParmN are heights of multilevel variables in meters. This image
can not be repeated, so all values must be listed.
OS HGT 5 2.0 4.0 10 30.0 50
B-9
-------
Keyword:
Purpose:
Syntax:
Parnil:
Parni2. 3
Pann4
Example:
LOG used on Pathways UA, SF and OS
Define location parameters for site.
Pathway LOG Parml Parm2 ParmS Pann4
Parml is the site identification number. Typically, this is a 5-digit number.
To avoid conflicts with current dispersion models expecting RAMMET type
meteorological input, we suggest the OS pathway SitelD contain only
numbers, no letters. Note, SitelD must agree with that given in the input
data.
Pann2 and ParmS are the longitude and latitude in decimal degrees.
Longitude and latitude can appear in either position Parm2 or ParmS. The
important point is to define both. North and south latitude are entered as
30.00N and 30.00S. Likewise, the longitude is entered as 170. 13E. Note
entering a latitude north of the Arctic (63.5 degrees N) where the sun does
not rise during all or part of the winter will cause a run-time error in Stage 3
processing.
Pann4 is the number of hours to be subtracted to convert times given on this
pathway to Local Standard Time (LST). NWS upper air data are normally
reported in Greenwich Mean Time. One should enter a value of 5 for Pann4
when processing such data for an East Coast location. Note, if times are
given in LST, a zero must still be entered for Pann4.
UA LOG 03820 34.37N 81.97E 5
Keyword:
Purpose:
Syntax:
Pannl:
Example:
LST used only on Pathway JB
Tuni on printed listing of generated meteorological data.
Pathway LST
This Keyword has no parameters.
MP LST
B-10
-------
Keyword:
Purpose:
MAP used only on Pathway OS
Identify and define the order of variables in data records
Syntax:
Parml:
Parm2 ...
Example:
Pathway MAP Parml Parm2 ParmS
Parml is of the form DATxx and defines the sequence for the input. The xx
indicates the record number.
The first record, DAT01, must begin with a date (year, month, and
day) and time. The time must indicate the hour of day, minutes is
optional. The order of the date and time variables is not important.
Parm2, Parm3, etc. are 4-character variable names for the OS variables to be
processed. Variable names are given in Appendix C. The following
restrictions apply:
• Each observation must be completely labeled with a date and tune,
which at least defines the year, month, day and hour of the
observation.
• The date and time data must be entered as integers and must precede
the data for all other variables. Note, the order of the date is not
important; year, month and day is just as acceptable as day, month
and year.
• The following limitations apply: Observations are limited to 20
records per observations. Records are limited to 40 variables per
record. Multi-level variables are limited to 10 levels.
The following input images describe a data set having three records per
observation. The date and time of the observation are stored in the first
record. Temperature, wind direction, and wind speed from two levels on a
meteorological tower are stored in the second (tower level 01) and third
records (tower level 02). There is no relationship assumed between the
sequence number, xx, given in DATxx with the measurement level given in
the multi-level variable name.
OS MAP DAT01 OSYR OSMO OSDY OSHR
OS MAP DAT02 TT01 WD01 WS01
OS MAP DAT03 TT02 WD02 WS02
B-ll
-------
Keyword:
Purpose:
MET used only on Pathway MP
Define diskfile of merged data.
Syntax:
Parml:
Parm2
Parm3
Examples:
Pathway MET Parml Parm2 ParmS
Parml is always DISK
Parm2 is the filename.
Parm3 is the integer number of hours needed to be subtracted from
Greenwich Mean Time to convert to Local Standard Time.
MP MET DISK [JSLMPRM.DAT1RAMSTL.DAT 5
MP MET DISK RAMSTL.DAT 5
Keyword:
Purpose:
MMP used only on Pathway MP
Define dispersion model and diskfile name for output.
Syntax:
Parml:
Parm2
ParmS
Examples:
Pathway MMP Parml Parm2 Parm3
Parml is always DISK
Parm2 is the filename
ParmS (optional) identifies the dispersion model. The default, if no model is
specified, is ISCST. Valid selections are as follows: ISCST, ISCSTDRY,
ISCSTWET, BLP, COMPLEX1, RAM, CALINE-3, RTDM, VALLEY,
ISCLT, CDM16, and CDM36.
MP MMP DISK [JSLMPRM.DATJRAMMET.DAT
MP MMP DISK RAMMET.DAT CDM36
B-12
-------
Keyword:
Purpose:
Syntax:
Parml:
Example:
OFF used only on Pathway UA
Turn off automatic modification checks
Pathway OFF
This keyword has no parameters.
UAOFF
to upper air data
Keyword:
Purpose:
Syntax:
Parml:
Example:
RUN used only on Pathway JB
Inhibit data processing; check run stream
Pathway RUN
This keyword has no parameters
JBRUN
syntax and stop
Keyword:
Purpose:
Syntax:
Parml:
Parm2
SFC on Pathway OS
Define surface characteristics of measurement site
OS SFC Parml Parm2 Parm3 ...
Parml is one of the following: SETUP SECTORS
see the following
VALUES
B-13
-------
Keyword:
Purpose:
SFC SETUP on Pathway OS
Define frequency and number of direction sectors for surface characteristics
Syntax:
Parm2:
ParmS:
Example:
SFC SETUP Parm2 Parm3
Parm2 specifies the frequency for the surface characteristics and must be one
of the following:
ANNUAL characteristics are constant for entire year
SEASON characteristics change as a function of season: Winter
(December - February); Spring (March - May);
Summer (June - August); Autumn (September -
November
MONTHLY ^characteristics change every calendar month
ParmS is the number of non-overlapping wind direction sectors over which
the surface characteristics vary; maximum of 12.
OS SFC SETUP SEASON 2
Keyword:
Purpose:
SFC SECTORS on Pathway OS
Define direction sectors for surface characteristics
Syntax:
Parm2:
ParmS:
Parm4:
Example:
OS SFC SECTORS Parm2 Parm3 Parm4
Parm2 is the sector index
ParmS defines the beginning wind direction for the sector
Parm4 defines the ending wind direction for the sector
OS SFC SECTORS 1 0 180
B-14
-------
Keyword:
Purpose:
Syntax:
Parml:
Parm2:
ParmS:
Parm4:
ParmS:
Parm6:
ParmT:
ParmS
Parm9
Example:
SFC VALUES on Pathway OS
Specify values for surface characteristic
OS SFC VALUES Parml Parm2 ... Parm9
Parml is the frequency index (1 for annual, 1-4 for season, or 1-12 for
monthly). Seasons are defined in MPRM as follows: Winter = December,
January and February (parml = 1); Spring = March, April, and May
(parml = 2); Summer = June, July, and August (parml = 3); Fall =
September, October, and November (parml = 4).
Parm2 is the sector index (maximum value 12)
ParmS is Noon-time albedo (default = .25)
Parm4 is Bowen ratio, (default = 0.70)
ParmS is surface roughness length (meters) at the site where meteorological
data are collected (default = 0.15 m)
Parm6 is surface roughness length (meters) at the site where the output from
Stage 3 are to be applied (default = 0.15 m)
Parrn? is minimum Monin-Obukhov length (meters) for stable conditions
(default = 2.0 m)
ParmS is fraction of net radiation absorbed by the ground (default = 0. 15)
Parm9 is anthropogenic heat flux (default = 0.0 Wm"2)
OS SFC VALUES 1 1 0.25 0.70 0.15 0.15 2.00 0.15 0.00
Keyword:
Purpose:
Syntax:
Parml:
Example:
STA used on Pathways JB, MP, UA, SF, OS AND MR
Signals beginning of input run stream data for pathway
Pathway STA
This keyword has no parameters
JBSTA
B-15
-------
Keyword:
Purpose:
TOP used only on Pathway UA
Purpose: Define 'clipping height' for upper air data
Syntax:
Parml:
Example:
Pathway TOP Parml
Parml is height in meters. Upper air data given for heights above ground
greater than Parml are ignored. Note, value must be entered as an integer
UATOP 7500
Keyword:
Purpose:
Syntax:
Parml:
Example:
TRA as used on Pathway MP
Purpose: Turn on trace notes to provide details of processing.
Pathway TRA
This Keyword has no parameters
MPTRA
Keyword:
Purpose:
Syntax:
Parml:
Example:
TRA as used on Pathways UA, SF and OS
Purpose: Turn on trace for missing data during QA processing.
Pathway TRA Parml, Parm2, ...
Parml, Parm2, ...are 4-character variable names as listed in Appendix C.
SF TRA PWTH PRES CLHT TSKC WD16 WIND
B-16
-------
keyword:
Purpose:
Syntax:
Parml:
Parm2
Farm 3
Examples:
VBL used only on Pathway MP
Purpose: Define methodology for processing meteorological variables
Pathway VBL Parml Parm2 Parm3 Parm4
Parml is a 4-character string identifying the meteorological variable. Valid
strings are: WIND, TEMP, MHGT, and STAB.
Parm2 is a 6-character string specifying the processing methodology. See
Table 3-3.
Parm3 is the height (m) associated with the variable (normally the
measurement height).
MP VBL WIND ONSITE 35.0
MP VBL STAB SASITE 10.0 _^
B-17
-------
-------
APPENDIX C
VARIABLE NAMES AND DEFAULT RANGE CHECKS
MPRM gives the user the ability to override the internal definitions for upper and
lower bounds, missing value indicator, and treatment of endpoints during quality assessment
checks during Stage 1 processing. This appendix presents the following:
• Variable names used to override the parameters
• A description of each variable and the units used
• Quality assessment default parameters for each variable
• Variables automatically audited during quality assessment.
There are seven fields in each table: variable name, description, units, range check
switch, missing flag, lower bound, and upper bound. Each of these fields is described
below. . .
Variable name
This is the four-character variable name used in the input images for redefining
quality assessment parameters (the CHK image on each pathway), activating auditing
of variables not automatically audited (the AUD image on each pathway) and defining
the on-site data map (the DAT and LVL images only on the OS-pathway).
If an asterisk (*) appears before the variable name, then the variable is automatically
audited during quality assessment. These variables are always audited on the upper
air and surface pathways. However, for the on-site pathway if the variable is not in
the data map. then the variable is omitted from the audit. If a person wants to audit
additional variables on any pathway, the AUD input image is used.
Description and units
A brief description and the units of each variable follows the name. For several
variables, a multiplier also appears in the units field. This can be identified by the
*10. *100, or *1000 following the units. Because the upper air and surface
observations are treated as integers within MPRM, multipliers are used to retain
significant digits prior to rounding the value to the nearest integer.
Range Check Switch
The Range Check Switch field indicates whether to exclude the lower and upper
bound ( = 1) or include the bounds •( = 2) in determining if the variable violates the
prescribed limits. This value can be changed by using the CHK input image.
Missing Value Indicator
The missing value indicator is the value used in the processor to represent missing
data for the variable. This value can be changed by the user on the CHK input
C-l
-------
image. This option is particularly useful if data are already extracted and a different
missing value flag was used.
Bounds
The last two fields, the Lower and Upper bounds, are the limits against which the
value of a variable is checked. If the value lies outside this interval, the endpoints
either included or excluded according to the Range Check Switch, then a quality
assessment violation is recorded. As in the Range Check Switch and Missing Flag.
these values can be modified using the CHK card.
If upper air soundings are to be extracted, an upper height limit is used above which
no data are extracted. The default height limit is 5000 meters. The value of the height limit
is stored in a variable named UATOP. The user can override this value by specifying a new
height on the UA TOP input image for the upper air pathway. A description of this image
and its syntax can be found in Appendix B.
Note: Tlie maximum number of levels that can be extracted is set in the processor
to 20. If 20 levels of data are extracted and UATOP has not been reached, no
additional data are extracted.
On the OS-pathway there are several variables with default values that can be
redefined using an input run-stream image. These include the number of observations per
hour (default value 1) and threshold wind speed (default value 1.0 m/s). The number of
observations per hour can be redefined using the OS AVG input image. The threshold wind
speed can be redefined using the OS CLM input image. In addition, the various parameters
defining surface characteristics are also given default values; these can be redefined using
the OS SFC VALUES input image (see Section 4.2.5).
C-2
-------
Table C-l
Variable Names, Units, and QA Default Settings for the UA Pathway
name
UAPR
UAHT
UATT
UATD
UAWD
UAWS
UASS
UADS
UALR
UADD
UAM1*
UAM2*'
Description
Atmospheric pressure
Height above ground level
Dry bulb temperature
Dew-point temperature
Wind direction
Wind speed
Wind speed shear
Wind direction shear
Temperature lapse rate
Dew pcint deviation
A.M. Mixing height
P.M. Mixing height
Units
millibars *10
meters
°C *10
= C *10
degrees from north
meters/second *10
(m/s)/(100 meters)
degrees/(100 meters)
=C/(100 meters)
CC/(100 meters)
meters
meters
Range
check
switch
1
2
1
1
2
2
2
2
2
2
2
2
Missing.
value
indicator
-9999
-9999
-9999
-9999
-9999 '
-9999
-9999
-9999
-9999
-9999
-9999
-9999
Bounds
Lower
5000
0
-350
-350
0
0
0
0
-2
0
50
50
Upper
10999
5000
+350
+350
360
500
5
90
5
2
2500
4500
*Automatically included in audit report.
C-3
-------
Table C-2
Variable Names, Units, and QA Default Settings for the SF Pathway
Vdriable
name
ALTP
SLVP*
PRES*
CLHT*
TSKC*
C2C3
CLC1
CLCZ
r*t r^t
CLCj
Ml (*f
CLCfa
ft f \
CLT 1
CLT2
f,, YT
CLTi
ft T I
CLT
XXCKffl IU;
xx
kilometers *10
°C *10
CC *10
°C *10
whole percent
tens of degrees
metersXsecond *10
millimeters * 1000
Range
switch
2
1
1
2
2
2
2
2
1
1
1
2
2
2
2
1
1
1
Missing
V3 I US
indicator
-9999
-9999
-9999
-9999
9999
9999
OOOO
7777
OOOO
7777
OOOO
7777
OOOO
7777
OOOOO
77777
OOOOO
77777
OOOOO
77777
OOOOO
77777
9999
-9999
-9999
-9999
-9999
-9999
-9999
-9999
-9
999
999
999
B
Lower
2700
9000
9000
0
0
0
_
n
u
n
u
n
u
n
u
n
u
n
u
0
0
-300
-650
-650
0
0
0
0
0
0
0
iounds
Upper
3200
10999
10999
300
1010
1010
910
91 0
910
om
7 1 U
7Q3\JU
98300
98300
98300
9292
1640
350
350
350
100
36
500
25400
100
100
100
NOTES: The three pressure variables (ALTP, SLVP, and PRES), the ceiling height (CLHT) and the sky
cover (TSKC) are also available on the OS-pathway.
Surface data reported by the NWS are archived as reported, in English units - MPRM converts
the surface data to ntks units prior to QA. Thus, with the exception of the altimeter
setting, all range check bounds are given in mks units.
SF01, SF02 and SF03 were added to allow for future enhancements to MPRM on the SF pathway.
* Automatically included in audit report.
X/ The two variables described have been combined to form one variable.
C-4
-------
Table C-3
Variable Names, Units, and QA Default Settings for the OS Pathway
Variable
name
HFLX
USTR
MHGT*
ZOHT
SAMT
PAMT
INSO
MR AD
DT01
DT02
DT03
US01
US02
US03
HTnn
SAnn*
SEnn*
SVnn
SWnn
SUnn
TTnn*
WDnr.*
WSnn*
VVnn
DPnn
RHnn
Vlnn
V2nn
V3nn
ALTP
SLVP*
PRES*
CLHT*
TSKC*
OSDY
OSMO
OSYR
OSHR
OSMN
Description
Surface heat flux
Surface friction velocity
Mixing height
Surface roughness length
Snow amount
Precipitation amount
Insolation
Net radiation
Temperature diff.(L) - L)
Temperature diff.(U - L)
Temperature diff.(U.- L)
User's scalar #1
User's scalar #2
User's scalar #3
Height
Std. dev. horizontal wind
Std. dev. vertical wind
Std. dev. v-comp. of wind
Std. dev. w-comp. of wind
Std. dev. u-comp. of wind
Temperature
Wind di rection
Wind speed
Vertical component of wind
Dew-point temperature
Relative humidity
User's vector #1
User's vector #2
User's vector #3
Altimeter pressure
Sea level pressure
Station pressure
Cei I ing height
Sky cover < total or opaque)
Day
Month
Year
Hour
Minute
Units
watts/square meter
meters/second
meters
meters
centimeters
centimeters
watts/square meter
watts/square meter
°C
°c
°c
user's units
user's units .
user's units
meters
degrees
degrees
meters/second
meters/second
meters/second
°C
degrees from north
meters/second
meters/second
°C
whole percent
user's units
user's units
user's units
inches of mercury
millibars *10
mi llibars *10
kilometers *10
tenths
Range
check
switch
1
1
1
1
2
. 2
1
1
1
i
1
1
1
1
1
1
1
1
1
1
1
2
2
1
1
2
1
1
1
*100 2
1
1
2
2
2
2
2
2
2
Missing
value
indicator
999
999
9999
999
999
999
9999
999
-999
-999
-999
999
999
999
9999
99
99
99
99
99
99
999
999
999
99
999
999
999
999
-9999
-9999
-9999
-9999
99
; -9
-9
-9
-9
-9
Bounds
Lower
-50
0
0
0
0
0
0
-50
-200
-200
-200
0
0
0
0
0
0
0
0
0
-30
0
0
0
•65
0
0
0
0
2700
9000
9000
0
0
1
1
0
0
0
Upper
800
2
4000
2
250
100
1250
800
500
500
500
100
100
100
4000
35
25
3
3
3
35
360
50
5
35
100
100
100
100
3200
10999
10999
300
10
31
12
99
24
60
1(U - L) indicates (upper level) - (lower level).
*Automatically included in audit report.
Note that the units for temperature difference are*°C. However, the range check for
temperature differences is based on the temperature gradient in °C/(100 meters).
Notes: The nn in variables HT to V3 refers to the level at which the observation was
taken; e.g., TT01 is temperature at the first level, WS02 is wind speed at the
second level.
The three pressure variables (ALTP, SLVP, and PRES), the ceiling height (CLHT),
and the sky cover (TSKC) are also available on the surface pathway.
C-5
-------
-------
APPENDIX D
EXAMPLE TEST CASES
The example test cases described in this appendix document testing conducted in
January 1996 using MPRM (dated 96030). The test case files along with the executables for
MPRM are available for downloading from the SCRAM Bulletin Board. Although not
exhaustive, the test cases exercise many of features and options encountered in a typical
analysis.
File Management
Keeping track of all the files involved in processing data through MPRM can be
somewhat troublesome without good file management and simple file naming conventions.
The following conventions were used to keep track of the example test case files: 1) files
associated with Stage 1 processing have a three digit identifier beginning with the numeral
'!' (e.g., TESTlxx.* or *.lxx); 2) files associated with Stage 2 processing have a three
digit identifier beginning with the numeral '2' (e.g., TEST2xx.* or *.2xx); 3) files
associated with Stage 3 processing have a three digit identifier beginning with the numeral
'3' (e.g., TEST3xx.* or *.3xx). In addition the following file extensions are used:
*.RPT General report files
*.ERR Error report files
*.INP Command input files
*.OUT Model output files
D-l
-------
File Maae
STAGE1N2 EXE
STAGES EXE
24157-94 MIX
24155-94 DAT
LAF-OS MET
24155-94 PPP
24155-94 001
24155-94 SAV
TEST121 INP
TEST121 ERR
TEST121 RPT
OQAUA 121
TEST122 INP
TEST122 ERR
TEST122 RPT
OQASF 122
TEST123 INP
TEST123 ERR
TEST123 RPT
OQAOS 123
TEST222 INP
TEST222 ERR
TEST222 RPT
MERGE 222
TEST223 INP
TEST223 ERR
TEST223 RPT
HERGE 223
TEST322 INP
TEST322 ERR
TEST322 RPT
TEST322 OUT
TEST323 INP
TEST323 ERR
TEST323 RPT
TEST323 OUT
TEST324 INP
TEST324 ERR
1EST324 RPT
TEST324 OUT
Size
705993
649730
2835
120048
112728
5172
3454
2143
276
737
3441
1541
361
4891
5058
116098
485
6499
4023
56601
242
804
4018
87316
288
1005
4755
121021
218
13021
20331
63410
424
16170
24429
55490
926
16103
25273
63410
Date
01-30-96
01-30-96
10-23-95
01-30-96
12-05-95
01-11-96
01-30-96
01-30-96
12-05-95
01-30-96
01-30-96
01-30-96
01-11-96
01-30-96
01-30-96
01-30-96
12-05-95
01-30-96
01-30-96
01-30-96
01-29-96
01-30-96
01-30-96
01-30-96
01-29-96
01-30-96
01-30-96
01-30-96
01-29-96
01-30-96
01-30-96
01-30-96
01-30-96
01-30-96
01-30-96
01-30-96
01-29-96
01-30-96
01-30-96
01-30-96
File Contents
Stage 1 and 2 Executable
Stage 3 Executable
Mixing Heights
Surface Data (CD-144 format)
On-site Data
Precipitation Data (TD-3240FB)
Altered Surface Data
Un- altered Surface Data
Command file for QA of mixing heights
Error file from QA of mixing heights
Report file from QA of mixing heights
Output from QA of mixing heights
Command file for QA of NWS data
Error file from QA of NUS data
Report file from QA of NUS data
Output from QA of NUS data
Command file for QA of on-site data
Error file from QA of on-site data
Report file from QA of on-site data
Output from QA of on-site data
Command file for merge of NUS data
Error file from merge of NUS data
Report file from merge of NHS data
Output from merge of NUS data
Command file for on-site merge
Error file from on-site merge
Report file from on-site merge
Output from on-site merge
Command file for Stage 3
Command file for Stage 3
Command file for Stage 3
Figure D-1 Files associated with the testing of MPRM (dated 96030)
D-2
-------
JB STA
JB OUT DISK TEST121.RPT
JB ERR DISK TEST121.ERR
JB FIN
Start JB input
Defines name for general
report file
Defines name for error report
file
Finish JB input
UA STA
UA IN2 USER 24157-94.MIX (A5,3I2,2X,14,14X,14) 24157
UA LOC 24157 117.53W 47.63N 0
UA EXT 94 10 31 94 12 01
UA IQA DISK IQAUA.121
UA OQA DISK OQAUA.121
UA FIN .
Start UA input
Provides information for
extracting mixing heights
Defines location of mixing
height data
Defines time period for
extraction of mixing heights
Defines name for OA input
file (extracted data file)
Defines name for OA output
file
Finish UA input
Figure D-2 Run stream for extraction and quality assurance of NWS
mixing height estimates.
D-3
-------
JB STA
JB OUT DISK TEST122.RPT
JB ERR DISK TEST122.ERR
JB FIN
SF STA
SF 1H2
SF IMS
SF LOC
SF EXT
SF IOA
SF OCA
SF AUD
SF TRA
SF FIN
DISK 24155-94.DAT CD144FB 24155
DISK 24155-94.PPP TD3240FB 9924155
24157 118.85U 45.67N 0
94 11 01 94 11 30
DISK IQAUA.122
DISK OOAUA.122
PUTH
PWTH PRES CLHT TSKC THPT UD16 WIND
Start JB input
Defines name for general
report file
Defines name.for error report
file
Finish JB input
Start SF input
Provides information for
extracting NWS surface data
Provides information for
extracting precipitation data
Defines location of NWS
surface data
Defines time period for
extraction of surface data
Defines name for QA input
file (extracted data file)
Defines name for QA output
file
Adds present weather (PWTH)
to the audit report
Adds specified variables to
trace report
Finish SF input
Figure D-3 Run stream for extraction and quality assurance of NWS
surface and precipitation data.
D-4
-------
JB STA
JB OUT DISK TEST123.RPT
JB ERR DISK TEST123.ERR
JB FIN
OS STA
OS IQA DISK LAF-OS.MET
OS MAP DAT01 OSYR OSMO OSDY OSHR WS01 TT01 DT01 WD01 SA01 I.NSO
OS FMT DAT01 (AX, 412, F9.1, 9X, 5F9.1)
OS LOG LAFAYE 122.60W 45.SON 0
OS EXT 94 11 01 94 11 30
OS DT1 2. 20.
OS HGT 1 20.
OS CHK INSO 2 9999 0 700
OS CHK
OS CHK
OS AUD
OS OQA
OS FIN
DT01 1 -999 -10 5
SA 1 99 0 50
INSO DT01
DISK OQAUA.123"
Start JB input
Defines name for general
report file
Defines name for error report
file
Finish JB input
Start OS input
Defines name of on-site data
file
Defines list of on-site
variables
Defines format for on-site
data
Defines location of on-site
data
Defines time period for
extraction of on-site data
Defines heights for Delta-T
measurements :
Defines heights for multi-
level variables
Redefines default upper and
lower bounds for QA of
insolation.
Redefines default bounds for
QA of Delta-T
Redefines default bounds for
QA of Sigma-Theta
Adds insolation and Delta-T
to the QA audit report
. Defines name for QA output
file
Finish OS input
Figure D-4 Run stream for extraction and quality assurance of on-site
data.
D-5
-------
JB STA
JB OOT DISK TEST223.RPT
JB ERR DISK TEST223.ERR
JB FIN
UA STA
UA OOA DISK OOAUA.121
UA FIN
SF STA
SF OOA DISK OQASF.122
SF FIN
OS STA
OS OOA DISK OOACS.123
OS FIN
KR STA
MR EXT 94 11 01 94 11 30
HR OOT DISK MERGE.223
MR FIN
Start JB input
Defines name for general
report file
Defines name for error report
file
Finish JB input
Start UA input
Provides name of upper air
output file to merge
Finish UA input
Start SF input
Provides name of surface
output file to merge
Finish SF input
Start OS input
Provide name of on-site
output file to merge
Finish OS input
Start MR input
Define time period of data to
merge
Define name of merge output
file
Finish MR input
Figure D-5 Run stream for merging of NWS mixing height and surface
data with on-site data.
D-6
-------
2.00 0.15 0.0
JB STA
JB OUT DISK TEST324.RPT
JB ERR DISK TEST324.ERR
JB F.IN
OS STA
OS LOG LAFAYE 122.60W 45.SON ' 0
OS SFC SETUP SEASON 2
OS SFC SECTORS 1 0 180
OS SFC SECTORS 2 180 360
OS SFC VALUES 1 1 0.50. 1.50 0.15 0.50
OS SFC VALUES 2 1 0.12 0.70 0.15 1.00 2.00 0.15 0.0
OS SFC VALUES 3 1 0.12 0.30 0.15 1.30 2.00 0.15 0.0
OS SFC VALUES 4 1 0.12 1.00 0.15 0.80 2.00 0.15-0.0
OS SFC VALUES 1 2 0.35 1.50 0.15 1.00 50.00 0.27 0.0
OS SFC VALUES 2 2 0.14 1.00 0.15 1.00 50.00 0.27 0.0
OS SFC VALUES, 3 2 0.16 2.00 0.15 1.00 50.00 0.27 0.0
OS SFC VALUES 4 2 0.18 2.00 0.15 1.00 50.00 0.27 0.0
OS FIN
MP STA
MP MET DISK MERGE.223 8
MP MMP DISK TEST324.0UT ISCSTWET
MP VBL WIND ONSITE 10
MP VBL TEMP ONSITE 2
MP VBL STAB TTDIFF 10
MP FIN __^_^__
Start JB input
Defines name for general
report file
Defines name for error report
file
Finish JB input
Start OS input
Defines on-site location
Specifies seasonal surface
characteristics,for 2 sectors
Defines bounds for sector 1
Defines bounds for sector 2
Data for season 1, sector, 1
Data for season 2, sector 1
Data for season 3, sector 1
Data for season 4, sector 1
Data for season 1> sector 2
Data for "season 2, sector 2
Data for season 3, sector 2
Data for season 4, sector 2
Finish OS input
Start MP input
Provides name of merge file
to process
Defines output file name and
dispersion model
Defines processing options
for wind speed and direction
Defines processing options
for temperature
Defines processing options
for stability
Finish MP input
Figure D-6 Run stream for processing NWS and on-site data for use in
wet deposition modeling.
D-7
-------
1.
2.
3.
4.
METEOROLOGICAL PROCESSOR FOR REGULATORY MODELS [MPRH (dated
30-JAN-96 10:19:28
STAGE 1 EXTRACTION AND QA OF METEOROLOGICAL DATA
*** JOB TERMINATED NORMALLY ***
********************************************************
STATUS REPORT PRIOR TO BEGINNING PROCESSOR RUN
REPORT FILE NAMES
ERROR MESSAGES: TEST122.ERR
SUMMARY OF RUN: TEST122.RPT
UPPER AIR DATA
THE PROCESS(ES) MPRM ANTICIPATES TO PERFORM ARE:
NONE - NO DATA TO BE PROCESSED ON THIS PATH
NWS SURFACE DATA
SITE ID LATITUDECDEG.) LONGITUOECDEG. )
24155 45.67N 118. 85W
THE PROCESS(ES) MPRM ANTICIPATES TO PERFORM ARE:
EXTRACT AND QUALITY ASSESSMENT
EXTRACT INPUT - OPEN: 24155-94.DAT
EXTRACT OUTPUT- OPEN: IQASF.122
QA OUTPUT - OPEN: OQASF.122
THE EXTRACT DATES ARE: STARTING: 1-NOV-94
ENDING: 30-NOV-94
OH-S1TE DATA
THE PROCESSCES) MPRM ANTICIPATES TO PERFORM ARE:
NONE - NO DATA TO BE PROCESSED ON THIS PATH
**** MPRM MESSAGE SUMMARY TABLE ****
0- 9 10-19 20-29 30-39 40-49 50-59 60-69 70-7'
JB
EOOOOOOOO
woooooooo
107000000
SF
EOOOOOOOO
woooooooo
100004000
000000000
07004000
96030)]
? TOTAL
0
0
7
0
0
4
0
11
Figure D-7a Report file for extraction and QA of surface data (1 of 2).
D-8
-------
METEOROLOGICAL PROCESSOR FOR REGULATORY MODELS [MPRM (dated 96030)]
30-JAN-96 10:19:28
STAGE 1 EXTRACTION AND QA OF METEOROLOGICAL DATA
**** WARNING MESSAGES ****
--- NONE --- . -
**** ERROR MESSAGES ****
--- NONE ---
********************************************************
*** JOB TERMINATED NORMALLY ***
**** SUMMARY OF THE QA AUDIT ****
SURFACE DATA j VIOLATION SUMMARY------, ' CIJES
TOTAL # LOWER UPPER % MISSlNtj
# OBS MISSING BOUND BOUND ACCEPTED FLAG
SLVP 720 000 100.00 -9999.0,
PRPS 720 400 99.44 -9999.0,
riHT 720 10 0 0 98.61 -9999.0,
TSH 7lo 2 0 0 99.72 99.0,
KC 720 100 99.86 99.0,
PU 720 . 000 100.00 99.0,
TH 720 0 0 0 100.00 99.0,
HZys 720 0 00 100.00 -9999.0,
TMPD 720 00 0 100.00 -9999.0,
WD16 720 500 99.31 -9999.0,
WIND 720 4 • 0 0 99.44 -9999.0,
NOTE: TEST VALUES MATCH INTERNAL SCALING APPLIED TO VARIABLES
(SEE APPENDIX C OF THE USER'S GUIDE)
THE FOLLOWING CHECKS WERE ALSO PERFORMED FOR THE SURFACE QA
OF 720 REPORTS, THERE WERE
30 CALM WIND CONDITIONS (WS=0, WD=0)
0 ZERO WIND SPEEDS WITH NONZERO WIND DIRECTIONS
0 DEW-POINT GREATER THAN DRY BULB TEMPERATURES
6 PRECIPIATION & WEATHER MISMATCH
THE TIMES OF THESE OCCURRENCES CAN BE FOUND IN THE MESSAGE
WITH QUALIFIERS CLM, ZNZ, DTT & PPT (RESP.)
THIS CONCLUDES THE AUDIT TRAIL
T VALUES |
LOWER UPPER
BOUND BOUND
9000.0,10999.0
9000.0,10999.0
0.0,
0.0,
0.0,
0.0,
0.0,
0.0,
-300.0,
0.0,
0.0,
FILE
300.0
10.0
10.0
92.0
92.0
1640.0
350.0
36.0
500.0
Figure D-7b Report file for extraction and QA of surface data (2 of 2).
D-9
-------
METEOROLOGICAL PROCESSOR FOR REGULATORY MODELS [MPRM (dated 96030)]
30-JAN-96 10:24:56
STAGE 2 MERGE METEOROLOGICAL DATA
****************************************
*** JOB TERMINATED NORMALLY
***
********************************************************
STATUS REPORT PRIOR TO BEGINNING PROCESSOR RUN
1. REPORT FILE HAMES
ERROR MESSAGES: TEST223.ERR
SUMMARY OF RUN: TEST223.RPT
Z. UPPER AIR DATA
THE PROCESS(ES) MPRM ANTICIPATES TO PERFORM ARE:
MERGE ONLY
QA OUTPUT - OPEN: OQAUA.121
3. KUS SURFACE DATA
THE PROCESS(ES) MPRM ANTICIPATES TO PERFORM ARE:
MERGE ONLY
OA OUTPUT - OPEN: OQASF.122
4. ON-SITE DATA
THE PROCESS(ES) MPRM ANTICIPATES TO PERFORM ARE:
MERGE ONLY
OA OUTPUT - OPEN: OQAOS.123
5. MERGED DATA
MERGE OUTPUT - OPEN: MERGE.223
***** USER INPUT PARAMETERS FOR MERGE *****
MERGED DATA BEGIN (YR/MO/DA) 94/11/ 1
AND END 94/11/30
THE OM-SITE LATITUDE AND LONGITUDE ARE:
LATITUDE
LONGITUDE
Figure D-8a
Report file for Stage 2 MERGE (1 of 2)
D-10
-------
METEOROLOGICAL PROCESSOR FOR REGULATORY MODELS [MPRM (dated 96030)]
30-JAN-96 10:24:56
STAGE 2 MERGE METEOROLOGICAL DATA
***** DAILY OUTPUT STATISTICS *****
MO/DA 1V 1 1V 2 1V 3 1V 4 1V 5 1V 6 11/ 7 1V 8 1V 9
NWS UPPER AIR SDGS O'OOOOOO.OO
NCDC MIXING HEIGHTS 6 6 6 6 6 J> ° ° °
NWS SFC OBSERVATIONS 24 24 24 24 24 24 24 24 24
ON-SITE OBSERVATIONS 24 24 24 24 24 24 24 24 24
MO/DA 11/11 1V12 11/13 11/14 11/15 11/16 11/17 11/18 11/19
NWS UPPER AIR SDGS 0 0 0 0 0 0 0 0 0
NCDC MIXING HEIGHTS 6 6 6 6 6 6 6 6 6
NWS SFC OBSERVATIONS 24 24 24 24 24 24 24 24 24
ON-SITE OBSERVATIONS 24 24 24 24 24 24 24 24 24
MO/DA 11/21 11/22 11/23 11/24 11/25 11/26 11/27 11/28 11/29
NWS UPPER AIR SDGS 0 0 0 0 0 0 0 0 0
NCDC MIXING HEIGHTS 6 6 6 .6 6 6 6 6 6
NWS SFC OBSERVATIONS 24 24 24 24 24 24 24 24 24
ON-SITE OBSERVATIONS 24 24 24 24 24 24 24 24 24
UPPER AIR OBS. READ: 32 .
SURFACE OBS. READ: 720
ON-SITE OBS. READ: 720
***** MERGE PROCESS COMPLETED *****
**** HPRM MESSAGE SUMMARY TABLE ****
11/10
0
6
24
24
11/20
0
6
24
24
11/30
0
6
24
24
0- 9 10-19 20-29 30-39 40-49 50-59 60-69 70-79 TOTAL
JB
EO 0 000 0 0 0
W01000000
14 7 O'O.O 0 0 0
OS
EO 0 0 - 0 0 0 0 0
WO 2 0 0 0.0 0 0
100000000
MR
EDO 00 0 00 0
WO 0 0 0 0 0 00
10 0 00 0 1 0 0
4 10 0 0 0 1-0 0
**** WARNING MESSAGES ****
0 JB W12 TEST: SUMMARY: ERROR/OR MISSING OS-LOC CARD
0 OS W15 AUTCHK: MHGT NOT INPUT: AUDIT & TRACE DISABLED
0 OS W15 AUTCHK: SE NOT INPUT: AUDIT & TRACE DISABLED
**** ERROR MESSAGES ****
--- NONE ---
0
1
11
0 '
2
0
0
0
1
15 '
Figure D-8b Report file for Stage 2 MERGE (2 of 2}
D-ll
-------
METEOROLOGICAL PROCESSOR FOR REGULATORY MODELS [MPRM (dated 96030)]
30-JAN-96 10:27:33
STAGE-3 PROCESSING OF MERGED METEOROLOGICAL DATA
********************************
*** JOB TERMINATED NORMALLY ***
********************************
1. FILENAMES AS DETERMINED DURING SETUP
TEST324 RPT OPENED SUCCESSFULLY
TEST324.ERR OPENED SUCCESSFULLY
MERGE 223 OPENED SUCCESSFULLY
TEST324.0UT OPENED SUCCESSFULLY
2. DISPERSION MODEL DEFINED DURING SETUP: 1SCSTWET
3. PROCESSING OPTIONS SELECTED DURING SETUP
PROCESS SCHEME
WIND ONSITE
TEMPERATURE ONSITE
MIXING HEIGHTS NWSWXX
STABILITY TTDIFF
4. STABILITY METHODS USED
NWSWXX 0
ONSITE 0
SESITE 0
SASITE 0
UNDWXX 0
TTDIFF 719
USERIN 0
5. PROCESSING ASSUMPTIONS
WIND SPEED/TURB. MEASUREMENT HEIGHT (M): 10.00
STACK HEIGHT (M) 10.00
TEMPERATURE HEIGHT (M) 2.00
6. LOCATIONS SPECIFIED IN SETUP
DATA SITE LONGITUDE LATITUDE
PATHWAY ID (DEGREES) (DEGREES)
UA 24157 117.53W 47.63N
SF 24155 118.85W 45.67N
OS LAFAYE 122.60W 45.SON
*****************************************
* LONGITUDE AND LATITUDE FOR PROCESSING *
* 122.60 45.50 *
*****************************************
Figure D-9a Report file for Stage 3 processing (1 of 3)
D-12
-------
METEOROLOGICAL PROCESSOR FOR REGULATORY MODELS [MPRM (dated 96030)]
30-JAN-96 10:27:33
STAGE-3 PROCESSING OF MERGED METEOROLOGICAL DATA
7. OUTPUT FILE NAMES.
ERROR REPORT FILE:
MET DATA FOR MODELING:
HEADER ON OUTPUT FILE:
TEST324.ERR
TEST324.0UT
24157
94
24155
94
8. SUMMARY OF DATA PROCESSING RESULTS
VARIABLE # VALID # MISSING
STABILITY 719 1
WIND SPEED ,673 1
WIND DIRECTION 719 1
RURAL MIXING HEIGHT 719 ' 1
URBAN MIXING HEIGHT 719 1
TEMPERATURE 719 1
9. DISTRIBUTION OF WIND SPEEDS
46 (Calms)
5.16 (Average)
WS CLASS 1 2 34 5 6
# HOURS 235. 265. 138. 31. 4.
AVERAGE 1.38 2.42 4.07 6.38 9.05 0.
10. RURAL STABILITY CATAGEORY RESULTS (# HOURS)
A B C DD DN EF
0 20 41 213 205 240
11. SURFACE CHARACTERISTICS USED
Month Sector Albedo
1 1
2 1
3 1
4 1
5 1
6 1
7 1
8 1
9 1
10 1
11 1
12 1
1 2
2 2
3 2
4 2
5 2
6 2
7 2
8 2
9 2
.10 2
11 2
12 2
0.5000
0.5000
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
n
1200
1200
1200
1200
.1200
.1200
.1200
.1200
.1200
.5000
.3500
.3500
.1400
.1400
.1400
.1600
.1600
.1600
.1800
.1800
.1800
.3500
Bowen
1.5000
1.5000
0.7000
0.7000
0.7000
0.3000
0.3000
0.3000
1.0000
1.0000
1.0000
1.5000
1.5000
1.5000
1.0000
1.0000
1.0000
2.0000
2.0000
2.0000
2.0000
2.0000
2.0000
1.5000
zO(meas)
0.
0.
0.
0.
0.
0.
0.
0.
0-.
0.
0.
0.
0.
0.
0.
0.
0.
0.
0.
0.
1500
1500
1500
1500
1500
1500
1500
1500
1500
1500
1500
1500
1500
1500
1500
1500
1500
1500
1500
1500
0.1500
0.1500
0
n
1500
1500
zO(appl)
0.5000
0.5000
1.0000
1.0000
1.0000
1.3000
1.3000
1.3000
0.8000
0.8000
0.8000
0.5000
1.0000
1.0000
1.0000
1.0000
1.0000
1.0000
1.0000
1.0000
1.0000
1.0000
1.0000
1.0000
0.
00
Min. L
2.
2.
2.
2.
2.
2.
2..
2.
2.
2.
2.
. 2.
50.
50.
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
50.0000
50.0000
50.0000
50.0000
50.0000
50.0000
50.0000
50.0000
50.0000
•sn
0000
eg
0.1500
0.1500
0.1500
0.1500
0.1500
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
.1500
.1500
.1500
.1500
.1500
.1500
.1500
.2700 .
.2700
.2700
.2700
.2700
.2700
.2700
.2700
.2700
.2700
.2700
.2700
Anth Heat
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
Figure D-9b
Report file for Stage 3 processing (2 of 3)
D-13
-------
METEOROLOGICAL PROCESSOR FOR REGULATORY MODELS tMPRM (dated 96030)]
30-JAN-96 10:27:33
STAGE-3 PROCESSING OF MERGED METEOROLOGICAL DATA
**** MPRM MESSAGE SUMMARY TABLE ****
0- 9 10-19 20-29 30-39 40-49 50-59 60-69 70-79 TOTAL
JB
E
U
I
0
0
2
0
0
0
0
0
0
0
0
0
0
0 .
0
0
0
0
0
0
0
0
0
0
0
0
2
OS
E
W
1
T
0
0
1
0
3
****
0 OS
0 OS
305
305
305
305
305
305
305
305
HP
HP
MP
HP
HP
MP
HP
MP
0
0
1
0
0
0
0
0
0 0
0 0
0 0
0 0
0
0
0
0
000
0 228 228
024
000
3 0 0 0 0 0 230 236
WARNING MESSAGES ****
W15 AUTCHK: MHGT NOT INPUT: AUDIT & TRACE DISABLED
W15 AUTCHK: SE NOT INPUT: AUDIT & TRACE DISABLED
W76
W76
W76
W76
W76
W76
W76
W76
DEPMET:
DEPMET:
DEPMET:
DEPMET:
DEPMET:
DEPMET:
DEPMET:
DEPMET:
NET
NET
NET
NET
NET
NET
NET
NET
RAD
RAD
RAD
RAD
RAD
RAD
RAD
RAD
•N
'N
'N
'N
'N
'N
'N
'N
< 0 DURING DAY ON
SUSPECT
SUSPECT
SUSPECT
SUSPECT
SUSPECT
SUSPECT
SUSPECT
( -62.)
( -73.)
( -78.)
( -52.)
( -73.)
( -78.)
( -78.)
94305/13
ON
ON
ON
ON
ON
ON
ON
94305/18
94305/19
94305/20
94305/21
94305/22
94305/23
94305/24
Figure D-9c
Report file for Stage 3 processing (3 of 3}
D-14
-------
241579410312
241579411011
241579411021
241579411031
241579411042
241579411052
241579411062
241579411071
241579411081
241579411091
241579411102
241579411111
241579411121
241579411131
241579411141
241579411151
241579411161
241579411172
241579411181
241579411191
241579411202
241579411211
241579411221
241579411232
678
1029
447
308
380
228
348
359
157
772
723
. 354
4
7
5
5
7
4
1
4
2
3
6
1
31111
171
67
668
143
7
2
1
2
66918
860
222
4
4
105117
872
141
333
9
1
4
.2
.9
.0
.4
.0
.3
.0
.5
.5
.1
.5
.7
.7
.6
.3
.0
.3
.8
.0
.8
.3
.2
.8
.5
3
6
3
3
1
3
0
3
1
2
4
2
5
4
2
1
2
9
3
4
8
5
1
3
.0
.4
.4
.8
.5
.2
.8
.5
.9
.6
.4
.3
.9
.8
.3
.6 .
.3
.5
.0
.3
.4
.5
.8
.2
2
1
1
1
1
2
2
1
2
1
2
2
1
1
1
1
2
1
1
2
1
1
2
. 2
733
653
898
357
274
152
288
327
321
651
253
2
7
4
4
3
2
3
4
7
4
1
43011
248
262
338
254
254
182
712
6
6
3
3
4
8
8
36512
383
541
107
251
9
3
2
3
.9
.5
.1
.7
.0
.4
.5
.9
.1
.5
.2
.0
.8
.1
.6
.0
.1
.6
.2
.4
.8
.7
.5
.1
2
7
4
3
2
2
3
3
4
3
1
4
5
6
2
3
3
7
4
6
6
3
2
2
.6
.3
.4
.7
.9
.2
.4
.2
.7
.5
.8
.9
.8
.2
.5
.0
.0
.2
.9
.7
.7
.1
.5
.3
Figure D-10
Extract from 24157-94.MIX providing NWS estimated
mixing heights
D-15
-------
FILE: 24155-94.001
This is the altered data for November 1, 1994 for station # 24155.
Selected records have been altered by including missing fields for use
in testing Stage 1 QA processing. Missing fields have been inserted
beginning with the record for 02:00.
....+.... 1....+ 2.... + 3 + 4 + 5 + 6 + 7 + -
nonnn mm hh vv ff rhh
yr dd ccc precip DD pppp T
241S594110100008580010001000000006103926142813041040093-8K008-3023-
24 155941 1 01 0100858001 0001 000000006503725 1 7281 4040038089 - 6K0084K020 -
2415594110102 580007001000000007503625162816039037089-7K0123K020-
2415594110103 80001000 000000007403621072816037036096--K012
24 155941 1 01 04 58001 000 0000000740362309281 6038037093 - 7KO 1 63K023 -
2415594110105 80001000 0000007703621102817039037089--K025
2415594110106 58001500 00008003525102817040037082-7K025-6095-
2415594110107 28006000 000086036 142819041038083-2K025-7100-
2415594110108 80006000 000092036 2820041038083-OM025-6100-
2415594110109 25004000 000095035 04203807670M025 161 001 792007
2415594110110 21004000 000091034 045040066 OM025171001382003
2415594110111 22004000 000091035 047041063 24025082002
24155941 101 12-- -220040000000000008803428192819047041061 554030082005
24155941 101 13- - -22004000000000000830352720281 8048042061 224030082002
24155941 10114- --220040000000000008303325202818048041 0561 14030082001
24 15594 1 1 01 1 5- - - 2200300000000000086033262028 1 80470400584 1 4030482004
2415594110116220225030000000000008603227152818045039061924030471204992209
2415594110117220225030000000000009503423052821042038073914030530855992209
24 15594 1 101 182202500200000000000096031 28082821 039035073633085692206
24155941 101 19-- -220020000000000010203125102823041036068313035382503
2415594110120---210020000000000010502921072823039034067513040582505
2415594110121060550020000000000011002924042825039034067863060882508
24155941 10122-- -210020000000000010902922032825037033073423060482504
24155941 10123- --10002000000000001 11029190428250370330734461 10
Key to CD- 144 Format:
Code Field Variable
mnnn 1-5 Station ID
yy 6-7 Year
mm 8-9 Month
dd 10-11 Day of Month
hh 12-13 Hour
ccc 14-16 CLHT Ceiling Height (hundreths of feet)
24-29 Present weather
24 Thunder Storm
25-26 PW Liquid Precip (Rain & Drizzle)
27-29 TH Frozen Precip
32-35 Sea Level Pressure (mb and tenths)
DO 39-40 WD16 Wind Direction (tens of degrees)
ff 41-42 WIND Wind Speed (knots)
pppp 43-46 PRES Station Pressure (hundreths of inches)
ttt 47-49 TMPD Dry Bulb (degrees F)
rhh 53-55 Relative Humidity (percent)
T 56 TS Total Cloud Cover
(C 79 KC Total Opaque Cloud Cover
8
K
-
-
-
-
8
-
-
5
1
5
2
1
3
5
7
4
2
1
6
2
1
Figure D-11
Altered records from 24155-94.DAT for testing Stage 1 QA
processing
D-16
-------
HPD99241500HPCPH11994100031 2400000005
HPD99241500HPCPH11994110001 0100000005
HPD99241500HPCPH11994110001 0400000005
HPD99241500HPCPHI1994110001 0500000005
HPD99241500HPCPHI1994110001 0800000099
HPD99241500HPCPHI1994110001 0900000099
HPD99241500HPCPHI1994110001 1000000099
HPD99241500HPCPH!1994110001 2500000025
HPD99241500HPCPHI1994110002 1600000005
HPD99241500HPCPH11994110002 1700000005
HPD99241500HPCPHI1994110002 2500000010
HPD99241500HPCPH11994110004 0600000005
HPD99241500HPCPH11994110004 0700000005
HPD99241500HPCPHI1994110004 0800000020
HPD99241500HPCPH11994110004 0900000005
HPD99241500HPCPHI1994110004 1000000005
HPD99241500HPCPH11994110004 1100000005
HPD99241500HPCPHI1994110004 1200000005
HPD99241500HPCPHI1994110004 1300000005
HPD99241500HPCPH11994110004 1400000005
HPD99241500HPCPH11994110004 1500000005
HPD99241500HPCPH!1994110004 1600000005
HPD99241500HPCPHI1994110004 1700000020
HPD99241500HPCPHI1994110004 1800000005
Figure D-12 Extract from 24155-94.PPP providing precipation data
9411
9411
9411
9411
9411
9411
9411
9411
9411
9411
9411
9411
9411
9411
' 9411
9411
9411
9411
9411
9411
9411
9411
9411
-9411
1 1
1 2
1 3
1 4
1 5
1 6
1 7
1 8
1 9
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
2.3
2.7
3.0
3.6
4.1
4.0
3.2
3.4
3.2
3.4
4.4
3.6
1.7
2.2
2.0
2.4
2.1
2.7
3.0
3.1
3.1
2.1
2.2
2.0
4.4
4.6
5.0
4.9
5.1
5.2
5.3
5.4
5.6
6.7
8.0
6.7
4.8
6.2
6.9
7.3
6.5
5.7
4.7
4.3
4.4
4.5
4.6
4.6
-1.0
-1.0
-0.9
-1.0
-1.0
-1.0
-0.9
-1.0
-0.9
0.6
0.6
0.0
-1.0
-0.5
-0.6
-0.3
-1.2
-1.2
-1.4
-1.4
-1.2
-1.2
-1.1
-1.0
165.0
168.0
189.0
196.0
206.0
197.0
199.0
206.0
215.0
219.0
215.0
264.0
242.0
169.0
187.0
195.0
185.0
182.0
187.0
184.0
183.0
203.0
220.0
231.0
35.0
14.0
15.3
15.0
13.5
13.0
19.0
15.2
14.8
15.9
15.7
23.0
24.3
27.4
21.4
18.9
17.8
14.3
14.5
15.2
15.3
25.6
18.4
20.0
0.0
0.0
0.0
0.0
0.0
0.0
'0.0
. 17.4
. 87.2
275.6
272.1
117.2
50.2
184.9
139.6
97.7
11.2
0,0
0.0
0.0
0.0
0.0
0.0
0.0
Figure D-13
Extract from LAF-OS.MET providing on-site meteorological
data
D-17
-------
24155
9411
9411
9411
9411
9411
9411
9411
9411
9411
9411
9411
9411
9411
9411
9411
9411
9««11
9411
9411
9411
9411
9411
9411
9411
1 1
1 2
1 3
1 4
1 S
1 6
1 7
1 8
1 9
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
345.0000
348.0000
9.0000
16.0000
26.0000
17.0000
19.0000
26.0000
35.0000
39.0000
35.0000
84.0000
62.0000
349.0000
7.0000
15.0000
5.0000
2.0000
7.0000
4.0000
3.0000
23.0000
40.0000
51.0000
94
2.3000
2.7000
3.0000
3.6000
4.1000
4.0000
3.2000
3.4000
3.2000
3.4000
4.4000
3.6000
1.7000
2.2000
2.0000
2.4000
2.1000
2.7000
3.0000
3.1000
3.1000
2.1000
2.2000
2.0000
24157
277.5 4
277.8 4
278.1 4
278.0 4
278.3 4
278.4 4
278.4 4
278.5 4
278.8 4
279.9 3
281.1 3
279.9 4
277.9 4
279.4 3
280.0 4
280.4 4
279.6 4
278.9 4
277.9 4
277.4 4
277.5 4
277.6 4
277.8 4
277.8 4
702.3
698.5
694.7
690.9
687.1
683.3
679.6
675.8
672.0
668.2
664.4
660.6
656.8
653.0
653.0
653.0
654.0
665.7
677.3
688.9
700.5
712.1
723.7
735.4
94
702.3
698.5
694.7
690.9
687.1
683.3
679.6
675.8
672.0
668.2
664.4
660.6
656.8
653.0
653.0
653.0
654.0
665.7
677.3
688.9
700.5
712.1
723.7
735.4
0.1577
0.1823
0.2268
0.3074
0.3668
0.3335
0.2552
0.2822
0.3230
0.3974
0.4904
0.3839
0.1493
0.2772
0.2334
0.1905
0.1692
0.2108
0.2341
0.2416
0.2416
0.1750
0.1816
0.1690
195.1
159.0
100.5
186.0
260.1
161.2
128.3
157.0
-998.0
-95.9
-170.2
-367.0
50.0
-73.2
-97.6
50.0
50.0
51.6
57.1
58.7
68.5
50.0
50.0
50.0
1.0000
1.0000
0.8000
0.8000
0.8000
0.8000
0.8000
0.8000
0.8000
0.8000
0.8000
0.8000
0.8000
1.0000
0.8000
0.8000
0.8000
0.8000
0.8000
0.8000
0.8000
0.8000
0.8000
0.8000
1
1
1
1
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1.27
O.CO
0.00
1.27
1.27
0.00
0.00
25.15
25.15
25.15
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
Figure D-14
Extract from TEST324.OUT providing the first 24 records
from the Stage 3 output for ISCSTWET
D-18
-------
METEOROLOGICAL PROCESSOR FOR REGULATORY MODELS [MPRM (dated 96030)3
30-JAN-96 10:19:19
STAGE 1 EXTRACTION AND QA OF METEOROLOGICAL DATA
**** SUMMARY OF THE QA AUDIT ****
MIXING NTS ! VIOLATION SUMMARY -j
TOTAL # LOWER UPPER %
# OBS MISSING BOUND BOUND ACCEPTED
UAM1 32 000 100.00
UAM2 32 000 100.00
] TEST VALUES \
MISSING LOWER UPPER
FLAG BOUND .BOUND
-9999.0, 50.0, 2500.0
-9999.0, 50.0, 4500.0
SURFACE DATA
SLVP
PRES
CLHT
TS
KC
PW
TH
HZVS
TMPD
WD16
WIND
TOTAL
# OBS
720
720
720
720
720
720
720
720
720
720
720
MISSING
0
4
10
2
1
0
0
0
0
5
4
VIOLATION SUMMARY
LOWER UPPER
BOUND BOUND
-TEST VALUES-
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
ACCEPTED
100.00
99.44
98.61
99.72
99.86
100.00
100.00
100.00
100.00
99.31
99.44
MISSING
FLAG
-9999.0,
-9999.0,
-9999.0,
99.0,
99.0,
99.0,
99.0,
-9999.0,
-9999.0,
-9999.0,
-9999.0,
LOWER UPPER
BOUND BOUND
9000.0,10999.0
9000.0,10999.0
0.0, 300.0
0.0,
0.0,
0.0,
0.0,
0.0,
-300.0,
0.0,
0.0,
10.0
10.0
92.0
92.0
1640.0
350.0
36.0
500.0
SITE SCALARS
INSO
DT01
] VIOLATION SUMMARY \
TOTAL # LOWER UPPER %
# OBS MISSING BOUND BOUND ACCEPTED
720 0 0 0 100.00
720 0 8 20 . 96.11
j TEST VALUES j
MISSING LOWER UPPER
FLAG BOUND BOUND
9999.0, 0.0, 700.0
-999.0, -10.0, 5.0
SITE VECTORS
SA
TT
WD
WS
TOTAL
# OBS
720
720
720
720
-VIOLATION SUMMARY
LOWER UPPER %
MISSING BOUND
BOUND ACCEPTED
20.00 M
15
0
0
0
97.78
99.86
99.86
99.86
| TEST VALUES {
MISSING LOWER UPPER
FLAG BOUND BOUND
,99.0, 0.0, 50.0
99.0, -30.0, 35.0
999.0, 0.0, 360.0
999.0, 0.0, 50.0
THE FOLLOWING CHECKS WERE ALSO PERFORMED FOR THE SURFACE QA
OF 720 REPORTS, THERE WERE
30 CALM WIND CONDITIONS (WS=0, WD=0)
0 ZERO WIND SPEEDS WITH NONZERO WIND DIRECTIONS
0 DEW-POINT GREATER THAN DRY BULB TEMPERATURES
6 PRECIPIATION & WEATHER MISMATCH
THE TIMES OF THESE OCCURRENCES CAN BE FOUND IN THE MESSAGE FILE
WITH QUALIFIERS CLM, ZNZ, DTT & PPT (RESP.)
THIS CONCLUDES THE AUDIT TRAIL
Figure D-15
Summary of Stage 1 QA audit results for UA, SF, OS
pathways.
D-19
-------
15 JB
0 JB
0 JB
0 JB
0 JB
0 JB
0 JB
0 SF
720 SF
0 SF
30502 SF
30502 SF
30503 SF
30504 SF
30504 SF
30505 SF
30505 SF
30506 SF
30507 SF
30507 SF
30508 SF
30508 SF
30508 SF
30508 SF
30509 SF
30509 SF
30509 SF
30509 SF
30509 SF
30510 SF
30510 SF
30510 SF
30510 SF
30510 SF
30510 SF
30511 SF
30511
30511
30511
30511
30511 SF
30602 SF
30905 SF
30906 SF
30907 SF
30909 SF
30922 SF
31006 SF
SF
SF
SF
SF
119 SETUP: FOUND "END OF FILE" ON DEVICE DEVIN 5
110 TEST: SUMMARY: NO UA-EXT CARD, NULL EXTRACT
111 TEST: SUMMARY: NO UA-IQA CARD, NULL QA
112 TEST: SUMMARY: NO UA-OQA CARD, NULL MERGE
110 TEST: SUMMARY: NO OS-EXT CARD, NULL EXTRACT
111 TEST: SUMMARY: NO OS-IQA CARD, NULL QA
112 TEST: SUMMARY: NO OS-OQA CARD, NULL MERGE
140 SFEXT: *** HLY SFC DBS & PRECIP EXTRACTION ***
149 RD144D: END-OF DATA WINDOW AFTER RECORD 721
149 SFEXT: 720 HLY WX & 720 PRECIP OBS EXTRACTED
SFQASM: CLHT MISSING ON 94/11/01/02
PPT SFQASM: WEATHER WITHOUT PRECIP ON 94/11/01/02
SFQASM: CLHT MISSING ON 94/11/01/03
SFQASM: CLHT MISSING ON 94/11/01/04
PPT SFQASM: PRECIP WITHOUT WEATHER ON 94/11/01/04
SFQASM: CLHT MISSING ON 94/11/01/05
PPT SFQASM: PRECIP WITHOUT WEATHER ON 94/11/01/05
SFQASM: CLHT MISSING ON 94/11/01/06
SFQASM: CLHT MISSING ON 94/11/01/07
SFQASM: WD16 MISSING ON 94/11/01/07
SFQASM: CLHT MISSING ON 94/11/01/08
SFQASM: WD16 MISSING ON 94/11/01/08
SFQASM: WIND MISSING ON 94/11/01/08
PPT SFQASM: PRECIP WITHOUT WEATHER ON 94/11/01/08
SFQASM: PRES MISSING ON 94/11/01/09
SFQASM: CLHT MISSING ON 94/11/01/09
SFQASM: WD16 MISSING ON 94/11/01/09
SFQASM: WIND MISSING ON 94/11/01/09
PPT SFQASM: PRECIP WITHOUT WEATHER ON 94/11/01/09
SFQASM: PRES MISSING ON 94/11/01/10
SFQASM: CLHT MISSING ON 94/11/01/10
SFQASM: TSKC MISSING ON 94/11/01/10
SFQASM: WD16 MISSING ON 94/11/01/10
SFQASM: WIND MISSING ON 94/11/01/10
PPT SFQASM: PRECIP WITHOUT WEATHER ON 94/11/01/10
SFQASM: PRES MISSING ON 94/11/01/11
SFQASM: CLHT MISSING ON 94/11/01/11
SFQASM: TSKC MISSING ON 94/11/01/11
SFQASM: TSKC MISSING ON 94/11/01/11
SFQASM: WD16 MISSING ON 94/11/01/11
SFQASM: WIND MISSING ON 94/11/01/11
SFQASM: PRES MISSING ON 94/11/02/02
CLM SFQASM: CALM WINDS ON 94/11/05/05
CLM SFQASM: CALM WINDS ON 94/11/05/06
CLM SFQASM: CALM WINDS ON 94/11/05/07
CLM SFQASM: CALM WINDS ON 94/11/05/09
CLM SFQASM: CALM WINDS ON 94/11/05/22
CLM SFQASM: CALM WINDS ON 94/11/06/06
721 SF 149 SFQASM: END OF FILE AFTER OBS #720
Figure D-16
Extract from the Stage 1 error report for the SF pathway.
D-20
-------
METEOROLOGICAL PROCESSOR FOR REGULATORY MODELS [MPRM (dated 96030)]
30-JAN-96 10:24:56
STAGE 2 MERGE METEOROLOGICAL DATA
***** DAILY OUTPUT STATISTICS *****
MO/DA 1V 1 1V 2 1V 3 1V 4 1V 5 1V 6 1V 7 1V 8 1V 9
NWS UPPER AIR SDGS 0 0 0 0 00 00 0
NCDC MIXING HEIGHTS
NWS SFC
ON-SITE
OBSERVATIONS
OBSERVATIONS
6
24
24
MO/DA 11/11
NWS UPPER AIR SDGS
NCDC MIXING HEIGHTS
NWS SFC
ON-SITE
OBSERVATIONS
OBSERVATIONS
0
6
24
24
MO/DA 11/21
NWS UPPER AIR SDGS
NCDC MIXING HEIGHTS
NWS SFC
ON-SITE
OBSERVATIONS
OBSERVATIONS
0
6
24
24
6
24
24
11/12
0
6
24
24
11/22
0
6
24
24
6
24
24
11/13
0
6
24
24
11/23
0
6
24
24
6
24
24
11/14
0
6
24
24
11/24
0
6
24
24
UPPER AIR DBS.
SURFACE
ON
-SITE
6
24
24
11/15
0
6
24
24
1.1/25
0
6
24
24
READ:
OBS. READ:
DBS. READ:
6
24
24
11/16
0
6
24
24
11/26
0
6
24
24
32
720
720
6
24
24
11/17
0
6
24
24
11/27
0
6
24
.24
6
24
24
11/18
0
6
24
24
11/28
. 0
6
24
24
6
24
24
11/19
0
6
24
24
1 1/29
0
6
24
24
11/10
0
6
24
24
11/20
0
6
24
24
'11/30
0
6
24
24
***** MERGE PROCESS COMPLETED *****
Figure D-17
Extract from the Stage 2 (MERGE) report file.
METEOROLOGICAL PROCESSOR FOR REGULATORY MODELS [MPRM
30- JAN -96 10:27:11
STAGE-3 PROCESSING OF MERGED METEOROLOGICAL
10. RURAL
A
TEST322 0
TEST323 39
TEST324 0
STABILITY CATAGEORY
B C
12 38
40 151
20 -41,
RESULTS (#
DD DN
225 248
44 240
213 205
(dated 96030)]
DATA
HOURS)
EF
197
205
240
Figure D-18
Extract from Stage 3 report files summarizing results of
stability classification.
D-21
-------
METEOROLOGICAL PROCESSOR FOR REGULATORY MODELS (MPRM), VERSION 1.2
TODAY'S DATE AND TIME: 28-APR-88 AT 15:23:37
PROCESSING OF MERGED METEOROLOGICAL DATA
METEORO
STABILITY CATEGORY DN
WIND DIRECTION
*• it
n
" MMP
F fine
HE
ENE
; g
F9P
i CwC
" SE
s *3&
<;<;?
^vu
• S
SSW
' Cll
ow
; wsw
' W
" yfjy
• fjy
NNH
SECTOR
1
2
3
4
5
6
7
8
<)
10
11
12
13
14
15
16
1
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0^000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
2
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0 . 000000
0.000000
0.000000
0.000000
LOGICAL JU1NI l-KtUUtNLI I-UNLIIUN
WIND SPEED CLASS
3
0.000000
0.010526
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.010526
0.000000
0.000000
0.000000
4
0.00000.0
0.010526
0.052632
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.115789
0.105263
0.000000
0.010526
0.021053
0.000000
0.000000
5
0.000000
0.000000
0.010526
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.073684
0.000000
0.000000
0.010526
0.000000
0.000000
6
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000 I
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
'STABILITY CATEGORY EF
WIND SPEED CLASS
WIND DIRECTION SECTOR
N
> HUE
NE
ENE
' E
ESE
' SE
f sSE
• S
ssw
sw
i wsw
I w
I WNW
• NW
Inn
NNW
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.052632
0.021053
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.010526
0.010526
0.063158
0.031579
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0 . 000000
0.000000
0.000000
0 . 000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000 j
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000 j
0.000000
o.oooooo •
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
Figure D-19
Portion of listing of joint frequency distribution for use with
the CDM16 dispersion model.
D-22
-------
METEOROLOGICAL PROCESSOR FOR REGULATORY MODELS (MPRM), VERSION 1.2
TODAY'S DATE AND TIME: 28-APR-88 AT 15:23:37
PROCESSING OF MERGED METEOROLOGICAL DATA
METEOROLOGICAL JOINT FREQUENCY FUNCTION
STABILITY CATEGORY, DN
WIND DIRECTION
355-005
005-015
015-025
025-035
035-045
045-055
055-065
065-075
075-085
085-095
095-105
105-115
115-125
125-135
135-145
145-155
155-165
165-175
175-185
185-195
195-205
205-215
215-225
i 225-235
! 235-245
245-255
255-265
265-275
275-285 •
285-295
295-305
305-315
315-325
325-335
335-345
345-355
SECTOR
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
1 ,
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
o.oobooo
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
2
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
WIND SPEED CLASS
3
0.000000
0.000000
0.000000
0.010526
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.010526
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
4
0.000000
0.000000
0.000000
0.010526
0.031579
0.021053
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.031579
0.073684
0.073684
0.031579
0.000000
0.000000
0.000000
0.010526
0.000000
0.021053
0.000000
0.000000
0.000000
0.000000
0.000000 .
0.000000
5
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.010526
0.000000
0.000000
o.dooooo
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.010526
0.063158
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.010526
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
6
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000 i
0.000000 i
0.000000
0.000000
0.000000
o.oooooo
0.000000
0.000000 I
0.000000 j
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0/000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000 j
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
Figure D-20
Portion of listing of joint frequency distribution for use with
the CDM36 dispersion model.
D-23
-------
METEOROLOGICAL PROCESSOR FOR REGULATORY MODELS (MPRM), VERSION 1.2
TODAY'S DATE AND TIME: 18-APR-88 AT 07:56:39
PROCESSING OF MERGED METEOROLOGICAL DATA
64
64
64
64
64
64
64
64
s 64
64
64
i 64
! 64
1 64
64
i £4
64
64
! 64
64
64
64
64
64
64
64
! 64
64
64
64
64
i 64
! 64
t 64
64
64
64
64
64
1
1 1
1 2
1 3
1 4
1 5
1 6
1 7
1 8
1 9
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
2 1
2 2
2 3
2 4
2 5
2 6
2 7
2 8
2 9
210
211
212
213
214
215
31.
48.
44.
43.
33.
42.
55.
53.
7.
331.
344.
356.
343.
299.
292.
274.
261.
237.
224.
227.
210.
232.
210.
200.
206.
222.
222.
230.
216.
217.
219.
216.
220.
221.
235.
211.
209.
207.
200.
9.2
15.0
15.0
12.7
12.7
13.9
20.8
17.2
13.9
10.3
12.7
13.9
10.3
8.1
12.7
13.9
10.3
8.1
9.2
12.7
18.3
16.1
13.9
17.2
16.1
13.9
16.1
18.3
15.0
16.1
15.0
12.7
15.0
15.0
15.0
15.0
16.1
16.1
15.0
511.
483.
456.
429.
401.
374.
347.
319.
292.
264.
237.
210.
182.
155.
155.
155.
155.
168.
189.
210.
231.
252.
272.
293.
314.
335.
355.
376.
397.
418.
438.
459.
480.
501.
522.
542.
563.
584.
584.
4.
4.
4.
4.
4.
4.
4.
4.
4.
4.
4.
4.
4.
4.
4.
4.
4.
5.
5.
4.
4.
4.
4.
4.
4.
4.
4.
4.
4.
4.
4.
4.
4.
4.
4.
4.
4.
4.
4.
23.0
21.9
23.0
23.0
24.1
24.1
26.1
26.1
25.0
24.1
26.1
27.0
27.0
28.9
28.9
28.9
28.0 •
21.9
21.9
21.9
24.1
25.0
23.0
24.1
24.1
23.0
23.0
23.0
23.0
23.0
23.0
21.9
23.0
26.1
28.9
33.1
35.1
37.0
39.9
Figure D-21
Portion of listing of meteorological data for use with the
RTDM dispersion model.
D-24
-------
METEOROLOGICAL
TODAY
PROCESSOR FOR REGULATORY MODELS XMPRM), VERSION 1.2 j
'S DATE AND TIME: 18-APR-88 AT 07:58:02
PROCESSING OF
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
64
! 64
! 64
64
64.
64
64
64
64
64
64
64
64
1 1
1 2
1 3
1 4
1 5
1 6
1 7
1 8
1 9
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
2 1
2 2
2 3
2 4
2 5
2 6
2 7
2 8
2 9
210
211
212
213
214
215
216
217
218
219
220
221
222
223
4.
6.
6.
5.
5.
6.
9.
7.
6.
4.
5.
6.
4.
3.
5.
6.
4.
3.
4.
5.
8.
1
7
7
7
7
2
3
7
2
6
7
2
6
6
7
2
6
6
1
7
2
7.2
6.2
7.7
7.2
6.2
7.2
8.2
6
7
6
7
2
7
5.7
6.7
6
6
6
7
.7
.7
7.2
7
6
7
8
6
6
6
8
9
9
.2
.7
.2
.2
.2
.7
.2
.8
.3
.8
31.
48.
44.
43.
33.
42.
55.
53.
7.
331.
344.
356.
343.
299.
292.
274.
261.
237.
224.
227.
210.
232.
210.
200.
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
206.0
222
222
230
0
0
0
216.0
217.0
219.0
216.0
220
221
235
211
209
0
0
0
0
0
207.0
200
204
198
201
202
205
214
215
217
0
.0
.0
.0
.0
.0
.0
.0
.0
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
5
5
4
4
4
4
4
'4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
1000.
1000.
1000.
1000.
1000.
1000.
1000.
1000.
1000.
1000.
1000.
1000.
1000.
1000.
1000.
1000.
1000.
1000.
1000.
MERGED
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1000.0
1000.0
1000
0
1000.0
1000
1000
0
0
1000.0
1000.0
1000.0
1000
1000
1000
0
0
0
1000.0
1000
0
1000.0
1000
1000
1000
1000
1000
1000
1000
1000
1000
1000
1000
1000
1000
.0
.0
.0
.0
.0
.0
.0
.0
.0
.0
.0
.0
.0
0.
0.
0.
0.
0.
0.
0.
0.
0.
METEOROLOGICAL DATA
0
0
0
0
0
0
0
0
0
0.0 |
0.0 I
0.0
0
0
0
0
0 . j
o !
0 - i
0
0.0
0.0
0.0
0.0
0.0
0
0
0
0
0.0
1
o.o . !
0
0
0
0
.0
.0
.0
.0 !
0.0 j
o.o !
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
.0 !
.0
.0
.0
.0 i
.0 • •!
.0 i
.0
.0
.0 ' •
.0
.0
.0
.0'
.0
.0
Figure D-22
Portion of listing of meteorological data for use with the
CALINE-3 dispersion model.
D-25
-------
-------
APPENDIX E
SUMMARY OF ERROR AND WARNING MESSAGES
During processing of the input images and the data, the processor writes messages to
the error/message file defined in the JB ERR input image (see Appendix B for a description
of this image). Five types of messages can be generated:
• An error that stops the processor from completing the original request for data
processing; considered a fatal error
• An error that may not stop processing
• Status of the processing
• Quality assessment violation
• A computation could not be performed during Stage 3 processing AND the trace
option is on.
A message from the processor has the form:
N PP a-|a2a3 SSSSSS: message
More detailed description of the message
code (up to 40 characters)
Subroutine from which the message is generated
Alphanumeric message code
— Pathway ID (JB, UA, SF, OS, MR, HP)
Counter
The message code is composed of two parts - a leading alphabetic character and a trailing
2-digit code. The alphabetic character (a: above) can be:
E fatal error; if the error occurs during processing of input images, the remainder of the
unages are processed to locate other possible problems with the images; if the error
occurs during processing of data on a pathway, processing ceases on that pathway and
the next step defined by the input images begins
W warning; further data processing may or may not be prohibited depending on the
processing requested through the input images;
E-l
-------
I information on the status of the processing - these messages monitor the progress of a
processor run;
Q quality assessment violation - a value for a variable was outside the interval defined
by the upper and lower bounds;
T an hourly computation could not be performed during Stage 3 processing AND the
hourly trace key was turned on using the input image MP TRA.
The 2-digit codes (a^ in the message code) are grouped into general categories
corresponding to the processing in Stages 1, 2, and 3. These categories are
00-19 Input image processing
20-29 File header and library processing
30-39 Upper air soundings and mixing heights processing
40-49 Surface observations processing
50-59 On-site observations processing
60-69 Merge processing
70-79 Stage 3 processing
** program trap - there is an error in program logic; the processor stops
immediately
Within the general categories are codes pertaining to processing in MPRM. These
codes are more specific than the general categories but do not completely specify the reason
for the message. That is left to the 40-character message. The codes are summarized by
pathway and severity and category at the end of each processor run in a table that is written
to the file defined by the JB OUT input image or, if this image is omitted, the default output
device. The MPRM processor uses device number (logical unit) 6 for this purpose.
Input Image Errors and Messages: 00 - 19
If an error is detected on an input image, a message is written to the message file and
any attempt to process data is prohibited. If a warning occurs, data may or may not be
processed, depending on the processing requkements specified within the run stream input
data. For example, a warning with a message code of W12 is written if there is no IQA
image on a pathway. If it is detected that the user wants to extract data, processing will be
halted as there is not output file (defined by use of the IQA input) for the extracted data.
EOO A keyword field is blank
E01 Repeated keyword/Improper keyword
E02 Error reading an input image
E-2
-------
EOS Error decoding a field on an input image
E04 Incomplete or superfluous information on an input image
EOS Error in a field - a keyword could not be determined
E06 A value or character is not within bounds or is unreasonable; improper
information specified in a field; no match with allowable names (see also code
W06 below)
EOT Error opening a tape or file; file not open; the file name was specified for
more than one device (logical unit) number
E10 Fatal write error to the temporary file
Ell Pathway status (status = -1) does not allow further processing
E12 Unable to proceed; previous errors on a pathway card (from subroutine
COMPLETE)
E13 The on-site data map and formats were not specified
E14 An attempt was made to change a previously established value for Stage 3
processing
WOO A blank image was encountered in the input images
W06 Value on an input card image may not be reasonable (see also code E06
above)
W10 Non-fatal write error writing to the temporary file
W12 Missing/errors on an input image - may or may not be fatal depending on the
processing requested
W15 Audit disabled for the on-site variable specified
110 No extraction on the pathway specified
111 No quality assessment on the pathway specified
112 No file on the pathway specified to merge
E-3
-------
119 End-of-file or IB END card encountered
File Header and Library .Errors and Messages: 20-29
Any messages that pertain to writing file headers during the initial processing or
messages issued by the library routines (those routines accessed by more than one subroutine)
are in this category.
E20 Header read error
E21 Header write error
E22 From subroutine FLHEAD: there were errors on the input file, so there are no
data to process
E23 From subroutine FLHEAD: error reading the headers placed in the output file
by input image processing
E24 From subroutines CHROND or ICHRND: The E24 error indicates a problem
in computing the chronological day. The data filename as specified in the
input image may be incorrect; as a result, MPRM is attempting to read the
wrong file. Also, extraneous data may be imbedded in the file. For example,
header and/or footer records are sometimes included to document data files;
such header/footer records may need to be removed prior to processing.
W22 From subroutine FLHEAD: An end-of-file was encountered reading the
headers on an input file, there is no processing of data from this pathway
123 From subroutine FLHEAD: an end-of-file reading the headers from the output
file - a correct condition
Upper Air Processing Errors and Messages: 30 - 39
Any messages that pertain to the upper air pathway, and issued after the input images
are processed, are in this category.
E32 There is an error reading or decoding the data and the count now exceeds the
maximum number of errors allowed
E35 Data blocking type specified incorrectly - allowable specifications are VB
(variable block) and FB (fixed block)
E-4
-------
E36 Error reading the file headers during Duality assessment - no data processed
W32 There is an error reading or decoding the data and the count is less than the
maximum number allowed - processing continues
W33 Sounding surface height is less than zero; the height is set to zero
W38 No soundings or mixing heights were retrieved because there was no match
found in the data with the station ID specified in the run stream input.
BO A message indicating that the point has been reached where processing of the
UA-data can begin
131 Automatic data modification for upper air soundings is enabled (see section 6
for a discussion of these modifications)
132 No data were extracted; a report of the tape/file contents is written to the
error/message file
137 A mixing height quality assessment lower bound violation; this message code
is written for the second and subsequent encounters of the mixing heights
within a day
D8 A mixing height quality assessment upper bound violation; this message code
is written for the second and subsequent encounters of the mixing heights
within a day
D9 An end-of-file was encountered on the input file in the expected position in the
file
Q34 The vertical gradients cannot be computed at one or more heights because one
or more heights are missing
Q35 The sounding height is not in any of the height intervals defined for the upper
air audit; the processor STOPS immediately and the last message in the
message file will identify the location of the problem; neither a summary table
nor an audit table is generated
Q36 From subroutine HTCALC: the heights have not been recomputed due to
missing data
Q37 A lower bound quality assessment violation
E-5
-------
Q38 An upper bound quality assessment violation
Surface Processing Errors and Messages: 40 - 49
Any messages that pertain to the surface pathway, and issued after the input images
are processed, are in this category.
E42 There is an error reading or decoding the data and the count now exceeds the
maximum number of errors allowed
E46 Error reading the file headers during quality assessment - no data processed
W42 There is an error reading or decoding the data and the count is less than the
maximum number allowed - processing continues
W43 Possible error decoding an over-punch character. The W43 error flag may
sometimes occur when MPRM attempts to decode a cloud type field (e.g.,
column 58 in a CD-144 file); valid cloud type codes are 'K', 'M\ 'N', 'O\
and 'R'. In such cases, there is no error - the W43 warning may be
disregarded.
\V48 No surface observations were retrieved because there was no match found in
the data with the station ID specified in the run stream input.
140 A message indicating that the point has been reached that processing of the
SF-data can begin
148 No data were extracted; a report of the tape/file contents is written to the
error/message file
149 An end-of-file was encountered on the input file in the expected position in the
file
Q47 A lower bound quality assessment violation
Q48 An upper bound quality assessment violation
On-site Processing Errors and Messages: 50 - 59
Any messages that pertain to the on-site pathway, and issued after the input images
are processed, are in this category.
E-6
-------
E50 There is an error reading an input file header
E51 There is an error writing an input file header to the output file
E52 There is an error reading or decoding the data and the count now exceeds the
maximum number of errors allowed
E53 There is an error writing data to the output file
E54 The observations are not sequential in time
£55 The number of observations exceeds the number expected for the hour, defined
as 1 (default) or on the input image OS AVG (note maximum of 12 allowed)
E56 An end-of-file on the input data was encountered before one complete
observation was read
W52 There is an error reading the data and the count is less than the maximum
number allowed - processing continues
157 An intra-hour observation violated a quality assessment lower bound
158 An intra-hour observation violated a quality assessment upper bound
159 An end-of-file was encountered on the input file in the expected position in the
file •
Q57 Lower bound quality assessment violation
Q58 Upper bound quality assessment violation
Merge Errors and Messages: 60-69
Any messages pertaining to combining the three data types (merge), and issued after
the input images are processed, are in this category.
E60 There is an error computing the chronological day from Julian day and year
E61 There is an error computing the Julian day and year from the chronological
day
E62 There is an error reading the upper air data
E-7
-------
E63 There is an error reading the surface data
E64 There is an error reading the on-site data
E65 There is an error writing the on-site data to the output file
E66 There is an error processing an input file's header cards
E67 No chronological days for merging were computed
167 The beginning chronological day is computed from the earliest available date
on the three pathways; the ending chronological day = beginning day + 367.
This message is generated if no MR EXT input is defined.
Stage 3 Errors and Messages: 70-79
Any messages that pertain to Stage 3 processing, and issued after the input images are
processed, are in this category.
E70 The preliminary processing (such as the latitude and longitude) has produced
an error; the input file has no data; the 40-character message further identifies
the source of the error
E71 There is an error reading the input data; the data are not a 1 - 24 hour clock;
the hour for on-site data is represented by the missing value indicator
W70 During preliminary processing, a value does not appear correct (e.g.. the
GMT to LST conversion factor); hour 23 data have been swapped in for hour
24 data for the surface pathway
W72 The mixing heights were not computed for the specified number of hours
\V73 The temperatures cannot be determined for the specified number of hours
\V74 The winds cannot be determined for the specified number of hours
\V75 The stability categories cannot be determined for the specified number of hours
W76 The surface roughness length cannot be determined for the number of hours
specified
170 End of header group reached on input file
E-8
-------
171 Station location for pathway changed from characters to 0 (zero) to conform to
RAMMET output specifications
175 Missing data has resulted in use of an alternate estimation scheme for stability,
the alternate scheme is reported in message
179 The end of the processing window, defined by the JB EXT image, was
encountered or, if no window was specified, the end-of-file was encountered
Trace Image Messages T72 - T76
The following are written only if the JB TRA image is present for Stage 3 processing
T72 The mixing height cannot be computed for the specified hour
T73 The temperature cannot be determined for the specified hour
T74 The winds cannot be determined for the specified hour
T75 The stability category cannot be computed for the specified hour and
methodology
T76 The surface roughness length cannot be determined for the specified hour
E-9
-------
-------
APPENDIX F
FORMATS OF DATA FILES
This appendix describes the formats of: 1) unprocessed (raw) meteorological data
files; 2) intermediate quality assured data files; and 3) processed data files for use in
dispersion modeling.
Unprocessed (Raw) Data FUes
The unprocessed data files include the following:
TD-5600 Unprocessed upper air data (NCDC Tape Deck)
TD-9689 NCDC estimated mixing heights (NCDC Tape Deck)
NCDC estimated mixing heights (SCRAM disk file)
CD-144 NWS surface data (80 column format)
SCRAM NWS surface data (compressed format)
SAMSON NWS surface data
TD-3240 NWS hourly precipitation data
F-l
-------
Table F-l
Tape Deck TD-5600 Format
Tape Positions
Variable
01-04
OS-OS
09-12
13-17
18-19
20-21
22-23
24-25
26-27
28-33
34-38
39-43
44-46
47-49
50-52
53-55
56-57
58
01-04
05-09
10-11
12-13
14-15
16-17
18-19
20-25
26-30
31-35
36-38
39-41
42-44
45-47
48-49
50
Element
Block Length
Observation Length
Deck Number
Station Number
Year
Month
Day
Hour
Number of Levels
Blank or ship position
Pressure
Height
Temperature
Relative Humidity
Wind Direction
Wind Speed
Blank
Level Type Indicator
Description
Number of bytes in this physical record - in binary. This occurs
once each block
Number of bytes in this logical record - in binary. This field
occurs at the beginning of each observation.
Unique for each type or source of data.
WBAN number or ship number
78 = 1978 etc.
01 = Jan., ... 12 = Dec.
Day of month: 01- 31
GMT: 01- 23
Number of 25 character levels contained in this observation.
Blank for land stations.
Pressure in millibars and tenths.
Height of the level, above sea level, in geopotential meters.
Signed plus = HOT above sea level
"Signed minus = HOT below sea level
Temperature of the level in degrees Celsius and tenths.
Signed plus = Positive temperature
"Signed minus = Negative temperature
Relative humidity of the level in whole percent.
Signed plus = Actual RH
"Signed minus = Estimated RH
Wind direction of the level in whole degrees
Wind speed of the level in meters per second.
Blank = blank
1 = Surface
2 = First Tropopause level
4 = Mandatory or significant level
8 = Generated level
0 = All others
Each data level is 25 bytes. Missing data fields are coded as all 9's (with signed fields being signed minus in recent years). The first
level is always the surface. All other levels then follow in decreasing pressure (ascending height).
Variable - Observations are packed as many as possible into variable length blocks that do not exceed 6000 bytes.
Standard - Format allows for up to 79 levels, including the surface of 25 positions each. Blanks are filled in following the
last reported level making each observation 200 character positions in length.
If observations contain more than 79 levels, the observation should continue in the next record and the number of
levels (tape position 18-19) would be coded 90-99, i.e., 90 and 91 = level 80 and 81 . etc.
Right most position of these fields may contain the characters A-I - Positive 1 through 9 and J-R = Negative 1 through 9.
A positive or negative 0 in this position may appear as a special character or a non-printable character.
F-2
-------
Table F-2
Tape Deck TD-9689 Format
Column
1-5
6-7
8-9
10-11
12
13
14-17
18-21
22-25
30
32-35
36-39
40-43
Element
NWS Station ID
Year
Month
Day of month
AM precipitation type:
1 = none
2 =
O __.
4 = missing
blank
AM mixing height (meters)
Average wind speed through
(m/s)
mixing depth
Surface wind speed (m/s)
PM precipitation type
PM mixing height (meters)
Average wind speed through
(m/s)
mixing depth
Surface wind speed (m/s)
F-3
-------
Table F-3
SCRAM Mixing Height Format
Column
1-5
6-7
8-9
10-11
14-17
32-35
Element
NWS Station ID
Year
Month
Day of month
AM mixing height (meters)
PM mixing height (meters)
F-4
-------
Table F-4
Card Deck CD-144 Format
Column
1-5
6-7
8-9
10-11
12-13
14-16
24-29
24
25-26
27-29
32-35
39-40
41-42
43-46
47-49
53-55
56
79
Element
NWS Station ID
Year
Month
Day of month
Hour (00 to 23)
Ceiling height (hundreds of feet)
Present weather
Thunder storms
Liquid precipitation
Frozen precipitation
Sea level pressure (mb and tenths)
Wind direction (tens of degrees)
Wind speed (knots)
Station Pressure (hundredths of inches)
Dry bulb temperature (degrees F)
Relative humidity (percent)
Total cloud cover (tenths)
Total opaque cloud cover (tenths)
F-5
-------
Table F-5
SCRAM Surface Format
Column
Element
1-5
NWS Station ID
6-7
Year
8-9
Month
10-11
Day of month
12-13
Hour (00 to 23)
14-16
Ceiling height (hundreds of feet)
17-18
Wind direction (tens of degrees)
19-21
Wind speed (knots)
22-24
Dry bulb temperature (degrees F)
25-26
Total cloud cover (tenths)
27-28
Total opaque cloud cover (tenths)
F-6
-------
SAMSON Data
SAMSON data consist of hourly surface observations archived on the Solar and
Meteorological Surface Observation Network (SAMSON) CD-ROM. These data are
available for 'first order' stations for the 30-year period 1961-1990; the data reside on a set
of three CD-ROMs.
In order to use the SAMSON data (MPRM does not access the SAMSON data
directly) one runs the extraction software provided with the CD-ROM. The SAMSON
software is DOS-based with an interactive user-friendly graphical interface. Output is written
to an ASCII file. If directed by the user, multiple years of data can be extracted and saved
to a file. However, one needs to be aware that MPRM does not expect multiple years of
data. If more than one year of data is provided to MPRM, an error is reported and
processing is terminated.
Retrieving data from the CD-ROM is completely under the control of the user. The
user specifies which variables to retrieve from a list of 21 variables stored for each station.
To be compatible with the data in the meteorological files on SCRAM, the ceiling height,
wind direction, wind speed, dry bulb temperature and opaque cloud cover should be
retrieved. These variables are sufficient for most of the models that MPRM supports, and
results in an ASCH file of about 400 Kb for one year of meteorological data. If dry and/or
wet deposition estimates are to be made, then several additional variables are needed. These
are: station pressure for dry deposition (resulting in a file size of about 445 Kb), and present
weather and hourly precipitation for wet deposition (resulting in a file size of about 537 Kb).
If all 21 variables are retrieved, then a file size of about 1.2 Mb is created. When
precipitation data are retrieved, the size will vary because precipitation amount is the last
field and is filled only if there was precipitation for the hour, making some records longer
than others.
When the data are retrieved from the CD-ROM, two records are written at the
beginning of the file that identify the station (first record) and the variables retrieved (second
record). MPRM processes both of these records to obtain information about the station
(e.g., latitude and longitude) and to determine how to process the data that follow. It is
imperative that the user not alter or delete these records. The two initial records, or
headers, begin with the tilde character (~). If more than one year of data are retrieved from
the CD-ROM, then two records beginning with the tilde appear before each year in the file.
When the second set of headers is encountered, MPRM will print a warning in the message
file and terminate normally. MPRM expects an integer value (the year), but encounters a
character value (the tilde), causing the error. However, the output for the first year will be
complete and intact. It is recommended that the user restrict data retrieved from CD-ROM to
one station and one year per file.
The header records are followed by the data records (one record per hour). Note that
SAMSON uses a 01 - 24 hour clock for labeling records. Thus, unlike the CD-144 format
F-7
-------
which uses a 00 - 23 clock, there is no need to adjust time labels at the beginning/end of the
day.
Data stored in the SAMSON format are in different units than the units in the CD-144
data, which are the units as recorded by the National Weather Service. MPRM converts the
SAMSON data to the units of the CD-144 data as part of the data processing.
The first record in the file retrieved from a SAMSON CD-ROM is a header record
providing the station name, location, etc. The format of this record is provided in Table
F-6.
The second record contains the list of variables (by position number) that appear in
the data file. Each variable is represented by a position number. This position number
always corresponds to that variable, no matter how many or how few variables are retrieved.
There is no particular format; the variable number appears above the column of data it
represents with at least one space (and usually many more) between the position numbers.
The third and subsequent records contain the weather elements retrieved from the
SAMSON CD-ROMs. The data are free format, i.e., there is at least one space between
each element in the record. The year, month, day, hour and observation indicator always
appear on each record. These are followed by the variables retrieved by the user. If all the
variables were retrieved, they would appear in the order shown hi Table F-7.
An online help feature is provided with the SAMSON CD-ROM data base. The
online help provides additional information on the variables, such as missing value
indicators, etc.
F-8
-------
Table F-6
Contents of the First Header Record in a SAMSON File
Field
01
02
03
04
05
06
07
08
Description
— to indicate a header record
WBAN station number identifier
City where station is located
State where station is located
The number of hours by which the local standard
time lags or leads Universal Time.
Station latitude
N = north, S = south
Degrees
Minutes
Station longitude
W = west, E = east
Degrees
Minutes
Elevation of the station in meters above sea level
Columns
001
002-006
008-029
031-032
033-036
039
040-041
043-044
047
048-050
052-053
056-059
F-9
-------
Table F-7
Order of Variables in a SAMSON File
Variable #
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
Description
Year, month, day, hour (LST), indicator
Extraterrestrial horizontal radiation
Extraterrestrial direct normal radiation
Global horizontal radiation
Direct normal radiation
Diffuse horizontal radiation
Total cloud cover
Opaque cloud cover
Dry bulb temperature
Dew point temperature
Relative humidity
Station pressure
Wind direction
Wind speed
Visibility
Ceiling height
Present weather
Precipitable water
Broadband aerosol optical depth
Snow depth
Days since last snowfall
Hourly precipitation
(may include a flag)
Units
Wm"2
WnT2
WnT2
WnT2
WnT2
tenths
tenths
°C
°C
percent
millibars
degrees
m s"1
kilometers
meters
—
millimeters
—
centimeters
--
inches and hundredths
F-10
-------
TD-3240 Precipitation Data
The TD-3240 precipitation data file is needed for wet deposition modeling if one is
obtaining surface data from a CD-144 file. The precipitation type is obtained from the
present weather fields in the hourly surface observation file (CD-144 or SAMSON) and Stage
3 converts the code to a precipitation code that ISCST can interpret. The precipitation rate is
obtained from the TD-3240 file. The TD-3240 data can also be used to supplement the
SAMSON precipitation data in the event there are little or no precipitation data for a station
(there are about 20 such stations which are noted in the SAMSON online help), or if
precipitation was not retrieved from the CD-ROM.
MPRM processes two precipitation formats: TD3240VB and TD3240FB. These
formats identify the TD-3240 precipitation data as either variable (VB) or fixed (FB) length
blocks, respectively. Precipitation data in a variable-length format are stored for an entire
day on one record, and only for those hours during which precipitation was reported. A
fixed-length format is also available in which one record contains the precipitation amount
for one hour. As with variable-length files, data are reported only for those days and hours
for which precipitation occurred. For variable-length formats, the preprocessor converts the
data to a fixed-length format, writes the result to a scratch file and uses the scratch file for
processing. The scratch file is deleted at the end of the run. Precipitation is reported in
inches and hundredths of an inch in the TD-3240 format. These units are converted to
millimeters for use in the ISCST dispersion model. The format of the precipitation data for
variable-length blocks is shown in Table F-8. The Station-id is a unique identifier assigned
by NCDC and is a concatenation of a state code (the first two digits) ranging from 01 to 48,
and 66, 67, and 91, and a cooperative network index (the last 4 digits) ranging from 0001 to
9999. It is not the WBAN number used to identify a station in the CD-144, SCRAM and
SAMSON formats.
Data groups in the same form as fields 009-012 are repeated as many times as
necessary such that the hours for which precipitation occurred for one day appear on one
record. The remaining data would begin hi field 013 and extend through field 104 if
precipitation occurred for all hours of the day. The final four fields on each record consists
of the accumulated amount, including zero precipitation, for the day.
Fixed-length blocks contain a stations's precipitation record for one hour on a
physical record. The structure is identical to the variable-length blocks, except that only one
hour of data appears on the record; i.e., fields 001 through 012. The final record for each
day consists of the accumulation record.
The National Climatic Data Center publication TD-3240 Hourly Precipitation (NCDC,
1990) contains a complete discussion of the format, definitions and remarks for each of the
fields presented above, including special flags that appear in field Oil. The conversion
between precipitation type and intensity and precipitation code is given in Table 4-9.
F-ll
-------
Table F-8
Format of Variable-Length TD-3240 Precipitation Data Record
Field
01
02
03
04
05
06
07
08
09
10
11
12
Description
Record type
Station identifier
Meteorological element type
Measurement units
Year
Month
Day (right justified, zero filled)
Number of data groups to follow
Hour (left justified, zero filled)
Value of meteorological element
Measurement flag #1
Quality flag #2 (not used, blank)
Columns
001-003
004-011
012-015
016-017
018-021
022-023
024-027
028-030
031-034
035-040
041
042
F-12
-------
Table F-9
Conversion of Reported Precipitation Type/Intensity to Precipitation Code
Precipitation Code
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Type
Rain
Rain
Rain
Rain Showers
Rain Showers
Rain Showers
Freezing Rain
Freezing Rain
Freezing Rain
(not used)
(not used)
(not used)
Drizzle
Drizzle
Drizzle
Freezing Drizzle
Freezing Drizzle
Freezing Drizzle
Snow
Snow
Snow
Snow Pellets
Snow Pellets
Snow Pellets
Intensity
Light
Moderate
Heavy
Light
Moderate
Heavy
Light
Moderate
Heavy
-
-
-
Light
Moderate
Heavy
Light
Moderate
Heavy
Light
Moderate
Heavy
Light
Moderate
Heavy
F-13
-------
25
26
27 '
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
(not used)
Ice Crystals
(not used)
Snow Showers
Snow Showers
Snow Showers
(not used)
(not used)
(not used)
Snow Grains
Snow Grains
Snow Grains
Ice Pellets
Ice Pellets
Ice Pellets
(not used)
Hail
(not used)
(not used)
Small Hail
(not used)
-
*
-
Light
Moderate
Heavy
-
-
-
Light
Moderate
Heavy
Light
Moderate
Heavy
-
*
-
-
*
-
* Intensity not reported for ice crystals, hail and small hail.
F-14
-------
Intermediate MPRM Data Files
The upper air and surface observations are written in a specific format after the data are
extracted. These formats .are retained until the data are merged in Stage 2. This discussion
does not apply to on-site data which are under the control of the user (i.e., the user specifies
the order and format for the data).
Upper Air Data
An extracted upper air data file is composed of two parts:
• A header record consisting of a year, month, day, hour group, the number of
sounding levels, and the morning and evening mixing heights. The format of the
header record is provided in Table F-10.
• Sounding data, if soundings were extracted, consisting of a pressure, height above
ground level, temperature, dew-point temperature, wind speed, and wind direction.
The format of this record is provided in Table F-l 1.
All values on the upper air pathway are written as integers. The 4-character names
used to identify the variables are listed in Appendix C along with the default parameters.
F-15
-------
Table F-10
Format of Header Record for Upper Air Data
Field
1
2
3
4
5
6
7
Element/Description
Year
Month
Day of month
Hour of the observation in Local Standard Time (LST).
Set to 12 if only mixing height data are extracted.
Number of sounding levels in this report (0 if no
soundings were extracted.
AM mixing height (meters)
PM mixing height (meters)
Format
12
12
12
12
15
15
15
Column(s)
2-3
4-5
6-7
8-9
10-14
16-20
22-26
Table F-ll
Format of Upper Air Data Records
Field
1
2
3
4
5
6
Element/Description
UAPR - Atmospheric Pressure (millibars)*
UAHT - Height above ground level (agl) (meters)
UATT - Dry bulb temperature (°C)*
UATD - Dew point temperature (°Q*
UAWD - Wind direction (tens of degrees from north)
UAWS - Wind speed (m/s)*
Format
15
15
15
15
15
15
Column(s)
2-6
8-12
14-18
20-24
26-30
32-36
Values are multiplied by 10 to retain one significant digit after the decimal point prior
to rounding the result to the nearest whole number.
F-16
-------
Surface Data
NWS surface data processed by MPRM are stored in two files: 1) a file defined
using the IQA keyword which contains the extracted data; and 2) a file defined by the OQA
keyword which contains the quality assured data. The two files are identical. Each hourly
surface observation processed by MPRM consists of two records formatted as shown in
Tables F-12a and F-12b. As with the upper air data, all values are reported as integers with
several variables being multiplied by 10 or 100 to retain significant digits; in addition,
several of the variables are two variables combined (concatenated) to form one integer value.
See Table C-l for a list of the variables and the applicable multipliers, etc.
Table F-12a
First Record of Stage 1 Output for the SF Pathway
Variable
Year (2-digits)
Month
Day
Hour
Altimeter pressure (mb)
Sea level pressure (mb)
Station pressure (mb)
Ceiling height (km)
Total//opaque sky cover (tenths)
2nd//3rd layer sky cover (tenths)
Layer 1 sky//coverage (tenths)
Layer 2 sky//coverage (tenths)
Layer 3 sky//coverage (tenths)
Layer 4 sky//coverage (tenths)
Format
12
12
12
12
15
15
15
15
15
15
15
15
15
15
Columns
02-03
04-05
06-07
08-09
11-15
17-21
23-27
29-33
35-39
41-45
47-51
53-57
59-63
65-69
F-17
-------
Table F-12b
Second Record of the Stage 1 output for the SF Pathway
Variable
Layer 1 cloud type//height (km)-
Layer 2 cloud type//height (km)
Layer 3 cloud type//height (km)
Layer 4 cloud type//height (km)
Present weather (2 types)
Horizontal visibility (km)
Dry bulb temperature (°C)
Wet bulb temperature (°C)
Dew point temperature (°C)
Relative humidity (percent)
Wind direction (degrees)
Wind speed (m/s)
Precipitation amount (mm)
Format
15
15
15
15
15
15
15
15
15
15
15
15
15
Columns
10-14
16-20
22-26
28-32
34-38
40-44
46-50
52-56
58-62
64-68
70-74
76-80
82-86
F-18
-------
All reports of sky conditions, cloud types and present weather are converted to the
TD-3280 numeric codes. These conversions are performed automatically as a part of the
extraction process on the SF-pathway. The codes used for reporting sky condition are given
in Table F-13. , • '
Table F-13
Sky Condition Codes
TD-3280 Code
00
01
02
03
04
05
06
07
08
09
CD-144 Code
0
1
2
4
5
7
8
X or -
blank
blank
Description and coverage
clear or less than 0. 1
thin scattered 0.1 to 0.5
scattered 0.1 to 0.5
thin broken 0.6 to 0.9
broken 0.6 to 0.9
thin overcast 1.0
overcast 1.0
obscuration 1.0
partial obscuration < 1.0
unknown
F-19
-------
The codes used for reporting obscuring phenomena and aloud type are given in Table
F-14. If no code is listed then there is no corresponding code in the CD-144 format.
Overpunch characters in the CD-144 format are represented by X/n where n is an integer.
An overpunch character as it appears in an ASCH file is also shown.
Table F-14
Obscuring Phenomena and Cloud Type Codes
Obscuring Phenomena
blowing spray
tmoko and haze
cniolco
haze
dust
blowing dust
blowing sand
blowing snow
ground fog
fog
ice fog
drizzle
rain
snow
ice crystals
other than fog
TD-3280
Code
01
03
04
05
06
07
30
36
44
45
48
SO
60
70
76
98
CD-144
Code
•
Xor-
Cloud Type
none
cumulus
towering cumulus
stratus fractus
stratus cumulus lenticular
stratus cumulus
stratus
cumulus fractus
cumulonimbus
cumulonimbus mammatus
altostratus
nimbostrats
altocumulus
altocumulus lenticular
altocumulus castellanus
altocumulus mammatus
cirrus
cirrocumulus lenticular
cirrostratus
cirrocumulus
TD-3280
Code
00
11
12
13
14
15
16
17
18
19
21
22
23
24
28
29
32
35
37
39
CD-144
Code
0
4
X/2orK
3
X/4 or M
5
X/5 or N
6
X/6 or 0
7
X/7 or P
8
9
X/9 or R
The code definitions for present weather conditions are given in Table F-15. Dashes
in a field indicate that there is no definition for that code. The 8-digit CD-144 format
weather conditions are converted to the 2-digit TD-3280 category.
F-20
-------
Table F-15
Present Weather Codes
Present Weather Description
TD-3280 Code
Thunderstorm - lighting and thunder
Severe thunderstorm - frequent intense lighting and thunder
Report of tornado or water spout
Light squall
Moderate squall
Heavy squall
Water spout
Funnel cloud
Tornado
Unknown
10
11
12
13
14
15
16
17
18
19
Light rain
Moderate rain
Heavy rain
Light rain showers
Moderate rain showers
Heavy rain showers
Light freezing rain
Moderate freezing rain
Heavy freezing rain
Unknown
20
21
22
23
24
25
26
27
28
29
Light rain squalls
Moderate rain squalls
Heavy rain squalls
Light drizzle
Moderate drizzle
Heavy drizzle
Light freezing drizzle
Moderate freezing drizzle
Heavy freezing drizzle
Unknown
30
31
32
33
34
35
36
37
38
39
F-21
-------
Light snow
Moderate snow
Heavy snow
Light snow pellets
Moderate snow pellets
Heavy snow pellets
Light snow crystals
Moderate snow crystals
Heavy snow crystals
Unknown
40
41
42
43
44
45
46
47
48
49
Light snow showers
Moderate snow showers
Heavy snow showers
Light snow squalls
Moderate snow squalls
Heavy snow squalls
Light snow grains
Moderate snow grains
Heavy snow grains
Unknown
50
51
52
53
54
55
56
57
58
59
Light ice pellet showers
Moderate ice pellet showers
Heavy ice pellet showers
Light hail
Moderate hail
Heavy hail
Light small hail
Moderate small hail
Heavy small hail
Unknown
60
61
62
63
64
65
66
67
68
69
F-22
-------
Fog
Ice fog
Ground Fog
Blowing dust
Blowing sand
Heavy fog
Glaze
Heavy ice fog
Heavy ground fog
Unknown
Smoke
Haze
Smoke and haze
Dust
Blowing snow
Blowing spray
Dust storm
__
— —
Unknown
Light ice pellets
Moderate ice pellets
Heavy ice pellets
—
—
—
—
—
—
Unknown
70
71
72
73
74
75
. 76
77
78
79
80
81
82
83
84
85
86
87
88
89
90 '
91
92
93
94
95
96
97
98
99
F-23
-------
Model Output Rles
ISCST
The meteorological input required to run ISCST depends on the application and
options employed. Basically, there are three options which determine the meteorological
variables needed to run the model. The modeling options available with ISCST include
concentration (with and without plume depletion), dry deposition, and wet deposition.
Minimum requirements, common to all options, are wind direction, wind speed, temperature,
stability class, and mixing height. The minimum requirements apply when one is modeling
concentration without deposition or plume depletion; the MPRM output format for this option
is described in Table F-17. Additional variables are needed if one is modeling dry
deposition and/or dry depletion; the MPRM output for dry deposition/depletion estimates is
described in Table F-18. Finally, precipitation data are needed if one is modeling wet
deposition and/or depletion; the MPRM output for wet deposition/depletion is described in
Table F-19. The data records for all three options are preceded by an identical header
record described in Table F-16.
F-24
-------
Table F-16
First Record of Output Files for ESCST, ISCSTDRY, and ISCSTWET
Field
01
02
03
04
Description
Surface Station Number
Surface Station Year
Mixing Height Station Number
Mixing Height Station Year
Format
16
16
16
16
Columns
01-06
08-13
15-20
22-27
Table F-17
Output File Format for ISCST
Field
01
02
03
04
05
06
07
08
09
10
Description
Year (2 digits)
Month
Day
Hour
Randomized flow vector
Wind speed (m/s)
Ambient temperature (kelvin)
Stability category
Rural mixing height (m)
Urban mixing height (m)
Format
12
12
12
12
F9.4
F9.4
F6.1
12
F7.1
F7.1
Columns
01-02
03-04
05-06
07-08
09-17
18-26
27-32
33-34
35-41
42-48
F-25
-------
Table F-18
Output Bile Format for ISCSTDRY
Field
01
02
03
04
05
06
07
08
09
10
11
12
13
Description
Year (2 digits)
Month
Day
Hour
Randomized flow vector
Wind speed (m/s)
Ambient temperature (kelvin)
Stability category
Rural mixing height (m)
Urban mixing height (m)
Surface friction velocity, application site
(m/s)
Monin-Obukhov length, application site
(m)
Surface roughness length, application
site (m)
Format
12
12
12
12
F9.4
F9.4
F6.1
12
F7.1
F7.1
F9.4
F10.1
F8.4
Columns
01-02
03-04
05-06
07-08
09-17
18-26
27-32
33-34
35-41
42-48
49-57
58-67
68-75
F-26
-------
Table F-19
Output Fue Format for ISCSTWET
Field
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
Description
Year (2 digits)
Month
Day
Hour
Randomized flow vector
Wind speed (m/s)
Ambient temperature (kelvin)
Stability category
Rural mixing height (m)
Urban mixing height (m)
Surface friction velocity, application site
(m/s)
Monin-Obukhov length, application site
(m)
Surface roughness length, application
site (m)
Precipitation code (0 for none, 1-18 for
liquid, 19 and above for frozen)
Precipitation amount (mm)
Format
12
12
12
12
F9.4
F9.4
F6.1
12
F7.1
F7.1
F9.4
F10.1
F8.4
14
F7.2
Columns
01-02
03-04
05-06
07-08
09-17
18-26
27-32
33-34
35-41
42-48
49-57
58-67
68-75
76-79
80-86
F-27
-------
BLP, COMPLEX1, RAM
This format accommodates several dispersion models: BLP, RAM, ISCST, and
COMPLEX!. The file contains two types of records, the first is a header record and the
second is the meteorological data. The second contains the data for one 24-hour period
(midnight to midnight) and is repeated until all data are listed. The data are written
unformatted to the file. The header and data records are described in Tables F-20 and F-21
respectively.
Table F-20
Header Record for the RAMMET Binary File
Field
Element/Description
5-digit NWS station identifier for surface data
2
Last 2 digits of beginning year for surface data
5-digit NWS station identifier for mixing height data
Last 2 digits of beginning year for mixing height data
Table F-21
Data Record for the RAMMET Binary File
Field
1
2
3
4
5
6
7
8
9
Element/Description
IYEAR - Last 2 digits of year
MONTH - Month (1-12)
DAY - Day of month (1-31)
PGSTAB - Array of P-G stability categories
SPEED - Array of wind speeds (m/s)
TEMP - Array of temperatures (K)
FLWVEC - Array of flow vectors (nearest 10 degrees)
RANFLW - Array of randomized flow vectors (nearest degree)
MTXHGT - Array of urban and rural mixing heights (m)
Missing
Value
0
-9
-99
-99
-99
-999
F-28
-------
CALINE-3
This format is specific to the CALINE-3 dispersion model. The file contains only
one type of formatted data record, one for each hour. The format for this record is
described in Table F-22.
Table F-22
CALINE-3 Output Format
Field
1
2
3
4
5
Element/Description
Wind speed (m/s)
Wind direction (nearest degree)
P-G stability category
Mixing height (m)
Background concentration
(ppm)
Format
F3.0
F4.0
11
F6.0
F4.0
Column(s)
1-3
4-7
8
9-14
15-18
Missing
Value
-9
-99
0
1000
0
F-29
-------
RTDM
This format is specific to the RTDM dispersion model (default). The file contains
only one type of formatted data record, one for each hour. The format of this record is
described in Table F-23.
Table F-23
RTDM Output Format
Field
1
2
3
4
5
6
7
8
Element/Description
Last 2 digits of year
Julian day of year
Hour in Local Standard Time (LST)
Wind direction (degrees)
Wind speed (miles/hr)
Mixing height (m)
P-G stability category
Temperature (°F)
Format
12
13
12
F6.0
F6.1
F6.0
F6.0
F6.1
Column(s)
1-2
3-5
6-7
9-14
15-20
21-27
28-33
34-39
Missing
Value
-999
-999
-999
-999
-999
The input variables listed above are the only ones allowed by current regulatory guidance.
The RTDM dispersion model provides for specification of other meteorological variables but
these require quite special meteorological observations, or at the very least an intimate
knowledge of the meteorological conditions appropriate to the dispersion problem to be
modeled.
VALLEY ISCLT CDM 2.0 (CDM16)
The input file describing the meteorological conditions for VALLEY, ISCLT, and the
CDM16 option in CDM 2.0 is in the form of a joint frequency distribution. The distribution
is constructed using 16 sectors, 6 wind speed classes, and 6 stability classes. The wind
speed classes are 0-3, 3-6, 6-10, 10-16, 16-21 and >21 kts.
F-30
-------
The stability categories for the CDM16 option of CDM 2.0 are:
P-G Class Category Description
1 A Very unstable
2 B Moderately unstable
3 C Sightly unstable
4 D daytime) Neutral (sunrise to sunset)
5 D (nighttime) Neutral (sunset to sunrise)
6 E-F Stable
The stability categories for the ISCLT and VALLEY dispersion models are:
P-G Class Category Description
1 A Very unstable
2 ' B Moderately unstable
3 C Sightly unstable
4 D Neutral
5 E Stable
6 F Very stable
The input files for these models are comprised of 96 records (i.e., one record for
each sector/stability combination). Each record contains the frequency data for six wind
speed classes. An example is presented in Figure D-19 in Appendix D.
CDM 2.0 (CDM36)
The input file describing the meteorological conditions for the CDM36 option of
CDM 2.0 is in the form of a joint frequency distribution. The distribution is constructed
using 36 sectors, 6 wind speed classes, and 6 stability classes. The wind speed classes are
0-3, 3-6, 6-10, 10-16, 16-21 and >21 kts.
The input file for the CDM36 option is comprised of 216 records (i.e., one record for
each sector/stability combination). Each record contains the frequency data for six wind
speed classes. An example is presented in Figure D-20 in Appendix D.
F-31
-------
-------
APPENDIX G
GLOSSARY
ABNORMAL JOB TERMINATION -- this statement, if found in the general report file,
indicates that an error condition was detected and further processing has been inhibited.
ASCII -- American Standard Code for Information Interchange.
ALT) Input -- an input image used to add variables to the default list of variables being
tracked on the UA, SF or OS pathway during quality assessment.
Audit Summary -- a written summary of the results for the variables tracked (audited)
during quality assessment.
Audit Variables -- variables that are tracked during quality assessment.
BBS - Bulletin Board System •
BLP -- Buoyant Line and Point source dispersion model (Appendix W to 40 CFR Part 51)
Bowen Ratio -- ratio of the upward flux of sensible heat to the energy flux used in
evaporation: a measure of the relative evaporative power of the atmosphere.
CALINE3 - A dispersion model used for estimating air concentrations near highways and
arterials - developed by the State of California (Appendix W to 40 CFR Part 51.
CD-144 Format -- Card Deck-144 data format available from NCDC for National Weather
Service surface observations commonly used for dispersion models. Each record represents
an 80-column "card image".
CDM 2.0 -- Climatological Dispersion Model (Appendix W to 40 CFR Part 51)
COMPLEXl — A multiple source complex terrain screening model for use in regulatory
modeling applications involving terrain above stack top (Appendix W to 40 CFR Part 51).
Conyective Mixing — mixing of atmospheric properties as a result of surface heating.
Dispersion Model - A group of related mathematical algorithms used to estimate (model)
the dispersion of pollutants in the atmosphere due to transport by the mean (average) wind
and small scale turbulence.
DOS -- Disk Operating System.
G-l
-------
EBCDIC -- Extended Binary Coded Decimal Interchange Code.
EOF -- End-of-File.
EPA — U. S. Environmental Protection Agency.
Error message -- a message written by the processor to the error/message file whenever an
error is encountered that will inhibit data processing.
Error/Message File -- a file used in all stages of processing for storage of messages written
by the processor.
Extracted Data File -- the file resulting from Stage 1 processing for storage of data retrieved
from a magnetic medium (disk or tape).
Extraction Process - the process of retrieving data from a magnetic medium.
Fatal Error -- any error which inhibits further data processing on a pathway or stops the
MPRM processor.
File Headers -- records written by the processor at the top of files during Stage 1 and Stage
2 processing. These records contain the input images from individual pathways in addition
to supplementary records tracking the history of the data set.
Flo^' Vector — The direction towards which the wind is blowing.
General Report File — a file written either to the default output device or a disk file
summarizing the processor results.
GMT -- Greenwich Mean Time, the time at the 0° meridian.
Harmonic Average Wind Speed -- [EO/ig/N]"1, where N is the total number of
observations and u, is the 1th wind speed observation. The harmonic average wind speed is
used by the CDM dispersion model in computing the effects of dilution.
Height Intervals ~ heights used for reporting the results of quality assessment of upper air
data (see also Interval Thickness).
Hypsometric Formula ~ a determination of the height difference between any two pressure
levels based on hydrostatic balance, which requires the mean virtual temperature of the layer.
Information(al) message -- any message written to the error/message file that reports the
status of the processing and further data processing is not affected.
G-2
-------
Initial Status Report -- the first page of the general report for Stage 1 and Stage 2
processing.
Input Command Structure -- the syntax and sequence of the input images.
Input Image - user supplied input, read through the default input device, controlling MPRM
data processing.
Interval Thickness — the height difference used in summarizing the quality assessment
results of upper air data (see also Height Interval).
IQA -- Input to Quality Assessment, an input image that defines the output file to receive
extracted data. This file also serves as the input file for the first pass through quality
assessment of the data.
ISCST -- Industrial Source Complex - Short Term dispersion model (Appendix W to 40 CFR
Part 51).
JB -- JoB: the 2-character code indicating that all fields on the input image pertain to the
overall operation of the processor.
JB Data - collective term for all input images that begin with the 2-character code JB.
JB Pathway -- collective term for logic associated with deciphering input images beginning
with the JB character code.
JCL — Job Control Language, an IBM mainframe's operating system control language for
batch jobs.
Joint Frequency Function — the joint frequency of wind direction sector, wind speed class
and stability category (see also STAR).
Kb -- kilobyte (1000 bytes)
Keyword -- the 3-character codes that follow immediately after the pathway ID in the input
run stream data.
Library Routines - a collection of subroutines that are called by two or more subroutines
and/or main program.
LST - Local Standard Time.
Math Co-processor — a computer chip used to speed up floating point arithmetic in a
personal computer.
G-3
-------
Mb -- megabyte (106 bytes)
Merged Data File ~ the file produced by Stage 2 processing consisting of available upper air
and mixing height data, surface observations and on-site data for a specified period of time.
Merge Processing -- the process by which data from the 3 pathways (UA, SF, OS) are
combined to produce a merged data file.
Meteorological Data File -- any file containing meteorological data, whether it be upper air
soundings, mixing heights, surface observations or on-site data, or any combination of these.
Missing Value -- alphanumeric character(s) that represent breaks in the temporal or spatial
record of an atmospheric variable.
Mixing Height -- the depth through which atmospheric pollutants are typically mixed by
dispersive processes.
Monthly Mean Value -- a one-month arithmetic average of a meteorological variable.
MPRM - Meteorological Processor for Regulatory Models, the software described in this
document.
MR - MeRge. the 2-character code indicating that all fields on the input image pertain to
combining of the data from the three pathways into a single unformatted file.
MR Data -- collective term for all input images that begin with the 2-character code MR.
MR Pathway -- collective term for logic associated with deciphering input images beginning
with the MR character code.
NCDC -- National Climatic Data Center, the federal agency responsible for distribution of
the National Weather Service upper air, mixing height and surface observation data.
NTIS - National Technical Information Services, the agency responsible for distribution of
technical information.
NWS -- National Weather Service.
OAQPS — Office of Air Quality Planning and Standards
OQA » Output from Quality Assessment, an input image that defines the output file to
receive data that have gone through quality assessment. This file is also used as the input
file for Stage 2 processing.
G-4
-------
On-site Data — data collected from a meteorological measurement program operated in the
vicinity of the site to be modeled in the dispersion analysis.
Opaque Sky Cover -- the amount of sky cover, expressed in tenths, that completely
obscures all that might be above it.
OS -- On-Site, the 2-character code indicating that all fields on the input image pertain to the
processing of on-site data
OS Data -- collective term for all input images that begin with the 2-character code OS, also
used to collectively refer to on-site data processed.
OS Pathway - collective term for logic associated with deciphering input images beginning
with the OS character code.
Overlay — one or more subprograms that reside on disk and are loaded into memory only
when needed.
Pasquill Stability Categories - a classification of the dispersive capacity of the atmosphere,
originally defined using surface wind speed, solar insolation (daytime) and cloudiness
(nighttime). They have since been reinterpreted using various other meteorological variables.
Pathway — one of the five major processing areas in MPRM. These are JB, OS, SF, UA,
and MR (see these entries in this section for a description).
PC — Personal Computer.
Processing Methodologies — options controlling Stage 3 processing.
Quality Assessment — judgment of the quality of the data.
Quality Assessment Check - determining if the reported value of a variable is reasonable
(see also Range Check).
Quality Assessment Message — message written to the error/message file when a data value
is determined to be suspect.
Quality Assessment Violation — occurrences when data values are determined to be suspect
(see also Range Check Violation).
RAM — (1) Random Access Memory on a personal computer.
(2) A multiple source dispersion model.
G-5
-------
RAMMET - Meteorological processor program used for regulatory applications capable of
processing twice-daily mixing heights (TD-9689 format) and hourly surface weather
observations (CD-144 format) for use in dispersion models (Appendix W to 40 CFR Part
51).
Range Check - determining if an observation of a variable falls within predefined upper and
lower bounds.
Range Check Switch -- parameter whose value indicates whether to include or exclude the
upper and lower bounds during range checks.
Range Check Violation - determination that the value of a variable is outside range defined
by upper and lower bound values (see also Quality Assessment Violation). .
Raw Data File - any file which has not been processed by MPRM
Regulatory Applications -- dispersion modeling involving regulatory decision-making as
described in Appendix W to 40 CFR Part 51.
Regulatory Model -- a dispersion model that has been approved for use by EPA (Appendix
W to 40 CFR Part 51).
Reporting Procedures - options available in Stage 3 processing for reporting the
availability of meteorological data for the selected dispersion model.
Roughness Length - see Surface Roughness Length
RTDM ~ Rough Terrain Dispersion Model. A multiple source complex terrain screening
model for use in regulatory1 modeling applications involving terrain above stack top
(Appendix W to 40 CFR Part 51).
Run Stream - collectively, all input images required to process data in MPRM.
-------
SF - SurFace, the 2-character code indicating that all fields on the input image pertain to the
processing of NWS hourly surface weather observations.
SF Data — collective term for all input images that begin with the 2-character code SF. also
used to collectively refer to NWS hourly surface weather observations.
SFC Input — keyword indicating on-site data supplied to the processor, consisting of surface
albedo. Bowen ratio, and surface roughness length as a function of wind direction and time
of year. This is an optional input.
SF Pathway — collective term for logic associated with deciphering input images beginning
with the SF character code.
SRDT -- Solar Radiation Delta-T; a method for estimating P-G stability using on-site
measurements of wind speed coupled with solar radiation during the day and vertical
temperature difference at night.
Stage 1 Processing — the process of extracting or retrieving meteorological data from raw
data files and subsequent quality assessment of the data, and all reports and files generated
during this process.
Stage 2 Processing — the process of combining or merging the three types of meteorological
data into an unformatted file, and all reports and files generated during this process.
Stage 3 Processing - the process of preparing meteorological data, processed in Stage 2, for
use by a dispersion model, and ajl reports and files generated during this process..
Standard Reporting Levels - mandatory pressure levels (and corresponding measured
atmospheric quantities) in a NWS upper air sounding.
STAR - (STability ARray) stability and wind rose summary, a joint frequency distribution
summary of stability category, wind speed and wind direction. The STAR data are used as
input for several long-term dispersion models such as CDM and ISCLT.
Station Identification — an integer or character string used to uniquely identify a station or
site as provided in the upper air (TD-5600 and TD-6201), mixing height (TD-9689), and
surface weather (CD-144 and TD-3280) data formats available from NCDC. There are no
standard station numbers for on-site data and the user may include any integer or character
string up to eight digits or characters.
Storage Formats — For magnetic tapes, the formats available from NCDC for storing upper
air and surface observations. See TD-1440, TD-3280, TD-5600, TD-6201, TD-9689 and
CD-144. For on-site data 'storage formats' refers to the format of the data on the input file.
G-7
-------
Subdirectory -- a director)' below the root, or highest level, directory or another
subdirectory', used for organization of files on a storage medium such as a PC hard disk.
Surface Albedo -- fractional amount of radiation incident on a surface that is reflected away
from the surface.
Surface Weather Observations -- a collection of atmospheric data on the state of the
atmosphere as observed from the earth's surface. In the U.S. the National Weather Service
collect these data on a regular basis at selected locations.
Surface Roughness Length -- height at which the wind speed extrapolated from a
near-surface wind speed profile becomes zero.
TD-1440 Format -- a format available from NCDC for summarizing NWS surface
Observations in an 80-column format; the CD-144 format is a subset of this formal. This
format has been superseded by the TD-3280 format.
TD-3280 Format - the current format available from NCDC for summarizing NWS surface
weather observations in an elemental structure, i.e., observations of a single atmospheric
variable are grouped together for a designated period of time.
TD-5600 Format -- a format available from NCDC for reporting NWS upper air sounding
data. This format has been superseded by the TD-6201 format.
TD-6201 Format -- the current format'available from NCDC for reporting NWS upper air
data. The file structure is essentially the same as the TD-5600 format except that there is
more quality assurance information.
TD-96S9 Format -- the format available from NCDC for mixing heights estimated from
morning upper air temperature and pressure data and hourly surface observations of
temperature.
Temperature lapse rate -- the fall of temperature per unit height, and is taken as positive
when temperature decreases with height.
TTN - Technology Transfer Network
Total Sky Cover -- the amount of sky, expressed in tenths, covered by a combination of
transparent and opaque clouds or obscuring phenomena.
Turbulence -- The irregular "eddy" motions in fluids, whether liquid or gaseous, which
cause an irreversible mixing of fluid properties between neighboring parcels.
G-8
-------
UA - Upper-Air, the 2-character code indicating that all fields on the input image pertain to
the processing of the twice-daily mixing height data and the upper air data.
UA Data ~ collective term for all input images that begin with the 2-character code UA,
also used to collectively refer to mixing height and upper air data processed.
UA Pathway - collective term for logic associated with deciphering input images beginning
with the UA character code.
Unformatted File ~ a file written without the use of a Fortran FORMAT statement.
Upper Air Data (or soundings) — meteorological data obtained from balloon-borne
instrumentation that provides information on pressure, temperature, humidity, and wind away
from the surface of the earth.
UTC ~ Universal Time Coordinate
VALLEY ~ a complex terrain dispersion model used as a first level screening model in
regulatory dispersion modeling (Appendix W to 40 CFR Part 51).
Warning Message - a message written by the processor to the error/message file whenever
a problem arises that may inhibit further data processing.
Wind Shear — the change in wind velocity with height.
G-9
-------
-------
TECHNICAL REPORT DATA
(Please read Instructions on reverse before completing)
1. REPORT NO.
EPA-454/B-96-002
3. RECIPIENTS ACCESSION NO.
4. TITLE AND SUBTITLE
5. REPORT DATE
Meteorological Processor for Regulatory Models (MPRM)
User's Guide
August 1996
6. PERFORMING ORGANIZATION CODE
7. AUTHOR{S)
Desmond T. Bailey
8. PERFORMING ORGANIZATION REPORT NO.
9. PERFORMING ORGANIZATION NAME AND ADDRESS
10. PROGRAM ELEMENT NO.
U.S. Environmental Protection Agency
Office of Air Quality Planning and Standards
Research Triangle Park, NC 27711
11. CONTRACT/GRANT NO.
12. SPONSORING AGENCY NAME AND ADDRESS
13. TYPE OF REPORT AND PERIOD COVERED
14. SPONSORING AGENCY CODE
15. SUPPLEMENTARY NOTES
16. ABSTRACT
The Meteorological Processor for Regulatory Models (MPRM) is a general purpose program used
to process meteorological data for use in EPA recommended air quality dispersion models. Capabilities
include quality assessment of meteorological data, detailed report generation, and the ability to process a
variety of meteorological data bases including both on-site (user collected) and National Weather Service
(NWS) meteorological data.
MPRM is comprised of three processing stages. Stage 1 (extraction and quality assessment)
retrieves meteorological data from various storage media provided by the user (e.g., magnetic tape,
floppy disk, and CD-ROM) and conducts the quality assessment of these data. The stage 1 report files
provide listings of missing, suspect, and invalid data. These reports provide necessary information
allowing users to correct problem data prior to its use in modeling. Stage 2 merges the corrected stage
1 data from the various MPRM pathways - upper air (UA), surface (SF) and on-site (OS). The third
and final stage performs the necessary processing to create a meteorological data file for use in a
dispersion model selected by the user. MPRM supports the following air quality dispersion modelos
which are recommended by EPA for use in regulatory applications (Appendix W to 40 CFR, Part 51):
BLP, CALINE-3, COM 2.0, COMPLEX1, ISCST, ISCLT, RAM, RTDM, and VALLEY.
KEY WORDS AND DOCUMENT ANALYSIS
DESCRIPTORS
b. IDENTIFIERS/OPEN ENDED TERMS
c. OOSAT1 FioU/Qronp
Air Pollution
Atmospheric Dispersion Modeling
Meteorological Processors
Meteorological Monitoring
18. DISTRIBUTION STATEMENT
19. SECURITY CLASS (Klfca)
Unclassified
21. NO. OF PAGES
200
Release Unlimited
20. SECURITY CLASS (Pegi)
Unclassified
EPA Form 2220-1 (Rev. 4-77) PREVIOUS EDITION IS OBSOLETE
-------
------- |