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 | 40 mins total | Ahsan | Uploading to cloudup was tricky as the files need to be downloaded from the linux box first. |
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 |
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 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 | Hoby |
default parameters used, runs in 2 mins but needed to fix a few things up |
Tasks | Time estimation | |
Hoby | Fix bias plotting for both empirical and physics-based models | 2days |
Ethan | 1) Streamline the VM generation with gen_coords.csh 2) Write scrip to stitch together multiple PDFs in PDFtk 3) VM domain baseplot to be passed to plot SRF by others | 2days (with other minor tasks) |
Ahsan | 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 2) Some python scripts (code that downloads data, code that processes data) that run one after another can and will be automated. | 5days |
Sung | The following 3 items are easy to automated, and where we can easily make mistakes.
|
|
Viktor |
| 2.5 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 | 40 mins total | Ahsan | Uploading to cloudup was tricky as the files need to be downloaded from the linux box first. |
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 |
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 | Hoby |
make a script that plots just this and loops over period values - done self contained input file used and model_params |
Tasks | Time estimation | |
Hoby | Fix bias plotting for both empirical and physics-based models | 2days |
Ethan | 1) Streamline the VM generation with gen_coords.csh 2) Write scrip to stitch together multiple PDFs in PDFtk 3) VM domain baseplot to be passed to plot SRF by others | 2days (with other minor tasks) |
Ahsan | 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 2) Some python scripts (code that downloads data, code that processes data) that run one after another can and will be automated. | 5days |
Sung | The following 3 items are easy to automated, and where we can easily make mistakes.
|
|
Viktor |
| 1 - 2 days |