Skip to content

Refreshing Machines

Brice Nichols edited this page Aug 20, 2019 · 4 revisions

Refershing AWS Machines for Integrated Runs

  • Clone this repo to any machine on the network
  • Copy/move any existing Soundcast run results from machines to be refreshed
  • Update the global config file for:
    • cloud_list (update the machine name, e.g., "cloud_list: aws-model03")
    • model_years: 2014,2025,2040,2050 (if running in "loose" integration, remove all years but 2050, otherwise don't change)
    • all other settings in the "vision2050_integrated.ini" config are configured for Vision 2050 runs, as of 8.20.19, and should not be changed. The standard settings will pull soundcast code for all run years (2014, 2025, 2040, 2050), copy configs for each year (stored in this repo), and copy TOD skims from the DSEIS TOD run, for 2014, 2025, and 2040. This config will not pull or replace any urbansim repos or data - be sure that this setting remains false to avoid overwriting any local urbansim data that has not yet been moved to the archive.
  • Run the script:
    • cloud_setup.py config\global\vision2050_integrated.ini
  • Check that the machine has been updated and skim file dates match the archive. Check the input_configuration files have valid input paths, model years, and that tolls are applied as expected.
  • Check that an Emme key is available (see this reference for key management in the Soundcast wiki
  • Check for sufficient space (~50 GB for urbansim, ~150 for each Soundcast run, so up to 400+ GB may be needed).
  • Start process in urbansim as detailed at http://twiki/Data/StartAnUrbanSimSimulationUsingLUVSetup

Clone this wiki locally