-
Notifications
You must be signed in to change notification settings - Fork 108
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
Unable to clean ensemble records - will put ert3 in an unrunnable state. #2731
Comments
The source of the problem is that ensemble-wide records are currently stored in a "special" global ensemble. Cleaning that would require deleting that ensemble in ert storage. This is currently not supported and would have to added to Together with Jonas and Julius, we discussed this, and noted that ert storage may not match well with what we try to do in ert3, leading to such hacks as a special ensemble to store ensemble-wide records. We concluded that we should look into improving ert storage to resolve these and related issues. I would therefore suggest that we do not add new functionality to Therefore, it may be better to postpone resolving this bug until we have done that. |
I agree! Added this issue to the list of related issue for the storage discrepancy milestone (#2707) |
Closing as related to ert3, which is no longer the direction taken by the project. |
This issue could be irrelevant depending on #2707
Describe the bug
ert3 clean -all
will not remove ensemble wide records.A possible scenario is that an issue occurs while loading them into ert. Then there is no way to get back to a runnable state.
To Reproduce
Steps to reproduce the behavior:
pip install ert
ert3 init --examples polynomial
ert3 record load designed_coefficients experiments/doe/coefficients_record.json
At this point neither running an experiment, nor trying to clean and reload, will be possible
4.
ert3 run doe
ert3 clean --all
ert3 record load designed_coefficients experiments/doe/coefficients_record.json
(the double output of response is as observed in terminal)
Expected behavior
Be able to in some sort properly get data into ert and continue my work
Enviromment
The text was updated successfully, but these errors were encountered: