4.4.12. Use MOVES for on-road mobile sources

4.4.12.1. Coordinating with other input files
4.4.12.2. Changing representative counties
4.4.12.3. Changing fuel month for representative counties

Extra files are needed for input to SMOKE when running with MOVES. These files are:

The MEPROC, MCXREF, and MFMREF files are installed in the $MBDAT directory for the default SMOKE configuration.

The subsections below describe how adjusting these files will allow you to perform a variety of changes to the on-road mobile processing.

4.4.12.1. Coordinating with other input files

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 pollutants (e.g., CO, NOX, and so on) as an input file to Movesmrg.

  • 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 representative counties for all counties for which you provide VMT data in the inventory.

4.4.12.2. Changing representative counties

Representative counties have previously been explained in Section 2.8.4.6, “Representative Counties”. The MCXREF file assigns representative counties for each county in your domain. To change the representative counties, this file should be edited to assign different representative 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.

4.4.12.3. Changing fuel month for representative counties

Reference fuel month have previously been explained in Section 2.8.4.7, “Reference Fuel month”. The MFMREF file assigns fuel month for each representative county in your domain. To change the fuel month, this file should be edited to assign a different fuel month to each representative county in the inventory. User must meet the criteria to share the same fuel month between representative counties.