*** PLEASE READ THIS BEFORE RUNNING SMOKE. *** == 1. Introduction == These packages contain scripts, inventories, and ancillary files related to the 2025eh_cb6v2_v6_11g case, for onroad and nonroad only. This is part of EPA's 2011v6.2 platform for air quality modeling. This platform will be used for assessing ozone transport within the continential U.S. and for other studies. CMAQ and CAMx model-ready emissions generated using these packages with SMOKE v3.6 should be identical to those used in EPA's 2011v6.2 platform. However, there may be emissions differences resulting from differences in the Linux operating system, hardware platform, and other system-specific differences. Additional information on the 2011v6.2 platform is available here: http://www.epa.gov/ttn/chief/emch/index.html#2011 The data files are divided into several directories: - 2025emissions contains emissions inventories for the year 2025 - ancillary_inputs contains general ancillary files (ge_dat), including those related to speciation, spatial allocation (gridding). and temporalization - ocean_chlorine contains a gridded ocean chlorine emissions file which is included in the final model-ready emissions - smoke_scripts_utils contains scripts to run SMOKE and utility programs - spatial_surrogates contains 12km, 36km, and 4km spatial surrogates Section 4 of this README includes information about the modeling sectors used in the platform. Section 5 of this README includes information about the inventories provided. Section 6 of this README includes information about the ancillary (non-inventory) files included. == 2. Requirements for processing emissions for air quality modeling == If you are only reviewing inventories and not developing emissions for air quality modeling, you do not need to install SMOKE or to follow the instructions below. Instead, unzip the files with the data of interest and examine those and the corresponding reports that are provided. If you plan to develop emissions for air quality modeling, SMOKE v3.6 is REQUIRED to process this case. SMOKE v3.6 uses a new temporal profile and cross-reference format, and the profiles and cross-references included in this package are not compatible with older versions of SMOKE. In addition, bug fixes and new features were implemented between SMOKE v3.5 and SMOKE v3.6, including compatibility with MOVES2014 for mobile emissions. Python: We also recommend (if not require) python version 2.6 or later, along with select python libraries. Many of the helper scripts included in this package use python. The python scripts within this package reference '#!/usr/bin/env python' or '#!/usr/bin/env python2.6'; you may need to change this on your computing platform. == 3. Installation of data files and scripts == This readme covers the installation of the SMOKE inventories, scripts, and ancillary files used for the 2011v6.2 platform. Choose an install directory on your system; we will refer to this directory as "INSTALL_DIR". To review/reproduce emissions for all sectors, unzip all the .zip files into INSTALL_DIR. The packages have subdirectories embedded within them, so it is important that all files be unpacked in the same place in order for the scripts to run. If you are only interested in reproducing or examining emissions for specific sectors, you may download and unzip only the data for those sectors from the 2011emissions directory, but for SMOKE processing you should also include the files in the directories: ancillary_inputs, ocean_chlorine, smoke_scripts_utils, and spatial_surrogates for the grid(s) you plan to run. All SMOKE inventories, scripts, and ancillary files used for the 2011v6.2 platform are provided, except emission factor tables for onroad processing via SMOKE-MOVES. The full set of emission factor tables is too large to permanently store on the FTP server and instead are furnished upon request. The following are NOT included in the packages: - SMOKE executables: These can be downloaded from http://www.smoke-model.org/. Again, SMOKE v3.6 is required. The SMOKE executables should be installed in INSTALL_DIR/smoke3.6/[platform], where [platform] varies depending on your computing platform. On EPA systems, [platform] = "Linux2_x86_64ifort". If you are not sure what [platform] should be, running a script once should produce an error message that will tell you in which directory the scripts expect to find the SMOKE executables. - I/O API utilities, such as m3xtract and juldate. For the scripts to run, these should be copied or linked to INSTALL_DIR/ioapi/[platform] (see above for a description of [platform]). - MCIP meteorology data, which is used for the afdust, onroad, onroad_catx_adj, onroad_rfl, biogenics (beis), and ptfire3D sectors. See MET_ROOT instructions below. The sea salt portion of the CAMx conversion (see section 9) requires CAMx-formatted WRF output, which is also not included in the package. Prior to running SMOKE, in each run script, you will need to edit the INSTALL_DIR (your install directory) and MET_ROOT (location of MCIP meteorology data) environment variable definitions at the top of the script. The MCIP data should be located in MET_ROOT/12US2/mcip_out/, or MET_ROOT/[grid]/mcip_out/ if processing emissions for a grid other than 12US2. SMOKE only uses the GRIDCRO2D, METCRO2D, and METCRO3D files. == 4. Case description and instructions for each sector == 2025eh_cb6v2_v6_11g emissions were processed for a 12km national grid (12US2), with CB6 speciation. Emissions processing is split into "sectors". Each sector has its own run scripts for processing, with one (or more) run scripts per case. (See section 7 for information about the run script zips.) All sectors are US-only unless otherwise noted. The sectors are: NONROAD: Off highway mobile source emissions. ONROAD: On highway mobile source emissions, excluding California. This sector is processed using SMOKE-MOVES with multiple scripts as described in section 4B. ONROAD_CA_ADJ: On highway mobile source emissions, California only. This sector is processed using SMOKE-MOVES with multiple scripts as described in section 4B. The onroad sector configuration is different in 2011v6.2 compared to 2011v6; the changes are described in detail in section 4B. Other sectors for 2025eh will be provided later. == 4B. Notes regarding onroad == Onroad emissions are processed using SMOKE-MOVES. The processing is split into multiple run scripts. In the 2011v6.2 platform, SMOKE-MOVES inputs were prepared using the latest version of MOVES: MOVES2014. This update introduces several changes to the onroad emissions modeling process. As described in the SMOKE online documentation, SMOKE-MOVES handles onroad emissions separately for FOUR types of processes (up from three in prior versions of SMOKE-MOVES): - On-network emissions (RatePerDistance, or RPD) - Off-network emissions, fuel vapor venting (RatePerProfile, or RPP) - Off-network emissions, extended idling (RatePerHour, or RPH) - Off-network emissions, non-venting, non-extended idle (RatePerVehicle, or RPV) For each of the two onroad sectors (onroad, onroad_ca_adj), there are separate run scripts for RPD, RPP, RPH, and RPV, plus a merge script that combines emissions from RPD, RPP, RPH, and RPV into a single emissions file per day. These scripts may take a particularly long time to run, especially RPD. Therefore, consideration should be given to running multiple RPD jobs in parallel, such as one job per quarter. The reason onroad has been split into two sectors - onroad and onroad_ca_adj - is in order to match SMOKE-MOVES annual emission totals with those provided by California for non-refueling sources. To do this, we split California into a separate sector, and ran SMOKE-MOVES with a control factor file (CFPRO) which nudges the emissions so that the annual totals post-SMOKE-MOVES equal those provided by CARB, at the county/CSCC6 level. (CSCC6 is "comparison SCC6", which serves as a bridge between MOBILE6-style SCCs used byprior versions of SMOKE-MOVES and the new MOVES2014-style SCCs.) For the onroad sector, a CFPRO is provided in the ancillary_inputs/ge_dat_for_2011eh_other.zip package which zeroes out gasoline refueling emissions in 53 Colorado counties. We zero out these emissions in order to prevent a double count with the ptnonipm sector, since that sector includes gasoline refueling emissions in these counties. == 4B1. DAYS_PER_RUN == SMOKE-MOVES can be run more efficiently if running more than one day at a time. For example, Movesmrg can create one 7-day emissions file more quickly than it can create seven individual 1-day emissions files. To turn on this feature, use the DAYS_PER_RUN variable, set to the number of days you wish to run in a single Movesmrg instance. The recommended value for DAYS_PER_RUN is 7. The onroad scripts in the 2025eh scripts .zip include a setting called "DAYS_PER_RUN", set to 1 as the default. The paramater setting can also be added to other onroad scripts. If DAYS_PER_RUN > 1, after Movesmrg is run, the run scripts will use the I/O API utility m3xtract to split up the multi-day emissions file into single day (25-hour) emissions files. Multi-day Movesmrg runs will never cross months. For example, if DAYS_PER_RUN = 7, then the last Movesmrg run of January will start on January 29th and end on January 31st (3 days), and the first Movesmrg run of February will start on February 1st and end on February 7th. Using the multi-day Movesmrg functionality requires multi-day MCIP files. For example, if DAYS_PER_RUN = 7, your METCRO2D files must also be 7 days (169 hours) long. These multi-day MCIP files should be stored in MET_ROOT/[grid]/mcip_out/Xday/, where X = DAYS_PER_RUN (i.e. /7day for DAYS_PER_RUN = 7). The primary drawback to using this multi-day Movesmrg functionality is an increase in the memory usage. == 5. Description of inventory packages == Inventories for 2025eh cases, onroad and nonroad, are included in the following files, all of which should be unpackaged in INSTALL_DIR: 2025emissions/2025eh_v6_11g_inputs_nonroad_part1.zip 2025emissions/2025eh_v6_11g_inputs_nonroad_part2.zip 2025emissions/2025eh_v6_11g_inputs_onroad.zip The two "inputs_nonroad" packages include the inventories for the nonroad sector. It was split into two .zips in order to reduce the size of each individual .zip. The "inputs_onroad" package includes the activity data for the onroad and onroad_ca_adj sectors. It does not include the emission factor tables also required to run SMOKE-MOVES; these are not stored on the FTP site due to their large size and instead are furnished upon request. See section 4 for a description of each modeling sector. == 6. Description of ancillary file packages == The following packages should be unpacked in INSTALL_DIR in order to process nonroad and onroad: ancillary_inputs/ge_dat_for_2011v2_gridding.zip ancillary_inputs/ge_dat_for_2011v2_other.zip ancillary_inputs/ge_dat_for_2011v2_speciation_cb6.zip ancillary_inputs/ge_dat_for_2011v2_temporal.zip spatial_surrogates/surrogates_CONUS12_2010_v5_20141015.zip The "surrogates" packages contain the gridding surrogates for 12US2 for the US. Surrogates for 36km (36US1) and 4km are also provided for the US only in the spatial_surrogates directory. The "gridding" package includes all SMOKE inputs related to gridding other than the spatial surrogates, including cross-references, surrogate descriptions, and gridded transportable fractions used in afdust_adj and othafdust_adj. The "speciation" packages include speciation profiles, cross-references, and VOC-to-TOG conversion factors. Separate .zips are provided for CB05 and CB6. Additional .zips are also provided for CB05 w/toxics (consistent with NATA) and SAPRC07TB. These two additional .zips, in particular the SAPRC07TB .zip, are provided on an as-is basis and do not include all of the speciation profiles needed in order to process the entire 2011v6.2 platform. In addition, we do not have onroad (SMOKE-MOVES) emission factor tables for SAPRC07TB. Since the future year cases were only run with CB6 speciation, only the CB6 speciation package contains any speciation-related ancillary files needed for 2017 or 2025. The "temporal" package includes temporal profiles and cross-references, including daily and hourly temporal profiles developed by the SMOKE program Gentpro for use in the rwc and ag sectors, respectively. The "other" ge_dat package includes all other SMOKE ancillary files not included in the above packages, including: - Inventory tables (INVTABLE) - Lists of sources to exclude from CAP/HAP integration (NHAPEXCLUDE) - SMOKE-MOVES ancillary files, including the reference county (MCXREF) and fuel month (MFMREF) cross-references, pollutant (MEPROC) and emission factor table (MRCLIST) lists, activity SCC to full SCC cross-references (SCCXREF), hourly speed profiles (SPDPRO), daily temperature data (METMOVES), and control factors for onroad_ca_adj and Colorado gasoline refueling (CFPRO) - Other miscellaneous SMOKE inputs, such as the ARTOPNT, COSTCY, HOLIDAYS, MACTDESC, NAICSDESC, ORISDESC, PELVCONFIG, PSTK, SCCDESC - Smkreport configuration files (REPCONFIG, all in ge_dat/repconfig/default) The run scripts (see section 7) are already set up to use the proper ancillary files and inventories for each sector and speciation. == 7. Description of script packages == For 2025 onroad and nonroad, these two run script packages should be unpacked in INSTALL_DIR: smoke_scripts_utils/2025eh_cb6v2_v6_11g_scripts_onroad_nonroad.zip smoke_scripts_utils/smoke_helper_scripts_2011v2platform_smoke36.zip The helper_scripts package includes scripts which are called by the primary run scripts. You should not have to run any of these scripts directly. The 2025eh scripts packages include the scripts that you run directly in order to replicate our emissions. Separate script(s) are provided for each sector. The scripts are unpacked to INSTALL_DIR/$CASE/scripts/. See section 4 for information pertinent to each sector. In general, you edit the INSTALL_DIR and MET_ROOT, and then run. For onroad sectors, run RPV/RPD/RPH/RPP first, then the merge.