Skip to content
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

Everest Storage: Persistent storage for re-runs #10037

Open
yngve-sk opened this issue Feb 11, 2025 · 0 comments
Open

Everest Storage: Persistent storage for re-runs #10037

yngve-sk opened this issue Feb 11, 2025 · 0 comments

Comments

@yngve-sk
Copy link
Contributor

Currently, we assume an Everest experiment runs once, and is then done. When we store Everest results in storage on the file system, it may make sense to be able to re-run the optimization part, but not re-evaluate the forward model in ERT. Everest is currently not set up for this, but it could be.

Rough idea of how to complete this:
When opening an Everest config, if the optimization output directory already contains an ERT storage with an experiment that pertains to that specific config (discriminated by name of the config file for example), set that experiment as the "active storage" of the run of the EverestRunModel. Ideally, running the run model should run as normal, but will get simulator cache hits on all controls to evaluate, so only the optimization part is re-run (disregarding some file reading from ert storage)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

1 participant