diff --git a/docs/everest/development.rst b/docs/everest/development.rst index b7728e9f4fa..c81d3affd26 100644 --- a/docs/everest/development.rst +++ b/docs/everest/development.rst @@ -91,8 +91,8 @@ The mapping from data models in EVEREST and ERT is done in the `ropt` library, i `Batches` in EVEREST can contain several different configurations depending on the algorithm used. Gradient-based algorithms can have a single function evaluation (`unperturbed controls`) per ``, a set of `perturbed controls` per `` to evaluate the gradient, or both. Derivative-free methods can have several function evaluations per `` and no `perturbed controls`. -**NOTE**: the optimizer may decide that some ``s are not needed, these are then skipped and the mapping from `ropt` -should reflect this (i.e., less ``s in the batch results than expected). +**NOTE:** the optimizer may decide that some `` are not needed, these are then skipped and the mapping from `ropt` +should reflect this (i.e., less `` in the batch results than expected). Another thing to note is that continuity for `realizations` between `ensemble` exists; however, this is not the case for `simulations` in `batches`. A `batch` can contain several different configurations (Fig 5) and `simulation 0` for ` = 0` can be either `unperturbed`