Overview

Duration:  27 July  -  7 Aug

completedin progresson holdreviewto do
89



(vs record 94 completed sprint 54)



Epic
Story
OwnerDeliverables
Link
Validation
  1. Re-run advanced IMs
    1. Support Vahid
  2. SRF gen with roughness (identify 4 faults to interrogate vertical extent of roughness - adjust plotting to address)
    1. WairarapNich
  3. Add HF path duration perturbation (Robin to provide more info)
  4. Help Ethan, Sarah, Mike with the workflow
  1. Jonney
  2. Viktor
  3. James
  4. James
  1. updated multiple models&aggreation script. and built OpenSeesMP.
  2. plot_srf_map.py updated
  3. Added, Sarah has run sims and analyzed output
  4. All three are running sims


  1. Updates to Adv_IM and OpenSees
  2. Plotting SRFs with Roughness
Ground Motion DB
  1. Hikurangi Geometry
  1. James
RRup plot createdHikurangi surface geometry
Cybershake
  1. Running 200m sims LF only - on Maui (starting Merit cycle)
  2. Empirical / Cybershake / ratio hazard maps

Jason

  1. Automated part complete. Running failed runs now. Seg-fault with WairarapNich and "rounding error"s with 3 faults + 2 rels.

Cybershake v21p1

2) CS20p4 Result Interogation

Slurm Workflow

  1. Workflow on TACC
  2. CH estimation based on linear regression
  3. Integrate with pre-processing (starting with VM)
    1. Separate db creation out of install
  4. Near-real time Simulation
  5. Integrate NHM 2 SRF : uncertainty (50 realisations/fault) Moonshine
  6. New E2E test - confirm what HF version to use (20.4.1.4)
  1. James
  2. Jason / Ethan
  3. Jonney
  4. Jonney
  5. James
  6. James(?)
  1. Done
  2. ?
  3. James and Jason have discussed an idea involving median runs (and corresponding dependancies)
    3a.seperated scripts for SRF and VM generation
    VM generation is included as part of automated workflow (not tested nor merged)
  4. ?
  5. 5 realisations of Monshine generated with uncertainty and median run
  1. Kisit and Tacc simulation validation
  2. -
  3. Adding Pre-processing into automated workflow
  4. ?
  5. NHM uncertainties
Workflow Calc
  1. 1) BA18 site amp
    1. Complete Run
    2. Validation Comparison
1) Jason1a) All simulations completed - one fault needs adjusting for extended period.
SeisTech
  1. SeisTech - Front-end
    1. Download Data
    2. Fix UHS
    3. Tidy up plots
    4. Map showing selected location
  2. Show results of GM Selection
  3. Rerun Hazard for Balmoral with specific vs30
  1. Tom
  2. Claudio
  3. Jason/Claudio
  1. Updated and fixed bugs
    1. Download Data - Now users can download data after they compute with few variables
    2. Fix UHS - By getting a station at a right time, now users can compute UHS data without computing Hazard Curve first
    3. Tidy up plots - Todo
    4. Map showing selected location - Implemented MapBox into our SeisTech, users now have a visual map that is interacting with users input (Lat & Lng) or Map itself by clicking the map.
  2.  
  3. Balmoral + Northland sites emp_db created. Same weighted ensemble to earlier. Hazard analysis done
  1. GMHazard Front-end
Machine Learning
  1. NN - GMM
    1. Interrogate results
    2. Extra Features
    3. Estimate covariance
    4. Poster outline
    5. Develop research plan (development, validation, publication)
  2. Meeting with students (data & task)
Claudio/Ethan
  1. NN-GMM
    1. In pogress, added support for event-based spatial & IM vs feature plot, aggregate spatial residual plots
    2. Added support for extra features: hypoecentre location + depth, fault length, strike, dbottom, ztor, zbot, is_point_source
    3. No progress
    4. Initial scribbles
    5. Started  Gantt chart
  2. Done
NN-GMM Figures
Web/Data Portal

  1. SimAtlas simulation+animation:
    1. More animations!!

2. Fix up / AWS hosting for GIS interface for Andrew

3. NZVM viewer

  1. Jonney
  2. Sung/Viktor
  3. Viktor

  1. changed the script to colleted xyts.e3d from existing CS v20p4_200 runs.
    1a. several faults have issues or not ran ( recorded and skipped)

2. Users can be removed, name/email updated, a bit of testing. Hosted at UC server. Can host more webservices under quakecoresoft domain.

3.


2. https://github.com/ucgmsim/SiteTesting

https://quakecoresoft.canterbury.ac.nz/site_testing


Data
  1. Isilon vs Nearline 25Tb swap
    1. Mount isilon on epicentre
  1. Sung
  2. Sung/Viktor

Isilon→ nobackup complete (nobackup → nearline in progress)


Misc
  1. Velocity Model basins
    1. Tim / Cameron continuance
    2. What runs contain stations in the basins
  2. Topo Regenerate NZ for GMT plotting
  3. RCC VM with Francois and host Seistech Core
  4. Posters draft (A3)
  1. Jason
  2. Viktor
  3. Sung
  4. James, Claudio, Viktor, Jason
  1. Identified simulations to run. Need to ask about simulation parameters before running these simulations

2. no more "errors" while plotting, very rough test ~1% faster plot. resolution we have been using was 3 second. Using 1s for large region much slower. 1.3 mins vs 9.3 mins NZ map.

3s1s

3.


1.Basin Modelling

1b) 20p8 Basin Simulation Validation

IM Calc





Bug fixes



Seismic risk



Empirical engine



Misc discussion points:

1) Core Hours - 200k expire end of August that we need to use

2) Intermediate Storage : nobackup storage quota introduced.

3) Hosting (AWS / Azure / Epicentre / qcoresoft) : Remove Azure?


  • No labels