The MOVES Runspec script Runspec_generator.pl is written in Perl, generates the scripts and inputs needed to run MOVES for each reference county. The MOVES Model can be run at any of the three domains/scales: national, county or project. The Runspec_generator.pl is only applicable to the county-level because this level of model detail is required by EPA for SIP and conformity analyses. For this scale, MOVES requires a MySQL input database containing local data for a single county. The Runspec_generator.pl is designed to prepare the MOVES importer and MOVES run scripts so that the fewest number of runs will produce all of the necessary emissions factors. In this approach, user can specify one or more groups of pollutants to model in the run control fil.
There are a total of four types of modeling pollutant groups: 1) Ozone precursors, 2) Toxics, 3) Particulate Matters, and 4) GreenHouse Gases (GHG) based on Table 2.12, “MOVES Pollutant Groups”. The choice of pollutant group(s) determines what pollutants are included in the three emission rate lookup tables (RPD, RPV, and RPP) by MOVES.
Runspec_generator.pl run after Met4moves. It assembles the instructions for MOVES to create MySQL input databases from XML files and creates the importer.csh scripts and assembles run specification XML files to run MOVES for a necessary range of conditions (for each emissions process: rate-per-distance, rate-per-vehicle, and rate-per-profile) based on the Met4moves output temperature list by county-specific runspec.csh.
The Runspec_generator.pl uses following steps:
Reads the reference county min/max temperature and 24-hours temperature profiles output file from Met4moves for RPP mode. Find detail information from Section 9.8.1, “MOVES_OUTFILE”
Reads the reference county specific min/max temperatures and average RH output file from Met4moves for RPD, RPV and RPH modes. Find detail information from Section 9.8.2, “MOVES_RH_OUTFILE”
Import the name of pollutant group to model from the run control file (contorl.in) based on Table 2.12, “MOVES Pollutant Groups”
Reads the run control file (control.in) and reference county file (countyrep.in) created by user.
Assembles instructions for MOVES to create MySQL input databases from XML files (data importer).
Assembles runspec XML files to run MOVES for a wide range of conditions.
Generates the run-specific temperature and humidity comma-separated-values (CSV) format file.
Assembles a batch list of data importer files, runspec files, and also a list of the MySQL output database names to be postprocessed.
importer.csh and runspec.csh scripts are used to create the on-road operating rateperdistance table (RPD), off-network processes ratepervehicle table (RPV), and vapor venting off-network rateperprofile table (RPP).
Review log file of the MOVES, called runlog_*.txt.
Table 5.1. Input Files
| File Name | Format | Description |
|---|---|---|
| countyrep.in | ASCII | Reference county file containing the county/state/country FIPS codes and the full path and file names for the files containing MOVES data for AGE, FUELSUPPLY, FUELFORM(optional), IM, POP, SourceType, HPMSVMT, VMT for each reference county |
| control.in | ASCII | Run control file that user specifies fields for the Database Host, Project Name, Model year, day type (weekday or weekend), pollutant and the met4moves MET output file for the batch run of MOVES |
| MOVES_OUTFILE | ASCII | Met4moves output for each fuel month for the MOVES Driver script (minimum and maximum temperatures, and 24-hour temperature profiles for all reference counties by temperature bin) |
| MOVES_RH_OUTFILE | ASCII | Met4moves outputs fuel month-specific averaged, min, and max temperatures and averaged RH values in local time for all reference counties by temperature bin |
| sourceTypeAgeDistribution | ASCII | Age distribution by source type over 30 vehicle model years |
| fuelSupply | ASCII | list directed file used to define the fuel properties, their market shares and the months that the fuels are used for each reference county |
| fuelformulation (optional) | ASCII | list directed file used to define the fuel supply and the months that the fuels are used for each reference counties |
| IMCoverage | ASCII | list directed file used to define the inspection and maintanance data available for each reference counties |
| sourcetypeyear | ASCII | Vehicle population by MOVES source type |
| HPMSVTypeYear | ASCII | list directed file used to define the annual VMT by Highway Performance Monitoring System (HPMS) vehicle type |
| dummy_avgspeeddistribution | ASCII | Speed distribution by roadway type and vehicle class. MOVES dummy inputs files provided with tool package in OUTDIR directory |
| dummy_monthvmtfraction | ASCII | list directed file that allocates annual VMT to the individual months |
| dummy_dayvmtfraction | ASCII | file that allocates month VMT day type, weekday or weekend and the decimal fraction of the proportion of vehicle miles travelled for the weekday or weekend day type |
| dummy_hourvmtfraction | ASCII | list directed file that allocates the day-type VMT to individual hours of the day |
| dummy_roadtypedistribution | ASCII | list directed file that allocates annual VMT to five MOVES roadway types |
| File Name | Format | Description |
|---|---|---|
| runspec.csh | ASCII | Batch or c-shell script to run required MOVES runs. Fine more information from Section 5.2.3.3, “MOVES Runspec batch script” |
| importer.csh | ASCII | Batch or c-shell Script to create MySQL MOVES databases and import the data. Fine more information from Section 5.2.3.2, “MOVES importer script” |
| InputDBlist | ASCII |
List of MySQL database names to process. It will be used as an input to MOVES Post-processing script. See example below: localhost /work/MOVES_Processing_Scripts/post_process 13121_2008_1 |
| Data importer files | ASCII | data importer files (*_imp.xml) |
| Runspec files | ASCII | runspec files (*_mrs.xml) |
| zonemonthhour files | ASCII | MOVES-formatted zonemonthhour (*_zmh.csv) contains temperature and RH data from the Met4Moves Meteorological processor. Relative Humidity is a single value averaged over the time period selected by the user in Met4Moves and averaged over the entire group of inventory counties that map to a reference county. |