One liner(s) for zone range information

[jcrivenaes]

The current Drogon example has now 6 script all doing zone to grid K counting mapping (different formats, different purpose). This becomes a burden of the end users, and there is a great potentiaal to simplify using a combinaion of fmu.tools and fmu.dataio

Propose to simplify according to the following style:

[mferrera]

Discussion 30 Sept 2024:

Summary

The consensus is that the context around this mapping needs to be matured and this is probably not a target for simplified functions yet. It may become one when approached from the top-down, cf #392.

Also that the format for .lyr files, in general, seems odd and possibly unnecessary to support by itself. It might be better contained by a .yml scheme with some script in fmu.tools to translate it when it is needed or as metadata contained within the grid metadata.

Context

Zone range information (zone->layer mapping) is used for several purposes. We are currently creating dataframes, .txt, .csv, and .lyr files for layers/zonations in Drogon.

• .yml files are used for QC in GRID3D_HC_THICKNESS and GRID3D_AVG_MAP
• .csv (verbose) zone->layer mapping (used in gendata_rft?)
• .txt (verbose) zone->layer mapping. Readable by ResInsight
• .lyr files can be used as input to
  • ResInsight
  • WellCompletions Webviz plugin

Use

This information is needed for Eclipse grids as they dont have zonation information

• But, currently do not upload Eclipse grids to Sumo (is this a pre-req for doing so?)
• Could this be part of SIM2SUMO instead?

The dataframe-generated format is uploaded to Sumo, none of the others are

• But, not clear if this is currently used anywhere

Implementation

One idea is to codify this data within grid metadata

• Essentially, these are already metadata for the grid zonation
• It can just be generated and attached within it when exporting grids
  • Or, exported separately

Possible action items

• Refine, specify yaml format
• See if ResInsight is interested in supporting this format
• Add more support in fmu.tools for these
  • I.e., fmu-tools can take in the yaml format and write out the .lyr, .txt, .csv formats as needed
• Propose to Drogon that these exports be simplified (i.e. try to land on one format) irrespective of the above action items

Appendix

.lyr format:

ResInsight has a page about this format here. Notably it also supports a color as a third column, which is not output by current Drogon exports and probably should not be.

It also supports the text format written below, calling is "FMU Layer Zone Table".

'Valysar'    1 - 10
'Therys'    11 - 27
'Volon'    28 - 32

.yml format:

zranges:
  - Valysar: [1, 10]
  - Therys: [11, 27]
  - Volon: [28, 32]

.txt format:

1 Valysar
2 Valysar
...
11 Therys
12 Therys
...
28 Volon
29 Volon
...

.csv/dataframe format:

The dataframe exported by dataio has the column labels LAYER,ZONE while "hand-made" csv exports do not.

1,Valysar
2,Valysar
...
11,Therys
12,Therys
...
28,Volon
29,Volon
...