Hello;

the parser code is progressing steadily - if not lightning fast - in the right 
direction. The current status is:

1. We have a bug with string keywords with emebedded spaces.
2. We are adding keywords to the list: 
https://github.com/OPM/opm-parser/tree/master/opm/parser/share/keywords - we 
are aiming at all the keywords in the Norne case, current status is <~ 50% 
complete.

When these two items are completed we aim to start integration with opm-core, 
for that process we would very much like to hear opinions from the rest of the 
OPM community. The current plan is roughly:

1. Create a thin - but growing layer ~ EclipseState which understands(?) 
ECLIPSE idiosyncrasies and combines information from the deck accordingly.
2. Write opm test applications to parse using both existing parser technology 
and the new parser.
3. Replace with new Deck / EclipseState functionality on a feature for feature 
basis - see below.

When it comes to grouping of Eclipse features we have identified the following:

Tables : The keywords like PVTG and SWOG and ... contain the data for one or 
several tables in a quite arcane format. We suggest to implement a class 
EclTable which can be populated from the Deck.

Grid and properties: Creating the ECLIPSE grid from COORDS / ZCORN / ACTNUM and 
loading the various property keywords like PORO and PERMX. This topic will 
require supporting the various manipulation keywords like MULTIPLY, EQUALS, 
COPY, .... For this task I would very much like to make ERT a required 
dependency.

Time stepping/schedule: Basically everything about the Schedule file.

Any opinions on this very welcome. As we consider the "Tables" properties to be 
the smallest we suggest to start there; but we are open to opinions.

As this will probably be a long lasting task - it would be nice if we could get 
the required "Umph" to create and manage a upstream branch at opm-core?

Joakim & Kristian


-------------------------------------------------------------------
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

Reply via email to