How to handle non-standard keywords

[opm]

How to handle non-standard keywords

[rolk]

I would suggest that all non-Eclipse keywords starts with OPM$ (or some other combination of OPM/FLOW and a special character). Schlumberger is very little likely to introduce something now with that prefix. I don't know about the design of the parser, but I reckon that it could be modified to scan for that exact prefix, and if found, lift the eight character restriction and just scan for whitespace as delimiter.

[OPMUSER]

ECLIPSE is on maintenance release cycle so it is highly unlikely that additional features (and keywords) will be added in the future. I concur that we need to identify non-Eclipse keywords and I don't think the nomenclature for this is terribly important, except that we will have to live with it forever and ever, so we need to choose carefully. So we could just go with a $ sign in front of the keyword and keep or relax the eight character limit.

As I mentioned previously, we could define two new keywords that defined and terminate OPM Flow keywords, similar to the ECHO and NOECHO keywords. So for example,

OPMSTART
SKPRWAT
.........
SKPRPOLY
.........
PINTDIMS
.........
OPMEND

With the OPMSTART/OPMEND keywords being usable in any ECLIPSE section. This has the advantage that we can have a separate section in the manual that defines all the non-standard keywords, instead of mixing them together. However, I would document the $SKPRPOLY option in the same manner.

I don't code in C++ so I don't which is the easier option to implement.