Figure 3.4, “Locations of intermediate and output files for SMOKE base case, basic configuration”, Figure 3.5, “Locations of intermediate and output files for SMOKE base case, advanced configuration”, and Figure 3.6, “Locations of intermediate and output files for SMOKE future-/past-year case” show the locations of the output files as well as the intermediate files. The output files go to the subdirectory of the
data/run_ directory called $ESCENoutput. This output directory has two subdirectories: the first is set by the $SPC environment variable from the Assigns file that sets the model and chemical mechanism being used for a SMOKE run; the second
is named merge. There can be just one set of these subdirectories (as in the basic configuration shown in Figure 3.4, “Locations of intermediate and output files for SMOKE base case, basic configuration”) or multiple sets (as in the advanced configuration shown in Figure 3.5, “Locations of intermediate and output files for SMOKE base case, advanced configuration”).
The $SPC subdirectory contains the category-specific model ready files, such as the model-ready files for nonpoint (stationary area)
only, nonroad mobile only, etc. The merge subdirectory contains the final model-ready files. The following list provides the logical names and descriptions of each
of the files in the basic configuration case.
run_:
$ESCEN/output/merge
For CMAQ:
EGTS3D_L: CMAQ 3-D hourly, gridded, speciated emissions file, excluding PinG emissions (from the Smkmerge program).
For CMAQ only:
PINGTS_L: Optional file that includes the hourly emissions for PinG stacks (or grouped stacks) for each hour (from Smkmerge).
STACK_GROUPS: Optional file that identifies PinG stacks (or grouped stacks), their locations, and stack parameters (from the Elevpoint program).
For UAM or CAMX:
EGTS_L: I/O API version of the 2-D merged low-level, hourly, gridded, speciated emissions file (from Smkmerge).
EGTS_UAM: Fortran binary 2-D merged low-level hourly, gridded, speciated emissions file (from the Smk2emis program).
ELEVTS_L: ASCII elevated-point-source stack parameters and hourly, speciated emissions (from Smkmerge).
run_:
$ESCEN/output/$SPC
AGTS_L and AGTS_S: Nonpoint (stationary area) and optionally nonroad mobile-source hourly, gridded, speciated emissions (from the Smkmerge program).
B3GTS_L and B3GTS_S: Biogenic hourly, gridded, speciated emissions in moles/hour and tons/hour (from the Tmpbeis3 program).
B3GTS_L_O and B3GTS_S_O: Tmpbeis3 output with the correct units needed by the AQM (from the Smkmerge program).
MGTS_L and MGTS_S: On-road mobile-source hourly, gridded, speciated emissions (from Smkmerge).
NGTS_L and NGTS_S: Nonroad mobile-source hourly, gridded, speciated emissions in moles/hour and grams/hour (these files are written by Smkmerge as an AGTS_L or AGTS_S file, with the scripts changing the files to the NGTS name).
PGTS_L and PGTS_S: Point-surce hourly, gridded, speciated emissions (from Smkmerge). This file would be created when modeling for UAM or CAMX, which need the low-level point sources but not the 3-D point sources. This file would not include the elevated-point-source
emissions if it were created using the SMK_ASCIIELEV_YN = Y setting.
PGTS3D_L and PGTS3D_S: Point-source 3-D, hourly, gridded, speciated emissions (from Smkmerge). This file would be created for CMAQ only, using the elevated layer fraction, which requires the option MRG_LAYERS_YN = Y.
The output file locations for the growth and control cases follow the same paradigm described in Section 3.2.4.3, “Configuration for growth and/or control case” for the intermediate files. The $fyr2 and/or $CNTLCASE environment variable values are inserted into the directory structure, as shown in Figure 3.6, “Locations of intermediate and output files for SMOKE future-/past-year case”. The output directories are then reset as follows:
Future/past-year case (no controls):
run_: Final model-ready output files. The files are the same as those in the base case, but with future-year emissions; see Section 3.2.5.1, “Configuration for base case” for more information.
$ESCEN_$fyr2/output/merge
run_: Source-category hourly, gridded, speciated files. In the advanced configuration, the $ESCEN_$fyr2/output/$SPC$ASCEN, $MSCEN, or $PSCEN values could be different from the $ESCEN value, resulting in separate directories (as shown in Figure 3.5, “Locations of intermediate and output files for SMOKE base case, advanced configuration”, but with the $fyr2 field included in the path name. The files are the same as those in the base case, but with future-year emissions; see Section 3.2.5.1, “Configuration for base case” for more information.
Control case (no growth):
run_: Final model-ready output files. The files are the same as those in the base case, but with controlled emissions; see Section 3.2.5.1, “Configuration for base case” for more information.
$ESCEN_$CNTLCASE/output/merge
run_: Source-category hourly, gridded, speciated files. In the advanced configuration, the $ESCEN_$CNTLCASE/output/$SPC$ASCEN, $MSCEN, or $PSCEN values could be different from the $ESCEN value, resulting in separate directories (as shown in Figure 3.5, “Locations of intermediate and output files for SMOKE base case, advanced configuration”, but with the $CNTLCASE field included in the path name. The files are the same as those in the base case, but with controlled emissions; see Section 3.2.5.1, “Configuration for base case” for more information.
Future/past-year and control case:
run_: Final model-ready output files. The files are the same as those in the base case, but with future-year, controlled emissions;
see Section 3.2.5.1, “Configuration for base case” for more information.
$ESCEN_$fyr2_$CNTLCASE/output/merge
run_: Source-category hourly, gridded, speciated files. In the advanced configuration, the $ESCEN_$fyr2_$CNTLCASE/output/$SPC$ASCEN, $MSCEN, or $PSCEN values could be different from the $ESCEN value, resulting in separate directories (as shown in Figure 3.5, “Locations of intermediate and output files for SMOKE base case, advanced configuration”, but with the $fyr2 and $CNTLCASE fields included in the path name. The files are the same as those in the base case, but with future-year, controlled emissions;
see Section 3.2.5.1, “Configuration for base case” for more information.