Storage of GMF Scenario IMT information is inconsistent
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenQuake Engine |
Fix Released
|
High
|
Michele Simionato |
Bug Description
The storage of IMT information for `GmfScenario` results (https:/
This causes results exported in XML format to be slightly wrong.
We get this:
<nrml xmlns:gml="http://
<gmfSet>
<gmf IMT="SA(0.1)">
<node gmv="1.
<node gmv="1.
<node gmv="1.
</gmf>
...
We expect this:
<nrml xmlns:gml="http://
<gmfSet>
<gmf IMT="SA" saPeriod="0.1" saDamping="5.0">
<node gmv="1.
<node gmv="1.
<node gmv="1.
</gmf>
...
Changed in oq-engine: | |
assignee: | nobody → Michele Simionato (michele-simionato) |
Changed in oq-engine: | |
status: | New → In Progress |
Changed in oq-engine: | |
importance: | Undecided → High |
Changed in oq-engine: | |
status: | In Progress → Fix Committed |
Changed in oq-engine: | |
milestone: | none → 1.0.0 |
status: | Fix Committed → Fix Released |
There is an easy fix in the function openquake. engine. db.models. get_gmfs_ scenario. I have also added in the export tests a check to make sure that the generate XML is valid for the NRML schema. See https:/ /github. com/gem/ oq-engine/ pull/1132