The PTHOUR file may optionally contain a packet to control the range of dates for which Smkinven will read data. When this feature is needed, the following entry should appear on the first line of the PTHOUR file.

DATERANGE MMDD(start) MMDD(end)

where MMDD is the two-digit month and day of the month at the start and end of the period of interest. For example, to request July 10th through 12th, the first line of the file should read:

DATERANGE 0710 0712

The year is implied by the data themselves; note that the files can only contain data for a single year. As an alternative to using the DATERANGE packet, you can manually break the year up into smaller periods in separate files, and only list the files of interest in the PTHOUR file. Note that reading in the whole year of data and extracting just a few days will take much more time than manually editing the file to contain just the days of interest. Also note that if you choose the manual editing option, you must select days that fully cover the modeling episode after accounting for time zone differences between the facility’s time zone and the modeling time zone (set by the OUTZONE option).

SMOKE uses the CEM ORIS ID and Boiler ID fields to match sources in the CEM hour-specific inventory to those in the annual inventory. Note that the CEM data hours are in standard local time (no daylight saving time adjustment). The format of the CEM hour-specific data is shown in Table 6.22, “CEM Format for individual hour-specific data files”.

The code numbers used in columns 12 through 15 have the following meanings:

This FF10 format uses the header described in Section 6.2.1.4, “Header records”.

The user specifies the data provided using this command in the header: FF10_HOURLY_POINT.

Sample header records for hourly point sources are shown below:

#FORMAT=FF10_HOURLY_POINT
#COUNTRY  US
#YEAR     year of inventory, e.g. 2008
#DESC     Point Hourly Source Inventory
#DESC     FF10 Point Hourly format

For EMS-95 formatted data, SMOKE requires that the sources in the PTHOUR file also be in the PTINV file. The values of the fields that are common to the hour-specific data and the annual data need to match exactly. These fields are Facility ID, Stack ID, Device ID, and Process ID. These fields are treated as text fields (not numeric) in SMOKE, so leading zeros need to be consistent between the hour-specific and annual or average-day inventory files.

There are two types of EMS-95 format available for hour-specific data. The traditional EMS-95 format is shown in Table 6.24, “EMS-95 Format for individual hour-specific files” and the wider EMS-95 format is shown in Table 6.25, “EMS-95 Wider Format for individual hour-specific files”. The traditional EMS-95 format has 7 columns available for the emissions values instead of 12 columns in the EMS-95 wider format. For some air pollutant values, the 7 columsns was not big enough to capture the low precision unless scientific notation is used. To use the EMS-95 wider format, the optional environmental variable HOURLY_WIDE_FMT needs to be set to Y.

To process pollutant names greater than 5 characters, you need to add the new field of inventory pollutant code known as CAS number from column 261 to 276. If this new field is filled, the POLID is not used. If the new field is not filled, the POLID is required to use the inventory data name. The CAS number will be used to distinguish which chemical compound or inventory pollutant is provided on each line of the file. Smkinven matches these numbers with the CAS numbers from an inventory table (INVTABLE) file, described in Section 6.10.4, “INVTABLE: Inventory table”. The CAS number does not necessarily have to be a valid CAS number; it can be any number as long as there is a match between the numbers in the SMOKE ORL file and the inventory table.