Current Code
Name | URL | Summary |
Functions and programs commonly used by more than one repo | ||
NonUniformGrid , RegionalSeismicityTectonics, SrfGen, geoNet | ||
kupe_preprocess | Test codes for generated SRF, VM. Need to be merged into above | |
EMOD3D and various C/Fortran codes by Rob Graves | ||
Orchestrates the automated GM simulation workflow using Slurm | ||
Calculates rrups and IMs out of GM simulation output | ||
| ||
Landslide and liquefaction | ||
hazard_search and event_search codes are accommodated here | ||
Workflow to compute and plot bias for multiple events | ||
Gmt related functions | ||
Automated 3D Visualization of Ground Motion Simulation with Generic Mapping Tools (GMT) | ||
Students_owned | ||
Velocity-Model (Ethan) |
| |
Vs30-mapping (Kevin) | project applying Thompson et al. (2014) regression krigging-based Vs30 mapping technique to NZ (Maintainer: Kevin Foster) | |
Vs30map_clean (Kevin) |
|
Not-current codes
Name | URL | Last update | Summary |
Stable | |||
SeisFinder | 8 Sep 2017 |
| |
gm_publish | 9 Jun 2017 | Automatic LaTeX generation for SeisFinder | |
ansible_seisfinder | 8 Nov 2017 | Automated installation of SeisFinder on a webserver | |
Outdated | |||
gm_sim_pkg | 6 Apr 2018 | Only used for real time workflow and external users | |
Auto-Vel-Mod-Generation | 1 May 2018 | Needed by gm_sim_pkg | |
Not maintained - Obsolete | |||
NonErgodic | 29 Oct 2016 |
| |
groundMotionStationAnalysis | 17 Aug 2016 |
| |
post-processing | 17 April 2018 | Superseded by IM_calculation, visualization | |
gm_sim_workflow | 13 Mar 2018 | Researchers still use this. Superseded by slurm_gm_workflow | |
cybershake_postprocessing | 22 Mar 2018 | Hazard code has been absorbed into seisfinder2 repo. |
Knowledge base
Ideas for improvement
- post-processing repo is still used by SrfGen. Needs restructuring
- QCore, Pre-process etc on Kupe are used by many different parts of workflow. We refrain from keeping these codebase up-to-date due to concern for unexpected consequence. We need a separate sandbox that is regularly kept up-to-date and auto-tested, which is then pushed to the production setup.