Difference between revisions of "CyberShake compilation guide"
From SCECpedia
Jump to navigationJump to search| Line 25: | Line 25: | ||
== SGT codes == | == SGT codes == | ||
| + | Once the external and internal dependencies are installed, the SGT codes can be compiled in any order. I usually compile them in the order they're executed in: | ||
| + | *PreCVM | ||
| + | *UCVM wrappers (plus optional smoothing) | ||
| + | *PreSGT | ||
| + | *The flavor of AWP you plan to use. | ||
| + | *SgtHead | ||
| + | *SgtTest | ||
== PP codes == | == PP codes == | ||
Revision as of 17:52, 21 August 2024
This document provides some high-level tips for compiling the software packages in cybershake-core. It assumes you've already cloned the repository.
Dependencies
External
Before compiling any codes in the repository, you should first make sure the following dependencies are available:
Internal
Next you should compile CyberShake or SCEC codes which are dependencies for other codes:
If you are planning to generate high-frequency stochastic seismograms, you also need to install the SCEC Broadband Platform.
SGT codes
Once the external and internal dependencies are installed, the SGT codes can be compiled in any order. I usually compile them in the order they're executed in:
- PreCVM
- UCVM wrappers (plus optional smoothing)
- PreSGT
- The flavor of AWP you plan to use.
- SgtHead
- SgtTest
