Julius Parulek
Julius Parulek
> Agree, but as you said .. not in this PR :)
> > Noting a crash: > > ``` > > $ ert es_mda --enable-experiment-server poly.ert > > Experiment failed: Phase must be an integer between (inclusive) 0 and 2, got...
We should consider making the Protobuf schema more flat. Otherwise we need to propage all ids to the jobs, which still is a viable solution though.
This should include creating a Workflow type messages in the protobuf schema, replacing thus the currently CloudEvents handling PRE_HOOKS and POST_HOOKS.
I would suggest to remove the `index` argument as it's quite redundant since the `index` is always built; i.e. inferred from the `data` as described :top:.
The `protobuf` is now relaxed to `protobuf
> What do you think?: `def _publish_event(self) -> def _event_publisher(self)` > > As this is a function that is designed to continuously publish events. Not a biggie, just a small...
Based on our current "protobuf" agenda the state_machine is implemented as a single experiment [state](https://github.com/equinor/ert/blob/main/src/ert/experiment_server/_schema.proto). Now it is very straightforward to update a node (eg. message Step {..}), wherein protobuf...
Nice start @markusdregi ! For `webviz-ert` purposes we need to classify the numerical records into `parameters`, `responses` and `observations`, which means to provide a fixed format also (ie., dimensionality, index...
Let's see if this is still an issue. Update: yest, that's the current behavior that it does not update the realizations in details view as failed, but left them when...