Framework for Regional Earthquake Simulation
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
Pegasus Added Agave/Wrangler helper script Oct 17, 2018
Workflow Changes necessary for 1.1.0 release Jan 31, 2019
common Changed createEVENT applications build to CMake Sep 13, 2018
createBIM updating CMakeLists; fixing a bug in ConcreteShearWall Jan 25, 2019
createEVENT Changes necessary for 1.1.0 release Jan 31, 2019
createLOSS Fixing Jansson calls for reading real numbers Nov 27, 2018
createSAM Adding a default seismic zone for MDOF-LU if not provided in BIM Feb 7, 2019
env Fixing windows build Sep 26, 2018
performSIMULATION Fixing issues on unix systems Jan 25, 2019
CMakeLists.txt Fixes for building/running on both Window and Linux Oct 2, 2018
Makefile Removing unused applications and updating Make files Jul 21, 2018
conanfile.txt initial import - really a branch from Workflowf1 but decided not to d… Nov 7, 2017


Regional Earthquake Simulation Workflow

The regional earthquake simulation workflow is a set of applications that together can estimate damage and loss based on a buildings database and hazard information for a region. The workflow goes through the following five main processes to obtain damage and loss estimates for each building in the region:

  1. Obtain the Building Information Model (BIM).

  2. Obtain the hazard event input on the building.

  3. Produce a Structural Analysis Model (SAM) of the building.

  4. Define and calculate the Engineering Demand Parameters (EDP) for the building model.

  5. Estimate the damage and loss.

In addition to these main processes, the following five intermediate files are defined and are used in the workflow as intermediate interfaces between the processes:

  1. BIM file: A file containing general information about the building.

  2. EVENT file: A file containing information about the hazard events input for the building.

  3. SAM file: A description of the structural analysis model including geometry, structural and material properties.

  4. EDP file: a file containing the definition and values of the engineering demand parameters (EDPs).

  5. DL file: a file containing the obtained damage and loss estimates for a building.

In this framework for regional simulation, the JSON format is adopted for all the intermediate files defined above. The implementations of the workflow applications provided in this repository are organized based on the previous 5 main processes, categorized based on their purpose, in the following sub-directories:

  • createBIM: This directory contains applications that can obtain a Building Information Model (BIM) from a database of buildings. Some examples of these applications are:

    • UrbanSimDatabase: This application generates BIM models given UrbanSim buildings and parcels csv files.

    • GenericBimDatabase: This application generates BIM models given a generic database in csv format with a minimal set of information about each building.

    More detailed documentation for the createBIM applications is available here

  • createEVENT: This directory contains applications to generate hazard event input given BIM.

    • LLNL-SW4: This application will read the building location from the BIM model and will output ground motion for simulating building response. The application uses a set of pre-computed ground motions for SF Bay Area earthquake event (Magnitude 7.0 earthquake at the Hayward fault) simulated using SW4.

    • [Experimental]: This application combines seismic hazard analysis (SHA) and ground motion record selection/scaling to provide ground motions for structural analysis based on a user-defined earthquake scenarios.

    • : This application assumes a set of recorded ground motion is provided and uses nearest-neighbor search to set the hazard input for each building using the nearest recorded ground motion.

  • createSAM: This directory contains applications to create structural analysis model (SAM) given BIM and Event data

    • MDOF_LU: This application use Hazus data to generate a MDOF non-linear shear building model.

    • AI-M-3 [Under Development]: This is an application that is currently under development that uses artificial intelligence to obtain SAM from BIM.

  • createEDP: This directory contains applications that generates a list of the required Engineering Demand Parameters (EDPs) to be obtained from structural analysis.

    • StandardEarthquakeEDP: This application uses the SAM to define the EDPs needed for damage and loss calculations due to an earthquake event.
  • performSIMULATION: applications in this directory will perform preprocessing of SAM, structural analysis and post processing to obtain EDP values.

    • This application will pre-process the SAM file to create an OpenSees model, run the model and post-process OpenSees outputs to update the EDP values.
  • performUQ: This directory contains scripts and applications to introduce uncertainties in the workflow applications. Current implementation relies on DAKOTA for handling uncertainties.

    • This implementation of performUQ relies on DAKOTA for handling uncertainties.
  • createLOSS: Applications in this directory are used to determine damage and loss.

    • FEMA_P58_LU: Damage and loss assessment tool that uses FEMA-P58 methodology. This tool was developed by Prof. Xinzheng Lu's research group at Tsinghua University [1].

    • PELICUN [Under development]: an efficient object-oriented damage and loss assessment python tool using FEMA-P58 methodology was developed by NHERI SimCenter and is currently being integrated with the regional simulation workflow.

  • Workflow: This directory contains scripts and examples to run the workflow with different configurations.

