Revisit binary disaggregation matrix result structure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenQuake (deprecated) |
Fix Released
|
Medium
|
Lars Butler |
Bug Description
Disaggregation NRML results are currently structured to assume 1 HDF5 file per result type, per site, per realization, per poe, etc. For example:
<?xml version="1.0" encoding="UTF-8"?>
<nrml xmlns:gml="http://
xmlns="http://
gml:
<disaggrega
</disaggreg
</nrml>
However, this can result in TONS of files in a large calculation. Thus, the python code written to write the data subsets (magdistpmf, latlonmagpmf, etc.) writes all types of results for a given site+poe+
Technically, we could keep the NRML structure the same and simply specify the same path for a collection of results. Like so:
<?xml version="1.0" encoding="UTF-8"?>
<nrml xmlns:gml="http://
xmlns="http://
gml:
<disaggrega
</disaggreg
</nrml>
Should we leave it like this (to allow flexibility of using individual files or separate files)?
Changed in openquake: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Lars Butler (lars-butler) |
milestone: | none → 0.4.6 |
Changed in openquake: | |
status: | Confirmed → In Progress |
Changed in openquake: | |
status: | In Progress → Fix Committed |
Changed in openquake: | |
status: | Fix Committed → Fix Released |
To avoid duplicating the same path several times, what we can do is changing the schema so that the disaggregationM atrixSet element contains only one path. esultField element, because they are common to all the nodes (that is locations) in the file.
The PMF types contained in the hdf5 file can be reported as attributes of the disaggregationR