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

Simulator cache not persistent across runs #10273

Open
9 tasks
yngve-sk opened this issue Mar 11, 2025 · 1 comment
Open
9 tasks

Simulator cache not persistent across runs #10273

yngve-sk opened this issue Mar 11, 2025 · 1 comment
Labels

Comments

@yngve-sk
Copy link
Contributor

What happened? (You can include a screenshot if it helps explain)

Since we now get simulator results from ERT storage, we should (if the experiment exists within the optimization output folder) be able to load an existing experiment, so that it can be searched for cached results.

Expected behavior:

  1. Run a case normally from the CLI
  2. Run it again and expect ROPT to skip all simulations as it already has the results

It is up for discussion how exactly we do this. Some things to consider:

  • --new-run will wipe the storage clean, but we could add another option to keep the storage, or opt for keeping the ERT storage by default.
  • This implies we only have one experiment per everest optimization case. If we have multiple experiments in the same storage, we need some mapping, which we currently have no setup for handling, so would opt for going with just one for now.

What did you expect to happen?

No response

steps to reproduce

Environment where bug has been observed

  • python 3.11
  • python 3.12
  • macosx
  • rhel7
  • rhel8
  • local queue
  • lsf queue
  • slurm queue
  • openPBS queue
@yngve-sk yngve-sk added the bug label Mar 11, 2025
@yngve-sk yngve-sk moved this to Backlog in SCOUT Mar 11, 2025
@yngve-sk
Copy link
Contributor Author

Duplicate of #10037

@yngve-sk yngve-sk marked this as a duplicate of #10037 Mar 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Backlog
Development

No branches or pull requests

1 participant