-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changed the damage outputs #10079
Changed the damage outputs #10079
Conversation
What's the main change being introduced in this PR? |
The headers, as written above. For instance
Or there is a single loss type (therefore no need to specify it) or |
Notice that no functionality is lost, in the worst case you can run multiple calculations (i.e. set total_losses=structural, then total_losses=nonstructural, then total_losses=contents). It can be annoying for the users but the simplification allows me to progress with #9746, so I need it right now. |
Companion of gem/oq-engine#10079
Warning: this PR is expected to BREAK:
check_all_outputs
/extract/agg_damages/<loss_type>
REST API, i.e. the QGIS pluginThis change is crucial for implementing #9746.
NB: classical_damage/case_master uses now
total_losses = structural+nonstructural
.NB: the numbers in case_7 are correct being
total_losses = structural+nonstructural+contents
.NB: specifying total_losses is now mandatory in damage calculations with multiple loss types