Structure of Codebase
(from SW Codebase 2019 page : qcore, visualisation and GMSimViz are not listed.
...
- Stable release of IM_calc and Pre-processing repos : Initially small team of 2~3 piloting, polishing up the process
- IM_Calc:
- Clean up
- Finish automated testing
- Comment style,
- README.md
- Release
- Pre-processing:
- Better estimation,
- Split the repo : Model_gen, Grid_gen
- Clean up
- Automated testing
- Comment style
- README.md
- Release
- IM_Calc:
- Slurm_gm_workflow & Qcore restructuring
- Slurm_gm_workflow:
- Restructure, split the repo. make all .yaml compliant
- Remove/update legacy code
- Integrate Pre-processing into automated workflow
- Logging
- Automated verification
- Estimation performance
- Visualisation
- Error handling
- Realisation name change
- Qcore
- Restructure
- Clean ujp
- Comments in Numpy style
- Increase automated unit test coverage
- API doc
- README
- Slurm_gm_workflow:
- SeisFinder2: Feature completion (3months time frame)
- Integration of GM selection
- Verification and regression testing etc.
- Lite version(?)
- README template : Example https://gist.github.com/PurpleBooth/109311bb0361f32d87a2 : TODO, Changelog etc.
- Standard for comment and API doc :https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html#example-googleNumPy vs Google
- Cybershake
- Include subduction
- Check the performance of new VM and run 1 cycle of Cybershake
- HF changes (inc. path duration)
- Deagg and determines more relevant faults, rerun Cybershake with less fault, higher res.
...