-
Hi! I am trying to run the scenario using the conditioned GMF calculator on Windows OS, however, the calculation fails on current master (**154b59f643f3f53e81b7382fd0a164ac59337129**). As per instruct…
-
# Implementation of Infrastructure Risk Assessment in OpenQuake
## Introduction
This issue introduces the implementation of infrastructure risk at system level in OpenQuake.
For the implementation,…
-
Dear Volkan,
I met a problem when I runing the 'Example 3.ipynb'. This issue happens in the 'hazard_curve(poes, results_dir, post_dir)' commend, under the '2) Post-process PSHA results' session. Th…
-
This line in the Kuehn model (https://github.com/gem/oq-engine/blob/b0a5b94ad4dad625dee2023972ef007286325d72/openquake/hazardlib/gsim/kuehn_2020.py#L534) assumes that the model["R"] values and the cor…
-
How to reproduce:
Start a scenario_risk calculation which produces no loss.
Calculation log:
```
2023-06-19T10:11:57.05,INFO,SpawnProcess-43/438836,erm@ermd running /tmp/tmpqze0bmd4/calc_9/job.i…
-
It is possible to run calculations with job.ini files with duplicated fields (for example, `aggregate_by`), and the engine uses the latest value passed. Instead, an error should be raised.
-
The current risk metrics supported by OpenQuake are insufficient for several use cases. It is fundamental to expand the current list of loss types to the following two parameters:
**1. - Damaged bu…
-
There are some units hard-coded for different loss types.
```
def get_units(self, loss_types):
"""
:param: a list of loss types
:returns: a string of space-separated u…
-
Additional metadata needed to adequately describe a file containing stochastic event set? Or is current structure sufficient by using `event_set` but not nesting events under it but instead linking to…
-
## What is the context or reason for the change?
Main changes proposed
- Remove `occupancy`, `occupancy_time`, `taxonomy_code` from exposure metadata, as this is contained within the data or prov…