Task

Expected time reqd.

People

Notes

1. Source          (HOBY)

GeoNet Mw email to SRF

(a)  from Mw tensor get Rup parameters

(b)  From Rup parameters use createSRF.py to make rupture SRF

(c)  Execution of createSRF.py

1minute

5mins

10sec

6min total

Hoby

a) Manually extract location, dip,strike, rake from Mw tensor (Ristau) into setSrfParams.py

b) Change TYPE=2 (point source to finite fault)

c) Run "createSRF.py"

Plotting of SRF

(a)  SRF plane(s) standard plotting

(b)  SRF on map to verify location (to come after domain set in step 2)

3mins

5mins

2mins

10min total

(a) Hoby

(b) Viktor

Execute ‘plotSRF.py’ (select title for top of script)

(a) Hoby : Just needed to change SRF name 

(b) Viktor: make 2 plots on 1 image, 1 zoomed in with slip visible, 2 whole of NZ showing outline/hypocentre

Finished automating. only SRF needed, no reliance on params.py etc...

2. Velocity Model Domain   (ETHAN/ROBIN)

From rupture location to VM dev and domain

(a)  From location and Mw determine VM origin, 3D extent, and simulation duration

(b)  Plot VM domain extent

(c)  Generate VM with H=0.1km for this domain

2mins

1mins

15 mins (on multiple cores)

20min total

Ethan, Robin,…

1) Origin lat/lon/depth written into 'generate_parameters.py' python script

2) Run 'generate_parameters.py', output is a text file which is read by the next step

3) Run 'genDomain.py' this generates the velocity model, extracts slices. Stores the results in Rapid_Model

Need to implement duration calculations

Need to streamline Gen_Coords to sync with model parameters

Run gen_cords.csh and plot

Create .p/s/d files

From non-uniform station grid, get statgrid points

(a)  Locations of statgrid points

(b)  Locations of GeoNet strong motion stations

(c)  From NZ Vs30 model get Vs30 values at all points

(ignore for now)

1-2 hours!!

10mins

~2hours

Ahsan, Chris

[need .ll file for all of NZ (Ahsan)] (Done)

run statcords (to get station locations corresponding to actual VM domain]

(a) Plot VM domain extent, stations (statgrid and GeoNet),

(b) color based on Vs30 values

2mins

(a) Viktor

(b) Not done

Only done as part of plotting PGA, PGV, PSA, PSA RATIOS

Where to get vs30 values?

3. Observed strong motions  (SUNG)

Obtain observations from GeoNet

(a)  Get recorded motion from GeoNet ftp

(b)  Process and reformat using defaults

(c)  Produce plots of acc/vel time series, response spectra

Ahsan

Plot IM values at GeoNet stations on map (for various IMs)

1 hour (GMT)

Ahsan

updating e3d.par domain info

Plot observed vel time series on map

5mins

Viktor

skipped, need to finish script that does this

Plot IM values as a function of Rrup and compare with empirical ground motion model (various IMs)

20min

1hour 30mins

Ahsan

Richard's code runs for 3 mins. Had to go through a number of iterations to get nice looking plots.

Has a good idea to reduce the time significantly. Knows what parameters to change.

Not easy to automate.

4. Perform GM Simulation   (SUNG)

Submit GM Simulation

(a)  prepare input params.py, pointing to SRF, VM, and stations of interest etc. (gen_cords.sh and statlist2gp.py need to be run)

(b)  LF sim (queue time + run time)

(c)  Once LF sim complete, run HF and BB sim

20mins

512 cores (8node) [wait+run 2hours]

30mins

4hours

Sung

1. Hoby uploaded SRF to Fitzroy 
2. Sung uploaded VelModel and model_params (output of gen_cords.sh) to Fitzroy
3. Sung created a recipe for the drill with params.py having all the parameters set, and other files copied from 2010Sep sim.
4. Modification to install.sh was not necessary, but we will eventually need to.
5. Almost forgot to produce .startcords from .ll. For HF, it is advised to use the FD version of .ll (ie. output of statlist2gp.py) in params.py

Good opportunity for automation. (a) can be done in a sec.

5. Post-processing   (VIKTOR)

LF Time slice animation

(a) tar, download data from Fitzroy to local

