Save and export event loss data for specific assets

Bug #1383291 reported by Michele Simionato
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenQuake Engine
Fix Released
Critical
Michele Simionato

Bug Description

The idea is to have configuration parameters specific_assets and specific_assets_csv to specify the assets where the event loss should be stored.
Moreover we want to perform disaggregation only on the specified assets.

We should clarify what to do when the specific_assets file contains asset_refs not in the exposure (for instance due to a misprint).
Should we:

1) simply ignore the non-existing assets
2) print a warning
3) raise an error?

Moreover, if a rupture gives a null loss to an asset, should we save the zero or not? Saving a zero is wasteful, but at least it is unambiguous (an asset could not appear because of a bug, not because its loss is zero).

Should we add a demo demoing the new feature?

Revision history for this message
Michele Simionato (michele-simionato) wrote :
description: updated
Changed in oq-engine:
assignee: nobody → Michele Simionato (michele-simionato)
milestone: none → 1.0.1
importance: Undecided → Critical
status: New → In Progress
description: updated
description: updated
description: updated
Changed in oq-engine:
status: In Progress → Fix Committed
Changed in oq-engine:
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.