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

Two different seeds are reported in the ERT log files #8024

Closed
larsevj opened this issue May 30, 2024 · 1 comment · Fixed by #8062
Closed

Two different seeds are reported in the ERT log files #8024

larsevj opened this issue May 30, 2024 · 1 comment · Fixed by #8062
Labels

Comments

@larsevj
Copy link
Contributor

larsevj commented May 30, 2024

Describe the bug
If you do not set the random seed in the ERT config file, then the ERT log file will give you two different seeds which it claims can reproduce your run, and it is impossible to know which one is the correct one.

To reproduce
Steps to reproduce the behaviour:

  1. pip install ert
  2. ert ensemble_experiment poly.ert
  3. cat logs/ert-log-* | grep -i seed

Expected behaviour
Only one seed should be reported in the log file. And should perhaps only generate one seed internally as well?

Screenshots

2024-05-30 10:06:48,831 - ert.enkf_main - MainThread - INFO - To repeat this experiment, add the following random seed to your config file:
2024-05-30 10:06:48,831 - ert.enkf_main - MainThread - INFO - RANDOM_SEED 272546428914041008920690008309831108620
2024-05-30 10:06:50,177 - ert.enkf_main - ert_cli_simulation_thread - INFO - To repeat this experiment, add the following random seed to your config file:
2024-05-30 10:06:50,178 - ert.enkf_main - ert_cli_simulation_thread - INFO - RANDOM_SEED 314929226635236985384246148466110134237

Environment

  • ERT/Komodo release: [10.2]
  • Python version: 3.11
  • Remote/HPC execution involved: [no]
@larsevj larsevj added the bug label May 30, 2024
@sondreso sondreso moved this to Todo in SCOUT Jun 3, 2024
@sondreso
Copy link
Collaborator

sondreso commented Jun 3, 2024

Potentially closed by: #7501

@oyvindeide oyvindeide moved this from Todo to Ready for Review in SCOUT Jun 5, 2024
@dafeda dafeda moved this from Ready for Review to Reviewed in SCOUT Jun 5, 2024
@github-project-automation github-project-automation bot moved this from Reviewed to Done in SCOUT Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants