You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
pip install ert
ert ensemble_experiment poly.ert
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]
The text was updated successfully, but these errors were encountered:
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:
pip install ert
ert ensemble_experiment poly.ert
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
Environment
The text was updated successfully, but these errors were encountered: