Extra files are needed for input to SMOKE when running with MOBILE6. These files are:
MEPROC: Mobile emission processes
MCREF: Mobile county cross-reference file
MVREF: Mobile source county settings file
M6LIST: MOBILE6 input scenario list file
MEFLIST: Mobile emission factors list file
MOBILE6 input files
The MEPROC, MCREF, and MVREF files are installed in the $MBDATemisfac_run.csh helper script creates the M6LIST file automatically. The MEFLIST file is created automatically by the default SMOKE scripts, using the helper script smk_run.csh. See Section 4.5.12.5, “Changing MOBILE6 inputs” for the description of the location for the MOBILE6 input files.
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, GSREF, and MOBILE6 input files. The MCREF, MVREF, and MOBILE6 input files must be coordinated with the inventory, and the MOBILE6 input files must be provided for the modeling
year. 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 same process-pollutant combinations (e.g., EXR__CO) as are indicated by the MOBILE6 inputs. The
MOBILE6 manual explains which pollutants are associated with which processes, except for user-defined pollutants based on
the MOBILE6 “ADDITIONAL HAPS” command.
For HAPS using the RATIOVOC command, the user has to define whether the emission factor is associated with exhaust (EXH) or evaporative (EVAP) processes. If the emission type is EXH, we could potentially have EXR and EXS emissions. With an emission type of EVAP, the corresponding SMOKE emission processes are HOT, DNL, RST, EVR, CRC, and RFL.
For HAPS using the RATIOPM command, the only SMOKE emission process is EXR.
For HAPS using the BEF command (basic emission factor), the possible SMOKE emission processes are EXR and EXS.
If there is any uncertainty about the processes that will be created, you can run MOBILE6 in stand-alone mode with your MOBILE6 inputs and see the emissions processes for which MOBILE6 creates the emissions.
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 have the correct MOBILE6 input commands so that they will be created. Please refer to the MOBILE6 manual for details
about which commands are needed for each pollutant.
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 ammonia must be included as EXR__NH3.
For the speciation profiles named in the GSREF file for each process-pollutant combination, the correct profile-pollutant combinations must be included in the GSPRO file. For example, if the GSREF file indicates that EXR__ACENAPHT25 should use profile 0000A for all SCCs, then the GSPRO file should have profile 0000A with pollutant ACENAPHT25.
When integrating toxics VOC and criteria VOCs and using MOBILE6, the NONHAPVOC or NONHAPTOG definition in the INVTABLE file and GSPRO files must be consistent.
The MCREF file must assign reference counties for all counties for which you provide VMT data in the inventory.
The MVREF file must select a spatial-averaging and temporal-averaging approach for all counties for which you provide VMT data in the
inventory.
The MOBILE6 inputs must be provided for all reference counties in the domain, using the naming convention explained in Chapter 8, SMOKE Input Files.
The MOBILE6 inputs must be provided for the modeling year (either base, future, or past year) and must include all date-specific information as recommended by the MOBILE6 documentation and/or other modeling guidance.
The emission processes that you can model are ultimately dependent upon the processes available in MOBILE6. In Section 2.8.4.5, “Emission processes”, we have previously listed the available emission processes and which types of pollutants (criteria, VOC, PM, Toxics, user-defined
HAPS) 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 above and in Section 2.8.4.5, “Emission processes”.
Reference counties have previously been explained in Section 2.8.4.7, “Reference counties”. The MCREF 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.
You may want to change the spatial or temporal averaging to improve the detail of the modeling effort (increasing the processing
time) or to decrease the processing time (reducing the detail of the modeling). The MVREF file must be changed using the file format described in Chapter 8, SMOKE Input Files to select the spatial or temporal averaging approach. As explained in the file format, the spatial approach can be “by county” or “by reference county”, and the temporal averaging can be day-specific (no averaging), weekly averaging, monthly averaging, or episodic averaging.
If you are using multiple meteorology averaging resolutions in the same run, you must also modify your on-road mobile script
to use multiple calls to the emisfac_run.csh helper script. The excerpt from the on-road mobile example script smk_mb_nctox.csh below is where the script must be changed to include additional calls to emisfac_run.csh for all four averaging approaches.
## Run emisfac for cases needed by averaging choices in MVREF file # foreach group ( episode ) # can include ( daily weekly monthly episode ) setenv GROUP_TYPE $group source emisfac_run.csh # Run programs endif
To change the temporal averaging needed, change the line with the foreach statement to use all of the following options inside the parentheses:
daily
weekly
monthly
episode
Changing MOBILE6 inputs requires you to take the following steps:
Prepare to name files using a “.in” extension on all files. Ensure that the “.in” extension is lower case.
Create MOBILE6 inputs as per MOBILE6 instruction manual and the following additional constraints placed by SMOKE.
Make sure that the case of the file names of external files referenced in MOBILE6 inputs are consistent with the actual file names.
Since SMOKE will most likely run on a UNIX-based operating system, the case of the external files referenced by the MOBILE6 inputs will matter. If the case of the file names referenced do not match the case of the actual files, then MOBILE6 will give errors that the files are not found and the Emisfac program will end with an error.
Further information about the format of the MOBILE6 input files is given in Chapter 8, SMOKE Input Files.
Put your files in a directory named based on the following additional instructions.
The MOBILE6 inputs for the case you want to run need to be in the correct directory as follows:
No control case name (CNTLCASE variable is not defined by the scripts):
MOBILE6 input directory is $MBDAT/m6_$EF_YEAR/
EF_YEAR is set following the rules described in
Section 4.3.4, “Script settings” (i.e., depends on YEAR, FYEAR, YEAR_OVERRIDE, and SMK_FUTURE_YN).
Control case name (CNTLCASE variable is defined by the scripts):
MOBILE6 input directory is $INVDIR/mobile/m6_${EFYEAR}_$CNTLCASE
Note that this setting does not depend on the SMK_CONTROL_YN setting.