Eclipse Input Data : Import custom keyword data

[hhgs]

When importing Input data on grdecl-format, the associated keyword for the data can be user defined in many modeling workflows. And the user defined keywords will typically not be an Eclipse static keyword.

To support these situations, a more flexible parsing of grdecl-data is needed. This could be to recognize when number of elements match the size of a read grid model. OPM-parser may have a custom JSON scheme for this.

[alfbr]

Not sure how convenient the Json set-up is in this case. It is a very specific use case, so it should be straight forward to code the parsing directly in Resinsight with the wanted functionality.

[andlaus]

When importing Input data on grdecl-format, the associated keyword for the data can be user defined in many modeling workflows. And the user defined keywords will typically not be an Eclipse static keyword.

I thought that these input grids are usually not hand-written but produced by some graphical modelling tools? are these additional keywords extensions by those tools or really user defined? In both cases, I suppose that the better fix would be to do this within opm-parser: for a set of well defined keywords, you can add a bunch of JSON files (maybe with some regular expression name matching, cf. the deck_name_regex attribute of the JSON files), if they really are completely arbitrary, "catch all" keyword support could be added to opm-parser fairly easily...