We need to store the exposure model in db when job starts
Bug #932736 reported by
Muharem Hrnjadovic
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenQuake (deprecated) |
Fix Released
|
Medium
|
Muharem Hrnjadovic | ||
Bug Description
Related to bug #809213 -- when a calculation starts we need to store the exposure model in the database first. All risk calculation logic shall access it from there using django model classes.
| Changed in openquake: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| assignee: | nobody → Muharem Hrnjadovic (al-maisan) |
| milestone: | none → 0.6.0 |
| tags: | added: 1model exposure risk techdebt |
Revision history for this message
| Muharem Hrnjadovic (al-maisan) wrote | #1 |
| Changed in openquake: | |
| status: | Confirmed → In Progress |
Revision history for this message
| Muharem Hrnjadovic (al-maisan) wrote | #2 |
| Changed in openquake: | |
| status: | In Progress → Fix Committed |
| Changed in openquake: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
There is no clean or cheap way to compute the per-asset value using the dicts thrown back by the NRML parser.