Structure of Codebase 

Image Modified

(from SW Codebase 2019 page : qcore, visualisation and GMSimViz are not listed.

This page is somewhat outdated, but contains some useful background)

...

• All the planned functionalities have been developed and tested
• Codebase has been cleaned up
• Good comments & documentation (README)
• Automated testing coverage over 80%
  
  

Ideally, we can have the package installed via "pip" command:

pip install qcore

The repositories we should aim to produce stable releases are (ordered by impact/risk analysis)

• IM_calculation
• Pre-processing
• Qcore
• Slurm_gm_workflow 

...

Moving Forward: Mid April - End of June

1. Stable release of IM_calc and Pre-processing repos : Initially small team of 2~3 piloting, polishing up the process
   1. IM_Calc: 
      1. Clean up
      2. Finish automated testing
      3. Comment style, 
      4. README.md 
      5. Release
   2. Pre-processing: 
      1. Better estimation, 
      2. Split the repo : Model_gen, Grid_gen
      3. Clean up
      4. Automated testing
      5. Comment style
      6. README.md
      7. Release
         
         
2. Slurm_gm_workflow & Qcore restructuringCompleting all features for SeisFinder2 
   1. Slurm_gm_workflow: 
      1. Restructure, split the repo. make all .yaml compliant
      2. Remove/update legacy code
      3. Integrate Pre-processing into automated workflow
      4. Logging
      5. Automated verification
      6. Estimation performance
      7. Visualisation
      8. Error handling
      9. Realisation name change
         
         
   2. Qcore
      1. Restructure
      2. Clean ujp
      3. Comments in Numpy style
      4. Increase automated unit test coverage
      5. API doc
      6. README
         
         
         
3. SeisFinder2: Feature completion (3months time frame)
   1. Integration of GM selection
   2. Verification and regression testing etc.
   3. Lite version(?)
4. README template : Example  https://gist.github.com/PurpleBooth/109311bb0361f32d87a2  : TODO, Changelog etc.
5. Standard for comment and API doc : Numpy styleNew featuresNumPy vs Google
6. Cybershake
   1. Include subduction
   2. Check the performance of new VM and run 1 cycle of Cybershake
   3. HF changes (inc. path duration)
   4. Deagg and determines more relevant faults, rerun Cybershake with less fault, higher res.