8.9.2. Mobile

8.9.2.1. M6LIST: MOBILE6 input scenario list file
8.9.2.2. M6MAP: Mobile source vehicle mapping file
8.9.2.3. MCODES: Mobile source codes file
8.9.2.4. MCREF: Mobile county cross-reference file
8.9.2.5. MEFLIST: Mobile emission factors list file
8.9.2.6. MEPROC: List of mobile emission processes and associated activities and pollutants
8.9.2.7. MVREF: Mobile source county settings file
8.9.2.8. SPDPRO: Mobile hourly speed profiles file
8.9.2.9. SPDREF: Mobile hourly speed cross-reference file

The directories where the mobile-specific input files should be stored are listed in Table 8.9, “Mobile-Specific Input File Locations”. The table also lists the programs that use each input file.

8.9.2.1. M6LIST: MOBILE6 input scenario list file

The M6LIST file lists the available MOBILE6 input scenario files. The scenario file name must include the six digit FIPS code of the county. Its format is shown in Table 8.84, “Format for M6LIST.

Table 8.84. Format for M6LIST

Line Position Description
1+ A Full name and path of MOBILE6 input scenario

Example 8.2. M6LIST file

/smoke/data/inventory/mobile/scenarios/summer037001.in
/smoke/data/inventory/mobile/scenarios/summer037057.in
8.9.2.1.1. MOBILE6 input scenario format

A MOBILE6 input scenario file must be provided for each reference county in the MCREF file. These files follow the same format as MOBILE6 input files; all commands are allowed except for the following:

  • AGGREGATED OUTPUT
  • AIR TOXICS
  • DAILY OUTPUT
  • DATABASE *
  • EMISSIONS TABLE
  • END OF RUN
  • EXPAND *
  • EXPRESS HC AS *
  • IDLE PM EMISSIONS
  • MOBILE6 BATCH FILE
  • MOBILE6 INPUT FILE
  • NO DESC OUTPUT
  • NO REFUELING
  • PARTICULATES
  • POLLUTANTS
  • REPORT FILE
  • RUN DATA
  • SPREADSHEET
  • WITH FIELDNAMES

The file must include either the MIN/MAX TEMPERATURES or HOURLY TEMPERATURE command and must have a SCENARIO RECORD command. SMOKE will ignore SPEED VMT, AVERAGE SPEED, or PARTICLE SIZE.

Example 8.3. MOBILE6 scenario file

SCENARIO RECORD    : 01001 96 07                                                                    
CALENDAR YEAR      : 1996                                                                           
EVALUATION MONTH   : 7                                                                              
DIESEL SULFUR      : 500                                                                            
MIN/MAX TEMPERATURE: 70.0 90.0                                                                      
ALTITUDE           : 1                                                                              
PARTICULATE EF     : PMGZML.CSV PMGDR1.CSV PMGDR2.CSV PMDZML.CSV PMDDR1.CSV PMDDR2.CSV              
FUEL RVP           : 7.8                                                                            
GAS AROMATIC%      : 25.0
GAS OLEFIN%        : 15.0
GAS BENZENE%       : 1.5
E200               : 50.0
E300               : 85.0
OXYGENATE          : MTBE  15.1  0.50
                   : ETBE  17.6  0.05
                   : ETOH  10.0  0.45
                   : TAME   6.0  0.00

8.9.2.2. M6MAP: Mobile source vehicle mapping file

The M6MAP file maps the 28 MOBILE6 vehicle types to the vehicle types in the mobile-source inventory. The format of the M6MAP file is shown in Table 8.85, “Format for M6MAP.

Table 8.85. Format for M6MAP

Position Name Type Description
A M6TYPE Char (6) MOBILE6 vehicle type
B INVTYPE Char (6) Inventory vehicle type

Example 8.4. M6MAP file

# MOBILE6 to SMOKE vehicle type mapping file
# base 8 vehicle types from SMOKE User's Manual
LDGV    LDGV
LDGT1   LDGT1
LDGT2   LDGT1
LDGT3   LDGT2
LDGT4   LDGT2
HDGV2b  HDGV
HDGV3   HDGV
HDGV4   HDGV
HDGV5   HDGV
HDGV6   HDGV
HDGV7   HDGV
HDGV8a  HDGV
HDGV8b  HDGV
HDGB    HDGV
LDDV    LDDV
LDDT12  LDDT
LDDT34  LDDT
HDDV2b  HDDV
HDDV3   HDDV
HDDV4   HDDV
HDDV5   HDDV
HDDV6   HDDV
HDDV7   HDDV
HDDV8a  HDDV
HDDV8b  HDDV
HDDBT   HDDV
HDDBS   HDDV
MC      MC

8.9.2.3. MCODES: Mobile source codes file

The MCODES file contains the codes for mobile source vehicle types and road classes. It is used to convert from the codes in the inventory to the codes used internally by SMOKE. The SCC section of the file maps the vehicle type and road class combinations to a mobile source SCC. The format of the MCODES file is shown in Table 8.86, “Format for MCODES.

Table 8.86. Format for MCODES

Line Position Description
1 A /VEHICLE TYPES/ header
2+ A Name of vehicle type from MBINV file (Char)
  B Number of vehicle type used in SMOKE files (Integer)
  C
Y - use vehicle type in modeling
N - do not use vehicle type
3 A /ROAD CLASSES/ header
4+ A Road class code from last 3 digits of SCC in MBINV file (Integer)
  B Road class code used in SMOKE files (Integer)
  C
Y - use road class code in modeling
N - do not use road class code
5 A /SCC/ header
6+ A Road class (Integer)
  B Vehicle type name (Char)
  C SCC (10-character)

