CyberShake Rupture Files - Revision history

Scottcal at 20:49, 22 December 2025

2025-12-22T20:49:50Z

Scottcal: /* RSQSim files */

2018-02-01T20:44:34Z

RSQSim files

Scottcal at 17:55, 1 February 2018

2018-02-01T17:55:41Z

Scottcal: /* Rupture Variation files */

2018-02-01T05:02:38Z

Rupture Variation files

Scottcal at 22:06, 31 January 2018

2018-01-31T22:06:37Z

Scottcal: Created page with "CyberShake uses rupture files to provide descriptions of rupture geometry, and, in some cases, slip information about individual events to be simulated. A description of thes..."

2018-01-31T21:32:17Z

Created page with "CyberShake uses rupture files to provide descriptions of rupture geometry, and, in some cases, slip information about individual events to be simulated. A description of thes..."

New page

CyberShake uses rupture files to provide descriptions of rupture geometry, and, in some cases, slip information about individual events to be simulated. A description of these files is below.

== UCERF2 files ==

To date, all CyberShake simulations have been performed using UCERF 2 events. These events can include both a rupture geometry file and a Standard Rupture Format (SRF) description of the event itself.

=== UCERF2 Rupture Geometry Files ===

Rupture geometry files contain a list of all the points which appear on the surface of the rupture. This information is needed to determine which SGTs should be saved (so that we have an SGT for each point on every rupture surface), and to generate a rupture variation when passed into the RupGen-api code. We can also use the rupture geometry to generate the list of points we need SGTs for when doing post-processing. Since 2014, we have tried to replace the SRF with the rupture geometry whenever possible, as it is a much smaller file and therefore reduces I/O.

The format of the rupture geometry files is:

Probability = <prob>
Magnitude = <mag>
GridSpacing = <spacing between elements, in km>
NumRows = <# rows>
NumCols = <# cols>
# Lat Lon Depth Rake Dip Strike
<data for (row 0,col 0)>
<data for (row 0,col 1)>
...
<data for (row 0,col c)>
<data for (row 1,col 0)>
...
<data for (row r,col c)>

A 'row' is defined as a set of rupture points all at the same depth, and rows are listed in the file from shallowest to deepest.

For ERF 35, we used 1 km spacing; this should be used with 0.5 Hz simulations. For ERF 36, we used 200 m spacing; this should be used with 1 Hz simulations.

These files are stored in <CyberShake root>/ruptures/Ruptures_erf<ERF ID>/<src ID>/<rup ID>/<src>_<rup>.txt. The path to the top-level ruptures directory is specified in [[CyberShake_Code_Base#Configuration_file | cybershake.cfg]], and the substructure is assumed in the [[CyberShake_Code_Base#PreSGT | PreSgt]] code.

The geometry files for ERF 35 and ERF 36 are available here: [http://hypocenter.usc.edu/research/cybershake/Ruptures_erf35.tgz ERF 35](127 MB) and here: [http://hypocenter.usc.edu/research/cybershake/ruptures_erf36.tgz ERF 36](3.9 GB)

=== Rupture Variation files ===

Initially, we precomputed rupture variations for all events and saved these to disk. This was done for the Graves & Pitarka (2006) (Rupture Variation Scenario ID 3) and Graves & Pitarka (2010) (Rup Var Scenario ID 4). The

== RSQSim files ==

@@ Line 59: / Line 59: @@
 </pre>
-Roughly speaking, the points are in order of depth fastest, then moving from one end of the rupture to the other.
+No order should be assumed for the points.
 These files will use the same directory structure (<CyberShake root>/ruptures/Ruptures_erf<ERF ID>/<src ID>/<rup ID>/<src>_<rup>.txt).

@@ Line 37: / Line 37: @@
 Initially, we precomputed rupture variations for all events and saved these to disk.  This was done for the Graves & Pitarka (2006) (Rupture Variation Scenario ID 3) and Graves & Pitarka (2010) (Rup Var Scenario ID 4).  These SRFs can be found on SCEC disks at /home/rcf-104/CyberShake2007/ruptures/RuptureVariations_35_V2_3 (Rup Var Scenario ID 3) and /home/rcf-104/CyberShake2007/ruptures/RuptureVariations_35_V3_2 (Rup Var Scenario ID 4), using the same <src id>/<rup id> directory hierarchy as the rupture geometry files.
-Starting in 2012, we stopped writing out all the SRFs.  Instead, they are generated on-demand in memory during the post-processing.  However, these files can still be generated by calling the _write_srf() function in genslip.  They follow the SRF format; version 1 is documented [http://www.example.com here] and version 2 [http... here].
+Starting in 2012, we stopped writing out all the SRFs.  Instead, they are generated on-demand in memory during the post-processing.  However, these files can still be generated by calling the _write_srf() function in genslip.  They follow the SRF format; version 1 is documented [http://hypocenter.usc.edu/research/cybershake/srf4.pdf here] and version 2 [http://hypocenter.usc.edu/research/cybershake/SRF-Description-Graves_2.0.pdf here].
 == RSQSim files ==

@@ Line 31: / Line 31: @@
 These files are stored in <CyberShake root>/ruptures/Ruptures_erf<ERF ID>/<src ID>/<rup ID>/<src>_<rup>.txt.  The path to the top-level ruptures directory is specified in [[CyberShake_Code_Base#Configuration_file | cybershake.cfg]], and the substructure is assumed in the [[CyberShake_Code_Base#PreSGT | PreSgt]] code.
-The geometry files for ERF 35 and ERF 36 are available here: [http://hypocenter.usc.edu/research/cybershake/Ruptures_erf35.tgz ERF 35](127 MB) and here: [http://hypocenter.usc.edu/research/cybershake/ruptures_erf36.tgz ERF 36](3.9 GB)
+The geometry files for ERF 36 are available here: [https://g-3a9041.a78b8.36fe.data.globus.org/cybershake/ruptures_erf36.tgz ERF 36](4.1 GB)
 === Rupture Variation files ===

@@ Line 11: / Line 11: @@
 The format of the rupture geometry files is:
-Probability = <prob>
+ Probability = <prob>
-Magnitude = <mag>
+ Magnitude = <mag>
-GridSpacing = <spacing between elements, in km>
+ GridSpacing = <spacing between elements, in km>
-NumRows = <# rows>
+ NumRows = <# rows>
-NumCols = <# cols>
+ NumCols = <# cols>
-#   Lat         Lon         Depth      Rake    Dip     Strike
+ #   Lat         Lon         Depth      Rake    Dip     Strike
-<data for (row 0,col 0)>
+ <data for (row 0,col 0)>
-<data for (row 0,col 1)>
+ <data for (row 0,col 1)>
-...
+ ...
-<data for (row 0,col c)>
+ <data for (row 0,col c)>
-<data for (row 1,col 0)>
+ <data for (row 1,col 0)>
-...
+ ...
-<data for (row r,col c)>
+ <data for (row r,col c)>
 A 'row' is defined as a set of rupture points all at the same depth, and rows are listed in the file from shallowest to deepest.