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

Unexpected failures if runpath string is not properly formatted #9313

Open
2 of 10 tasks
larsevj opened this issue Nov 22, 2024 · 0 comments
Open
2 of 10 tasks

Unexpected failures if runpath string is not properly formatted #9313

larsevj opened this issue Nov 22, 2024 · 0 comments

Comments

@larsevj
Copy link
Contributor

larsevj commented Nov 22, 2024

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

A user had forgotten to include the <> around the ITER and IENS in the runpath format string. This resulted in the gui showing all realizations finished successfully however only the last realization showed progress for each forward model step. Reason being that all realizations ran in the same runpath folder. Ert logged a warning due to no substitution string, but this is difficult for a user to notice.

What did you expect to happen?

Should give a better warning if there is no and , or %d?

steps to reproduce

Environment where bug has been observed

  • python 3.10
  • python 3.11
  • python 3.12
  • macosx
  • rhel7
  • rhel8
  • local queue
  • lsf queue
  • slurm queue
  • openPBS queue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

2 participants