For instance, for a classical PSHA calculation that requires hazard curves, hazard maps and uhs the output folder should look like (considering a source model logic tree containing a single source model with ID = 1, and a GSIM logic tree with two gmpes for a single tectonic region type with ID=1 and ID=2):
- job_1:
- hazard_curves: - hazard_curves_1_1.xml - hazard_curves_1_2.xml - hazard_curves_mean.xml - hazard_curves_quantile_0.1.xml - hazard_curves_quantile_0.9.xml
- hazard_map: - hazard_map_1_1.xml - hazard_map_1_2.xml - hazard_map_mean.xml - hazard_map_quantile_0.1.xml - hazard_map_quantile_0.9.xml
- uhs: - uhs_1_1.xml - uhs_1_2.xml - uhs_mean.xml - uhs_quantile_0.1.xml - uhs_quantile_0.9.xml
To facilitate users in browsing hazard results generated by oq-engine, we need to better organize the hazard results when they are serialized to xml.
For each calculation a folder has to be generated, with the following structure:
- job_id: result_ type1:
- hazard_ result_ logic_tree_ id1.xml
- hazard_ result_ logic_tree_ id2.xml
….
- hazard_ results_ mean.xml
- hazard_ results_ quantile_ quantile_ level1. xml
- hazard_ results_ quantile_ quantile_ level2. xml result_ type2:
….
- hazard_
- hazard_
- hazard_ result_ type3:
….
For instance, for a classical PSHA calculation that requires hazard curves, hazard maps and uhs the output folder should look like (considering a source model logic tree containing a single source model with ID = 1, and a GSIM logic tree with two gmpes for a single tectonic region type with ID=1 and ID=2):
- hazard_ curves_ 1_1.xml
- hazard_ curves_ 1_2.xml
- hazard_ curves_ mean.xml
- hazard_ curves_ quantile_ 0.1.xml
- hazard_ curves_ quantile_ 0.9.xml
- hazard_map_1_1.xml
- hazard_map_1_2.xml
- hazard_map_mean.xml
- hazard_ map_quantile_ 0.1.xml
- hazard_ map_quantile_ 0.9.xml
- uhs_1_1.xml
- uhs_1_2.xml
- uhs_mean.xml
- uhs_quantile_ 0.1.xml
- uhs_quantile_ 0.9.xml
- job_1:
- hazard_curves:
- hazard_map:
- uhs: