Extra files are needed for input to SMOKE when running with MOVES. These files are:
MEPROC: Mobile emission processes
MCXREF: Mobile reference county cross-reference file
MFMREF: Mobile fuel month file
MRCLIST: List of MOVES Lookup Tables for Movesmrg
RUNCTL: Runcontrol file
The MEPROC, MCXREF, and MFMREF files are installed in the $MBDAT
The subsections below describe how adjusting these files will allow you to perform a variety of changes to the on-road mobile processing.
The MEPROC file must be coordinated with the INVTABLE, GSPRO, and GSREF. The MCXREF and MFMREF must be coordinated with the inventory. The following list indicates all of the things that you must check for when creating
any of these files.
The MEPROC file must have all of the process-pollutant combinations (e.g., EXH__CO, EXH__NOX, and so on) as an input file to Movesmrg. The Table 2.6, “MOVES Pollutants associated with SMOKE Emissions Processes (SmokeProcIDs)” explains which pollutants are associated with which processes.
User has an option to choose whether aggregated SMOKE emissions process or not. If user chooses the aggregated emission process as EXH, we could potentially have EXR, EXS, CXR, CXS, CEI, and EXT. With an emission process of EVP, the corresponding SMOKE emission processes are EPM, EFV, EFL, and RFL.
If a pollutant that you want to model is not in the MEPROC file, it will not be modeled by SMOKE correctly. All pollutants that you wish to include in the outputs must be in the MEPROC file.
All pollutants in the MEPROC file must also be in the INVTABLE file with Keep = Y, including the INVTABLE limitation that the file pollutant names are limited to 11 characters for on-road mobile pollutants.
All pollutants in the MEPROC file must be available in SMOKE-ready MOVES lookup tables.
All process-pollutant combinations in the MEPROC file must also be included in the GSREF file. The format for the “pollutant” entry in the GSREF is <emission process>__<pollutant>. Note that the joiner between <emission process> and <pollutant> is a double underscore.
A single underscore will prevent the processing from working properly. For example, running exhaust carbon monoxide must be included as EXR__CO.
When integrating toxics HAPs and criteria TOG and using MOVES, the NONHAPTOG definition in the INVTABLE file and GSPRO files must be consistent.
The MCXREF file should assign reference counties for all counties for which you provide VMT data in the inventory.
The emission processes that you can model are ultimately dependent upon the processes available in MOVES. In Table 2.6, “MOVES Pollutants associated with SMOKE Emissions Processes (SmokeProcIDs)”, we have previously listed the available emission processes and which types of pollutants (criteria, VOC, PM, Toxics) are
associated with each. You can change which processes are included in your modeling by adding or removing processing from the
MEPROC file, as long as you are consistent with the documentation Section 8.9.2.1.4, “MEPROC: List of mobile emission processes and associated activities and pollutants”.
Reference counties have previously been explained in Section 2.8.4.4, “Reference Counties”. The MCXREF file assigns reference counties for each county in your domain. To change the reference counties, this file should be edited
to assign different reference counties to each county in the inventory. After editing this file, you must make sure that no
counties in the inventory have been left out of the file.
Reference fuel month have previously been explained in Section 2.8.4.5, “Reference Fuel month”. The MFMREF file assigns fuel month for each reference county in your domain. To change the fuel month, this file should be edited to
assign a different fuel month to each reference county in the inventory. User must meet the criteria to share the same fuel
month between reference counties.