Difference between revisions of "CyberShake Data for Asimaki Team"
| Line 5: | Line 5: | ||
As an initial test, we've retrieved CyberShake Study 22.12 low-frequency RotD50 data for 6 sites (LADT, PAS, SBSM, STNI, USC, WNGC) at 6 periods (2, 3, 4, 5, 7.5, 10 sec). | As an initial test, we've retrieved CyberShake Study 22.12 low-frequency RotD50 data for 6 sites (LADT, PAS, SBSM, STNI, USC, WNGC) at 6 periods (2, 3, 4, 5, 7.5, 10 sec). | ||
| − | === | + | === Database data format === |
The data is available as a SQLite file, downloadable here. | The data is available as a SQLite file, downloadable here. | ||
| Line 31: | Line 31: | ||
*IM_Period: RotD50 period | *IM_Period: RotD50 period | ||
*IM_Value: RotD50 acceleration value, in cm/s2. | *IM_Value: RotD50 acceleration value, in cm/s2. | ||
| + | |||
| + | === Distance metrics === | ||
| + | |||
| + | As part of his GMM calculations, Kevin calculates a number of distance metrics needed for the NGAWest2 GMMs. A zip file containing CSVs for each site, with Rrup, Rjb, Rx, and Ry0 is available here. | ||
Revision as of 21:15, 19 May 2023
This page documents assembling CyberShake 22.12 data for the Asimaki Team in spring 2023.
Initial data retrieval
As an initial test, we've retrieved CyberShake Study 22.12 low-frequency RotD50 data for 6 sites (LADT, PAS, SBSM, STNI, USC, WNGC) at 6 periods (2, 3, 4, 5, 7.5, 10 sec).
Database data format
The data is available as a SQLite file, downloadable here.
The SQLite database consists of two tables, CyberShake_Site_Info and IM_Data.
The CyberShake_Site_Info schema is: CyberShake_Site_Info (Site_Name TEXT, Site_Lat REAL, Site_Lon REAL, Model_Vs30 REAL, Z1_0 REAL, Z2_5 REAL)
- Site_Name: the 3-5 character CyberShake site name
- Site_Lat: the latitude of the site
- Site_Lon: the longitude of the site
- Model_Vs30: The Vs30 value, created by querying the velocity model at 1-meter increments in the range [0.5, 29.5] and taking the slowness average. Note that for CyberShake, we apply a Vs floor of 500 m/s when we generate the velocity mesh used for the simulations. Therefore, values less than 500 m/s in the model aren't "seen" by the simulations.
- Z1_0: The Z1.0 value. We determine this value by querying the model in 10-meter increments, and selecting the point at which the Vs value crosses from below 1000 m/s to above. If the value crosses more than once, we use the 2nd crossing.
- Z2_5: The Z2.5 value. As with Z1.0, we query the model in 10-meter increments and select the point where Vs crosses from below 2500 m/s to above. If there are multiple crossings, we use the 2nd crossing.
The IM_Data schema is: IM_Data (Site_Name TEXT, Run_ID INTEGER, Source_ID INTEGER, Rupture_ID INTEGER, Rup_Var_ID INTEGER, Magnitude REAL, Site_Rupture_Dist REAL, IM_Period REAL, IM_Value REAL)
- Site_Name: the 3-5 character CyberShake site name
- Run_ID: the CyberShake run ID associated with the Study 22.12 LF run for this site
- Source_ID: the source ID of the event, assigned in UCERF2
- Rupture_ID: the rupture ID of the event, assigned in UCERF2
- Rup_Var_ID: the rupture variation ID of the event, which identifies a unique hypocenter location and slip distribution
- Magnitude: magnitude of the event. Note that all rupture variations for the same source ID and rupture ID will share the same magnitude.
- Site_Rupture_Dist: a distance metric between the site and rupture. I believe this is the shortest distance between the site and any point on the rupture surface.
- IM_Period: RotD50 period
- IM_Value: RotD50 acceleration value, in cm/s2.
Distance metrics
As part of his GMM calculations, Kevin calculates a number of distance metrics needed for the NGAWest2 GMMs. A zip file containing CSVs for each site, with Rrup, Rjb, Rx, and Ry0 is available here.