Other directories included in this repository are:

  • include: a directory containing header files or header-only libraries used by the workflow applications.

  • utils: a directory containing utility applications which are not an essential part of the workflow but can facilitate using some of the workflow applications.


  • C++11 compliant compiler: many of the workflow applications included use C++11 features, consequently they may need a newer C++11 compliant compiler.

  • OpenSees: The workflow applications require an installation of OpenSees to carry out structural analysis using the finite element method.

  • DAKOTA: The workflow applications require an installation of DAKOTA to handle and propagate the uncertainties defined in the input files for the workflow applications.

  • Python: The workflow requires Python 2.7.

  • Perl: The workflow makes use of a modified version of the DPrePro preprocessor Perl script distributed with DAKOTA, and thus requires Perl. Later releases may switch to the newer python version of the script as the Perl script is deprecated as of DAKOTA 6.8.

  • Conan package manager: This repository uses Conan for dependency management. Conan is a python library and can be installed using the following instructions

Building the source code on Unix-like systems

Before building the workflow, the following dependencies will need to be installed:

  1. GNU Compiler Collection (gcc & g++ ) version 4.8.1 or newer.
  2. GNU Make.
  3. CMake

This repository uses CMake for the build process. The general instructions for building the workflow application is as follows:

  1. Install the dependencies using Conan
conan install ..
  1. Use CMake to generate the make files
cmake ..
  1. Build the applications using the generated make files

Building the source code on Ubuntu Linux

Before building the source code on Ubuntu Linux and running it, the dependencies can be installed using the following commands:

sudo apt-get update
sudo apt-get install gcc g++ python perl

After installing the dependencies, building the workflow applications can then be done similar to other unix systems, using the instructions above for unix systems. Running the workflow applications will require installing other dependencies like OpenSees and DAKOTA. Instructions to building these software applications from their source code on Ubuntu Linux are available on their respective websites.

Building the source code on Windows

Building the workflow applications on Windows requires the following:

  1. Visual Studio 2017 community edition
  2. CMake

The steps to build all the applications are as follows:

  1. Install the dependencies using Conan
conan install ..
  1. Use CMake to generate the make files
cmake .. -G "Visual Studio 15 2017 Win64"
  1. Open the generated Visual Studio project (Project.sln) and build all the workflow applications.


Sample data files for regional simulation of Anchorage, Alaska are available in DesignSafe data depot in the community folder in the following location SimCenter/Datasets/AnchorageM7. If you cannot access the data, please contact the SimCenter using Slack or by email.

Pegasus Workflow

The Pegasus workflow can be found in the Pegasus directory.

Before submitting workflow, please run make to make sure all the executables required by the workflow have been built.

The workflow is set up to execute in two different execution environments: local HTCondor pool, Stampede 2 or TACC Wrangler. The first is good for small to medium sized runs as turnaround time is usually pretty good. Large workflows should be mapped to TACC Wrangler.

Submitting a workflow for local HTCondor pool execution can be done by executing:


Submitting to TACC Stampede2 can be done on the host with the command:

    ./submit-workflow stampede2
    ./submit-workflow wrangler

Testing Workflow Components

If you wish to try out existing workflow components with new parameters, or to develop new components, you may wish to consider using the 'test harness' provided in this repository. See the README in the tests directory for details.


NHERI SimCenter provides the source code of the regional earthquake simulation workflow as-is and makes no representations or warranties of any kind concerning the source code and the results obtained from them, whether expressed, implied, statutory, or other. This includes, without limitation, warranties of title, merchantability, fitness for a particular purpose, non-infringement, absence of latent or other defects, accuracy, or the presence or absence of errors, whether or not known or discoverable.


The SimCenter would like to acknowledge Prof. Jack Baker for his discussions about seismic hazard analysis, ground motion spatial correlation, selection and scaling of ground motion records, in addition to sharing Matlab codes developed by his research group to simulate spatially-correlated ground motions. The SimCenter would also like to acknowledge the contributions of OpenSHA, a library used by the hazard tool documented herein. We thank the Computational Infrastructure for Geodynamics which is funded by the National Science Foundation under awards EAR-0949446 and EAR-1550901. The SimCenter is supported by a grant from the National Science Foundation (NSF) under cooperative agreement CMMI 1612843. Materials in this document do not necessarily represent the views of NSF.


[1] Zeng X., Lu X.Z., Yang T., Xu Z., "Application of the FEMA-P58 methodology for regional earthquake loss prediction", Natural Hazards (2016), 10.1007/s11069-016-2307-z