CyberShake Study 22.10
CyberShake Study 22.10 is a proposed study in Southern California which will include deterministic low-frequency (0-1 Hz) and stochastic high-frequency (1-50 Hz) simulations. We will use the Graves & Pitarka (2019) rupture generator and the high frequency modules from the SCEC Broadband Platform v22.4.
- 1 Status
- 2 Data Products
- 3 Science Goals
- 4 Technical Goals
- 5 Sites
- 6 Velocity Model
- 7 High-frequency codes
- 8 Spectral Content around 1 Hz
- 9 Verification
- 10 Updates and Enhancements
- 11 Output Data Products
- 12 Computational and Data Estimates
- 13 Lessons Learned
- 14 Stress Test
- 15 Performance Metrics
- 16 Production Checklist
- 17 Presentations, Posters, and Papers
This study is in the planning phase. We estimate calculations will begin in October 2022.
We are planning to use CVM-S4.26 with a GTL applied, and the CVM-S4 1D background model outside of the region boundaries.
We are investigating applying the Ely-Jordan GTL down to 700 m instead of the default of 350m. We extracted profiles for a series of southern California CyberShake sites, with no GTL, a GTL applied down to 350m, and a GTL applied down to 700m.
Sites (the CVM-S4.26 basins are outlined in red):
These are for sites outside of the CVM-S4.26 basins:
|Site||No GTL||350m GTL||700m GTL|
These are for sites inside of the CVM-S4.26 basins:
|Site||No GTL||350m GTL||700m GTL|
Our proposed algorithm for generating the velocity model is as follows:
- Query the CVM-S4.26 model ('cvmsi' string in UCVM) for each grid point.
- Check the Vs value at the grid point latitude and longitude with depth=0:
- If Vs<1000, leave the data unchanged.
- If Vs>=1000, then apply the Ely GTL using 700m as the transition depth.
- We will populate the surface mesh point by querying at a depth of 25m, after the GTL modification has been made.
For this study, we will use the Graves & Pitarka high frequency module (hb_high) from the Broadband Platform v22.4, hb_high_v6.0.5. We will use the following parameters. Parameters in bold have been changed for this study.
|nbu||4 (not used)|
|ifft||0 (not used)|
|flol||0.02 (not used)|
|fhil||19.9 (not used)|
|irand||Seed used for generating SRF|
|tlen||Seismogram length, in sec|
|fmax||10 (not used)|
|rvfac||Calculated using BBP hfsims_cfg.py code|
Spectral Content around 1 Hz
We investigated the spectral content of the Broadband CyberShake results in the 0.5-3 second range, to look for any discontinuities.
The plot below is from WNGC, Study 15.12 (run ID 4293).
Below is a plot of the hypocenters from the 706 rupture variations which meet the target.
These events have a different distribution than the rupture variations as a whole.
|Fault||Percent of target RVs||Percent of all RVs|
Additionally, 88% of the selected events have a magnitude greater than the average for their source. 4% are average, and 8% are lower.
Below is a spectral plot but which includes all rupture variations and the overall mean (in orange).
We created spectral plots for 7 additional sites (STNI, SBSM, PAS, LGU, LBP, ALP, PLS), located here:
Updates and Enhancements
Output Data Products
Computational and Data Estimates
- Perform validation for Northridge, Chino Hills, Whittier, Landers, Hector Mine, and North Palm Springs
- For each validation event, calculate BBP results, CS results, and CS results with BBP Vs30 values
- Check for spectral discontinuities around 1 Hz
Decide if we should stick with rvfrac=0.8 or allow it to vary
- Determine appropriate SGT, low-frequency, and high-frequency seismogram durations
- Update high-frequency Vs30 to use released Thompson values
Integrate refactoring of BBP codes into latest BBP release Switch to using github repo version of CyberShake on Summit Update to latest UCVM (v22.7)
- Switch to optimized version of rupture generator
- Test DirectSynth code with fixed memory leak from Frontera
- Switch to using Pegasus-supported interface to Globus transfers
- Test bundled glide-in jobs for SGT and DirectSynth jobs