Epic | | Owner | Deliverables | |
---|
Validation | 1) 400m Whole NZ validation run (tectonic classification)2) Re-run advanced IMs 32) Plot both models geometry from GCMT for finite fault model
| 1) RobinJonney 2) Jonney3) James |
|
|
Ground Motion DB | 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) ? |
| Hikurangi surface geometryCybershake |
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) lower south island / all rels (KISTI)(Maui) Central South island / all rels (Maui)all faults/1 rel (KISTI) (Maui)uses 500k) remaining faults/all rels (KISTI)4) Empirical DS - DB calculation 5) Empirical / Cybershake / ratio hazard maps | 1)Jason2) Sung |
|
|
Slurm Workflow | - Generalize hacks for KISTI
- CH estimation based on linear regression
- Integrate with pre-processing (starting with VM)
- Separate db creation out of install
- Create generic slurm for the rest of install, make install operate on each fault
- Create a generic slurm for VM generation
- 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
- Cybershake Workflow Improvements
| - James
- Jason / Brendon
- Jonney
- James
- Jonney
- Jason / Jonney
|
|
|
SeisTech | - GM Selection for Empirical
- Integrate workflow into seistech master
- Synthetic tests for GCIM between Empirical and Simulation (1 rupture, N ruptures)For Daniel: - what tasks for him to do?
- Testing, trial calculations
- Automate documentation
- Front-end
Milestone #2- authentication.
user access to individual tab controlled by authentication- User data managed by API, and additional user data kept in a separate db
- Data integrity and consistency between Auth0 and separate db maintained.
- Milestone #3
- API call framework - plan the API proxy
- Create Mock API's with canned JSON response
- Call mocked API from the front end and ingest JSON. To demonstrate an example of full functionality of the front end
- Milestone #4: API – 2
- Create an API proxy - including error messages for restricted access
- Call existing Core API’s from the front end replacing the mocks.
- JWT authorisation between the proxy and the core API
- Milestone #5: Deployment of 3 core environments
- Deploy DEV, TEST/EA, PROD versions
- Deployment is fully automated via scripts and config files.
- Update or switch-over is easily achieved utilizing deployment slots
- Disruption is kept minimal when updated.
4) Empirical DS - DB calculation
| - Daniel / Claudio
- Background task (Jason)
- Andy
|
| Roadmap (scientific functionality list) Production - TODO (longer term tasks) |
IM Calc |
|
|
|
|
Bug fixes |
|
|
|
|
Seismic risk |
|
|
|
|
Machine Learning | - NN - GMM
- Implement an initial basic pipeline with some NN config + flexible feature selection & preprocessing
- Add hypo-depth to NN GMM dataset
- GM Classifier – see link
| Claudio |
| GM classifier - progess |
Empirical engine |
|
|
|
|
Vs30 |
|
|
|
|
Misc | - SimAtlas simulation+animation:
- Test auto workflow with batch 4. (total 100 faults)
- Once batch 4 is done. Keep fueling the fireBatch 5 - keeping continual work
- Data management policy
- (classification of data importance
.- )
- Plan to incorporate this as part of business as usual – what data do we need to keep and what can be regenerated as needed
- NoisePy
- NeSI allocation: Chat with NeSI, keep subscription allocation separate)
- Velocity Model basins
| - Sung/Jonney
- Sung
- Viktor
- Jason
|
|
|