Skip to content

Data Access

Philip Maechling edited this page Jun 4, 2022 · 1 revision

Methods for accessing CyberShake data

The following are our venues for distributing CyberShake data and metadata:

  • Study wiki pages, hosted on strike.scec.org, an AWS instance
  • A public MariaDB database (focal.usc.edu)
  • For each study, we create a stand-alone SQLite database with the MariaDB content for that study. This database is stored in a single file, which can then be distributed to users. It’s often faster than the MariaDB database, especially for complex queries, though it can be several hundred GB in size.
  • The project filesystem at USC CARC.
  • A public Globus collection.

Study metadata

  • Distributed through study wiki pages
  • MariaDB database
  • SQLite database

Hazard Maps

  • Linked from study wiki pages

Hazard Curves

  • MariaDB database for selected periods
  • SQLite database for selected periods

Intensity measures (geometric mean PSA, RotD PSA, duration)

  • MariaDB database for selected periods
  • SQLite database for selected periods
  • Project filesystem at USC CARC has intensity measure files for all periods
  • Intensity measures for Study 15.12 are available through the Globus collection

Seismograms

  • Project filesystem at USC CARC has all seismograms
  • Seismograms for Study 15.12 are available through the Globus collection

Planned CyberShake data access tool

  • Goal is to simplify access to CyberShake data, particularly data files on project filesystem at USC CARC
  • Python application
  • Prompts the user with questions to determine what subset of data to retrieve
  • Queries the database to retrieve intensity measures and metadata
  • Interfaces with Globus collection to retrieve requested data files