Assumed syntax in parameters.txt is not aligned with semeio

[berland]

Reference implementation for parameters.txt-parsing is in
https://github.com/equinor/semeio/blob/master/semeio/jobs/design_kw/design_kw.py

This is not in line with:

fmu-dataio/src/fmu/dataio/_utils.py

Line 220 in c3111c9

GLOBVAR:VOLON_FLOODPLAIN_VOLFRAC 0.256355

which interprets a nested dictionary structure from the keys based on colons in the key string.

Semeio actively ignores prefixes before colons in keys.

[perolavsvendsen]

I don't immediately understand the reasoning behind what semeio does, but is it a different use case? E.g. should outgoing metadata also just include parameters unique after stripping everything before colon (except exceptions i.e. LOG10_)?

The primary use case for these parameters in the metadata right now is for clients such as Webviz to be able to offer filtering based on them. E.g. "show me all data from iteration X where parameter Y has value Z".

[berland]

Semeio has taken a deliberate decision to ignore prefixes (before colon) when executing DESIGN_KW. If fmu-dataio then starts to add meaning to that otherwise ignored prefix, we need to be careful.

The reason for semeios decision is to let users switch between design matrix parameters (DESIGN_KW) and history matching parameter (GEN_KW, which always adds a prefix).

[berland]

Context: equinor/semeio#59 and equinor/semeio#163

[perolavsvendsen]

Thanks. fmu-dataio is not aware of the contents, it merely parses and puts into outgoing metadata for a data object. So the actual question then is probably how this should look like in the metadata. E.g when user switches between GEN_KW and DESIGN_KW.

[berland]

Problem is perhaps mitigated in #102