Skip to content

fmu-dataio can't distinguish unmappable from not mapped yet #307

Description

@tnatt

The build_global_config_stratigraphy function is responsible for converting mappings from .fmu into the legacy config.stratigraphy format used by fmu-dataio.

It works by marking all horizons and zones mapped to SMDA as stratigraphic=True. All remaining horizons and zones defined in .fmu under config.rms are set to stratigraphic=False.

The challenge is that stratigraphic=False currently covers two different cases:

  • The horizon/zone has explicitly been marked as unmappable by the user.
  • The horizon/zone has not yet been mapped.

Because these cases can't be distinguished, fmu-dataio cannot raise an error or warning when users forget to map a horizon or zone (as it previously did). As a result, data that could and should be mapped to SMDA may silently end up with stratigraphic=False.

Not sure how and where to best solve this, or even if we want to solve this... but we should at least have a way to clearly indicate to users that some horizons or zones have not yet been mapped, either to SMDA or as explicitly unmappable. Right now it is only the checklist in the GUI that will indicate it.

Discussions needed 🙂

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions