Jonas Grønås Drange

Should we include prefect ensembles and ert3 experiments in this milestone?

Updated proposal: What is shared between the clients and the server is: - the hierarchical structure of the entire experiment - a distributed log The hierarchical structure is a tree...

> Either the `experiment server` needs to hold all chunks of logs sent to clients Yes, I think this is probably best. There are multiple ways to truncate logs like...

Yeah, _OPEN_ is also ambiguous. I think _View_ is closer to the truth. Also, its appearance should match the fact that it is clickable (i.e. a button). This button should...

This is a good idea. I think, however, that the solution to this problem should be general. I.e. there's a configuration directive that allows you to pick up this file...

If RMS is not near the python interpreter, we're also planning to implement a _Reporter REST API_ that could be utilized as well.

But we write a lot of files in the run_path prior to running `job_dispatch.py`. So why isn't this caught earlier?

Majority of run models are now implementing this interface in this branch: https://github.com/jondequinor/ert/tree/complete-experiment-api

An implementation was started here https://github.com/equinor/ert/pull/2050 but abandoned because it did not fix the issue it was trying to fix.

**Transformation multiplexing/singleplexing** There's clearly a need for multiplexing transformations, i.e. transformations that create multiple records from one file, or vice-versa—or both. Transformations already do singleplexing with `from_record` and `to_record`. Multiplexing...