CyberShake BBP Verification: Difference between revisions
From SCECpedia
Jump to navigationJump to search
Created page with " == Related Entries == *[] *[]" |
No edit summary |
||
| Line 1: | Line 1: | ||
This page documents our CyberShake Broadband Platform validation work, running the BBP validation events through CyberShake. | |||
== Related Entries | == Events == | ||
We plan to run the following events from the BBP: | |||
*Northridge | |||
*Landers | |||
*North Palm Springs | |||
*Whitter | |||
*Chino Hills | |||
== Process == | |||
*We will identify about 10 stations from the BBP station list to run in CyberShake. | |||
* | |||
*We will run the BBP validation events with the Graves & Pitarka modules to produce BBP results for comparison. | |||
== Data Products == | |||
We will produce the following data products to compare CyberShake results with BBP results: | |||
== Related Entries | |||
*[] | *[] | ||
*[] | *[] | ||
Revision as of 05:58, 5 December 2020
This page documents our CyberShake Broadband Platform validation work, running the BBP validation events through CyberShake.
Events
We plan to run the following events from the BBP:
- Northridge
- Landers
- North Palm Springs
- Whitter
- Chino Hills
Process
- We will identify about 10 stations from the BBP station list to run in CyberShake.
- We will run the BBP validation events with the Graves & Pitarka modules to produce BBP results for comparison.
Data Products
We will produce the following data products to compare CyberShake results with BBP results:
== Related Entries
- []
- []
