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
What happened? (You can include a screenshot if it helps explain)
Currently no matter what value you set for iteration in the load results manually tool, it will only try to load from the iteration that is connected to the ensemble. If you have manually created a new ensemble, this is usually 0.
Reason is the following code which is used to load results from runpath, in libres_facade.py:
def load_from_forward_model(
self,
ensemble: Ensemble,
realisations: npt.NDArray[np.bool_],
iteration: Optional[int] = None,
) -> int:
if iteration is not None:
warnings.warn(
"The iteration argument has no effect, iteration is read from ensemble",
DeprecationWarning,
stacklevel=1,
)
What did you expect to happen?
Would expect the tool to load from the iteration specified.
Had a chat with a couple of users who use this functionality, and we came to the following that would be flexible enough to cover their needs, while keeping the internals consistent:
When manually creating an experiment it should be possible to also set the iteration number in addition to the experiment and ensemble name. It should default to 0
In the load results manual window the runpath should be editable so they can load from anywhere
In the load results manual window we should write what will be replaced by when loading results. This should not be editable, the user can get the same results by editing the runpath manually in step 2.
What happened? (You can include a screenshot if it helps explain)
Currently no matter what value you set for
iteration
in the load results manually tool, it will only try to load from the iteration that is connected to the ensemble. If you have manually created a new ensemble, this is usually 0.Reason is the following code which is used to load results from runpath, in
libres_facade.py
:What did you expect to happen?
Would expect the tool to load from the iteration specified.
steps to reproduce
Environment where bug has been observed
--enable-scheduler
The text was updated successfully, but these errors were encountered: