Best Practices:
Tips to keep track of files and
 organize your MOVES runs
        FHWA Resource Center
 EPA Office of Transportation and Air Quality
                              EPA-420-B-09-027

-------
                                    &EPA
Naming Strategies
  Name all the files you use for a specific run using
  the same name, but with different extensions (eg.
  Washtenaw2008_in, Washtenaw2008.mrs,
  Washtenaw2008_out)
   - Identifies each part of the run file
   - Helps organize information
  When testing MOVES include "Test" or "Temp" in
  the name
   - Mysql/data folder can get cluttered
   - Allows for easier clean-up
                                                           2

-------
                                                 &EPA
         Other Tips
            Save all Run Specs outside of the MOVES
            directory folders
            - Folders installed in MOVES will be overwritten when new
              versions of MOVES are installed
            - Input files can be saved in or near the folder containing the
              corresponding MOVES runspec
            Decide on the Scale before making any other
            selections on the panel
            - Changing scale after making selections may reset those
              selections
When using COM, the folder where the runspec is saved is the folder that is
opened, so having them close makes importing files easier

-------
                                       &EPA
Other Tips
  Any run used for official purposes should be
  archived completely
   -  Including batch files, run specs, MOVES code and
     configuration files, supplemental code, default database, user
     input databases, etc.
   -  Months or years later, runs can be reproduced
  Save output to same MySQL database
   -  Except for very large files
   -  Easy to find output files
                                                                 4

-------
                                              &EPA
           Pre-Aggregation
            ^^^^^H=
             MOVES calculations can take a long time.
             Aggregation of inputs is one way to reduce the
             number of calculations and speed up a run.
             Aggregation of inputs will affect results; while
             aggregation of outputs does not affect results.
             Proper aggregation is a policy issue and will be
             addressed in guidance.
Pre-aggregation is one way to get results quickly, but at the expense of using less
precise calculations of the results.
I favor "no aggregation" unless there is a good reason.

-------