CyberShake PBR Study

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.

Example output.db Database Contents

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)
  
• Rupture Generator Used: Graves 3.2 (Rupture Variation Scenario: 4)
  
• SGT Software Used: (GP V3.03) SGT Variation ID: 5
  
• CVM Used: CVM-S4 (Model: 1)

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:

• 55 S. San Andreas;CC+BB+NM+SM
• 64 S. San Andreas;CH+CC+BB+NM+SM
• 85 S. San Andreas;PK+CH+CC+BB+NM+SM
• 86 S. San Andreas;PK+CH+CC+BB+NM+SM+NSB
• 91 S. San Andreas;SM+NSB
• 92 S. San Andreas;SM+NSB+SSB

Source_id Rupture_id
85	4
85	3
85	2
85	5
86	3
64	3
86	2
64	4
86	4
85	1
64	2
86	1
55	2
55	3
64	5
92	2
92	3
91	3
91	4
86	5
91	2

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

-bash-4.1$ ./pbrquery.py output.db showall
Site Name: PACI2 (Hazard Dataset ID: 21, Azimuth: -64.0)
Source: 85     Rupture: 4     Variation: 284
    PGA       PGV       PSA5.0    PSA3.0    PSA1.0    PSA0.5    PSA0.1
NS  41.99654  30.78150  62.22515  162.39929 44.31287  43.04405  42.46454  
EW  38.32506  37.59424  80.60545  108.30460 42.63656  38.89466  38.69648  
RNS 31.39390  30.78150  79.57469  84.12362  36.67549  32.69110  31.81637  
REW 43.25701  37.59424  67.67639  170.74208 46.27419  43.80020  43.67790  

• 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):
• NS, EW - Un-rotated components
• RNS, REW - Rotated components

We show both results to help check rotation results.

Querying

Querying the sqlite database can be done through pbrquery.py. It supports three commands:

./pbrquery.py output.db showall

This command will dump everything in the database, output.db.

./pbrquery.py output.db sites

This command will show all the sites in the database, output.db.

./pbrquery.py output.db query [site=PACI2] [source=85] [rupture=4] [variation=2]

This command will display only sites matching the given parameters. So, for example, if we wanted values for all sites on source 85, rupture 4, we would do:

./pbrquery.py output.db query source=85 rupture=4

If we wanted to see all PACI2 sites:

./pbrquery.py output.db query site=PACI2

If we wanted to see all variation 7 sites:

./pbrquery.py output.db query variation=7

All scripts located at /home/scec-00/davidgil/cybershake_pbr

High Freq Sites

• High Frequency Curves
• USC 34.0192 -118.286
• s758 33.37562 -117.53532
• WNGC 34.041824 -118.0653
• STNI 33.93088 -118.17881
• LADT 34.05204 -118.25713
• S351 34.21142 -118.21085

PBR Sites

• Fall 2011 PBR Sites
• Perris PERR2 838
• UCR UCR 839
• Moreno Valley MRVY 840
• Mt. Marie Louise N Grass Valley 3 GV03 841
• Mt. Marie Louise N Grass Valley 5 GV05 842
• Black Butte BKBU 843
• Lovejoy Buttes LBUT2 844
• Piute Butte 1 PIBU 845
• Nuevo 2 NUEVO 846
• Perris Rimrock 1 PERRM 847
• Mockingbird Van Buren MKBD 848
• Gopher Gulch GOPH 849
• Gibraltar GLBT 850
• Pacifico 1 SG PACI2 851
• Punchbowl 1 PBWL 852
• Lake Mathews Drive LMAT 853
• Lake Perris N LPER 854
• Acton ACTN 855

Steps

1. Identify CS code to calculate peak amps
2. Combine rotation and peak amp calls
3. define PBR processing output format schema
4. implement cs_pbr table in sqllite
5. write tests that load simple data sets, and shows a query that will produce the output table above
6. write query to find 10 ruptures close to PERR2
7. Estimate Rotation Angle of each fault
8. processing 20 PERR2 ruptures

Program inputs:

The user configurable parameters that should be input to our rotation program include:

• CyberShake_Study_ID: 35 #CyberShake 1.0 = 35, CyberShake 2.2 = 40
• CyberShake_Site_Name: PERR2 #Site Short Name
• Rotation_Angle: -40.0 # Decimal Degrees from North
• List of Ruptures (with wildcards permitted):
  • SourceID/*
  • SourceID/RuptureID/*
  • SourceID/RuptureID/VariationID

Example Simulation Configuration File

#
# CS PBR Processing Configuration File
#
# cs_study_ids:
# 35 is CyberShake 1.0
# 40 is CyberShake 2.2
#
cs_study_id = 35
#
# cs_site_name:
# PERR2 is Perris PBR
# GV03 is Marie Louise Grass Valley
cs_site_name = PERR2
#
# rotation: Decimal degrees
# 0 = ns
# -40 = 40 degrees counter clockwise
rotation = -40.0
#
# Variation List:
# src.rup.varid
# src.rup.*
# src.*
variation = 12.20.15

Program Outputs:

The program should produce an sqllite data file that can be queried to produce a report, with a list of rows for each rupture variation, with the following columns in each row

• CyberShakeStudyID:
• SiteName:
• SiteNumber:
• RotationAngle:
• SourceID:
• RuptureNumber:
• VariationNumber:
• NS_PGA (m/s/2):
• NS_PGV (m/s):
• NS_PSA5.0 (m/s/s):
• NS_PSA3.0 (m/s/s):
• NS_PSA1.0 (m/s/s):
• NS_PSA0.5 (m/s/s):
• NS_PSA0.1 (m/s/s):
• Rot_PGA (m/s/2):
• Rot_PGV (m/s):
• Rot_PSA5.0 (m/s/s):
• Rot_PSA3.0 (m/s/s):
• Rot_PSA1.0 (m/s/s):
• Rot_PSA0.5 (m/s/s):
• Rot_PSA0.1 (m/s/s):