Area-, mobile-, and point-source inventories are provided to SMOKE as ASCII text files using the logical file names ARINV, MBINV, and PTINV, respectively. These files may either contain the actual inventory data (i.e. source characteristics, emissions data, and other information) or they can contain a list of file names with full paths (i.e. /apps/smoke/data/inventory/nei02/area/arinv.ida.txt); in the latter case, we call the file a “list file”. When the inventory is a list file, SMOKE will open and read the data in each of the listed files and combine the data into one inventory. This is useful when the individual inventories are in different formats; for example, criteria emissions are typically in IDA format, while the ORL format is used for toxics emissions. You may also choose to separate your data into multiple files, splitting the data by country or into EGU versus nonEGU point sources, or to reduce the individual file sizes. Some inventory formats require that a list file is used; this will be noted in the format descriptions.
An inventory list file can be created using the UNIX ls. The following command will create the ARINV file containing a list of all files starting with arinv in the $ARDAT directory, complete with full paths.
ls $ARDAT/arinv* > $ARINV
You will still need to edit this file to add format information (see Section 8.2.1.2, “File format header”).
All area-, mobile-, and point-source inventory files must include information specifying the file format being used. This is accomplished using a header entry, either in each individual inventory file or in the list file, if one is being used. Valid format options are:
If you want to give the format information in the list file, you need to append an additional format label to the #LIST header. For example, #LIST IDA indicates that the current file is in list format and that the listed files are IDA format. List files can include multiple #LIST <format> entries to include multiple file types; the given format is assumed to apply to all files until another #LIST <format> is encountered. Format indicators in the individual inventory files will override settings in the list file. A sample list file is shown below.
#LIST IDA /apps/smoke/data/inventory/nei02/area/arinv.ida.txt #LIST TOXICS /apps/smoke/data/inventory/nti02/area/arinv.orl.txt
In this case, SMOKE will assume that the file /apps/smoke/data/inventory/nei02/area/arinv.ida.txt is in IDA format and the file /apps/smoke/data/inventory/nti02/area/arinv.orl.txt is in ORL format. Alternatively, these files could be listed like so:
#LIST /apps/smoke/data/inventory/nei02/area/arinv.ida.txt /apps/smoke/data/inventory/nti02/area/arinv.orl.txt
In this case, the /apps/smoke/data/inventory/nei02/area/arinv.ida.txt file must include the #IDA header and the /apps/smoke/data/inventory/nti02/area/arinv.orl.txt file must include the #TOXICS header.
Inventory files can include both required and optional fields. In the format tables for each file, required fields are labeled “required”; optional fields are labeled either “recommended”, “optional”, or “not used by SMOKE”. For column-specific file formats, you may leave blank the fields that are optional. List-directed files, on the other hand, must have a default value (usually -9) for these fields.
The IDA and ORL formats used for the area-, mobile-, and point-source inventories require a set of header records at the beginning of each file. The general format of the header records is:
command parm1 parm2 ... parm n
The command field starts in the first column of the row. The remainder of the line is list-directed, with each field separated by blanks. The specific header commands vary by source category and format and are listed in Table 8.29, “Inventory header commands for IDA and ORL formats”.
Table 8.29. Inventory header commands for IDA and ORL formats
| Command | Parameter | Description and Values | |||
|---|---|---|---|---|---|
|
N/A | N/A | |||
| #TYPE | File type | First nonblank character after #TYPE to the last character of the line. For on-road mobile activity data, the word “activity” must appear in this header entry; otherwise, SMOKE assumes that the file contains emissions data. | |||
| #COUNTRY | Country name | Valid names are those in the COSTCY file (US, CANADA, MEXICO, etc.) | |||
| #YEAR | Data year | Number from 1900 to 2200 | |||
| #DESC | Description | Description of the data (not used by SMOKE) | |||
| #DATA or #POLID | data1 data2 ... data n | Only used for IDA-format files. Defines the pollutants for which emissions data is provided; “data1” in the ID of the first pollutant, “data2” is the ID of the second pollutant, and so on. | |||
| #UNITS | units1 units2 ... units n | Only used for on-road mobile activity data in IDA format. Defines the units associated with the activity data; “units1” are the units for “data1”, “units2” are the units for “data2”, and so on. Not used for emissions data because the units are built into the file formats. |
Sample header records are given for each file in their respective sections.
When using EMS-95 inventories, the ARINV, MBINV, and PTINV files are usually a list file (see Section 8.2.1.1, “Inventory list files”) that lists individual inventory files in EMS-95 format. This list file must contain one or more INVYEAR packets. This packet acts as a switch that sets the inventory year for the files, each of which will get the year designated by the packet until another INVYEAR packet appears in the file. In this way, multiple years of inventory data can be combined into one SMOKE inventory. The format of the INVYEAR packet is INVYEAR <four-digit year> and is shown in the example below.
#LIST EMS-95 INVYEAR 1996 /apps/smoke/data/inventory/smraq95/area/arinv.ems95.txt