1) 400m Whole NZ validation run (tectonic classification)2) Re-run advanced IMs

2)Generate gcmt faults to find correct orientation

3) Srf generation Subduction specific behaviour for GCMT (Robin to add more info)

1) RobinJonney

2) JonneyJames

1. still in progress
2. Plots generated and passed on to Robin

1) Ground Motion Extraction

2) Hikurangi Geometry

3) Tectonic Classification

4) Mw Reconciliation (comparison : John Ristau vs international dataset)

5) Comparison with VH2017

1)Viktor

2) James

3) Mike /  James

4) ?

5) ?

1. ?
2. On hold for this sprint
3. Mike continuing

1) Cybershake Subduction (8 faults) :

Complete BB after IM plot checks

2)Running 200m sims LF only - on Kisti / Maui (until Maui comm allocation leaves 100k)

1. lower south island / all rels (KISTI)(Maui)
2. Central South island / all rels (Maui)
3. all faults/1 rel (KISTI) (Maui)
4. remaining faults/all rels (KISTI)

uses  500k)

• Northern South Island

2) 4) Empirical DS - DB calculation

53) Empirical / Cybershake / ratio hazard maps

Jason

1) Jason150k used on Comm00213 since start of June. Using ~10-15k a day at the moment. 500/~4500 realisations

2) SungCompleted & plotted (with issues) need to investigate it.

1. Generalize hacks for KISTI
2. CH estimation based on linear regression
3. Integrate with pre-processing (starting with VM)
   1. Separate db creation out of install
   2. Create generic slurm for the rest of install, make install operate on each fault
   3. Create a generic slurm for VM generation
4. Pre-processing - GCMT to realisation – add some conditional logic about tectonic type (Brendon / Robin to consult about conditional parameters)
5. Near-real time Simulation plan
6. Cybershake Workflow Improvements

1. James
2. Jason / Brendon Ethan
3. Jonney
4. James
5. Jonney
6. Jason / Jonney

1. Work mostly complete. Final tests on Kisti underway. Checks on tacc yet to begin.
2. ?
3. Deferred
4.  
5. Done (from Jason side).

1. GM Selection for Empirical
   1. Integrate workflow into seistech master
   2. Synthetic tests for GCIM between Empirical and Simulation (1 rupture, N ruptures)
   3. For Daniel: - what tasks for him to do?
   4. Testing, trial calculations
2. Automate documentation
3. Front-end

1. 1. Milestone #2
      1. authentication.
      2. user access to individual tab controlled by authentication
      3. User data managed by API, and additional user data kept in a separate db
      4. Data integrity and consistency between Auth0 and separate db maintained.
   2. Milestone #3
      1. API call framework - plan the API proxy
      2. Create Mock API's with canned JSON response
      3. Call mocked API from the front end and ingest JSON. To demonstrate an example of full functionality of the front end
   3. Milestone #4: API – 2
      1. Create an API proxy - including error messages for restricted access
   1. 1. Call existing Core API’s from the front end replacing the mocks.
      2. JWT authorisation between the proxy and the core API
   2. Milestone #5: Deployment of 3 core environments
      1. Deploy DEV, TEST/EA, PROD versions
      2. Deployment is fully automated via scripts and config files.
      3. Update or switch-over is easily achieved utilizing deployment slots 
      4. Disruption is kept minimal when updated.

1. GM Selection for Empirical
   1. Integrate basic (single branch) empirical GMS
2. Automate documentation
3. Front-end

1. Daniel / Claudio
2. Background task (Jason)
3. Andy

1) Done (no testing)

Roadmap (scientific functionality list)

Production - TODO (longer term tasks)

Frontend

1. NN - GMM
   1. Implement an initial basic pipeline with some NN config + flexible feature selection & preprocessingSpatial plots
   2. Add hypo-depth to NN GMM dataset
2. GM Classifier – see link

1) Added (generalised) functionality for spatial map plotting. Currently supports IM residual maps, few others to be added.

2) Worked on validation & PhaseNet evaluation with Mike, 70-80% done in terms of integrating PhaseNet as p-wave picker (will allow multiple

1. SimAtlas simulation+animation:
   1. Test auto workflow with batch 4. (total 100 faults)
   2. Once batch 4 is done. Keep fueling the fire
   3. Batch 5 - keeping continual work
2. Data management policy
   1.  (classification of data importance
   .
3. NoisePy
4. NeSI allocation: Chat with NeSI, keep subscription allocation separate)
5. 1. )
   2. Plan to incorporate this as part of business as usual – what data do we need to keep and what can be regenerated as needed
6. NoisePy
7. Velocity Model basins
8. Dashboard
   1. Add comm00213 as a separate allocation
   2. Changes of storage (TB): With Fortnightly update info added
   3. Zero point at the start of the allocation (graph doesn't start midway)
9. Vs30 ServerVelocity Model basins

1. Sung/Jonney
2. Sung
3. Viktor
4. Jason
5. Sung
6. Viktor
   
   

1. Running
2. Automated management code done.
3. on hold
4. -
5. (a) done, (b-c) to be done
6. Done