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 used as the production database server. Currently, it maintains all the necessary
Focal DB
SQLite files
Because of performance issues, we could no longer keep all past studies in the
CyberShake rupture info
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 Seismogram Access
This is detailed at Accessing CyberShake Seismograms.
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:
