Background:

New Cybershake install structure (realization/[HF|LF|BB]) with yaml and params.py both present  is now available.

Parameter Folder Structure: Parameters and locations in new folder hierarchy

Tasks:

       remove params*.py usage from the files 1-14 for manual workflow

  1. install.py                                               8h
  2. set_runparams.py                               4h
  3. submit_emod3d.py                              4
  4. run_emod3d.sl.template                    4
  5. submit_post_emod3d                        2
  6. run_hf_mpi.sl.template                     1
  7. submit_post_emod3d.py                    4 
  8. tets_post_emod3d.sh                       1
  9. run_post_emod3d.sl.template          1
  10. install_bb.py                                        4
  11. run_bb_mpi.sl.template                        1
  12. submit_hf.py                                        4
  13. submit_bb.py                                       4
  14. statlist2gp.py                                         3
  15. test yaml on new install structure with benchmark 4h
  16. Decide exact params location in the new folder structure with team and complete Parameters and locations in new folder hierarchy    5h
  17. Genrate root_params.yaml by modifying script 1-13 according to 16  4h
  18. Genrate fault_params.yaml by modifying script 1-13 according to 16  6h
  19. Genrate sim_params.yaml by modifying script 1-13  according to 16   8h
  20. Genrate vm_params.yaml by modifying script 1-13  according to 16   4h
  21. write testing code and do benchmark testing                                         8h
  22. clean up the code and do benchmark testing                                         8h

Progress:

Task 1-21 done. All params*.py remove. Required functionalities for manual workflow all done and tested

We can run cybershake manual workflow with params versioning in the new install structure with yaml files

 

Todo:

1.Clean up the manual workflow and testing code.

2.Then merge params branch into master and do benchmark testing

3. Then make the automatic workflow work.

 

  • No labels