RSQSim CyberShake - Revision history

Kmilner at 20:52, 3 July 2018

2018-07-03T20:52:01Z

Scottcal: /* Small-scale catalog, ERFID=42 */

2018-04-10T19:41:23Z

Small-scale catalog, ERFID=42

Kmilner at 17:42, 10 April 2018

2018-04-10T17:42:47Z

Kmilner at 19:10, 7 February 2018

2018-02-07T19:10:20Z

Kmilner at 19:08, 7 February 2018

2018-02-07T19:08:42Z

Kmilner: /* Rupture hierarchy */

2018-02-07T01:56:38Z

Rupture hierarchy

Kmilner at 01:33, 7 February 2018

2018-02-07T01:33:28Z

Kmilner at 01:23, 7 February 2018

2018-02-07T01:23:12Z

Kmilner at 01:14, 7 February 2018

2018-02-07T01:14:19Z

Kmilner at 01:08, 7 February 2018

2018-02-07T01:08:43Z

← Older revision		Revision as of 20:52, 3 July 2018
Line 95:		Line 95:
	* Catalog/ERF Mappings: /home/scec-02/kmilner/simulators/catalogs/rundir2585_1myrs/erf_mappings.bin		* Catalog/ERF Mappings: /home/scec-02/kmilner/simulators/catalogs/rundir2585_1myrs/erf_mappings.bin
	* ERF Metadata XML: /home/scec-02/kmilner/simulators/catalogs/rundir2585_1myrs/erf_params.xml		* ERF Metadata XML: /home/scec-02/kmilner/simulators/catalogs/rundir2585_1myrs/erf_params.xml
		+
		+	== 259k Year Candidate Catalog, ERFID=49 ==
		+
		+	This is a 250k year catalog which addresses some of the rupture propagation velocity issues seen with the previous CyberShake/RSQSim simulations. It is Bruce Shaw's Catalog 2740, and is inserted as ERF 29. We will initially test on 9 CyberShake sites (USC, PAS, WNGC, SBSM, STNI, LAPD, s119, s279, s480). The latter 3 sites are intended to help understand differences between 3-D CyberShake and 1-D broadband, and are chosen because they have high Vs30 values which are similar to the BBP 1-D Vs30 value for the LA Basin.
		+
		+	Catalog details:
		+	* Name: Bruce 2470 1myr
		+	* Average element area: 1.35 km^2
		+	* Min Mag Considered: 6.5
		+	* Num Events: 83,407 M>=6.5 events (1889 sources)
		+	* Catalog Duration Used: ~250k years
		+	* More information: https://github.com/kevinmilner/rsqsim-analysis/tree/master/catalogs/rundir2740
		+
		+	=== Input file locations ===
		+
		+	* SRF files: /home/scec-02/kmilner/simulators/catalogs/rundir2740/cybershake_inputs
		+	* Point files: /home/scec-02/kmilner/simulators/catalogs/rundir2740/cybershake_inputs
		+	* Catalog/ERF Mappings: /home/scec-02/kmilner/simulators/catalogs/rundir2740/erf_mappings.bin
		+	* ERF Metadata XML: /home/scec-02/kmilner/simulators/catalogs/rundir2740/erf_params.xml

@@ Line 65: / Line 65: @@
 | [[File:USC_5085_s33801.png|thumb|left|750px|Seismograms at USC for event 33801]]
 | [[File:event_33801.png|thumb|left|700px|event 33801, M7.71 on the SAF, Garlock, and San Jacinto]]
 |}

← Older revision		Revision as of 17:42, 10 April 2018
Line 66:		Line 66:
	\| [[File:event_33801.png\|thumb\|left\|700px\|event 33801, M7.71 on the SAF, Garlock, and San Jacinto]]		\| [[File:event_33801.png\|thumb\|left\|700px\|event 33801, M7.71 on the SAF, Garlock, and San Jacinto]]
	\|}		\|}
		+
		+	== 1m Year Candidate Catalog, ERFID=48 ==
		+
		+	The first 1 million year candidate catalog, an extension of Bruce's 2585 (the catalog used for the UCERF3 hazard comparison paper), is inserted as ERF 48. We will initially test on 6 CyberShake sites (USC, PAS, WNGC, SBSM, STNI, LAPD).
		+
		+	Catalog details:
		+	* Name: Bruce 2585 1myr
		+	* Average element area: 1.35 km^2
		+	* Min Mag Considered: 6.5
		+	* Num Events: 252,534 M>=6.5 events (3154 sources)
		+	* Catalog Duration Used: 1 million years
		+	* More information: https://github.com/kevinmilner/rsqsim-analysis/tree/master/catalogs/rundir2585_1myr
		+
		+	=== Input file locations ===
		+
		+	* SRF files: /home/scec-02/kmilner/simulators/catalogs/rundir2585_1myrs/cybershake_inputs
		+	* Point files: /home/scec-02/kmilner/simulators/catalogs/rundir2585_1myrs/cybershake_inputs
		+	* Catalog/ERF Mappings: /home/scec-02/kmilner/simulators/catalogs/rundir2585_1myrs/erf_mappings.bin
		+	* ERF Metadata XML: /home/scec-02/kmilner/simulators/catalogs/rundir2585_1myrs/erf_params.xml

@@ Line 25: / Line 25: @@
 *In the Ruptures table, we are setting NumRows and NumCols to 0, but using the correct value for NumPoints.
 *In the Ruptures table, Start/End Lat/Lon/Depth now represents the cube (in 3-d, non-rotated) which contains the entire rupture
-*In the CyberShake_Site_Ruptures table, Site_Rupture_Dist now represents rRup (3-d site/source distance) to the GMPE comparison "Significant Subsections" surface, which can be greater than Cutoff_Dist. This field is usually used to look at amplitudes with distance, so the closest raw rupture surface distance may not be appropriate. This listed distance can be either less or greater than the actual raw rupture distance. Ruptures included in this table are all ruptures for which the raw rupture distance is less than the cutoff dist. The raw rupture distance is used for cutoff distance checks.
+*In the CyberShake_Site_Ruptures table, Site_Rupture_Dist now represents rRup (3-d site/source distance) to the GMPE comparison "Significant Subsections" surface, which can be greater than Cutoff_Dist. This field is usually used to look at amplitudes with distance, so the closest raw rupture surface distance may not be appropriate. This listed distance can be either less or greater than the actual raw rupture distance. Ruptures included in this table are all ruptures for which the raw rupture distance is less than the cutoff dist. The horizontal distance to the center of the nearest raw rupture triangular element is used for cutoff distance checks.
 === Input file changes ===

@@ Line 9: / Line 9: @@
 [[File:Rsqsim_rupture_mapping.png|thumb|right|400px|RSQSim Rupture Types]]
 RSQSim catalogs generate ruptures on triangular elements. Those elements each have an associated UCERF3 fault subsection, which in turn has an associated fault section (e.g. Mojave S). GMPE comparisons use the associated UCERF3 subsections (after applying a filter to remove subsections for which only a few elements participate).
-*Raw RSQSim Rupture: the actual simulator elements that ruptured in the RSQSim event. This is what is used in CyberShake. NOTE: we also filter all elements which are more than 100km from the nearest mapped "Significant Subsection" in order to filter out stray elements which could have ruptured co-seismically (perhaps unrelated) in another part of the state but don't contribute to hazard)
+*Raw RSQSim Rupture: the actual simulator elements that ruptured in the RSQSim event. This is what is used in CyberShake (in the SRF, and for distance cutoff calculations). NOTE: we also filter all elements which are more than 100km from the nearest mapped "Significant Subsection" in order to filter out stray elements which could have ruptured co-seismically (perhaps unrelated) in another part of the state but don't contribute to hazard. [[:File:Rsqsim_stray_element_example.png|Example of rupture with stray elements to the N-W which are filtered out]])
 *Significant Subsections: mapped UCERF3 subsections for which at least 20% of each subsection (by area) participates in the rupture. This is what is used for GMPE comparisons, and some distance calculations in the database.
 Here is the structure for the RSQSim ERF:
@@ Line 25: / Line 25: @@
 *In the Ruptures table, we are setting NumRows and NumCols to 0, but using the correct value for NumPoints.
 *In the Ruptures table, Start/End Lat/Lon/Depth now represents the cube (in 3-d, non-rotated) which contains the entire rupture
-*In the CyberShake_Site_Ruptures table, Site_Rupture_Dist now represents rRup (3-d site/source distance) to the GMPE comparison "Significant Subsections" surface, which can be greater than Cutoff_Dist. This field is usually used to look at amplitudes with distance, so the closest raw rupture surface distance may not be appropriate. This listed distance can be either less or greater than the actual raw rupture distance. Ruptures included in this table are all ruptures for which the raw rupture distance is less than the cutoff dist.
+*In the CyberShake_Site_Ruptures table, Site_Rupture_Dist now represents rRup (3-d site/source distance) to the GMPE comparison "Significant Subsections" surface, which can be greater than Cutoff_Dist. This field is usually used to look at amplitudes with distance, so the closest raw rupture surface distance may not be appropriate. This listed distance can be either less or greater than the actual raw rupture distance. Ruptures included in this table are all ruptures for which the raw rupture distance is less than the cutoff dist. The raw rupture distance is used for cutoff distance checks.
 === Input file changes ===

