Sorry I forget one aspect:
*Parser & defaults*: The default values are used in two cases: 1. If the deck contains explicit default markers of the form 'n*' 2. If a record is terminated prematurely. If the Json configuration has a default value specified for the item(s) in question it is simple - the deck item is initialized with the default value and everything is hunka dory. However - what to do if the item does not have a default value specified, e.g. WELSPECS / --- A fully defaulted record / -- Keyword termination This keyword clearly does not make much sense, and Eclipse will abort during the parse stage. I want the parser to accept this, and then let the Schedule constructor throw an exception when we are trying to access the unitialized values of the WELSPECS keyword. For the example at hand this might seem a bit relaxed - and the Eclipse behaviour more sensible; however there many cases where the actual default value can not be used (i.e. use -1 to indicate no limit for ...) and the calling scope must take care in differentiating between a valid -1 and a defaulted -1; in addition the Json configuration must have many default values which can not really be used as such - they only serve as markers of default behaviour; I would prefer to avoid filling up the configuration with such invalid values. joakim
_______________________________________________ Opm mailing list [email protected] http://www.opm-project.org/mailman/listinfo/opm
