Julius Parulek

Consume Protobuf events from dispatcher and pass them to the statemachine

1

**Issue** Resolves #3699 **Approach** First sketch of consuming protobuf events in the experiment server. ## Pre review checklist - [ ] Added appropriate release note label - [ ] PR...

Create experiment builder

1

It would make sense to implement experiment builder, exposing thus `simulation_arguments` as different parameters that currently come in a form of dictionary entries. Part of such builder is to then...

Process Protobuf events in experiment server

1

Ingest Protobuf events in the experiment server. Depends on https://github.com/equinor/ert/issues/3616. @BjarneHerland's PR can be used as source of inspiration https://github.com/equinor/ert/pull/3568

Add Protobuf experiment level events to base run models

1

Currently there was not need to produce events from based run models, but experiment server does produce the events (CloudEvents at the moment), which should become Protobuf events.

Create experiment_id when running Experiment Server

1

There is an ambiguity between `Ensemble.id_` / `BaseRunModel._ee_id` and `experiment_server_id`. We should create experiment id properly and propagate it correctly to Ensemble Evaluator and further to the JobRunner. Please see:...

Before we decide whether to employ gRpc we should make some performance analysis wrt. websockets and protobuf.

We need to provide Protobuf objects from jobqueue manager also. Take a look at https://github.com/equinor/ert/issues/3616 for reference.

See more details in https://github.com/equinor/ert/issues/3443

Based on to the successful performance measurement tests https://github.com/equinor/ert/issues/3581 and once https://github.com/equinor/ert/issues/3616 is completed, Protobuf data format should be employed for the client / GUI end of the experiment server...

Depends on #3415