(b)  From TS produce PGV and MMI plot

(c)  Produce TS animation

10mins

25mins

25min

Viktor

needed to fix up scripts to work with new parameter style

mainly needed to fix script to use new parameter style, should run automatically after step A
run time only ~3 minutes 

need to automate a little more, run time ~5 mins

Script preparation

At SMS locations compare sim vs. obs

(a) compare waveforms

(b) Compare IMs as a function of Rrup (multiple IMs; sim, obs, empirial)

(c) Compare sim, obs, empirical response spectra at individual locations

(d) Plot overall bias as a function of vibration period (both sim and empirical)

(e) Preparing input for (f)

(f) Plot bias(residual) at specific locations on a map

10mn

(a)–(c) 30 mins

(d) 20mn

(e) 10 mins

(f) 5 mins

• Make sure to use fd_*.ll station lists instead of geonet*.ll
• There were some errors during the bias plotting, so I need to remove that part of the code to plot the IMs
  
  

default parameters used, runs in 2 mins but needed to fix a few things up

1) Update all_geoNet_stations.ll to include SMS that closed in 2010. This will add more stations to the list and we won't have a problem when dealing
with historical events. Kevin would need to update the Vs30 stations list accordingly.

2) Some python scripts (code that downloads data, code that processes data) that run one after another can and will be automated.

3)Coordinates with Viktor for plotting IMs on map. Currently I and Viktor separately gather velocity model domain data etc,for GMT plotting,
which is a manual task. Supply Viktor IMs data file for him to plot.

1. Create shared parameter files that can be imported into other steps in the workflow (Saves need for configuring params.py and get_cords.sh)
2. Automated file transfer to Fitzroy
3. Automated installation of a job
   
   

1. 2 days
2. 2 days
3. 2 days

1. Finish script to plot observed timeseries on map
2. Run plots automatically when data has been retrieved
3. Determine format and implement for plotting stations on map with PGV, PGA, PSA data etc...
   and figure out easiest way to plot PGV stations on overlay

2.5 days
1 - 2 days
2 days 

Task

Expected time reqd.

People

Notes

1. Source          (HOBY)

GeoNet Mw email to SRF

(a)  from Mw tensor get Rup parameters

(b)  From Rup parameters use createSRF.py to make rupture SRF

(c)  Execution of createSRF.py

1minute

5mins

10sec

6min total

Hoby

a) Manually extract location, dip,strike, rake from Mw tensor (Ristau) into setSrfParams.py

b) Change TYPE=2 (point source to finite fault)

c) Run "createSRF.py"

Plotting of SRF

(a)  SRF plane(s) standard plotting

(b)  SRF on map to verify location (to come after domain set in step 2)

3mins

5mins

2mins

10min total

(a) Hoby

(b) Viktor

Execute ‘plotSRF.py’ (select title for top of script)

(a) Hoby : Just needed to change SRF name 

(b) Viktor: make 2 plots on 1 image, 1 zoomed in with slip visible, 2 whole of NZ showing outline/hypocentre

Finished automating. only SRF needed, no reliance on params.py etc...

2. Velocity Model Domain   (ETHAN/ROBIN)

From rupture location to VM dev and domain

(a)  From location and Mw determine VM origin, 3D extent, and simulation duration

(b)  Plot VM domain extent

(c)  Generate VM with H=0.1km for this domain

2mins

1mins

15 mins (on multiple cores)

20min total

Ethan, Robin,…

1) Origin lat/lon/depth written into 'generate_parameters.py' python script

2) Run 'generate_parameters.py', output is a text file which is read by the next step

3) Run 'genDomain.py' this generates the velocity model, extracts slices. Stores the results in Rapid_Model

Need to implement duration calculations

Need to streamline Gen_Coords to sync with model parameters

Run gen_cords.csh and plot

Create .p/s/d files

From non-uniform station grid, get statgrid points

(a)  Locations of statgrid points

(b)  Locations of GeoNet strong motion stations

(c)  From NZ Vs30 model get Vs30 values at all points

(ignore for now)

1-2 hours!!

10mins

~2hours

Ahsan, Chris

[need .ll file for all of NZ (Ahsan)] (Done)

run statcords (to get station locations corresponding to actual VM domain]

(a) Plot VM domain extent, stations (statgrid and GeoNet),

