Difference between revisions of "CyberShake Study 22.12"

From SCECpedia
Jump to navigationJump to search
Line 30: Line 30:
  
 
== Production Checklist ==
 
== Production Checklist ==
 +
 +
=== Science to-dos ===
 +
 +
*Determine which validation events need to be completed before the study
 +
*For each validation event, calculate BBP results, CS results, and CS results with BBP Vs30 values
 +
*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
 +
 +
=== Technical to-dos ===
 +
 +
*Integrate refactoring of BBP codes into latest BBP release
 +
*Switch to using github repo version of CyberShake on Summit
 +
*Update to latest UCVM (v19.4)
 +
*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
  
 
== Presentations, Posters, and Papers ==
 
== Presentations, Posters, and Papers ==

Revision as of 20:15, 8 July 2022

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.x.

Status

This study is in the planning phase. We estimate calculations will begin in October 2022.

Data Products

Science Goals

Technical Goals

Sites

Velocity Model

Verification

Updates and Enhancements

Output Data Products

Computational and Data Estimates

Lessons Learned

Stress Test

Performance Metrics

Production Checklist

Science to-dos

  • Determine which validation events need to be completed before the study
  • For each validation event, calculate BBP results, CS results, and CS results with BBP Vs30 values
  • 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

Technical to-dos

  • Integrate refactoring of BBP codes into latest BBP release
  • Switch to using github repo version of CyberShake on Summit
  • Update to latest UCVM (v19.4)
  • 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

Presentations, Posters, and Papers