Difference between revisions of "Adding to CyberShake"
From SCECpedia
Jump to navigationJump to search| Line 5: | Line 5: | ||
To add a new ERF, the following steps are required: | To add a new ERF, the following steps are required: | ||
| − | # A list of ruptures (or rupture variations) with magnitudes and probabilities must be created externally, and added to the Ruptures table (and | + | === Database modifications === |
| + | |||
| + | # A new ERF ID should be added to the ERF_IDs table of the [[CyberShake_Data#CyberShake_database_overview | CyberShake database]]. | ||
| + | # An entry for the Rupture Surface Resolution (either the grid spacing, in km, or the element area, in km^2) must be added to the ERF_Metadata table for the new ERF ID, as this is required. | ||
| + | # A list of ruptures (or rupture variations) with magnitudes and probabilities must be created externally, and added to the Ruptures table (and Rupture_Variations, if variations are created). | ||
| + | # The CyberShake_Site_Ruptures table must be populated for each site we plan to compute curves for with the new ERF, so CyberShake knows which ruptures to include. | ||
| + | # The Rupture_Variations table must be populated (ideally including hypocenter locations). This can either be done by using a rupture generator to create and count rupture variations, or the ERF which already supplies rupture variations, such as RSQSim-generated ERFs. | ||
| + | |||
| + | === Stage ruptures === | ||
| + | |||
| + | A physical copy of all the ruptures of interest must be staged on the remote clusters we plan to calculate curves on. I recommend using Globus to do the directory transfer. | ||
| + | |||
| + | === Register ruptures in the replica catalog (RC) === | ||
| + | |||
| + | The ruptures on the remote system must be registered in the [[CyberShake_Workflow_Framework#Replica_Catalog_.28RC.29 | Replica Catalog]] on shock. | ||
Revision as of 18:01, 27 September 2018
Below we outline the steps required to add new kinds of input data to CyberShake.
Contents
New ERF
To add a new ERF, the following steps are required:
Database modifications
- A new ERF ID should be added to the ERF_IDs table of the CyberShake database.
- An entry for the Rupture Surface Resolution (either the grid spacing, in km, or the element area, in km^2) must be added to the ERF_Metadata table for the new ERF ID, as this is required.
- A list of ruptures (or rupture variations) with magnitudes and probabilities must be created externally, and added to the Ruptures table (and Rupture_Variations, if variations are created).
- The CyberShake_Site_Ruptures table must be populated for each site we plan to compute curves for with the new ERF, so CyberShake knows which ruptures to include.
- The Rupture_Variations table must be populated (ideally including hypocenter locations). This can either be done by using a rupture generator to create and count rupture variations, or the ERF which already supplies rupture variations, such as RSQSim-generated ERFs.
Stage ruptures
A physical copy of all the ruptures of interest must be staged on the remote clusters we plan to calculate curves on. I recommend using Globus to do the directory transfer.
Register ruptures in the replica catalog (RC)
The ruptures on the remote system must be registered in the Replica Catalog on shock.
