• Wavelet and simulated Annealing SliP inversion (WASP)
  • Suggested Citation
  • Authors
  • References
• Installation
  • Prerequisites
  • Wasp Installation Scripts
• Local Testing
• Using the Docker Image
  • Building the docker image locally
  • Run the docker image interactively
  • Run full end to end tests in the container

Wavelet and simulated Annealing SliP inversion (WASP)

---

This code uses a nonlinear simulated annealing inversion method to model slip amplitude, rake, rupture time, and rise time on a discretized fault plane, finding the solution that best fits the observations in the wavelet domain. WASP currently accomodates observations from (1) teleseismic broadband stations, (2) regional strong-motion accelerometer stations, (3) static and high-rate Global Navigation Satellite Systems stations, and (4) Interferometric Synthetic Aperture Radar.

The inversion approach is based on the method of Ji et al. (2002, 2003) and Shao et al. (2011). The original inversion package was developed by Dr. Chen Ji. Koch et al. (2019) modified the heuristic rules used to automatically define the search ranges for finite-fault inversions based on the moment tensor solution, and incorporated regional strong-motion waveforms into the workflow. They also converted the codebase of the software package from Fortran 77 to Fortran 95, improving its flexibility. Goldberg et al. (2022) enabled the integration of satellite geodetic observations into the inversion framework.

The Regional Green's functions are calculated using the method of Zhu & Rivera (2002).

Suggested Citation

Koch, P., Goldberg, D.E., Hunsinger, H., Melgar, D., Riquelme, S., Yeck, W.L., and Haynie, K.L., 2024, Wavelet and simulated Annealing SliP inversion (WASP), version 1.0.0: U.S. Geological Survey software release, https://doi.org/10.5066/P1EKKUNW.

Authors

• Pablo Koch - National Seismological Center, University of Chile
• Dara E. Goldberg - National Earthquake Information Center (NEIC) of the Geologic Hazards Science Center
• Heather Hunsinger - Geologic Hazards Science Center
• Diego Melgar - Department of Earth Sciences, University of Oregon
• Sebastian Riquelme - National Seismological Center, University of Chile
• William L. Yeck - National Earthquake Information Center (NEIC) of the Geologic Hazards Science Center
• Kirstie L. Haynie - Geologic Hazards Science Center

References

Users of this code should consider citing the following relevant publications:

• Ji, C., D. J. Wald, and D. V. Helmberger (2002). Source description of the 1999 Hector Mine, California, earthquake, Part I: Wavelet domain inversion theory and resolution analysis, Bulletin of the Seismological Society of America, 92, no. 4, 1192–1207, https://doi.org/10.1785/0120000916.
• Ji, C., D. V. Helmberger, D. J. Wald, and K. F. Ma (2003). Slip history and dynamic implications of the 1999 Chi-Chi, Taiwan, earthquake, Journal of Geophysical Research, 108, no. B9, https://doi.org/10.1029/2002jb001764. Shao, G. F., X. Y. Li, C. Ji, and T. Maeda (2011). Focal mechanism and slip history of the 2011 M-w 9.1 off the Pacific coast of Tohoku Earthquake, constrained with teleseismic body and surface waves, Earth Planets and Space, 63, no. 7, 559-564, https://doi.org/10.5047/eps.2011.06.028.
• Koch, P., F. Bravo, S. Riquelme, and J. G. F. Crempien (2019). Near-real-time finite-fault inversions for large earthquakes in Chile using strong-motion data, Seismological Research Letters, 90, no. 5, 1971–1986, https://doi.org/10.1785/0220180294.
• Goldberg, D. E., P. Koch, D. Melgar, S. Riquelme, and W. L. Yeck (2022). Beyond the Teleseism: Introducing Regional Seismic and Geodetic Data into Routine USGS FiniteFault Modeling, Seismological Research Letters, 93, 3308–3323, https://doi.org/10.1785/0220220047.
• Zhu, L., & Rivera, L. A. (2002). A note on the dynamic and static displacements from a point source in multilayered media: A note on the dynamic and static displacements from a point source. Geophysical Journal International, 148(3), 619–627. https://doi.org/10.1046/j.1365-246X.2002.01610.x.

Disclaimer and License Information

Disclaimer License

Installation

Prerequisites

In order to compile and/or install the source code there are a number of prerequisite requirements:

1. gfortran: To compile the code in fortran_code
2. cmake: To compile the code in fortran_code
3. gcc: To provide support to miniforge/conda for compiling c code
4. miniforge/conda: To install python dependencies. Miniforge can be installed using the provided script: miniforge_install.sh

Wasp Installation Scripts

Automated installation of the dependencies and fortran code has been provided in the form of the install script install.sh. Currently this install script only supports installation on linux systems as the fortran code cannot be compiled on MacOS. To instal the code please ensure that all of the prerequisites are available and miniforge/miniconda/anaconda environment has been initialized

1. source install.sh <path to the local neic-finitefault repository> (with other optional configurations available, run sudo bash user_install.sh -h for the help information)

   1. NOTE: The scripts in ./install.d may be run individually to suit the individuals needs. For example, to only rerun compilation of the fortran you can singularly run wasp.sh.

2. conda activate ff-env

The following documents provide more information about the installation process:

• Data Dependencies: Provides a list of data required to run the code
• Code Dependencies: Provides a list of dependencies required to run the code
• Manual Installation: Provides a list of steps to manually install dependencies and code without reference to a specific operating system.

Local Testing

Tests and linting can both be run locally:

1. To run all python unit tests: poe test
   1. The full end to end inversion tests take a consideral amount of time to run. As a result, they are skipped by default and can be enabled by setting the following environment variables to "True"
      • RUN_ALL
      • RUN_END_TO_END
2. To run python linting: poe lint

Using the Docker Image

This repository provides a Dockerfile to locally build a docker image for the dependencies and source code. Below are some creating and using the image. See the Dockerfile for the build steps/configuration.

While these commands listed are docker commands. The commands should be 1 to 1 with Podman commands. Replace the word "docker" in the command with "podman".

Building the docker image locally

1. Go to the top level of your local repository: cd <path to the local repository>
2. Build the image: docker build .
   • Useful Optional Flags (must come before specifying the location of the Dockerfile):
     • give the image a name: -t <name>
     • build to a specific layer: --target <layer name>
       • Available layers: packages, wasp-python, wasp-fortran, wasp-dependencies, wasp
     • add a build argument: --build-arg <KEY>=<VALUE>
       • Available argument keys: FROM_IMAGE

Run the docker image interactively

• docker run --rm -i <name> bash
  • Useful Optional Flags (must come before the name and specifying a bash shell):
    • mount the image to a local directory: -v <path to local directory>:<path to location in the docker container>
    • open a port (might be useful for jupyter notebooks that need to display on a web browser): -p <host port>: <container port>

Run full end to end tests in the container

• docker run <name>