Save only non zero losses in the table event_loss_asset

Bug #1427226 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

This provides a tremendous speedup, so big that it is worth the risk of not knowing if an asset is missing because of a bug or because it is zero. Otherwise computations would be impossibly slow.

Revision history for this message
Michele Simionato (michele-simionato) wrote :
Changed in oq-engine:
importance: Undecided → Critical
assignee: nobody → Michele Simionato (michele-simionato)
milestone: none → 1.4.0
status: New → In Progress
Revision history for this message
Michele Simionato (michele-simionato) wrote :
Revision history for this message
Michele Simionato (michele-simionato) wrote :

Also, the exported event_loss_asset CSV file should have the same order in the test than when exported:

https://github.com/gem/oq-risklib/blob/save-non-zero-losses/openquake/qa_tests_data/event_based_risk/case_2/expected/event_loss_asset.csv

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.