Example 8.5. MCODES file

/VEHICLE TYPES/
LDGV   0100   Y
LDGT1  0102   Y
LDGT2  0104   Y
HDGV   0107   Y
LDDV   3000   Y
LDDT   3006   Y
HDDV   3007   Y
MC     0108   Y
LDGT   0106   N
/ROAD CLASSES/
110 01  Y
111 01  Y
130 02  Y
150 06  Y
170 07  Y
190 08  Y
210 09  Y
230 11  Y
250 12  Y
270 14  Y
290 16  Y
310 17  Y
330 19  Y
/SCC/
110 LDGV   2201001110
130 LDGV   2201001130
150 LDGV   2201001150
170 LDGV   2201001170
190 LDGV   2201001190
210 LDGV   2201001210
230 LDGV   2201001230
250 LDGV   2201001250
270 LDGV   2201001270
290 LDGV   2201001290
310 LDGV   2201001310
330 LDGV   2201001330
110 LDGT1  2201021110
130 LDGT1  2201020130
150 LDGT1  2201020150
170 LDGT1  2201020170
190 LDGT1  2201020190
210 LDGT1  2201020210
230 LDGT1  2201020230
250 LDGT1  2201020250
270 LDGT1  2201020270
290 LDGT1  2201020290
310 LDGT1  2201020310
330 LDGT1  2201020330
...

8.9.2.4. MCREF: Mobile county cross-reference file

The MCREF file is a list-directed file used to assign reference counties to inventory counties. Its format is shown in Table 8.87, “Format for MCREF.

Table 8.87. Format for MCREF

Line Position Description
1+ A Two-digit state FIPS code for inventory county (Integer)
  B Three-digit county FIPS code for inventory county (Integer)
  C Two-digit state FIPS code for reference county (Integer)
  D Three-digit county FIPS code for reference county (Integer)

Example 8.6. MCREF file

01 001  01 001
01 003  01 001
01 005  01 001
01 007  01 001
01 009  01 001
01 011  01 001
01 013  01 001
01 015  01 001
01 017  01 001
01 019  01 001

8.9.2.5. MEFLIST: Mobile emission factors list file

The MEFLIST file is used to provide the file names of available emission factors files to the Temporal program. This file cannot be created very easily until the Emisfac program has been run. Therefore, this file is generated automatically by the example SMOKE run scripts. The format of the MEFLIST file i shown in Table 8.88, “Format for MEFLIST.

Table 8.88. Format for MEFLIST

Line Position Description
1+ A Full name and path of emission factors file

8.9.2.6. MEPROC: List of mobile emission processes and associated activities and pollutants

The MEPROC file lists the emission processes and pollutants that will be generated by MOBILE6 for modeling on-road mobile sources. The available emission processes are listed in Section 2.8.4.5, “Emission processes”. The format of the MEPROC file is shown in Table 8.89, “Format for MEPROC.

Table 8.89. Format for MEPROC

Line Position Description
1+ A Activity name (Character)
  B Mobile emissions process (Character)
  C+ Associated pollutant name(s) for activity and process combination (Character)

Example 8.7. MEPROC file

VMT EXR CO NOX TOG
VMT EXS CO NOX TOG
VMT HOT TOG
VMT DNL TOG
VMT RST TOG
VMT EVR TOG
VMT CRC TOG
VMT RFL TOG

8.9.2.7. MVREF: Mobile source county settings file

The MVREF file is a list-directed file that assigns settings for various options to each reference county defined in the MCREF file. Its format is shown in Table 8.90, “Format for MVREF.

Table 8.90. Format for MVREF

Line Position Description
1+ A Two-digit state FIPS code for reference county (Integer)
  B Three-digit county FIPS code of reference county (Integer)
  C

Setting for spatial averaging of meteorology data

  • 1 - data are county specific
  • 2 - data are averaged over all counties sharing a reference county
  D

Setting for temporal averaging of meteorology data

  • 1 - no averaging; create hourly profiles for each day
  • 2 - average data over weeks
  • 3 - average data over months
  • 4 - average data over entire episode
  E

Setting for local roads

  • 1 - model both rural and urban local roads using MOBILE6 local road type (uses default average speed)
  • 2 - model both rural and urban local roads using MOBILE6 arterial road type with speeds from mobile inventory
  • 3 - model rural local roads using MOBILE6 arterial road type and urban local roads using MOBILE6 local road type
  • 4 - model rural local roads using MOBILE6 local road type and urban local roads using MOBILE6 arterial road type

Example 8.8. MVREF file

01 001 2 2 1
04 001 2 2 1
04 013 2 2 1
04 019 2 2 1
05 001 2 2 1

8.9.2.8. SPDPRO: Mobile hourly speed profiles file

The SPDPRO file is used to provide hourly speed profile data to MOBILE6. The format of this file is shown in Table 8.91, “Format for SPDPRO.

Table 8.91. Format for SPDPRO

Line Position Description
1+ A Profile number (Integer)
  B Hourly speed for midnight local time (Real)
  C Hourly speed for 1 am local time (Real)
  ... ...
  Y Hourly speed for 11 pm local time (Real)

8.9.2.9. SPDREF: Mobile hourly speed cross-reference file

The SPDREF file is used to match hourly speed profiles to the mobile sources. Its format is shown in Table 8.92, “Format for SPDREF.

Table 8.92. Format for SPDREF

Line Position Description
1+ A Six digit country/state/county FIPS code (Integer)
  B Ten digit Source Classification Code (Character)
  C Profile number (Integer)