(b) color based on Vs30 values

2mins

(a) Viktor

(b) Not done

Where to get vs30 values?

3. Observed strong motions  (SUNG)

Obtain observations from GeoNet

(a)  Get recorded motion from GeoNet ftp

(b)  Process and reformat using defaults

(c)  Produce plots of acc/vel time series, response spectra

Ahsan

Plot IM values at GeoNet stations on map (for various IMs)

1 hour (GMT)

Ahsan

updating e3d.par domain info

Plot observed vel time series on map

5mins

Viktor

need to automate location of stations involved, zoom levels etc... code exists, needs to be brought together / cleaned up

Plot IM values as a function of Rrup and compare with empirical ground motion model (various IMs)

20min

1hour 30mins

Ahsan

Richard's code runs for 3 mins. Had to go through a number of iterations to get nice looking plots.

Has a good idea to reduce the time significantly. Knows what parameters to change.

Not easy to automate.

4. Perform GM Simulation   (SUNG)

Submit GM Simulation

(a)  prepare input params.py, pointing to SRF, VM, and stations of interest etc. (gen_cords.sh and statlist2gp.py need to be run)

(b)  LF sim (queue time + run time)

(c)  Once LF sim complete, run HF and BB sim

20mins

512 cores (8node) [wait+run 2hours]

30mins

4hours

Sung

1. Hoby uploaded SRF to Fitzroy 
2. Sung uploaded VelModel and model_params (output of gen_cords.sh) to Fitzroy
3. Sung created a recipe for the drill with params.py having all the parameters set, and other files copied from 2010Sep sim.
4. Modification to install.sh was not necessary, but we will eventually need to.
5. Almost forgot to produce .startcords from .ll. For HF, it is advised to use the FD version of .ll (ie. output of statlist2gp.py) in params.py

Good opportunity for automation. (a) can be done in a sec.

5. Post-processing   (VIKTOR)

LF Time slice animation

(a) tar, download data from Fitzroy to local

(a)  Produce TS animation

(b)  From TS produce PGV plot

(c)  Produce MMI plot from PGV

30mins

30mins

5min

5min

Viktor

(can be streamlined, at later date)

vm domain used by default, determine if regional sites should be added (crowding), padding around vm based on rot, domain if rotation small

mostly automated TS animation, some parameters needed such as colour range

single script does both PGV, MMI - need to finish automating colour range for PGV

Script preparation

At SMS locations compare sim vs. obs

(a) compare waveforms

(b) Compare IMs as a function of Rrup (multiple IMs; sim, obs, empirial)

(c) Compare sim, obs, empirical response spectra at individual locations

(d) Plot overall bias as a function of vibration period (both sim and empirical)

(e) Preparing input for (f)

(f) Plot bias(residual) at specific locations on a map

10mn

(a)–(c) 30 mins

(d) 20mn

(e) 10 mins

• Make sure to use fd_*.ll station lists instead of geonet*.ll
• There were some errors during the bias plotting, so I need to remove that part of the code to plot the IMs
  
  

make a script that plots just this and loops over period values - done self contained input file used and model_params

1) Update all_geoNet_stations.ll to include SMS that closed in 2010. This will add more stations to the list and we won't have a problem when dealing
with historical events. Kevin would need to update the Vs30 stations list accordingly.

2) Some python scripts (code that downloads data, code that processes data) that run one after another can and will be automated.

3)Coordinates with Viktor for plotting IMs on map. Currently I and Viktor separately gather velocity model domain data etc,for GMT plotting,
which is a manual task. Supply Viktor IMs data file for him to plot.

1. Create shared parameter files that can be imported into other steps in the workflow (Saves need for configuring params.py and get_cords.sh)
2. Automated file transfer to Fitzroy
3. Automated installation of a job
   
   

1. 2 days
2. 2 days
3. 2 days

1. Fix plotting script for SRF to show fault location clearly, Create plotting script that takes PGV and MMI, create plotting script for station resuduals.
2. Automatically calculate default parameters where possible, allow scripts to be run where paths / needed inputs can be passed to them.
3. connect scripts where input from one should automatically run another where possible eg: create PGV, MMI data and instantly plot it

1 - 2 days
1 - 2 days
1 - 2 days