CyberShake PBR Study - Revision history

Maechlin: /* Example output.db Database Contents */

2013-03-23T00:15:49Z

Example output.db Database Contents

2013-03-22T22:20:02Z

2013-03-22T22:19:37Z

2013-03-22T22:15:43Z

Example output.db Database Contents

2013-03-22T22:15:25Z

Example output.db Database Contents

2013-03-22T19:04:49Z

Example output.db Database Contents

2013-03-22T19:03:32Z

Example output.db Database Contents

2013-03-22T19:01:46Z

Example output.db Database Contents

2013-03-22T19:01:30Z

2013-03-20T19:20:41Z

Example Results

@@ Line 11: / Line 11: @@
 *CVM Used: CVM-S4 (Model: 1)
-We have populated the database with data from the PACI2 site. For this initial database, we have included all rupture variations from the following rupture IDs and source IDs:
+We have populated the database with data from the PACI2 site. For this initial database, we have included rupture variations from the following rupture IDs and source IDs:
 <pre>
@@ Line 38: / Line 46: @@
 </pre>
-All seismograms were rotated to -64 degrees before calculating the PSA values.
+All seismograms were rotated to -64 degrees before calculating the PSA values. In our results, we show two components of amplitudes, and we show both the NS-oriented amplitudes, and the rotated amplitudes to help check these results.
 == Example Results ==

@@ Line 6: / Line 6: @@
 The example output.db contains information from the low-frequency component of the CyberShake 2.2 runs. The amplitudes in this data file were calculated using CyberShake codes and the following input parameters:
-ERF Used: UCERF 2 (ERF ID: 35)<br />
+*ERF Used: UCERF 2 (ERF ID: 35)<br />
-Rupture Generator Used: Graves 3.2 (Rupture Variation Scenario: 4)<br />
+*Rupture Generator Used: Graves 3.2 (Rupture Variation Scenario: 4)<br />
-SGT Software Used: (GP V3.03) SGT Variation ID: 5<br />
+*SGT Software Used: (GP V3.03) SGT Variation ID: 5<br />
-CVM Used: CVM-S4 (Model: 1)
+*CVM Used: CVM-S4 (Model: 1)
 We have populated the database with data from the PACI2 site. For this initial database, we have included all rupture variations from the following rupture IDs and source IDs:

@@ Line 4: / Line 4: @@
 == Example output.db Database Contents ==
-The example output.db contains information from the low-frequency component of the CyberShake 2.2 runs. Specifically, this refers to:
+The example output.db contains information from the low-frequency component of the CyberShake 2.2 runs. The amplitudes in this data file were calculated using CyberShake codes and the following input parameters:
-UCERF 2 (ERF ID: 35)<br />
+ERF Used: UCERF 2 (ERF ID: 35)<br />
-Rupture Generator: Graves 3.2 (Rupture Variation Scenario: 4)<br />
+Rupture Generator Used: Graves 3.2 (Rupture Variation Scenario: 4)<br />
-SGT Variation ID: 5<br />
+SGT Software Used: (GP V3.03) SGT Variation ID: 5<br />
-Velocity Model: CVM-S4 (Model: 1)
+CVM Used: CVM-S4 (Model: 1)
-I have populated the database with data from the PACI2 site. Specifically I have included all rupture variations from the following rupture IDs and source IDs:
+We have populated the database with data from the PACI2 site. For this initial database, we have included all rupture variations from the following rupture IDs and source IDs:
 <pre>

@@ Line 9: / Line 9: @@
 Rupture Generator: Graves 3.2 (Rupture Variation Scenario: 4)<br />
 SGT Variation ID: 5<br />
-Velocity Model CVM-S4 (Model: 1)
+Velocity Model: CVM-S4 (Model: 1)
 I have populated the database with data from the PACI2 site. Specifically I have included all rupture variations from the following rupture IDs and source IDs:

@@ Line 6: / Line 6: @@
 The example output.db contains information from the low-frequency component of the CyberShake 2.2 runs. Specifically, this refers to:
-ERF ID: 35<br />
+UCERF 2 (ERF ID: 35)<br />
-Rupture Variation Scenario: 4<br />
+Rupture Generator: Graves 3.2 (Rupture Variation Scenario: 4)<br />
 SGT Variation ID: 5<br />
-Model: 1 (CVM-S)
+Velocity Model CVM-S4 (Model: 1)
 I have populated the database with data from the PACI2 site. Specifically I have included all rupture variations from the following rupture IDs and source IDs:

@@ Line 1: / Line 1: @@
 This CyberShake Precarious Balanced Rock Study will evaluate whether CyberShake ground motions are likely to knock over known Precarious Rocks. Here we define the processing inputs and outputs for this study.
 [[image:New_PBRs.png|200px|thumb|right]]
 == Example Results ==

@@ Line 14: / Line 14: @@
 </pre>
-*First Row: Name, Study number, Site Number, Rotation Angle)
+*First Row: Name, Hazard Dataset ID: Data we pulled from (21 = CyberShake 2.2, low frequency), Azimuth: Rotation Angle
 *Second Row: Source, Rupture, Variation
 *Intensity Measures (in cm/sec2, cm/sec):