This
...
Note that his page is for internal sharing purposes only, it is likely inaccurate and out-of-date, and therefore it is advised to conduct researchers directly if you want more reliable information
~540 (all in NZ)
| Version | Num sources | SRF generation | VM domain | VM generation | Simulation specs | Estimated core-hours | Actual core hours | Notes |
|---|---|---|---|---|---|---|---|---|
| v17.8 | 15 (dominant in Canterbury) | vX.XX rupgenerator 3 hypo and 2 slip dist per source | automated based on PGV>5cm/s; 15kmRup, 5km land cutoff Default depth and duration scaling | 0.4km regular grid, Vs_min=500 | Transition freq = 0.25Hz | ~3k Fitzroy | First implementation; Focus on running workflow and comparison with empirically-derived hazard curves | |
| v17.9 | ~161 (South Island) | hypo every 20 km along strike, 3 slip dist per source | Same as v17.8 | as for v17.8 | as for v17.8 | ~30k Fitzroy | Focus on extending number of sources and srf uncertianties | |
v17.10 | 540 (NZ-wide; just extend v17.9 to more sources) | Same as v17.9 | as for v17.9 | as for v17.9 | as for v17.9 | ~?? Fitzroy | ||
v17.11 (planning) | ~100 (Canterbury) | ?? Possibly more hypocentres down-dip | a. Improve depth scaling and duration scaling. Consider time step | 0.2km regular grid, Vs_min=500 | Transition frequency = 0.5 Hz | ~500k Fitzroy(?) | Focus on producing NZ-wide output at lower freq transition | |
| v ?? | ? |
Verification process:
Fault rupture (SRF) files:
...
Velocity model (VM) files:
...
- Check if given VM parameter (folder path) exists
- .p, .s, .d and params_vel.py files must exist
- warns if model_params/coords/bounds etc don't exist using params_vel sufx in filename
- params_vel matching hh/xlen vs nx for x, y, z
- file size = nx * ny * nz * 4 bytes, checked for .p, .s, .d
- if numpy available: checks first xz slice for >0 and not NaN in .p, .s, .d
Simulation process:
...
is the front page for the Cybershake NZ project, describing the corresponding computational and scientific components.
An Outline of the project which includes a table to compare the main features of different versions are presented: Outline
Ideas for future implementations are presented here: Outline
A step-by-step manual to run a version of Cybeshake is presented here: Cybershake Run Manual
Cybershake uses national hazard model file. The corrections applied to this file is presented here: Corrections applied to the base NHM fault file
Details of the important runs of Cybershake are presented Cybershake v18.6 and Cybershake v17.8
A high-level to do list is presented here: Cybershake to-do list
Post-processing:
...
Prioritization:
To do now:
- Automated IM plot on the map for all simulations
- Automated standard post-processing for all simulations
- Hazard curve calculations from simulated ground motions
- Empirical hazard calculations
To do before v17.9:
- Config file for batch submission of the simulations
- Verification code for param files for SRFs and VMs (e.g., transition frequency, grid size)
- Wall clock and number of cores estimations
- Automated check to see if the runs for LF, HF, and BB are done successfully
- Comparison and combination of the simulated and empirical hazard analyses
To do, but no timeline for completion:
- ...
...