SDAC - configuration file changes for Scenario Damage Assessment

Bug #922106 reported by Muharem Hrnjadovic
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenQuake (deprecated)
Fix Released
Medium
Unassigned

Bug Description

[et=11h]
[at=]

Add/implement the configuration file changes for the Scenario Damage Assessment Calculator.

Tags: risk sdac
tags: added: risk
tags: added: sdac
John Tarter (toh2)
description: updated
Changed in openquake:
importance: Undecided → Medium
milestone: none → 0.6.0
John Tarter (toh2)
summary: - configuration file changes for Scenario Damage Assessment
+ SDAC - configuration file changes for Scenario Damage Assessment
John Tarter (toh2)
Changed in openquake:
milestone: 0.6.0 → 0.6.1
description: updated
Revision history for this message
Andrea Cerisara (acerisara) wrote :

I've just had a discussion with Vitor about this feature. This was the original requirement:

"""
In order to incorporate this calculator within OpenQuake, the configuration file needs to support a set of new parameters. The following list describes them:

* flag to indicate that the Scenario Damage Assessment Calculator will be triggered.
* flag to indicate if aggregated damage distributions should be computed.
* flag to indicate if a collapse map should be extracted.
"""

The idea is to always compute the aggregate damage distributions and the collapse map without putting any flag in the configuration file. If the user specifies the "--output-type=xml" parameter from the command line both artifacts will be stored as nrml files. Also, the data will be available in the database to be extracted with the extract tool.

Changed in openquake:
assignee: nobody → Andrea Cerisara (andreacerisara-b)
status: New → In Progress
Revision history for this message
Andrea Cerisara (acerisara) wrote :

The configuration file for this calculator will be exactly the same as for the Scenario calculator, except for the [RISK] section where we will have a FRAGILITY key (for the fragility model) instead of the standard VULNERABILITY key.

Changed in openquake:
status: In Progress → Fix Committed
Changed in openquake:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.