← Older revision		Revision as of 01:33, 7 February 2018
Line 30:		Line 30:

	*Since the rupture geometry files also expect GridSpacing, NumRows, and NumCols, we are using the same approach as in the database. GridSpacing is replaced by AveArea, and NumRows and NumCols are replaced by NumPoints.		*Since the rupture geometry files also expect GridSpacing, NumRows, and NumCols, we are using the same approach as in the database. GridSpacing is replaced by AveArea, and NumRows and NumCols are replaced by NumPoints.
		+	*Hazard curve/disaggregations require an ERF specific XML file, erf_params.xml. This file also references paths to 2 files, a mappings binary file and a simulator geometry file. If this file is relocated, referenced files must be copied and paths updated in the XML file. TODO: fix disagg code to work with this file rather than hardcoded UCERF2

	=== Code changes ===		=== Code changes ===

@@ Line 7: / Line 7: @@
 === Rupture hierarchy ===
-RSQSim catalogs generate ruptures on triangular elements. Those elements each have an associated UCERF3 fault subsection, which in turn has an associated fault section (e.g. Mojave S). GMPE comparisons use the associated UCERF3 subsections (after applying a filter to remove subsections for which only a few elements participate). Here is the structure for the RSQSim ERF:
+[[File:Rsqsim_rupture_mapping.png|thumb|right|400px|RSQSim Rupture Types]]
-*Source: all ruptures which involve the same set of UCERF3 fault sections (aka 'parent sections'). Source names are all of the sections involved, and sources are sorted alphabetically
+RSQSim catalogs generate ruptures on triangular elements. Those elements each have an associated UCERF3 fault subsection, which in turn has an associated fault section (e.g. Mojave S). GMPE comparisons use the associated UCERF3 subsections (after applying a filter to remove subsections for which only a few elements participate).
 *Rupture: an individual RSQSim rupture (with it's own full slip/time history) that occurred in the RSQSim catalog. Ruptures are sorted by magnitude (increasing)
 *Rupture Variation: there is 1 rupture variation for each rupture, as each rupture has as slip/time history from RSQSim
@@ Line 18: / Line 25: @@
 *In the Ruptures table, we are setting NumRows and NumCols to 0, but using the correct value for NumPoints.
 *In the Ruptures table, Start/End Lat/Lon/Depth now represents the cube (in 3-d, non-rotated) which contains the entire rupture
-*In the CyberShake_Site_Ruptures table, Site_Rupture_Dist now represents rRup (3-d site/source distance) to the GMPE comparison surface, which can be greater than Cutoff_Dist. This field is usually used to look at amplitudes with distance, so the closest raw rupture surface distance may not be appropriate. This listed distance can be either less or greater than the actual raw rupture distance. Ruptures included in this table are all ruptures for which the raw rupture distance is less than the cutoff dist.
+*In the CyberShake_Site_Ruptures table, Site_Rupture_Dist now represents rRup (3-d site/source distance) to the GMPE comparison "Significant Subsections" surface, which can be greater than Cutoff_Dist. This field is usually used to look at amplitudes with distance, so the closest raw rupture surface distance may not be appropriate. This listed distance can be either less or greater than the actual raw rupture distance. Ruptures included in this table are all ruptures for which the raw rupture distance is less than the cutoff dist.
 === Input file changes ===

@@ Line 7: / Line 7: @@
 === Rupture hierarchy ===
-<Kevin, can you fill this in?>
+RSQSim catalogs generate ruptures on triangular elements. Those elements each have an associated UCERF3 fault subsection, which in turn has an associated fault section (e.g. Mojave S). GMPE comparisons use the associated UCERF3 subsections (after applying a filter to remove subsections for which only a few elements participate). Here is the structure for the RSQSim ERF:
 === Database changes ===
@@ Line 22: / Line 26: @@
 *A new version of DirectSynth, DirectSynth_RSQSim, was created, which takes in an input file consisting of a list of SRFs for processing.
-== Small-scale test ==
+== Small-scale catalog, ERFID=42 ==
-Initially, we are using a small RSQSim catalog (? kyrs, ? events) with elements with an average area of ~1.4 km^2, for testing on 4 CyberShake sites (USC, PAS, WNGC, SBSM).
+* SRF files: /home/scec-02/kmilner/simulators/catalogs/rundir2457/cybershake_inputs
 === Test seismograms ===