search

equinor / ert

ERT - Ensemble based Reservoir Tool - is designed for running ensembles of dynamical models such as reservoir models, in order to do sensitivity analysis and data assimilation. ERT supports data assimilation using the Ensemble Smoother (ES), Ensemble Smoother with Multiple Data Assimilation (ES-MDA) and Iterative Ensemble Smoother (IES).
https://ert.readthedocs.io/en/latest/
GNU General Public License v3.0
103 stars 107 forks source link

ERT crashed unexpectedly when opening empty responses.json #8365

Closed yngve-sk closed 2 months ago

yngve-sk commented 3 months ago

EDIT: The user was about to somehow run ERT and got this error: ERT crashed unexpectedly with "SummaryConfig must be given at least one key", with an empty responses.json (might not be the direct cause of this error). Recommend checking the user report slack link.

Empty is OK if there are no responses. Only issue if there is a mismatch between current ert config and responses.json content when doing a simulation run (should not be possible). The user report was describing a "run", if that was running an experiment, the responses.json should be written as a result of the ert config contents. When just opening a storage in itself (i.e., when opening Manage Experiments) it is not necessarily corresponding to the current ert config if it changed.

Ref user report: https://equinor.slack.com/archives/CDPJULWR4/p1720115022000759

oyvindeide commented 2 months ago

An empty file is by design, as that means no responses are expected. It is still valid json, so we can load the spesification from it. In the edge case of no responses registered, and ensemble will report HAS_DATA, although you could argue that it does not have data.

sondreso commented 2 months ago

Empty responses.json should not result in an error message when opening ERT (and even when migrating). As @oyvindeide says, this is by design.

larsevj commented 2 months ago

Was reported that the user had manually manipulated storage, which provoked this error. Since we cannot guard against all such cases, I will close this issue for now.