Difference between revisions of "CyberShake Code Base"
From SCECpedia
Jump to navigationJump to search| Line 15: | Line 15: | ||
=== PreCVM === | === PreCVM === | ||
| + | This code stands for "Pre-Community-Velocity-Model". It has to be run before the UCVM codes, since it generates the required UCVM input files. | ||
| − | + | <b>Source code location:</b> http://source.usc.edu/svn/cybershake/import/trunk/PreCVM/ | |
| − | <b>Source code location:</b> | ||
<b>Author:</b> | <b>Author:</b> | ||
<b>Typical run configuration:</b> | <b>Typical run configuration:</b> | ||
<b>Input files:</b> | <b>Input files:</b> | ||
<b>Output files:</b> | <b>Output files:</b> | ||
Revision as of 20:47, 18 October 2017
This page details all the pieces of code which make up the CyberShake code base, as of November 2017. Note that this does not include the workflow middleware, or the workflow generators; that code is detailed at CyberShake Workflow Framework.
Conceptually, we can divide up the CyberShake codes into three categories:
- Strain Green Tensor-related codes: These codes produce the input files needed to generate SGTs, actually calculate the SGTs, and do some reformatting and sanity checks on the results.
- Synthesis-related codes: These codes take the SGTs and perform seismogram synthesis and intensity measure calculations.
- Data product codes: These codes insert the results into the database, and use the database to generate a variety of output data products.
Below is a description of each piece of software we use, organized by these categories.
Overview of the codes involved in the SGT part of CyberShake, source file (ODG)
PreCVM
This code stands for "Pre-Community-Velocity-Model". It has to be run before the UCVM codes, since it generates the required UCVM input files.
Source code location: http://source.usc.edu/svn/cybershake/import/trunk/PreCVM/ Author: Typical run configuration: Input files: Output files:
