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 and to plot

(c)  Execution of createSRF.py

1minute

25sec

2min total

Hoby/Viktor

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

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

Use either version "3.3" or "5.3.2a"

c) Run "createSRF.py"

Please note that the execution time of createSRF.py may change based on the event size

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, then extract slices

1mins

20 mins (on multiple cores)

15 mins for slices

4 mins for H=0.2km VM creation (30 mins for H=0.1km)

20min total

March Drill

Setup code - 4 mins

generateDomain initial (inc. getting CMT data) - 2+2=4 min

creating VM (inc. manual adjustment) - 10+1 = 11

genDomain - 6+6+6 = 18

Total ~37-40 minutes

Ethan, Robin,…

(inc. getting CMT data) - 2+2=4 min

creating VM (inc. manual adjustment) - 10+1 = 11

genDomain - 6+6+6 = 18

Total ~37-40 minutes

Ethan, Robin,…

March Drill

1. Tidy up params_vel.py (some params are redundant) and include corners for plotting before mesh generation
   
2. Run gen_corrds during VM and place all model params alongside VM files (Done)
   
3. Integrate the gen_cords into the first step to enable the domain to be plotted on a map and checked / changed if necessary (Done)
   
4. Split the VM generation from VM interrogation / slice generation to allow the VM to be copied while slices are being generated
5. Will need a wall clock time estimation done before VM calculation (Done)
   
6. Merge  EXTENT_Z_SPACING, EXTENT_LATLON_SPACING and HH (Done)
   
7. Change names of to be consistent  ORIGIN_LAT, ORIGIN_LON,ORIGIN_ROT retain these names , (MODEL_LAT,_LON,_ROT ) (Done)
   
8. Write xy2ll into the gen_params.py script to write the domain corners into params_vel.py (Done)
   
9. Plot the vm domain box within gen_params.py
   
10. Include gen_cords.py within genDomain to keep coords and .p .s and .d binary files in together (Done Duplicate of 2)
    

 There was an error in the auto-VM generation on hypocentre which needed to be fixed, and then the code had to be obtained from github again. (Done)

(Sung) == items below have beem completed after Feb. drill

1.nx,ny,nzare automatically updated if user manually edits other values like (extent_x,_y,_zmax)

2. if extent_x, extent_y and extent_zmax are not divisible byhh, it automatically increases extent_* to the first divisible value

 3. it will automatically work outflo  (based on min_vs/(5*hh).  The initial value offlo is automated, but user can manually override it by editing params_vel.py  (More in item 4)

4.In params_vel,py,  extent_x, extent_y, and extent_zmax, sim_duration andflohave automatically generated initial value.  User can manually edit params_vel.py to override them, but user MUST run *validate_parameters.py*, which will check the integrity of  the parameter file, and adjust automated values such asnx,ny,nzandsufx.  This will overwrite params_vel.py  (also keeps a backup of old params_vel.py) and show before and after changes side-by-side.

(Ethan)

Remove topography from preliminary plot to speed up investigateDomain.py

Change default CPTs to extend their range

March Drill (I've just put this here for now because I didn't want to delete anything)

(Robin)

Issues encountered/comments

1. nx and ny were incorrectly doubled (already fixed).
2. Development oversights leaving out the writing of params, and importing of shared.

Overall if everything went smoothly and no manual adjustment was required, this would total something around 15 minutes. (note this is also dependent on the VM domain size/source magnitude).

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

(d) Produce IM data files for stations on map plots in GMT

(e) Produce Vs30 input files for stations

Ahsan

Took 5 mins to create input file for downloading data from geoNet

Finished downloading data in 13.1 secs

Done Vs30 calcs in 25.0 secs

Processing .V1A files ...

Done processing in 219.4 secs

Creating acc and vel plots for all Observed SMSs ...

Done plotting acc, vel in 160.6 secs.

Creating pSA plots for all Observed SMSs ...

Done pSA plots in 181.2 secs.

Writting IMs for GMT plotting ...

Done in 32.2 secs.

python2 run_event.py  614.36s user 5.28s system 98% cpu 10:32.05 total

10:32 to 11:11 to run post processing code with observations only. code ran in

192.43s, took 5 mins to set the input file. The inputs for this input file

and the input file for downloading data are duplicated.

using a log scale for plotting observations only IMs on map results in values smaller than 1 to be

negative and difficult to interpret. Had to manually adjust cpt color scales for

better plots, and manually move gmt plots otherwise they are over written.

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

3 mins

Viktor

Viktor was away, and I (Ahsan) performed this task. It was some what unclear how the GMT plotting scripts (behind the scenes) got its input, e.g the domain boundary. The code ran without problems. There was a need to display the color bar on a log scale, which I was not able to do through the GMT scripts but had to rewrite the natural log of the data instead of the plain data. It was unclear what the log=True option achieves in the python wrapper to the GMT scripts.

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)

Ahsan

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)   File transfer and install

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

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

(a)5mins

(b)1:40~3:30 hours (queue+run)

(c)13 min

Sung

(1) We need a standardized event name stored somewhere.

(2) File transfer to Fitzroy could be more simplified. Occasionally I had no right permission to access the files generated by other team members.

==> Solution: Each module (VM, Source, Station) can have an "install" script that is executed by the person-in-charge that transfers the necessary files to the appropriate location (derived from the standardised event name)

(3) Many codes from various repositories are increasingly becominginter-dependent. We need to make a shared library soon.

(4) Wall clock limit estimation is reasonably accurate, with Fitzroy being prone to fluctuate occasionally. (IO suspected). DB needs some tweak to mark outliers.

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

9 min

Viktor

1) The animation is working fine for single event. However, if there are 2 SRF files in the run, you need to modify the parameter file such that it will generate the animation of the specific event that you want

2) we might want to generate the animation for the multiple events as well??

3) It would be great if we could include "*modelparams*" in the tar file from Fitzroy, which is needed for (5f) plotting

Script preparation and test

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)–(d) 20 mins

(e) 4 mins

(f) 5 mins

Hoby

I have still used Richard code because Daniel/Jason mentioned that they sill have some issue in the std of bias between Obs and empiricalGMM. Once the PP is done there will be significant save in time in terms of file preparation because I will use the same config. as Ahsan

(f) requires modelparamsfile/Srf; need to make sure we have them copied in hypocentrer

1) Srf plot location need to be modified

2)

2)

2days

2days

2-5 days

(1) 2 hours

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 

1. Non-uniform grid should probably run after the VM
2. Include non-uniform grid generation to the automatized workflow
3. Parameters for the grid should be read from the VM file
4. Make sure the format of the output is usable