CyberShake Data
This page provides an overview of CyberShake Data, and how to access it.
CyberShake data can be broken down into the following elements based on when it is used in simulations:
- Input data needed for CyberShake runs, such as which ruptures go with which site. This information is stored in the CyberShake database.
- Temporary data generated during CyberShake production runs. This data remains on the cluster and is purged.
- Output data products generated by CyberShake runs. This data is transferred from the cluster to SCEC disks, and some of it is inserted into the CyberShake database for quick access.
We will focus on (1) and (3).
Contents
CyberShake database overview
CyberShake data is served through 2 on-disk relational database servers running MySQL/MariaDB, and an SQLite file for each past study.
MySQL/MariaDB Databases
The two databases used to store CyberShake data are focal.usc.edu ('focal') and moment.usc.edu ('moment').
Moment DB
Moment is the production database server. Currently, it maintains all the necessary inputs, metadata on all CyberShake runs, and results for Study 15.12 and Study 17.3.
Read-only access to moment is:
host: moment.usc.edu user: cybershk_ro password: CyberShake2007 database: CyberShake
Focal DB
Focal is the database server for external user queries. We plan to remove all but the most recent few studies from focal, but this is still in progress, so for now focal has all inputs, metadata, and results up through Study 15.12.
Read-only access to focal is:
host: focal.usc.edu user: cybershk_ro password: CyberShake2007 database: CyberShake
SQLite files
CyberShake input data
At the beginning of a CyberShake run, the database is queried to determine site information (name, latitude, longitude). This can be found in the CyberShake_Sites table.
The database is also used to determine which ruptures fall within the 200 km cutoff. This information is used to construct the necessary volume and select the correct rupture files for processing. This can be found in the CyberShake_Site_Ruptures table, which contains a list of ruptures for each site which fall within a given cutoff.
Both of these tables are populated by Kevin when we select new sites for CyberShake processing.
CyberShake output data
CyberShake runs produce the following output data, divided into data staged back from the cluster, and local data products:
Data staged from cluster:
- Seismograms
- Peak spectral acceleration
- RotD results (for some studies)
- Duration results (for some studies)
Local data products:
- Hazard curves
- Disaggregation results
- Hazard maps
CyberShake Output File Access
Seismogram access is detailed at Accessing CyberShake Seismograms.
The CyberShake database has a variety of information about each rupture.
Information on accessing ERF data, rupture data, and hazard curve data is available at [CyberShake DB Queries].
To distinguish between the different rupture generators, velocity models, ERFs at different resolutions, etc., you need to know the correct IDs to use. The wiki pages for each Study detail the IDs which are relevant for that study.
CyberShake Data Request Website
We have developed a prototype CyberShake data access website. It can retrieve the most common CyberShake data requests for our most recent CyberShake Simulations. It may be useful as a way to review the types of data products available from a CyberShake Hazard Model. At this time, however, it requires a SCEC login (username/pwd) to use. Please request a SCEC login if you with to try this access method. A description and link to the site is below:
