AN IMPORTANT NOTE ABOUT THIS CASE --------------------------------- The packages in this directory contain scripts, inventories, and ancillary files related to the 2017ct_mats_fnl_05b case that was used for the PM NAAQS proposal RIA analysis. Most emissions for this case are taken from the 2017ct_ref_05b case, with only the EGU (ptipm sector) emissions changing. Therefore, you must successfully process all sectors (except ptipm) for the 2017ct_ref_05b case prior to creating the final merged AQ model-ready emissions for the 2017ct_mats_fnl_05b case. For the 2017ct_ref_05b and corresponding 2005 emissions, see: ftp://ftp.epa.gov/EmisInventory/2005v4_3/mats/ Documentation on the 2017 and 2005 emissions cases is available at: http://epa.gov/ttn/chief/emch/toxics/MATS_Final_Emissions_Modeling_TSD_9Dec2011.pdf The 2020 EGU emissions provided in this package are based on the final run of IPM that was used for the MATS final rule (see http://www.epa.gov/mats/) and also includes reductions from the Cross State Air Pollution Rule (see http://www.epa.gov/airtransport/) A. Introduction ------------------------------- This readme file covers the installation of the SMOKE inventories, scripts, and ancillary files used for the 2017ct_mats_fnl_05b PM NAAQS case. These include EGU inventories for processing the ptipm sector. SMOKE v2.7 and the IOAPI package are required in order to succesfully process the emissions using these scripts.The scripts assume that the SMOKE executables are located in: $SMK_HOME/smoke2.7/$SMOKE_EXE The default $SMK_HOME is the package root plus the "smoke" directory. For example: $SMK_HOME = /home/user/package/smoke This path is set in each individual script file and can be modified if necessary. B. Emissions used from other cases ---------------------------------- All emissions required for running the ptipm sector are contained in this package. All other sector emissions are part of the 2017ct_ref_05b package as described above. C. Extraction of inventory files ------------------------------- All of the provided inventory zips need to be extracted in the proper directory for the run scripts to access the inventories. For the 2017ct_mats_fnl_05b case , all inventory data zips should be extracted under the "project root" path. The project root is the package root (i.e., the base directory containing the subsys, smoke, ge_dat, and project directories) followed by the project name, e.g., "pm_naaqs_ria". For example, if the package root is /home/user/package, then the project root is /home/user/package/pm_naaqs_ria The inventory files will be extracted under the project root to each respective case input directory. Because this package contains only one sector, all emissions will fall under a path similar to: /home/user/package/pm_naaqs_ria/2017ct_mats_fnl_05b/inputs/ptipm All relevant subdirectories will be created during extraction to the project root. The inventory zip files and their contents are: 2017ct_mats_fnl_05b_ptday_ptipm.zip: -2017ct_mats_fnl_05b ptipm ptday 2017ct_mats_fnl_05b_orl_pt.zip: -2017ct_mats_fnl_05b ptipm D. Extraction of ancillary files ------------------------------- The provided ancillary zips need to be extracted in the proper directory for the run scripts can access the inputs. For the 2017ct_mats_fnl_05b case, all ancillary input zips should be extracted under the "package root" path. For this case the package root is the base directory containing the smoke, ge_dat, and project directories. For example, if the package root is /home/user/package , then the ancillary input will be extracted to: /home/user/package/ge_dat The ancillary inputs are contained in the zip file: 2017ct_mats_fnl_05b_ge_dat.zip E. Extraction of scripts ------------------------ The scripts zip needs to be extracted in the proper directory for successful completion. For the 2017ct_mats_fnl_05b case, the scripts zip should be extracted under the "project root" path. For this case the package root (the base directory containing the smoke, ge_dat, and project directories) followed by the project name: pm_naaqs_ria. For example, if the package root is /home/user/package, then the project root is /home/user/package/pm_naaqs_ria The script files will be extracted under the project root to the 2017ct_mats_fnl_05b scripts directory. For example, using the above project root, the scripts will be in: /home/user/package/ldghg_ph2/2017ct_mats_fnl_05b/scripts All relevant subdirectories will be created during extraction to the project root. There is one zip file that contains all scripts for the processing of the 2017ct_mats_fnl_05b case: -2017ct_mats_fnl_05b_scripts.zip F. Configuring the scripts --------------------------- All scripts must be edited in order to specify the package root and meteorological data root. These environment variables can be set near the top of each script file. The package root uses the "INSTALL_DIR" environment variable. Set this to the path where your smoke, ge_dat, and project root paths are located. For example: /home/user/package The meteorological data root uses the "MET_ROOT" environment variable. MCIP meteorology is used for processing of the on_moves sectors and the biogenics (BEIS) sector. The specified path should contain 36km 2005 year data. The scripts should be setup to run for the entire 2005 year and should require no other edits. G. Running the scripts ------------------------ Most sectors can be processed simply by running the "Annual" or "Monthly" script after making all path edits. The 36US1 domains should always be run before the other domains as these are set up to create necessary intermediate files. Running ptipm: -------------- In order to run the ptipm sector, the script beginning with "Onetime" must be executed for the grid so that annual intermediate files can be created. On successful completion of the "Onetime" script, the associated script that starts with "Daily" should be run to process the daily inventories and emissions. In order to successfully process the PTDAY files for the daily emissions, the variable "NAMEBREAK_DAILY" may need to be edited in the ptipm scripts. The NAMEBREAK_DAILY should be set to the number of underlines (_) in the path to the PTDAY files plus the number of underlines in the section of the name of the PTDAY files that comes before the month name. H. Generating the model-ready files (i.e., merging emissions from different sectors) -------------------------------------------------------------------------------- The "Sector_mrggrid" script is used to generate the merged CMAQ low level model- ready netCDF files. This script will use the sectorlist file provided in the scripts path and all of the sector level emissions. All sector-level processed emissions used to merge the 2017ct_ref_05b run are required to successfully merge the 2017ct_mats_fnl_05b case. The scripts and inputs are located in the 2005v4_3/2017emis directory on the CHIEF site. The last column of the sectorlist file for each grid run may need to be altered in order to point to the correct project root for each 2017ct_ref_05b sector being merged. Alternatively, the previously created sector emissions used to merge 2017ct_ref_05b can be copied into a case/intermed directory under the current project root without modifying the sectorlist files. For example, if the nonroad for 2017ct_ref_05b (as specified in the sectorlist) came from the 2005ct_05b case, then all emis_mole files would be copied from old_projectroot/2005ct_05b/intermed/nonroad to pm_naaqs_ria/2005ct_05b/intermed/nonroad. All model-ready files, including inline and low level files, will be output to the output directory under the project root path.