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.

Sign up for GitHub

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

Jump to bottom

Manual update should be disabled when no realizations have run #10500

Open
1 of 9 tasks
xjules opened this issue Mar 28, 2025 · 1 comment · May be fixed by #10519
Open
1 of 9 tasks

Manual update should be disabled when no realizations have run #10500

xjules opened this issue Mar 28, 2025 · 1 comment · May be fixed by #10519
Assignees
@jonathan-eq
Labels
bug

Comments

@xjules
Copy link
Contributor

xjules commented Mar 28, 2025 •
edited
Loading

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

After creating new experiment via manage experiments GUI and executing initialize form scratch, the user is allowed to run manual update, which then crashes with the following error:

Image

What did you expect to happen?

Manual update should be disabled for ensembles without realizations.

Steps to reproduce

Open poly example, create new experiment, initialize from scratch and select start simulation and do manual update.

Environment where bug has been observed

  • Python 3.11
  • Python 3.12
  • macOS
  • RHEL8
  • RHEL9
  • Local queue
  • LSF queue
  • Slurm queue
  • OpenPBS queue
@xjules xjules added the bug label Mar 28, 2025
@xjules xjules moved this to Todo in SCOUT Mar 28, 2025
@xjules xjules changed the title Manual update should be disable when no realizations have run Manual update should be disabled when no realizations have run Mar 31, 2025
@jonathan-eq jonathan-eq self-assigned this Apr 1, 2025
@jonathan-eq jonathan-eq moved this from Todo to In Progress in SCOUT Apr 1, 2025
@jonathan-eq
Copy link
Contributor

jonathan-eq commented Apr 1, 2025 •
edited
Loading

@xjules What if we only show the ensembles that have no realizations with RealizationStorageState.UNDEFINED?

@jonathan-eq jonathan-eq linked a pull request Apr 1, 2025 that will close this issue
Open
9 tasks
@jonathan-eq jonathan-eq moved this from In Progress to Ready for Review in SCOUT Apr 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jonathan-eq jonathan-eq

Labels
bug
Projects
SCOUT
Status: Ready for Review
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix gui manual update and evaluate ensemble able to run with no defined realizations jonathan-eq/ert
2 participants
@xjules @jonathan-eq