Notes on AER2CAL (v1.21)

Provisional AER2CAL to read NEW AERMOD(09292) output file with double-precision reals!
Concentrations are read as R*8 and then converted to R*4 using SNGL function.  If
initial read with R*8 fails, reads using R*4 are attempted.


Notes on AER2CAL (through v1.1)

AER2CAL uses an AERMOD control file to obtain information about how AERMOD
is run, passing this information into a CALPUFF unformatted data file for
each unformatted AERMOD concentration file.  The information currently
extracted includes:
	- Names of AERMOD unformatted concentration files
        - Species name
	- Period simulated
	- Receptor locations

1.  First generation translator does not fully interpret all variations
    in the AERMOD control file (check outcomes carefully!)

2.  Output type assumed to be in the AERMOD "postfile" is concentration.  If
    multiple output types (CONC, DEPOS, DDEP, WDEP) are created by AERMOD, 
    AER2CAL will not process any files because the order of the output types
    seems to be variable and no documentation is included in the postfile.

3.  AERMOD control file constraints

	a) Date-time range of application is ONLY read from the ME STARTEND
	   record.  AER2CAL expects this record to look like the standard
           or optional form:

	   ME STARTEND 1989 01 01 1989 01 02          (hours 1-24 assumed)
	   ME STARTEND 1989 01 01 01 1989 01 02 24    (hours explicit)

	   No other variations are allowed.  Furthermore, if the DAYRANGE
           is used (with or without STARTEND) AER2CAl will halt because this
           construct may be used to model only segments of the period and 
           CALPOST processing of the AER2CAL output file requires an unbroken
           period.
           CAUTION:  AERMOD runs for the intersection of time periods
           specified in the control file and time periods contained in the 
           meteorological files.  AER2CAL passes the control-file times to
           its output file, but the data records may not cover this period.

	b) Each POSTFILE must be unformatted, as controlled by the format
	   string UNFORM in the OU POSTFILE records.  The PLOT format is
	   not supported.

	c) AER2CAL requires that the POSTFILE data are 1-hour averages, and
	   will not process any other averaging times.

	d) Only DISCCART receptors should be in the AERMOD application.  The
	   receptor locations may be read from DISCCART records in the control
	   file, or from DISCCART records in an external receptor file that
	   is identified by the RE INCLUDED record in the AERMOD control file.

4.  No geo-reference data are available in the AERMOD files.  Default
    values for the map projection, datum, and time zone are placed in
    the CALPUFF data files.  These will frequently be incorrect for the
    receptor coordinates used by AERMOD, and should be disregarded in
    subsequent processing.

5.  The AERMOD version number is not available in the control file or the
    unformatted POSTFILE, so it is currently assigned by a data statement in
    AER2CAL to 00000.  For this reason, the version number should be
    disregarded in any subsequent processing.