Background
The current folder structure is
RunFolder/[Type of Run]/[RunVersion]/Runs/[fault]/[calc]/[realisation]
The new proposed folder structure is:
RunFolder/[Type of Run]/[RunVersion]/[MethodologyVersion]/Runs/[fault]/[realisation]/[calc]
Type of Run: is defined as the collection e.g. Cybershake, Validation etc
Run Version: is the version of the run e.g. 18p6 for Cybershake 18p6
Methodology Version: is the version of the calculation e.g. GMsim15.1 or Emp18p6
fault: is the fault name e.g. AlpineF2K
realisation: is the realisation name e.g. AlpineF2K-HYP01-47-S1244
calc: Is the type of calculation being done e.g. LF, HF, BB, IM_Calc
Notes
Story / Deliverable
When User install and run a Cybershake / Validation workflow it will store the data in the new proposed folder structure
Tasks
1) Create a benchmark Cybershake v18p9 run - Done
2) Make the changes required to folder structure - 1.5 Day - Done
3) Run Cybershake v18p9 again - 1 Day - Done
4) Check to see the results are the same - 0.5 Day
5) Make changes as necessary - 0 - 1 Day
Progress
For manual install/simulation the script will now take only one SRF. Related codes are all modified to read new folder directory.
(This means we might need a wrapper code for users that still prefer having multiple srf runs in one install)
Modified scripts for automated workflow. Tested with v18p9 runs. workflow seems fine, but simulation results are not verified.