Øyvind Eide
Øyvind Eide
In the documentation there is a pretty good summary of what it does: ```# Observations grouping by type is performed: An observation type is defined as shown on the ERT...
We should be able to validate this by checking if there is a `SummaryConfig` and that there should be an `ECL` or `flow` forward model, this should just be a...
In terms of closing this, we can add a cross validation at startup. If there is a SummaryConfig (i.e. we expect to read summary files after the forward model), but...
Doing some testing, and looks good so far! It would be great if I also could see what `` would be replaced by in the runpath (read only), adding a...
For more contextual information, from (@verveerpj): **Issue** Recently auto scaling for controls has been added in the form of the `auto_scale` keyword. This keyword directs the optimizer to scale the...
Related to: https://github.com/equinor/everest-models/issues/94 and https://github.com/equinor/everest-models/issues/93, and should be coordinated somewhat in time. Should also add documentation for how the scaling works.
This is somewhat related to the ensemble evaluator, as that has seen significant upgrades related to this. That means this issue might be blocked for now, but not 100% sure.
Blocked by: #8754
A warning here is probably a good idea. We should make sure the user know that deletion is slow, and should probably make them do it on their own, but...
Also be aware that ert already has functionality for this, so if we can align the two, that is beneficial.