Hello;
I just merged a PR to the opm-parser. As part of that PR the parser has become
slightly stricter (as if it was not already strict enough ....), and maybe it
will now barf on things which previously "worked". Specifically this is two
things:
Keywords missing records: Let us say you have used the TABDIMS keyword to say
that you have two equil regions; but your EQUIL keyword only has one record:
EQUIL
OWC GOC PC1 PC2 ..... /
ANOTHERKEYWORD
.....
This would previously 'work' - you will now get an exception.
Default on multivalued items: You can ask a scalar item, i.e. a wellrate, if it
has been defaulted with the ->defaultApplied() method. The flag holding this
information is scalar, so it does not make sense to ask a multivalued item
whether it has been defaulted. This will now raise an exception. (NB: You can
still use defaults like
PERMX
1000*
/
To fill up the the PERMX field with 1000 consecutive default values (if that is
set in the JSON config) - but you can not afterwards ask the keyworditem
whether the default has been applied.
Jaokim
-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you
_______________________________________________
Opm mailing list
[email protected]
http://www.opm-project.org/mailman/listinfo/opm
