ARDAY: Area source day-specific emissions
ARHOUR: Area source hour-specific emissions
ARINV: Area-source annual or average-day emissions
MBINV: Mobile-source activity and emissions
PTDAY: Point source day-specific emissions
PTHOUR: Point source hour-specific emissions
PTINV: Point source annual or average day emissions
The directories where the inventory files should be stored are listed in Table 8.1, “Inventory File Locations”. The table also lists the programs that use each input file.
Area-, mobile-, and point-source inventories are provided to SMOKE as ASCII text files using the logical file names
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.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. 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
directory, complete with full paths.
You will still need to edit this file to add format information (see Section 22.214.171.124, “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:
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 ORL and FF10 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.12, “Inventory header commands for ORL, and FF10 formats”.
Table 8.12. Inventory header commands for ORL, and FF10 formats
|Command||Parameter||Description and Values|
|#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
|#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||
In wild/Rx fires ORL format files (#ORL FIRE (“Section 126.96.36.199, “ORL FIRE Format””) and day-specific #ORL FIREEMIS file (“Section 188.8.131.52, “ORL FIRE Emission Format””), it defines a complete list of pollutant names from day-specific ORL FIREEMIS files; “data1” is the first pollutant name or CAS number, “data2” is the second pollutant name( or CAS number ), and so on.
Sample header records are given for each file in their respective sections.