This page provides rough outlines on the current progress on Cybershake in NZ. 

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

VersionNum sourcesSRF generationVM domainVM generationSimulation specsEstimated core-hoursActual core hoursNotes
v17.815 (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=500Transition freq = 0.25Hz~3k Fitzroy 

First implementation;

Focus on running workflow and comparison with empirically-derived hazard curves

v17.9 (planning)~100 (dominant in Canterbury, but most of Sth Island)

hypo every X km along strike,

Y slip dist per source

automated for PGV>5cm/s ...

Improved depth scaling

as for v17.8as for v17.8~30k Fitzroy Focus on extending number of sources and srf uncertianties
v17.10

~100 (Canterbury)

?as for v17.9

0.2km regular grid,

Vs_min=500
Transition frequency = 0.5 Hz~170k Fitzroy Focus on improved freq transition in South Island
v17.11~540 (all in NZ)?as for v17.9

as for v17.8

as for v17.8~500k Fitzroy(?) Focus on producing NZ-wide output at lower freq transition

 

Verification process:

Fault rupture (SRF) files:

Velocity model (VM) files:

 

 

    1. Check if given VM parameter (folder path) exists
    2. .p, .s, .d and params_vel.py files must exist
    3.  warns if model_params/coords/bounds etc don't exist using params_vel sufx in filename
    4.  params_vel matching hh/xlen vs nx for x, y, z
    5. file size = nx * ny * nz * 4 bytes, checked for .p, .s, .d
    6. if numpy available: checks first xz slice for >0 and not NaN in .p, .s, .d

Simulation process: