Running SMOKE for other grids
This README describes how to take an existing Emissions Modeling Platform package and adapt it for processing a modeling domain other than 12US1 or 12US2.
Contents
GRIDDESC
First, the grid description for your domain must be added to the GRIDDESC from the script package (ge_dat/gridding/griddesc*). All scripts must point to your new GRIDDESC.
Update directory_definitions.csh script
The following lines in the directory_definitions.csh script in INSTALL_DIR/CASE/scripts must be updated:
- setenv REGION_ABBREV [grid name you want to appear in filenames]
- setenv REGION_IOAPI_GRIDNAME [grid name in the GRIDDESC]
- setenv MET_ROOT [your MCIP files for this particular domain]
Other updates to grid-specific SMOKE inputs will also need to be made in the individual sector scripts. The remainder of this README outlines these grid-specific SMOKE inputs.
Spatial surrogates
Most script packages on newftp.epa.gov include three sets of SMOKE-ready spatial surrogates: 36km resolution, 12km, and 4km. All three sets cover the entire CONUS, plus portions of Canada/Mexico. These surrogates can be used for any 36km, 12km, and 4km domain, even those which cover a smaller area than the CONUS, as long as:
- Your domain uses the same Lambert projection centered on 40N 97W
- Your domain does not extend beyond the reaches of the surrogates
- (If it does, SMOKE will still run, but emissions in the outlying areas will be zero)
If you need spatial surrogates for a larger area, or for a different resolution or projection, then you must run the Surrogate Tool to generate a new set of spatial surrogates. Scripts and inputs for running the Surrogate Tool may be provided at a later time.
Afdust transportable fraction (XPORTFRAC)
The XPORTFRAC file is based on land use and is used to apply reductions to gridded fugitive dust emissions in the afdust, othafdust, and othptdust sectors. This file is grid-specific but is not year-specific.
A program to prepare a new XPORTFRAC file is available in this package:
More information on how to run this program is available in the README_afdust_xportfrac file in that package. This program requires the GRIDCRO2D file from MCIP.
Biogenic land use (BELD)
For running biogenic emissions with the BEIS model in SMOKE, or inline in CMAQ, you need a corresponding land use file. BELD version 4.1 land use data is provided in this package, along with scripts for preparing this data for SMOKE processing for any domain:
There are two steps: Run the spatial allocator to convert 24 tiles to your domain of interest, and then run a 'water fix' step which improves the coverage of inland water based on the GRIDCRO2D file from MCIP. More information on how to prepare this data is available in the REAME_beld4.1_land_use file in that package.
We may make BELD version 5 land use data available at a later time.
Biogenic season file (BIOSEASON)
For running biogenic emissions with the BEIS model in SMOKE, or inline in CMAQ, it is recommended that you provide a BIOSEASON file which specifies the length of the growing season across the domain. SMOKE does not absolutely require a BIOSEASON; you may run with the entire domain for the entire modeling period set to the growing season or not, but this is only realistic for short, small domain applications.
BIOSEASON files are created with the SMOKE program Metscan. A script to run Metscan is available in this package:
Metscan requires the METCRO2D files from MCIP. In addition to running Metscan itself, the bioseason script also:
- Combines all METCRO2D files into a single episode-long file (Metscan requires a single METCRO2D rather than daily METCRO2Ds)
- Runs Metscan separately for the spinup period (if applicable) and the base year and then concatenates the resulting BIOSEASON files together
- Adds one extra day onto the end of the BIOSEASON to prevent a SMOKE error at the end of the episode
MET4MOVES
The rate-per-profile (RPP) portion of SMOKE-MOVES requires a file containing daily gridded minimum and maximum temperature data. This file is created by the SMOKE program met4moves. Scripts for running met4moves are available in this package:
Separate scripts for Metcombine and Met4moves are provided. Metcombine, which combines variables from the METCRO2D and METCRO3D files, must be run first. More information on how to run Met4moves is available in README_met4moves from the same package.
