You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a larger issue which tries to link several issues into one.
Currently the current format of the stratigraphy block in the global config has several limitations
The format should be improved so that (at minimum)
there exists a clear relationship between zones and horizons
the format is suitable for including this block into the case metadata e.g. under fmu.model.stratigraphy as it is important information in various visualization contexts.
thoughts
improve user friendliness and allow for easy updates by creating a simplified export function of stratigraphy from the model from inside RMS e.g. "export_stratigraphy".
keep the stratigraphy mapping to official SMDA names as separate dictionary
could the .fmu be utilized in this new way?
how to handle multiple stratigraphic columns and also grid zone names and the relationship between the intervals?
Other important issues related to mapping masterdata to fmu data, that might influence the thought process
This is a larger issue which tries to link several issues into one.
Currently the current format of the stratigraphy block in the global config has several limitations
The format should be improved so that (at minimum)
fmu.model.stratigraphy
as it is important information in various visualization contexts.thoughts
.fmu
be utilized in this new way?Other important issues related to mapping masterdata to fmu data, that might influence the thought process
The text was updated successfully, but these errors were encountered: