Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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)

...

3 hypo and 2 slip dist per source

...

automated based on PGV>5cm/s; 15kmRup, 5km land cutoff

...

First implementation;

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

...

 

...

hypo every 20 km along strike,

3 slip dist per source

...

v18.5

...

 

 

...

v17.11

(planning)

...

a. Improve depth scaling and duration scaling. Consider time step lengthening within stability limit

...

0.2km regular grid, Vs_min=500

...

 

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:

...

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:

  1. Automated IM plot on the map for all simulations 
  2. Automated standard post-processing for all simulations 
  3. Hazard curve calculations from simulated ground motions
  4. Empirical hazard calculations 

To do before v17.9:

  1. Config file for batch submission of the simulations 
  2. Verification code for param files for SRFs and VMs (e.g., transition frequency, grid size)
  3. Wall clock and number of cores estimations
  4. Automated check to see if the runs for LF, HF, and BB are done successfully 
  5. Comparison and combination of the simulated and empirical hazard analyses

To do, but no timeline for completion:

  1.  ...

 

 

 

 

 

 

 

 

 

 

 

 

 

 

...