Difference between revisions of "CyberShake Workplan"
| Line 1: | Line 1: | ||
| − | + | == Goal: == | |
PSHA-3DWP hazard curve anywhere in California and an expression of uncertainties for any hazard curve. | PSHA-3DWP hazard curve anywhere in California and an expression of uncertainties for any hazard curve. | ||
Create basis for operational 3DWP ground motion forecasting system. | Create basis for operational 3DWP ground motion forecasting system. | ||
General approach usable anywhere in the world | General approach usable anywhere in the world | ||
| − | + | ||
| + | == How to: == | ||
UCERF2.0 (then 3.0) used to create extended ERF | UCERF2.0 (then 3.0) used to create extended ERF | ||
| Line 11: | Line 12: | ||
Modify Olsen code to support SGT creation and seismogram synthesis | Modify Olsen code to support SGT creation and seismogram synthesis | ||
| − | + | == Example Value-Adds: == | |
| + | |||
PAGER for any CyberShake event | PAGER for any CyberShake event | ||
Building response (18 story steel frame building) for full suite of rupture variations for specific events. Try for all Northridge variations. | Building response (18 story steel frame building) for full suite of rupture variations for specific events. Try for all Northridge variations. | ||
| Line 19: | Line 21: | ||
Seismogram Library: | Seismogram Library: | ||
| − | + | == CyberShake Data Management (Primary Calculation) == | |
Amplitudes, Waveforms, for any event in catalog | Amplitudes, Waveforms, for any event in catalog | ||
| Line 45: | Line 47: | ||
Ask questions about a site. What was simulation region, what was velocity model, what was rupture variation selection, what was peak amplitudes, what was different complements, what are smallest amplitudes | Ask questions about a site. What was simulation region, what was velocity model, what was rupture variation selection, what was peak amplitudes, what was different complements, what are smallest amplitudes | ||
| − | + | == Software Infrastructure Issues: == | |
Multiple codes | Multiple codes | ||
| Line 51: | Line 53: | ||
Ability of both systems to get same answer at 0.5Hz | Ability of both systems to get same answer at 0.5Hz | ||
| − | + | == EERF Issues == | |
Automated conversion into and out of SRF format for Olsen code. | Automated conversion into and out of SRF format for Olsen code. | ||
| Line 59: | Line 61: | ||
Introduction of linked events | Introduction of linked events | ||
| − | + | == Site specific information == | |
Sites in background regions | Sites in background regions | ||
| − | + | == Validation == | |
| + | |||
Comparison of CyberShake amplitudes to empirical amplitudes. Does cybershake reproduce the empirical distribution? | Comparison of CyberShake amplitudes to empirical amplitudes. Does cybershake reproduce the empirical distribution? | ||
Validation of UCEERF | Validation of UCEERF | ||
| Line 74: | Line 77: | ||
Comparison of seismograms to “unusual records” including I-10/I-215, Northridge garden center, and santa monica and I-14 fallen freeways | Comparison of seismograms to “unusual records” including I-10/I-215, Northridge garden center, and santa monica and I-14 fallen freeways | ||
| − | + | == Calculation Optimizations: == | |
Create EERF: | Create EERF: | ||
| Line 84: | Line 87: | ||
Combine seismogram extraction with peak amplitude calculation to output seismograms and peak amplitudes | Combine seismogram extraction with peak amplitude calculation to output seismograms and peak amplitudes | ||
| − | + | == Visualization Issues: == | |
Need maps of ruptures and rupture variations. | Need maps of ruptures and rupture variations. | ||
Need maps showing simulation volume and ruptures in the simulation volume. | Need maps showing simulation volume and ruptures in the simulation volume. | ||
| − | + | == Data Management Issues == | |
Develop computational data product dependency chart. Any time a new data model is created calculate resulting data products that use the data item. Then populate, as sparse storage, those data products as they are calculated. | Develop computational data product dependency chart. Any time a new data model is created calculate resulting data products that use the data item. Then populate, as sparse storage, those data products as they are calculated. | ||
| + | == Query Capabilities Needed == | ||
Create a Simulation Description Request Format: | Create a Simulation Description Request Format: | ||
Data Request Format: | Data Request Format: | ||
Revision as of 06:56, 19 February 2011
Contents
Goal:
PSHA-3DWP hazard curve anywhere in California and an expression of uncertainties for any hazard curve. Create basis for operational 3DWP ground motion forecasting system. General approach usable anywhere in the world
How to:
UCERF2.0 (then 3.0) used to create extended ERF Create 3D velocity model by embedding high resolution background models. Update CVM evaluation system to include up to 10 validation events. Modify Olsen code to support SGT creation and seismogram synthesis
Example Value-Adds:
PAGER for any CyberShake event Building response (18 story steel frame building) for full suite of rupture variations for specific events. Try for all Northridge variations. Short-term ERF probabilities Adjustor (PA) ShakeMap for any Rupture Rupture Library: Seismogram Library:
CyberShake Data Management (Primary Calculation)
Amplitudes, Waveforms, for any event in catalog Maps
UCERF3.0 (ERF) UCEERF3.0 (Extended ERF) UCVM (Unified California Velocity Model) Location of every sites. Closest curve to any geographical site GTL profile every site Vertical profile for every site All velocity meshes in simulation regions All ruptures in simulation region PSHA Maps (intensity measures include PGV, PSA2.0s, SA3,0,SA5,0,SA10.0) PSHA Hazard Curves Single component hazard curve Disaggregrated Curves to identify ruptures based on any parameters Rupture variations Fault Geometries Fault Maps Elevation Parameter plots (initial stress, hypocenter, final slip, slip rate, Supershear), and animations, of every SRF. Hazard curve to rupture variation set to sorted amplitudes (by peak intensity measure, by distance) to amplitude values to seismograms for amplitudes to rupture variation to slip on rupture to velocity model used. Ask questions about a site. What was simulation region, what was velocity model, what was rupture variation selection, what was peak amplitudes, what was different complements, what are smallest amplitudes
Software Infrastructure Issues:
Multiple codes Checks by Rob with Kim’s code Ability of both systems to get same answer at 0.5Hz
EERF Issues
Automated conversion into and out of SRF format for Olsen code. Background seismicity Establish sufficient variability Introduction of rise-time variability Introduction of linked events
Site specific information
Sites in background regions
Validation
Comparison of CyberShake amplitudes to empirical amplitudes. Does cybershake reproduce the empirical distribution? Validation of UCEERF Validation of UCVM Amplitude (and distribution) of CyberShake amps by distance compared against empirical attenuation relationship. Spectral content of seismograms compared to observed seismograms GOF for seismograms from rupture variations of historical earthquakes Frequency content of rupture sources Comparison of hazard curves to precarious rocks sites Comparison of seismograms to “unusual records” including I-10/I-215, Northridge garden center, and santa monica and I-14 fallen freeways
Calculation Optimizations:
Create EERF: Create set of statewide rupture variations Create set sites Map rupture variations to sites Define minimum set of velocity meshes Associate velocity mesh for each site Combine seismogram extraction with peak amplitude calculation to output seismograms and peak amplitudes
Visualization Issues:
Need maps of ruptures and rupture variations. Need maps showing simulation volume and ruptures in the simulation volume.
Data Management Issues
Develop computational data product dependency chart. Any time a new data model is created calculate resulting data products that use the data item. Then populate, as sparse storage, those data products as they are calculated.
Query Capabilities Needed
Create a Simulation Description Request Format: Data Request Format: Name: User: - Data Builder - Parser - Verifier - Reducer - Annotator - Packer - Notifier
