EPIC: Harmonize with ERT terminology and concepts where possible

[perolavsvendsen]

fmu-dataio	ERT
case	experiment

Hypothesis: "Case" (fmu-dataio) is the same as "Experiment" (ERT).

Investigate if this is the case. Pay extra attention to when and why the Experiment ID is changing.

Current assumptions on fmu.case.uuid

• Does not change, even if new ERT runs are directed to the same runpath (requirement)
• Reflects current behavior on /scratch (overwriting, appending, etc) (requirement)

(Suspicion is that the rules for regenerating experiment.id is different, and will not be 1:1 with current behavior of files on /scratch, and hence not follow this principle.)

• Include _ERT_EXPERIMENT_ID in case metadata #670

Possible next steps:

• When experiment ID is exposed in metadata, and has been for a while, get feedback from e.g. Sumo and Webviz if this is in fact identical.
• Consider using the experiment.ID as fmu.case.uuid

If experiment.id is sufficiently different from fmu.case.uuid, consider to keep both

• experiment ID will provide a useful link to ERT, possibly.

---

fmu-dataio	ERT	Webviz
iteration	ensemble	ensemble

Rename from "iteration" to "ensemble"?

• Rename fmu.iteration to fmu.ensemble #459

---

End state: Some form of harmony between concepts used by/in ERT and concepts used in results handling