From JOKVA at statoil.com Tue Jul 5 10:55:21 2016 From: JOKVA at statoil.com (=?iso-8859-1?Q?J=F8rgen_Kvalsvik?=) Date: Tue, 5 Jul 2016 10:55:21 +0000 Subject: [Opm] opm-parser master requires ERT updates Message-ID: <0DE2898B514EE542B05967D975C25F505C4F8A04@WS343.statoil.net> Hi, please update and rebuild to the latest ERT master to keep opm-parser building. ------------------------------------------------------------------- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From yli15 at uwyo.edu Thu Jul 7 01:45:45 2016 From: yli15 at uwyo.edu (Ye Li) Date: Thu, 7 Jul 2016 01:45:45 +0000 Subject: [Opm] About a workflow to read the OPM code. Message-ID: Hi, all: Thanks for creating OPM, such a meaningful project. I have several years experience with reservoir simulation. I want to read the code of OPM to learn the "black box" behind the reservoir simulation. However, I am stuck and do not know where I should start. I went through several modules, like ope-common-master, opm-core-master, opt-grid-master, and etc.. If I want to learn the code of OPM FLOW, for example, where should I start and how to follow? Thanks for your time, and I do appreciate. Sincerely, Richard Li Geological Modeling & Simulation Department of Geology & Geophysics 1000 E. University Avenue Dept 3006 University of Wyoming Laramie, WY 82071 USA yli15 at uwyo.edu GE315 Ph: 307-766-9895 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Atgeirr.Rasmussen at sintef.no Thu Jul 7 07:05:48 2016 From: Atgeirr.Rasmussen at sintef.no (Atgeirr Rasmussen) Date: Thu, 7 Jul 2016 07:05:48 +0000 Subject: [Opm] About a workflow to read the OPM code. In-Reply-To: References: Message-ID: <907862D0-999D-4603-A847-B8A3941D2AFC@sintef.no> Hi Richard, Thanks for your interest in OPM! The amount of code that goes into building Flow is quite large, and reading it all is not really a feasible project. That said, it should not be too hard to find the parts that interest you the most. The most central class for Flow is the BlackoilModelBase class, on which all Flow variants is based (the solvent and polymer versions have their own model classes that inherit from this one). You'll find it in the opm-simulators module. To see how it works, start with the nonlinearIteration() method, which is the main entry point, and follow the function calls. One of the best ways to do this is to compile a debug version of flow (pass "Debug" as CMAKE_BUILD_TYPE to cmake) and run it in a debugger. You'll find the equations are being set up by the assemble() method, and in particular the assembleMassBalanceEq() method it calls. I hope this gets you started. If there are other aspects that are more interesting to you, please tell us. For example you can find the deck input in opm-parser, fluid properties in opm-material etc. Good luck! Atgeirr Flø Rasmussen 7. jul. 2016 kl. 03.45 skrev Ye Li >: Hi, all: Thanks for creating OPM, such a meaningful project. I have several years experience with reservoir simulation. I want to read the code of OPM to learn the "black box" behind the reservoir simulation. However, I am stuck and do not know where I should start. I went through several modules, like ope-common-master, opm-core-master, opt-grid-master, and etc.. If I want to learn the code of OPM FLOW, for example, where should I start and how to follow? Thanks for your time, and I do appreciate. Sincerely, Richard Li Geological Modeling & Simulation Department of Geology & Geophysics 1000 E. University Avenue Dept 3006 University of Wyoming Laramie, WY 82071 USA yli15 at uwyo.edu GE315 Ph: 307-766-9895 _______________________________________________ Opm mailing list Opm at opm-project.org http://opm-project.org/cgi-bin/mailman/listinfo/opm -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus at dr-blatt.de Tue Jul 12 11:05:41 2016 From: markus at dr-blatt.de (Markus Blatt) Date: Tue, 12 Jul 2016 13:05:41 +0200 Subject: [Opm] adding custom cell data to output and visualize it. Message-ID: <20160712110541.GA28584@boromir.dr-blatt.de> Hi, let us imagine that I have a custom vector containing data attached to the cells. Is there a way to output this data in addition to the default values to eclipse output? How? I assume that such an additional field can be easily visualized with ResInsight or am I wrong? Markus From JOKVA at statoil.com Tue Jul 12 11:14:57 2016 From: JOKVA at statoil.com (=?iso-8859-1?Q?J=F8rgen_Kvalsvik?=) Date: Tue, 12 Jul 2016 11:14:57 +0000 Subject: [Opm] adding custom cell data to output and visualize it. In-Reply-To: <20160712110541.GA28584@boromir.dr-blatt.de> References: <20160712110541.GA28584@boromir.dr-blatt.de> Message-ID: <0DE2898B514EE542B05967D975C25F505C4FA293@WS343.statoil.net> The support for custom vectors is rather non-existent still unfortunately, but if it's something that's useful to you during testing you can quickly patch opm-output to do it for your case. Would that work for you? ________________________________________ Fra: Opm [opm-bounces at opm-project.org] på vegne av Markus Blatt [markus at dr-blatt.de] Sendt: 12. juli 2016 13:05 Til: opm at opm-project.org Emne: [Opm] adding custom cell data to output and visualize it. Hi, let us imagine that I have a custom vector containing data attached to the cells. Is there a way to output this data in addition to the default values to eclipse output? How? I assume that such an additional field can be easily visualized with ResInsight or am I wrong? Markus _______________________________________________ Opm mailing list Opm at opm-project.org http://opm-project.org/cgi-bin/mailman/listinfo/opm ------------------------------------------------------------------- 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 From abir at statoil.com Tue Jul 12 11:25:12 2016 From: abir at statoil.com (Alf Birger Rustad) Date: Tue, 12 Jul 2016 11:25:12 +0000 Subject: [Opm] adding custom cell data to output and visualize it. In-Reply-To: <20160712110541.GA28584@boromir.dr-blatt.de> References: <20160712110541.GA28584@boromir.dr-blatt.de> Message-ID: <3FF3DEAF482AE047BE357963DF9C4F8AB491C26E@WS319.statoil.net> For debug purposes, you can trick it by replacing one of the output vectors with your custom vector when output is written. Currently, we only have a fixed set of vectors written out, you will find them here: https://github.com/OPM/opm-output/blob/master/opm/output/eclipse/EclipseWriter.cpp#L696 If you use the trick above, you should be able to visualize it directly from the simulation. Alternatively, you can just print your custom vector to some file (in ASCII), and place it as one of the properties in the input grdecl file (that is where the grid is given on the input side), for instance put it under PERMY. Resinsight will happily open up the grdecl file as input with various cell properties included. Cheers, Alf ________________________________________ From: Opm [opm-bounces at opm-project.org] on behalf of Markus Blatt [markus at dr-blatt.de] Sent: Tuesday, July 12, 2016 1:05 PM To: opm at opm-project.org Subject: [Opm] adding custom cell data to output and visualize it. Hi, let us imagine that I have a custom vector containing data attached to the cells. Is there a way to output this data in addition to the default values to eclipse output? How? I assume that such an additional field can be easily visualized with ResInsight or am I wrong? Markus _______________________________________________ Opm mailing list Opm at opm-project.org http://opm-project.org/cgi-bin/mailman/listinfo/opm ------------------------------------------------------------------- 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 From joakim.hove at gmail.com Tue Jul 12 11:35:05 2016 From: joakim.hove at gmail.com (Joakim Hove) Date: Tue, 12 Jul 2016 13:35:05 +0200 Subject: [Opm] adding custom cell data to output and visualize it. In-Reply-To: <20160712110541.GA28584@boromir.dr-blatt.de> References: <20160712110541.GA28584@boromir.dr-blatt.de> Message-ID: > > > let us imagine that I have a custom vector containing data attached to > the cells. Is there a way to output this data in addition to the > default values to eclipse output? How? > If this is static - i.e. initial data; you can quite simply add to the simprops list here: https://github.com/OPM/opm-simulators/blob/master/opm/autodiff/FlowMain.hpp#L751 If you are kind-of-desperate; I could help you with post processing trickery manipulate a restart file - essentailly replacing e.g. the SWAT vectors with something of your choice. Joakim -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus at dr-blatt.de Tue Jul 12 11:40:27 2016 From: markus at dr-blatt.de (Markus Blatt) Date: Tue, 12 Jul 2016 13:40:27 +0200 Subject: [Opm] adding custom cell data to output and visualize it. In-Reply-To: <3FF3DEAF482AE047BE357963DF9C4F8AB491C26E@WS319.statoil.net> References: <20160712110541.GA28584@boromir.dr-blatt.de> <3FF3DEAF482AE047BE357963DF9C4F8AB491C26E@WS319.statoil.net> Message-ID: <20160712114027.GB28584@boromir.dr-blatt.de> On Tue, Jul 12, 2016 at 11:25:12AM +0000, Alf Birger Rustad wrote: > [...] Alternatively, you can just print your custom vector to some file (in ASCII), and place it as one of the properties in the input grdecl file (that is where the grid is given on the input side), for instance put it under PERMY. Resinsight will happily open up the grdecl file as input with various cell properties included. That sounds like a neat idea. I guess the array needs to have cartdims[0]*cartdims[1]*cartdims[2] size, right? I.e. have values for all cells of the cartesian grid no matter whether they active or not. Markus -- Dr. Markus Blatt - HPC-Simulation-Software & Services http://www.dr-blatt.de Hans-Bunte-Str. 8-10, 69123 Heidelberg, Germany, USt-Id: DE279960836 Tel.: +49 (0) 160 97590858 From markus at dr-blatt.de Tue Jul 12 11:53:15 2016 From: markus at dr-blatt.de (Markus Blatt) Date: Tue, 12 Jul 2016 13:53:15 +0200 Subject: [Opm] adding custom cell data to output and visualize it. In-Reply-To: References: <20160712110541.GA28584@boromir.dr-blatt.de> Message-ID: <20160712115315.GC28584@boromir.dr-blatt.de> On Tue, Jul 12, 2016 at 01:35:05PM +0200, Joakim Hove wrote: > > > > > > let us imagine that I have a custom vector containing data attached to > > the cells. Is there a way to output this data in addition to the > > default values to eclipse output? How? > > > > > If this is static - i.e. initial data; you can quite simply add to the > simprops list here: > https://github.com/OPM/opm-simulators/blob/master/opm/autodiff/FlowMain.hpp#L751 > Thanks. Seems like the way to go as this is the process number after the initial load balancing of the grid. Markus -- Dr. Markus Blatt - HPC-Simulation-Software & Services http://www.dr-blatt.de Hans-Bunte-Str. 8-10, 69123 Heidelberg, Germany, USt-Id: DE279960836 Tel.: +49 (0) 160 97590858 From huntrods at athabascau.ca Wed Jul 13 16:16:22 2016 From: huntrods at athabascau.ca (Richard Huntrods) Date: Wed, 13 Jul 2016 09:16:22 -0700 Subject: [Opm] Greetings & compile questions Message-ID: <57866956.6090504@athabascau.ca> Greetings! My name is Richard Huntrods, currently on Vancouver Island Canada. My background is in Chemical Engineering (B.Sc. & M.Eng.). I spent 5+ years in the 1980's writing reservoir simulators for a few companies in Alberta, Canada. Since then I moved into consulting, then full-time teaching. I'm currently teaching Computer Science at Athabasca University - a distance education university in Alberta. I have always been interested in reservoir simulation, and recently have begun compiling and using the FLOW simulator from the OPM project. I have successfully compiled and used the OPM suite on Ubuntu 14.04 as per the build guidelines. I also have kept detailed notes of my process, from starting VirtualBox on a Windows 7 PC through installing Ubuntu 14.04 and then obtaining and building the OPM sources. I also wrote a few shell scripts to help automate the process and have confirmed it a few times with clean builds. I would be willing to share my documents and scripts if desired. I'm now in the process of building OPM from source on Ubuntu 16.04. I *almost* works. With a few minor changes required in dependency packages, I have been able to get all the sources compiled and running. However, there's a problem with FLOW - it won't recognize many of the output keywords such as ECHO, NOECHO, RPTSCHED from the SPE test cases, and many more in the Norne test case. I am sure it's a missing dependency in the Eclipse input code, but have not yet isolated it. I am wondering who is currently working on compiling under Ubuntu 16.04 and whether or not they would be willing to share any tips and problems they may already have seen and diagnosed. I'd be very willing to contribute to this process. Thanks in advance, and again welcome to everyone. -Richard Huntrods, P.Eng. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From rlwalker at usc.edu Wed Jul 13 16:18:56 2016 From: rlwalker at usc.edu (Robert Walker) Date: Wed, 13 Jul 2016 11:18:56 -0500 Subject: [Opm] Greetings & compile questions In-Reply-To: <57866956.6090504@athabascau.ca> References: <57866956.6090504@athabascau.ca> Message-ID: Could you please share what changes you took in order to get OPM to compile in 16.04? I have tried repeatedly, always to no avail. Thank you, Robert Walker Robert L. Walker MS Petroleum Engineering Mork Family Department of Chemicals and Materials Sciences University of Southern California ---------------------------------------------- Mobile US: +1 (213) - 290 -7101 Mobile EU: +34 62 274 66 40 rlwalker at usc.edu On Wed, Jul 13, 2016 at 11:16 AM, Richard Huntrods wrote: > Greetings! > > My name is Richard Huntrods, currently on Vancouver Island Canada. My > background is in Chemical Engineering (B.Sc. & M.Eng.). I spent 5+ years in > the 1980's writing reservoir simulators for a few companies in Alberta, > Canada. Since then I moved into consulting, then full-time teaching. I'm > currently teaching Computer Science at Athabasca University - a distance > education university in Alberta. > > I have always been interested in reservoir simulation, and recently have > begun compiling and using the FLOW simulator from the OPM project. > > I have successfully compiled and used the OPM suite on Ubuntu 14.04 as per > the build guidelines. I also have kept detailed notes of my process, from > starting VirtualBox on a Windows 7 PC through installing Ubuntu 14.04 and > then obtaining and building the OPM sources. I also wrote a few shell > scripts to help automate the process and have confirmed it a few times with > clean builds. > > I would be willing to share my documents and scripts if desired. > > I'm now in the process of building OPM from source on Ubuntu 16.04. I > *almost* works. With a few minor changes required in dependency packages, I > have been able to get all the sources compiled and running. However, > there's a problem with FLOW - it won't recognize many of the output > keywords such as ECHO, NOECHO, RPTSCHED from the SPE test cases, and many > more in the Norne test case. I am sure it's a missing dependency in the > Eclipse input code, but have not yet isolated it. > > I am wondering who is currently working on compiling under Ubuntu 16.04 > and whether or not they would be willing to share any tips and problems > they may already have seen and diagnosed. I'd be very willing to contribute > to this process. > > Thanks in advance, and again welcome to everyone. > > -Richard Huntrods, P.Eng. > > --- > This email has been checked for viruses by Avast antivirus software. > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.avast.com_antivirus&d=DQIGaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=BWOpUsAp5dvI5cUiP4uZxQ&m=qbIKjpGeOhvtwostnRTC5p9V0wsirdcX9RbtKOkuI7w&s=_hMLXiktxfJ8yF0dbbwO_cjbttnHK0PTEcP29JZ4j4g&e= > _______________________________________________ > Opm mailing list > Opm at opm-project.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__opm-2Dproject.org_cgi-2Dbin_mailman_listinfo_opm&d=DQIGaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=BWOpUsAp5dvI5cUiP4uZxQ&m=qbIKjpGeOhvtwostnRTC5p9V0wsirdcX9RbtKOkuI7w&s=hVFvKKG4-2XTUZBrMu3t78wMESN10o9n69OYI2OuCq8&e= -------------- next part -------------- An HTML attachment was scrubbed... URL: From huntrods at athabascau.ca Wed Jul 13 16:55:15 2016 From: huntrods at athabascau.ca (Richard Huntrods) Date: Wed, 13 Jul 2016 09:55:15 -0700 Subject: [Opm] Greetings & compile questions In-Reply-To: References: <57866956.6090504@athabascau.ca> Message-ID: <57867273.4080406@athabascau.ca> Robert, There was one significant change to my compile procedure for Ubuntu 14.04. First, allow me to briefly explain my scripts and then the change I made: opm-source.sh - gets all the opm sources using git. opm-depends.sh - uses apt-get install to install all the dependencies required to compile opm sources. opm-ert.sh - gets ert source and compiles & installs it. opm-make.sh - compiles & installs the opm sources (except for resinsight). Here's where things differ between Ubuntu 14.04 and Ubuntu 16.04 When I ran the opm-depends.sh script, I found the error file showed two problems that weren't problems with Ubuntu 14.04: 1. libboost1.55 not found; manually search for newer (apt search libboost | grep libboost) and install: sudo apt-get install libboost-dev-all 2. libumfpack5.6.2 not found; manually search for newer (apt search libumfpack | grep libumfpack) and install: sudo apt-get install libumfpack5.7.1 However, apt-get replies libumfpack5.7.1 is already the newest version, so really don’t need to do this step. Once I installed the latest libboost-dev-all, the rest of the compile process for OPM proceeded without any problems that I could see. FLOW was created in /usr/local/bin, and it ran. However, as I said in my prior email, the output keywords are not recognized. Note: I compile ResInsight in a separate set of shell scripts (but similar to those above): res-source.sh - get the ResInsight sources using git oct-depends.sh - apt-get install the dependencies to compile octave oct-make.sh - compile & install octave res-make.sh - compile & install ResInsight Cheers, -Richard Huntrods, P.Eng. On 7/13/2016 9:18 AM, Robert Walker wrote: > Could you please share what changes you took in order to get OPM to > compile in 16.04? I have tried repeatedly, always to no avail. > > Thank you, > > Robert Walker > > Robert L. Walker > MS Petroleum Engineering > Mork Family Department of Chemicals and Materials Sciences > University of Southern California > ---------------------------------------------- > Mobile US: +1 (213) - 290 -7101 > Mobile EU: +34 62 274 66 40 > rlwalker at usc.edu > > On Wed, Jul 13, 2016 at 11:16 AM, Richard Huntrods > > wrote: > > Greetings! > > My name is Richard Huntrods, currently on Vancouver Island Canada. > My background is in Chemical Engineering (B.Sc. & M.Eng.). I spent > 5+ years in the 1980's writing reservoir simulators for a few > companies in Alberta, Canada. Since then I moved into consulting, > then full-time teaching. I'm currently teaching Computer Science > at Athabasca University - a distance education university in Alberta. > > I have always been interested in reservoir simulation, and > recently have begun compiling and using the FLOW simulator from > the OPM project. > > I have successfully compiled and used the OPM suite on Ubuntu > 14.04 as per the build guidelines. I also have kept detailed notes > of my process, from starting VirtualBox on a Windows 7 PC through > installing Ubuntu 14.04 and then obtaining and building the OPM > sources. I also wrote a few shell scripts to help automate the > process and have confirmed it a few times with clean builds. > > I would be willing to share my documents and scripts if desired. > > I'm now in the process of building OPM from source on Ubuntu > 16.04. I *almost* works. With a few minor changes required in > dependency packages, I have been able to get all the sources > compiled and running. However, there's a problem with FLOW - it > won't recognize many of the output keywords such as ECHO, NOECHO, > RPTSCHED from the SPE test cases, and many more in the Norne test > case. I am sure it's a missing dependency in the Eclipse input > code, but have not yet isolated it. > > I am wondering who is currently working on compiling under Ubuntu > 16.04 and whether or not they would be willing to share any tips > and problems they may already have seen and diagnosed. I'd be very > willing to contribute to this process. > > Thanks in advance, and again welcome to everyone. > > -Richard Huntrods, P.Eng. > > --- > This email has been checked for viruses by Avast antivirus software. > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.avast.com_antivirus&d=DQIGaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=BWOpUsAp5dvI5cUiP4uZxQ&m=qbIKjpGeOhvtwostnRTC5p9V0wsirdcX9RbtKOkuI7w&s=_hMLXiktxfJ8yF0dbbwO_cjbttnHK0PTEcP29JZ4j4g&e= > > _______________________________________________ > Opm mailing list > Opm at opm-project.org > https://urldefense.proofpoint.com/v2/url?u=http-3A__opm-2Dproject.org_cgi-2Dbin_mailman_listinfo_opm&d=DQIGaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=BWOpUsAp5dvI5cUiP4uZxQ&m=qbIKjpGeOhvtwostnRTC5p9V0wsirdcX9RbtKOkuI7w&s=hVFvKKG4-2XTUZBrMu3t78wMESN10o9n69OYI2OuCq8&e= > > > --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kai.Bao at sintef.no Wed Jul 13 17:04:17 2016 From: Kai.Bao at sintef.no (Kai Bao) Date: Wed, 13 Jul 2016 17:04:17 +0000 Subject: [Opm] Greetings & compile questions In-Reply-To: <57866956.6090504@athabascau.ca> References: <57866956.6090504@athabascau.ca> Message-ID: If your problem looks like the thing discussed in the following link, https://github.com/OPM/opm-parser/issues/876 I was also suprised when I first time saw these messages. You can take a look at this Pull Request. https://github.com/OPM/opm-simulators/pull/756 I do not think it is something related to Ubuntu 16.04. It is that OPM decided that to output all the keywords are not used in the simulation through the above PR. Nothing is changed in the simulation side though. Hope it helps your quesiton. Best, Kai ________________________________________ From: Opm [opm-bounces at opm-project.org] on behalf of Richard Huntrods [huntrods at athabascau.ca] Sent: Wednesday, July 13, 2016 6:16 PM To: opm at opm-project.org Subject: [Opm] Greetings & compile questions Greetings! My name is Richard Huntrods, currently on Vancouver Island Canada. My background is in Chemical Engineering (B.Sc. & M.Eng.). I spent 5+ years in the 1980's writing reservoir simulators for a few companies in Alberta, Canada. Since then I moved into consulting, then full-time teaching. I'm currently teaching Computer Science at Athabasca University - a distance education university in Alberta. I have always been interested in reservoir simulation, and recently have begun compiling and using the FLOW simulator from the OPM project. I have successfully compiled and used the OPM suite on Ubuntu 14.04 as per the build guidelines. I also have kept detailed notes of my process, from starting VirtualBox on a Windows 7 PC through installing Ubuntu 14.04 and then obtaining and building the OPM sources. I also wrote a few shell scripts to help automate the process and have confirmed it a few times with clean builds. I would be willing to share my documents and scripts if desired. I'm now in the process of building OPM from source on Ubuntu 16.04. I *almost* works. With a few minor changes required in dependency packages, I have been able to get all the sources compiled and running. However, there's a problem with FLOW - it won't recognize many of the output keywords such as ECHO, NOECHO, RPTSCHED from the SPE test cases, and many more in the Norne test case. I am sure it's a missing dependency in the Eclipse input code, but have not yet isolated it. I am wondering who is currently working on compiling under Ubuntu 16.04 and whether or not they would be willing to share any tips and problems they may already have seen and diagnosed. I'd be very willing to contribute to this process. Thanks in advance, and again welcome to everyone. -Richard Huntrods, P.Eng. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus _______________________________________________ Opm mailing list Opm at opm-project.org http://opm-project.org/cgi-bin/mailman/listinfo/opm From huntrods at athabascau.ca Wed Jul 13 17:20:14 2016 From: huntrods at athabascau.ca (Richard Huntrods) Date: Wed, 13 Jul 2016 10:20:14 -0700 Subject: [Opm] Greetings & compile questions In-Reply-To: References: <57866956.6090504@athabascau.ca> Message-ID: <5786784E.8000906@athabascau.ca> Kai, Thank you for the reply. However, the keywords I've reported do work perfectly in Flow compiled on Ubuntu 14.04. They don't work on the same code compiled in the same way on Ubuntu 16.04. My suspicion is that a dependency library is either missing or changed. This causes some component of Flow to compile improperly, or not be compiled at all, and this results in the keywords not being recognized. I don't see any fatal compile errors in my logs so I suspect a component has not been compiled for some reason. At the moment, I just don't know which one or why. However, I suspect libtool may be involved. Compiling under Ubuntu 16.04, Cmake reports "libtool is not present" in every module (in my logs). I have confirmed that both libtool and libtool-bin have been correctly installed. I suspect something has moved between Ubuntu 14.04 and 16.04 and the location in the cmake text files needs to be updated. I'm still checking this out. Cheers, -Richard Huntrods, P.Eng. On 7/13/2016 10:04 AM, Kai Bao wrote: > If your problem looks like the thing discussed in the following link, > > https://github.com/OPM/opm-parser/issues/876 > > I was also suprised when I first time saw these messages. > > > You can take a look at this Pull Request. > > https://github.com/OPM/opm-simulators/pull/756 > > I do not think it is something related to Ubuntu 16.04. It is that OPM decided that to output all the keywords are not used in the simulation through the above PR. > > Nothing is changed in the simulation side though. > > Hope it helps your quesiton. > > Best, > Kai > ________________________________________ > From: Opm [opm-bounces at opm-project.org] on behalf of Richard Huntrods [huntrods at athabascau.ca] > Sent: Wednesday, July 13, 2016 6:16 PM > To: opm at opm-project.org > Subject: [Opm] Greetings & compile questions > > Greetings! > > My name is Richard Huntrods, currently on Vancouver Island Canada. My > background is in Chemical Engineering (B.Sc. & M.Eng.). I spent 5+ years > in the 1980's writing reservoir simulators for a few companies in > Alberta, Canada. Since then I moved into consulting, then full-time > teaching. I'm currently teaching Computer Science at Athabasca > University - a distance education university in Alberta. > > I have always been interested in reservoir simulation, and recently have > begun compiling and using the FLOW simulator from the OPM project. > > I have successfully compiled and used the OPM suite on Ubuntu 14.04 as > per the build guidelines. I also have kept detailed notes of my process, > from starting VirtualBox on a Windows 7 PC through installing Ubuntu > 14.04 and then obtaining and building the OPM sources. I also wrote a > few shell scripts to help automate the process and have confirmed it a > few times with clean builds. > > I would be willing to share my documents and scripts if desired. > > I'm now in the process of building OPM from source on Ubuntu 16.04. I > *almost* works. With a few minor changes required in dependency > packages, I have been able to get all the sources compiled and running. > However, there's a problem with FLOW - it won't recognize many of the > output keywords such as ECHO, NOECHO, RPTSCHED from the SPE test cases, > and many more in the Norne test case. I am sure it's a missing > dependency in the Eclipse input code, but have not yet isolated it. > > I am wondering who is currently working on compiling under Ubuntu 16.04 > and whether or not they would be willing to share any tips and problems > they may already have seen and diagnosed. I'd be very willing to > contribute to this process. > > Thanks in advance, and again welcome to everyone. > > -Richard Huntrods, P.Eng. > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > > _______________________________________________ > Opm mailing list > Opm at opm-project.org > http://opm-project.org/cgi-bin/mailman/listinfo/opm > . > --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From Kai.Bao at sintef.no Wed Jul 13 19:32:06 2016 From: Kai.Bao at sintef.no (Kai Bao) Date: Wed, 13 Jul 2016 19:32:06 +0000 Subject: [Opm] Greetings & compile questions In-Reply-To: <5786784E.8000906@athabascau.ca> References: <57866956.6090504@athabascau.ca> , <5786784E.8000906@athabascau.ca> Message-ID: Hi, Richard, If the message you saw looks like the following, then it is a pure output recently introduced by OPM with https://github.com/OPM/opm-simulators/pull/756. I am not sure whether we should report them as Error or Warning. However, you will see these messages both under ubuntu 14.04 and 16.04 for sure. You just need to update all your repos under ubuntu 14.04 then compile again. Best, Kai Error: Keyword 'SATOPTS' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/NORNE_ATW2013.DATA, line 34 Error: Keyword 'TRACERS' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/NORNE_ATW2013.DATA, line 50 Error: Keyword 'NSTACK' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/NORNE_ATW2013.DATA, line 102 Error: Keyword 'OPTIONS' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/NORNE_ATW2013.DATA, line 111 Error: Keyword 'GRIDUNIT' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/NORNE_ATW2013.DATA, line 131 Error: Keyword 'MESSAGES' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/NORNE_ATW2013.DATA, line 137 Error: Keyword 'NOECHO' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/NORNE_ATW2013.DATA, line 143 Error: Keyword 'SPECGRID' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/GRID/IRAP_1005.GRDECL, line 10 Error: Keyword 'NOECHO' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/NORNE_ATW2013.DATA, line 252 Error: Keyword 'NOECHO' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/NORNE_ATW2013.DATA, line 269 Error: Keyword 'TRACER' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/NORNE_ATW2013.DATA, line 274 Error: Keyword 'FIPNUM' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/PETRO/FIPNUM_0704.prop, line 9 Error: Keyword 'EQLNUM' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/PETRO/EQLNUM_0704.prop, line 9 Error: Keyword 'RPTSOL' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/NORNE_ATW2013.DATA, line 384 Error: Keyword 'DATE' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/SUMMARY/summary.data, line 9 Error: Keyword 'NOECHO' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/NORNE_ATW2013.DATA, line 461 Error: Keyword 'ZIPPY2' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/NORNE_ATW2013.DATA, line 635 Error: Keyword 'PIMULTAB' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/PI/pimultab_low-high_aug-2006.inc, line 8 Error: Keyword 'WPAVE' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 176 Error: Keyword 'GRUPNET' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 180 Error: Keyword 'VAPPARS' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 195 Error: Keyword 'NETBALAN' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 199 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 216 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 311 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 330 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 469 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 504 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 833 Error: Keyword 'WTRACER' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 883 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 887 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 1118 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 1141 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 1171 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 1324 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 1347 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 1353 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 1376 Error: Keyword 'WTRACER' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 1419 Error: Keyword 'WTRACER' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 1463 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 1467 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 1511 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 1535 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 1680 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 1705 Error: Keyword 'WTRACER' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 1963 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 1967 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 2120 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 2186 Error: Keyword 'WTRACER' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 2346 Error: Keyword 'WTRACER' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 2440 Error: Keyword 'WTRACER' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 2469 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 2498 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 2584 Error: Keyword 'WTRACER' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 2687 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 2715 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 2765 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 2794 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 2919 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 2950 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 3110 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 3140 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 3344 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 3374 Error: Keyword 'WTRACER' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 3598 Error: Keyword 'WTRACER' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 3630 Error: Keyword 'WTRACER' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 3879 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 3909 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 3939 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 4035 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 4068 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 4130 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 4161 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 4392 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 4423 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 4454 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 4541 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 4810 Error: Keyword 'WTRACER' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 4867 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 4871 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 4902 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 4933 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 4992 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5026 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5060 Error: Keyword 'WTRACER' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5094 Error: Keyword 'WTRACER' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5127 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5189 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5226 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5289 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5358 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5364 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5395 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5427 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5490 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5552 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5630 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5663 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5669 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5702 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5820 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5850 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5880 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5886 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5916 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 5947 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 6005 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 6136 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 6169 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 6287 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 6319 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 6325 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 6419 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 6481 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 6676 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 6680 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 6769 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 7010 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 7043 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 7076 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 7082 Error: Keyword 'WTRACER' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 7143 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 7147 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 7239 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 7272 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 7336 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 7415 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 7452 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 7617 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 7652 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 7687 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 7755 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 7798 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 7834 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 8067 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 8135 Error: Keyword 'GECON' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 8264 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 8297 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 8335 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 8653 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 8685 Error: Keyword 'WTEST' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 8869 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 8873 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 8908 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 9027 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 9066 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 9157 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 9185 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 9371 Error: Keyword 'RPTSCHED' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 9405 Error: Keyword 'WTEST' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 9438 Error: Keyword 'WPITAB' is not supported by flow. In file /home/paean/devel/OPM/opm/opm-data/norne/INCLUDE/BC0407_HIST01122006.SCH, line 9442 ________________________________________ From: Opm [opm-bounces at opm-project.org] on behalf of Richard Huntrods [huntrods at athabascau.ca] Sent: Wednesday, July 13, 2016 7:20 PM To: Kai Bao; opm at opm-project.org Subject: Re: [Opm] Greetings & compile questions Kai, Thank you for the reply. However, the keywords I've reported do work perfectly in Flow compiled on Ubuntu 14.04. They don't work on the same code compiled in the same way on Ubuntu 16.04. My suspicion is that a dependency library is either missing or changed. This causes some component of Flow to compile improperly, or not be compiled at all, and this results in the keywords not being recognized. I don't see any fatal compile errors in my logs so I suspect a component has not been compiled for some reason. At the moment, I just don't know which one or why. However, I suspect libtool may be involved. Compiling under Ubuntu 16.04, Cmake reports "libtool is not present" in every module (in my logs). I have confirmed that both libtool and libtool-bin have been correctly installed. I suspect something has moved between Ubuntu 14.04 and 16.04 and the location in the cmake text files needs to be updated. I'm still checking this out. Cheers, -Richard Huntrods, P.Eng. On 7/13/2016 10:04 AM, Kai Bao wrote: > If your problem looks like the thing discussed in the following link, > > https://github.com/OPM/opm-parser/issues/876 > > I was also suprised when I first time saw these messages. > > > You can take a look at this Pull Request. > > https://github.com/OPM/opm-simulators/pull/756 > > I do not think it is something related to Ubuntu 16.04. It is that OPM decided that to output all the keywords are not used in the simulation through the above PR. > > Nothing is changed in the simulation side though. > > Hope it helps your quesiton. > > Best, > Kai > ________________________________________ > From: Opm [opm-bounces at opm-project.org] on behalf of Richard Huntrods [huntrods at athabascau.ca] > Sent: Wednesday, July 13, 2016 6:16 PM > To: opm at opm-project.org > Subject: [Opm] Greetings & compile questions > > Greetings! > > My name is Richard Huntrods, currently on Vancouver Island Canada. My > background is in Chemical Engineering (B.Sc. & M.Eng.). I spent 5+ years > in the 1980's writing reservoir simulators for a few companies in > Alberta, Canada. Since then I moved into consulting, then full-time > teaching. I'm currently teaching Computer Science at Athabasca > University - a distance education university in Alberta. > > I have always been interested in reservoir simulation, and recently have > begun compiling and using the FLOW simulator from the OPM project. > > I have successfully compiled and used the OPM suite on Ubuntu 14.04 as > per the build guidelines. I also have kept detailed notes of my process, > from starting VirtualBox on a Windows 7 PC through installing Ubuntu > 14.04 and then obtaining and building the OPM sources. I also wrote a > few shell scripts to help automate the process and have confirmed it a > few times with clean builds. > > I would be willing to share my documents and scripts if desired. > > I'm now in the process of building OPM from source on Ubuntu 16.04. I > *almost* works. With a few minor changes required in dependency > packages, I have been able to get all the sources compiled and running. > However, there's a problem with FLOW - it won't recognize many of the > output keywords such as ECHO, NOECHO, RPTSCHED from the SPE test cases, > and many more in the Norne test case. I am sure it's a missing > dependency in the Eclipse input code, but have not yet isolated it. > > I am wondering who is currently working on compiling under Ubuntu 16.04 > and whether or not they would be willing to share any tips and problems > they may already have seen and diagnosed. I'd be very willing to > contribute to this process. > > Thanks in advance, and again welcome to everyone. > > -Richard Huntrods, P.Eng. > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > > _______________________________________________ > Opm mailing list > Opm at opm-project.org > http://opm-project.org/cgi-bin/mailman/listinfo/opm > . > --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus _______________________________________________ Opm mailing list Opm at opm-project.org http://opm-project.org/cgi-bin/mailman/listinfo/opm From liuming1035 at gmail.com Thu Jul 14 00:59:05 2016 From: liuming1035 at gmail.com (Ming Liu) Date: Thu, 14 Jul 2016 08:59:05 +0800 Subject: [Opm] Greetings & compile questions In-Reply-To: <57866956.6090504@athabascau.ca> References: <57866956.6090504@athabascau.ca> Message-ID: Hi Richard, I think what kai said is very clear, recently we are working on the improvement of the print file, that is .PRT file, we believe this will give the user clear messages that some keywords are not supported by flow currently, that's why you can see lots of output. I'm sorry this output brings you the trouble, but do not worry, nothing changed in the source code about summary file and restart file, you can still check results with any visualization tools you like, such as resinsight. Best regards, Liu Ming 2016-07-14 0:16 GMT+08:00 Richard Huntrods : > Greetings! > > My name is Richard Huntrods, currently on Vancouver Island Canada. My > background is in Chemical Engineering (B.Sc. & M.Eng.). I spent 5+ years in > the 1980's writing reservoir simulators for a few companies in Alberta, > Canada. Since then I moved into consulting, then full-time teaching. I'm > currently teaching Computer Science at Athabasca University - a distance > education university in Alberta. > > I have always been interested in reservoir simulation, and recently have > begun compiling and using the FLOW simulator from the OPM project. > > I have successfully compiled and used the OPM suite on Ubuntu 14.04 as per > the build guidelines. I also have kept detailed notes of my process, from > starting VirtualBox on a Windows 7 PC through installing Ubuntu 14.04 and > then obtaining and building the OPM sources. I also wrote a few shell > scripts to help automate the process and have confirmed it a few times with > clean builds. > > I would be willing to share my documents and scripts if desired. > > I'm now in the process of building OPM from source on Ubuntu 16.04. I > *almost* works. With a few minor changes required in dependency packages, I > have been able to get all the sources compiled and running. However, > there's a problem with FLOW - it won't recognize many of the output > keywords such as ECHO, NOECHO, RPTSCHED from the SPE test cases, and many > more in the Norne test case. I am sure it's a missing dependency in the > Eclipse input code, but have not yet isolated it. > > I am wondering who is currently working on compiling under Ubuntu 16.04 > and whether or not they would be willing to share any tips and problems > they may already have seen and diagnosed. I'd be very willing to contribute > to this process. > > Thanks in advance, and again welcome to everyone. > > -Richard Huntrods, P.Eng. > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > > _______________________________________________ > Opm mailing list > Opm at opm-project.org > http://opm-project.org/cgi-bin/mailman/listinfo/opm > -------------- next part -------------- An HTML attachment was scrubbed... URL: From huntrods at athabascau.ca Thu Jul 14 01:45:30 2016 From: huntrods at athabascau.ca (Richard Huntrods) Date: Wed, 13 Jul 2016 18:45:30 -0700 Subject: [Opm] Greetings & compile questions In-Reply-To: References: <57866956.6090504@athabascau.ca> Message-ID: <5786EEBA.7050401@athabascau.ca> Hi Liu, I understand. I'm not talking about Eclipse keywords that are not in the Ubuntu 14.04 version today. I am talking about keywords that work today in flow compiled on ubuntu 14.04 but are missing when you compile the same exact source code in Ubuntu 16.04. Keywords like ECHO and NOECHO. Something in the ubuntu 16.04 build process isn't compiling or linking everything correctly. I am currently diggin deeper to see which dependencies have changed between 14.04 and 16.04. I do know there's an issue with libtool. It's not installed by default in Ubuntu 16.04 but was in Ubunty 14.04. Worse, when you install it in 16.04, somehow it's not where Cmake wants it to be, which I am sure is affecting the build / link process. I'm tracking that down. There are also different (newer) versions of dependencies between ubuntu 14.04 and ubuntu 16.04: libumfpack5.6.2 (now libumfpack5.7.1 in ubuntu 16.04) libboost1.55-dev-all (now libboost1.58-dev-all in ubuntu 16.04) and libsuperlu3-dev (now libsuperlu-dev in ubuntu 16.04) Finally, C++ is installed by default in Ubuntu 16.04 at version 5, not 4.7. The problem for me is that it's a very complex build process, and trying to figure out which new dependency library is causing the compile process to hiccup is difficult. However, I'm working away at it. Cheers, -Richard On 7/13/2016 5:59 PM, Ming Liu wrote: > Hi Richard, > > I think what kai said is very clear, recently we are working on the > improvement of the print file, that is .PRT file, we believe this > will give the user clear messages that some keywords are not supported > by flow currently, that's why you can see lots of output. I'm sorry > this output brings you the trouble, but do not worry, nothing changed > in the source code about summary file and restart file, you can still > check results with any visualization tools you like, such as resinsight. > > Best regards, > Liu Ming > > 2016-07-14 0:16 GMT+08:00 Richard Huntrods >: > > Greetings! > > My name is Richard Huntrods, currently on Vancouver Island Canada. > My background is in Chemical Engineering (B.Sc. & M.Eng.). I spent > 5+ years in the 1980's writing reservoir simulators for a few > companies in Alberta, Canada. Since then I moved into consulting, > then full-time teaching. I'm currently teaching Computer Science > at Athabasca University - a distance education university in Alberta. > > I have always been interested in reservoir simulation, and > recently have begun compiling and using the FLOW simulator from > the OPM project. > > I have successfully compiled and used the OPM suite on Ubuntu > 14.04 as per the build guidelines. I also have kept detailed notes > of my process, from starting VirtualBox on a Windows 7 PC through > installing Ubuntu 14.04 and then obtaining and building the OPM > sources. I also wrote a few shell scripts to help automate the > process and have confirmed it a few times with clean builds. > > I would be willing to share my documents and scripts if desired. > > I'm now in the process of building OPM from source on Ubuntu > 16.04. I *almost* works. With a few minor changes required in > dependency packages, I have been able to get all the sources > compiled and running. However, there's a problem with FLOW - it > won't recognize many of the output keywords such as ECHO, NOECHO, > RPTSCHED from the SPE test cases, and many more in the Norne test > case. I am sure it's a missing dependency in the Eclipse input > code, but have not yet isolated it. > > I am wondering who is currently working on compiling under Ubuntu > 16.04 and whether or not they would be willing to share any tips > and problems they may already have seen and diagnosed. I'd be very > willing to contribute to this process. > > Thanks in advance, and again welcome to everyone. > > -Richard Huntrods, P.Eng. > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > > _______________________________________________ > Opm mailing list > Opm at opm-project.org > http://opm-project.org/cgi-bin/mailman/listinfo/opm > > --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -------------- next part -------------- An HTML attachment was scrubbed... URL: From liuming1035 at gmail.com Thu Jul 14 01:59:22 2016 From: liuming1035 at gmail.com (Ming Liu) Date: Thu, 14 Jul 2016 09:59:22 +0800 Subject: [Opm] Greetings & compile questions In-Reply-To: <5786EEBA.7050401@athabascau.ca> References: <57866956.6090504@athabascau.ca> <5786EEBA.7050401@athabascau.ca> Message-ID: Hi Richard, If I understand you correctly, you have already been built and run FLOW, that means you don't have any issue related to the compile and linker. The only issue is that when you running flow, some messages are output in the terminal saying that " Error: Keyword 'NOECHO' is not supported by flow. In file /home/liuming/work/opm/opm-data/norne/NORNE_ATW2013.DATA, line 143 Error: Keyword 'SPECGRID' is not supported by flow. In file /home/liuming/work/opm/opm-data/norne/INCLUDE/GRID/IRAP_1005.GRDECL, line 10 " But after these keywords, flow is still running, right? Probably the confused thing is that these kinds of messages did not show before, that's because we introduce these messages early this week, that is this PR https://github.com/OPM/opm-simulators/pull/756. But regarding ubuntu 16.04, there is a potential issue could lead to the failure of the build process, please check issue here https://github.com/OPM/opm-simulators/issues/757 Best regards, Liu Ming 2016-07-14 9:45 GMT+08:00 Richard Huntrods : > Hi Liu, > > I understand. > > I'm not talking about Eclipse keywords that are not in the Ubuntu 14.04 > version today. I am talking about keywords that work today in flow > compiled on ubuntu 14.04 but are missing when you compile the same exact > source code in Ubuntu 16.04. Keywords like ECHO and NOECHO. > > Something in the ubuntu 16.04 build process isn't compiling or linking > everything correctly. I am currently diggin deeper to see which > dependencies have changed between 14.04 and 16.04. > > I do know there's an issue with libtool. It's not installed by default in > Ubuntu 16.04 but was in Ubunty 14.04. Worse, when you install it in 16.04, > somehow it's not where Cmake wants it to be, which I am sure is affecting > the build / link process. I'm tracking that down. > > There are also different (newer) versions of dependencies between ubuntu > 14.04 and ubuntu 16.04: > libumfpack5.6.2 (now libumfpack5.7.1 in ubuntu 16.04) > libboost1.55-dev-all (now libboost1.58-dev-all in ubuntu 16.04) > and libsuperlu3-dev (now libsuperlu-dev in ubuntu 16.04) > Finally, C++ is installed by default in Ubuntu 16.04 at version 5, not > 4.7. > > The problem for me is that it's a very complex build process, and trying > to figure out which new dependency library is causing the compile process > to hiccup is difficult. However, I'm working away at it. > > Cheers, > > -Richard > > > On 7/13/2016 5:59 PM, Ming Liu wrote: > > Hi Richard, > > I think what kai said is very clear, recently we are working on the > improvement of the print file, that is .PRT file, we believe this will > give the user clear messages that some keywords are not supported by flow > currently, that's why you can see lots of output. I'm sorry this output > brings you the trouble, but do not worry, nothing changed in the source > code about summary file and restart file, you can still check results with > any visualization tools you like, such as resinsight. > > Best regards, > Liu Ming > > 2016-07-14 0:16 GMT+08:00 Richard Huntrods : > >> Greetings! >> >> My name is Richard Huntrods, currently on Vancouver Island Canada. My >> background is in Chemical Engineering (B.Sc. & M.Eng.). I spent 5+ years in >> the 1980's writing reservoir simulators for a few companies in Alberta, >> Canada. Since then I moved into consulting, then full-time teaching. I'm >> currently teaching Computer Science at Athabasca University - a distance >> education university in Alberta. >> >> I have always been interested in reservoir simulation, and recently have >> begun compiling and using the FLOW simulator from the OPM project. >> >> I have successfully compiled and used the OPM suite on Ubuntu 14.04 as >> per the build guidelines. I also have kept detailed notes of my process, >> from starting VirtualBox on a Windows 7 PC through installing Ubuntu 14.04 >> and then obtaining and building the OPM sources. I also wrote a few shell >> scripts to help automate the process and have confirmed it a few times with >> clean builds. >> >> I would be willing to share my documents and scripts if desired. >> >> I'm now in the process of building OPM from source on Ubuntu 16.04. I >> *almost* works. With a few minor changes required in dependency packages, I >> have been able to get all the sources compiled and running. However, >> there's a problem with FLOW - it won't recognize many of the output >> keywords such as ECHO, NOECHO, RPTSCHED from the SPE test cases, and many >> more in the Norne test case. I am sure it's a missing dependency in the >> Eclipse input code, but have not yet isolated it. >> >> I am wondering who is currently working on compiling under Ubuntu 16.04 >> and whether or not they would be willing to share any tips and problems >> they may already have seen and diagnosed. I'd be very willing to contribute >> to this process. >> >> Thanks in advance, and again welcome to everyone. >> >> -Richard Huntrods, P.Eng. >> >> --- >> This email has been checked for viruses by Avast antivirus software. >> https://www.avast.com/antivirus >> >> _______________________________________________ >> Opm mailing list >> Opm at opm-project.org >> http://opm-project.org/cgi-bin/mailman/listinfo/opm >> > > > > > Virus-free. > www.avast.com > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From huntrods at athabascau.ca Thu Jul 14 04:02:21 2016 From: huntrods at athabascau.ca (Richard Huntrods) Date: Wed, 13 Jul 2016 21:02:21 -0700 Subject: [Opm] Greetings & compile questions In-Reply-To: References: <57866956.6090504@athabascau.ca> <5786EEBA.7050401@athabascau.ca> Message-ID: <57870ECD.6060707@athabascau.ca> Hi Liu, On 7/13/2016 6:59 PM, Ming Liu wrote: > Hi Richard, > > If I understand you correctly, you have already been built and run > FLOW, that means you don't have any issue related to the compile and > linker. > The only issue is that when you running flow, some messages are output > in the terminal saying that > " > Error: Keyword 'NOECHO' is not supported by flow. > In file /home/liuming/work/opm/opm-data/norne/NORNE_ATW2013.DATA, line > 143 > > Error: Keyword 'SPECGRID' is not supported by flow. > In file > /home/liuming/work/opm/opm-data/norne/INCLUDE/GRID/IRAP_1005.GRDECL, > line 10 > " > But after these keywords, flow is still running, right? Correct. The SPE 1 & 3 case as well as Norne all ran to completion and gave the same output as 14.04. > > Probably the confused thing is that these kinds of messages did not > show before, that's because we introduce these messages early this > week, that is this PR https://github.com/OPM/opm-simulators/pull/756. OK. That makes sense. My build of flow on Ubuntu 14.04 was done July 7 15:54 PDT. (I just checked the dates on /usr/local/bin. That would mean that if I were to build flow again on ubuntu 14.04 (using the latest code) I would see the same error messages when I run cases. That's good to know. I'll probably do that this week. :-) > > But regarding ubuntu 16.04, there is a potential issue could lead to > the failure of the build process, please check issue here > https://github.com/OPM/opm-simulators/issues/757 Thanks. My most recent build on ubuntu 16.04 today, trying to use the latest libraries was even worse. Flow did not compile (fatal compile errors). Checking my dependencies script, I see that I did install the latest libeigen, which the issue states does not work. This is very enjoyable for me. I'm also working to convert some of my very old datasets from other simulators to the Eclipse 100 deck format. I do wish there was a pdf copy of the Eclipse manual around. I looked but there's only course notes and such, unless I've missed something. Seeing the issues you highlighted, I think I'll sign up to join the github conversations tomorrow. Cheers, -Richard > > Best regards, > > Liu Ming > > > 2016-07-14 9:45 GMT+08:00 Richard Huntrods >: > > Hi Liu, > > I understand. > > I'm not talking about Eclipse keywords that are not in the Ubuntu > 14.04 version today. I am talking about keywords that work today > in flow compiled on ubuntu 14.04 but are missing when you compile > the same exact source code in Ubuntu 16.04. Keywords like ECHO > and NOECHO. > > Something in the ubuntu 16.04 build process isn't compiling or > linking everything correctly. I am currently diggin deeper to see > which dependencies have changed between 14.04 and 16.04. > > I do know there's an issue with libtool. It's not installed by > default in Ubuntu 16.04 but was in Ubunty 14.04. Worse, when you > install it in 16.04, somehow it's not where Cmake wants it to be, > which I am sure is affecting the build / link process. I'm > tracking that down. > > There are also different (newer) versions of dependencies between > ubuntu 14.04 and ubuntu 16.04: > libumfpack5.6.2 (now libumfpack5.7.1 in ubuntu 16.04) > libboost1.55-dev-all (now libboost1.58-dev-all in ubuntu 16.04) > and libsuperlu3-dev (now libsuperlu-dev in ubuntu 16.04) > Finally, C++ is installed by default in Ubuntu 16.04 at version > 5, not 4.7. > > The problem for me is that it's a very complex build process, and > trying to figure out which new dependency library is causing the > compile process to hiccup is difficult. However, I'm working away > at it. > > Cheers, > > -Richard > > > On 7/13/2016 5:59 PM, Ming Liu wrote: >> Hi Richard, >> >> I think what kai said is very clear, recently we are working on >> the improvement of the print file, that is .PRT file, we believe >> this will give the user clear messages that some keywords are not >> supported by flow currently, that's why you can see lots of >> output. I'm sorry this output brings you the trouble, but do not >> worry, nothing changed in the source code about summary file and >> restart file, you can still check results with any visualization >> tools you like, such as resinsight. >> >> Best regards, >> Liu Ming >> >> 2016-07-14 0:16 GMT+08:00 Richard Huntrods >> >: >> >> Greetings! >> >> My name is Richard Huntrods, currently on Vancouver Island >> Canada. My background is in Chemical Engineering (B.Sc. & >> M.Eng.). I spent 5+ years in the 1980's writing reservoir >> simulators for a few companies in Alberta, Canada. Since then >> I moved into consulting, then full-time teaching. I'm >> currently teaching Computer Science at Athabasca University - >> a distance education university in Alberta. >> >> I have always been interested in reservoir simulation, and >> recently have begun compiling and using the FLOW simulator >> from the OPM project. >> >> I have successfully compiled and used the OPM suite on Ubuntu >> 14.04 as per the build guidelines. I also have kept detailed >> notes of my process, from starting VirtualBox on a Windows 7 >> PC through installing Ubuntu 14.04 and then obtaining and >> building the OPM sources. I also wrote a few shell scripts to >> help automate the process and have confirmed it a few times >> with clean builds. >> >> I would be willing to share my documents and scripts if desired. >> >> I'm now in the process of building OPM from source on Ubuntu >> 16.04. I *almost* works. With a few minor changes required in >> dependency packages, I have been able to get all the sources >> compiled and running. However, there's a problem with FLOW - >> it won't recognize many of the output keywords such as ECHO, >> NOECHO, RPTSCHED from the SPE test cases, and many more in >> the Norne test case. I am sure it's a missing dependency in >> the Eclipse input code, but have not yet isolated it. >> >> I am wondering who is currently working on compiling under >> Ubuntu 16.04 and whether or not they would be willing to >> share any tips and problems they may already have seen and >> diagnosed. I'd be very willing to contribute to this process. >> >> Thanks in advance, and again welcome to everyone. >> >> -Richard Huntrods, P.Eng. >> >> --- >> This email has been checked for viruses by Avast antivirus >> software. >> https://www.avast.com/antivirus >> >> _______________________________________________ >> Opm mailing list >> Opm at opm-project.org >> http://opm-project.org/cgi-bin/mailman/listinfo/opm >> >> > > > > Virus-free. www.avast.com > > > > --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -------------- next part -------------- An HTML attachment was scrubbed... URL: From liuming1035 at gmail.com Thu Jul 14 04:43:11 2016 From: liuming1035 at gmail.com (Ming Liu) Date: Thu, 14 Jul 2016 12:43:11 +0800 Subject: [Opm] Greetings & compile questions In-Reply-To: <57870ECD.6060707@athabascau.ca> References: <57866956.6090504@athabascau.ca> <5786EEBA.7050401@athabascau.ca> <57870ECD.6060707@athabascau.ca> Message-ID: Hi Richards, That would mean that if I were to build flow again on ubuntu 14.04 (using the latest code) I would see the same error messages when I run cases. Yes. My most recent build on ubuntu 16.04 today, trying to use the latest libraries was even worse. Flow did not compile (fatal compile errors). Checking my dependencies script, I see that I did install the latest libeigen, which the issue states does not work. Could you please open an issue on the related modules in the pages of OPM project, and follow the details , that would be very helpful for the others to solve your problem. Best regards, Liu Ming 2016年7月14日星期四,Richard Huntrods 写道: > Hi Liu, > > On 7/13/2016 6:59 PM, Ming Liu wrote: > > Hi Richard, > > If I understand you correctly, you have already been built and run FLOW, > that means you don't have any issue related to the compile and linker. > The only issue is that when you running flow, some messages are output in > the terminal saying that > " > Error: Keyword 'NOECHO' is not supported by flow. > In file /home/liuming/work/opm/opm-data/norne/NORNE_ATW2013.DATA, line 143 > > Error: Keyword 'SPECGRID' is not supported by flow. > In file > /home/liuming/work/opm/opm-data/norne/INCLUDE/GRID/IRAP_1005.GRDECL, line 10 > " > But after these keywords, flow is still running, right? > > Correct. The SPE 1 & 3 case as well as Norne all ran to completion and > gave the same output as 14.04. > > > Probably the confused thing is that these kinds of messages did not show > before, that's because we introduce these messages early this week, that > is this PR > https://github.com/OPM/opm-simulators/pull/756. > > OK. That makes sense. My build of flow on Ubuntu 14.04 was done July 7 > 15:54 PDT. (I just checked the dates on /usr/local/bin. > > That would mean that if I were to build flow again on ubuntu 14.04 (using > the latest code) I would see the same error messages when I run cases. > That's good to know. I'll probably do that this week. :-) > > > But regarding ubuntu 16.04, there is a potential issue could lead to the > failure of the build process, please check issue here > https://github.com/OPM/opm-simulators/issues/757 > > > Thanks. > > My most recent build on ubuntu 16.04 today, trying to use the latest > libraries was even worse. Flow did not compile (fatal compile errors). > Checking my dependencies script, I see that I did install the latest > libeigen, which the issue states does not work. > > This is very enjoyable for me. I'm also working to convert some of my very > old datasets from other simulators to the Eclipse 100 deck format. I do > wish there was a pdf copy of the Eclipse manual around. I looked but > there's only course notes and such, unless I've missed something. > > Seeing the issues you highlighted, I think I'll sign up to join the github > conversations tomorrow. > > Cheers, > > -Richard > > > Best regards, > > Liu Ming > > > 2016-07-14 9:45 GMT+08:00 Richard Huntrods >: > >> Hi Liu, >> >> I understand. >> >> I'm not talking about Eclipse keywords that are not in the Ubuntu 14.04 >> version today. I am talking about keywords that work today in flow >> compiled on ubuntu 14.04 but are missing when you compile the same exact >> source code in Ubuntu 16.04. Keywords like ECHO and NOECHO. >> >> Something in the ubuntu 16.04 build process isn't compiling or linking >> everything correctly. I am currently diggin deeper to see which >> dependencies have changed between 14.04 and 16.04. >> >> I do know there's an issue with libtool. It's not installed by default in >> Ubuntu 16.04 but was in Ubunty 14.04. Worse, when you install it in 16.04, >> somehow it's not where Cmake wants it to be, which I am sure is affecting >> the build / link process. I'm tracking that down. >> >> There are also different (newer) versions of dependencies between ubuntu >> 14.04 and ubuntu 16.04: >> libumfpack5.6.2 (now libumfpack5.7.1 in ubuntu 16.04) >> libboost1.55-dev-all (now libboost1.58-dev-all in ubuntu 16.04) >> and libsuperlu3-dev (now libsuperlu-dev in ubuntu 16.04) >> Finally, C++ is installed by default in Ubuntu 16.04 at version 5, not >> 4.7. >> >> The problem for me is that it's a very complex build process, and trying >> to figure out which new dependency library is causing the compile process >> to hiccup is difficult. However, I'm working away at it. >> >> Cheers, >> >> -Richard >> >> >> On 7/13/2016 5:59 PM, Ming Liu wrote: >> >> Hi Richard, >> >> I think what kai said is very clear, recently we are working on the >> improvement of the print file, that is .PRT file, we believe this will >> give the user clear messages that some keywords are not supported by flow >> currently, that's why you can see lots of output. I'm sorry this output >> brings you the trouble, but do not worry, nothing changed in the source >> code about summary file and restart file, you can still check results with >> any visualization tools you like, such as resinsight. >> >> Best regards, >> Liu Ming >> >> 2016-07-14 0:16 GMT+08:00 Richard Huntrods < >> >> huntrods at athabascau.ca >> >: >> >>> Greetings! >>> >>> My name is Richard Huntrods, currently on Vancouver Island Canada. My >>> background is in Chemical Engineering (B.Sc. & M.Eng.). I spent 5+ years in >>> the 1980's writing reservoir simulators for a few companies in Alberta, >>> Canada. Since then I moved into consulting, then full-time teaching. I'm >>> currently teaching Computer Science at Athabasca University - a distance >>> education university in Alberta. >>> >>> I have always been interested in reservoir simulation, and recently have >>> begun compiling and using the FLOW simulator from the OPM project. >>> >>> I have successfully compiled and used the OPM suite on Ubuntu 14.04 as >>> per the build guidelines. I also have kept detailed notes of my process, >>> from starting VirtualBox on a Windows 7 PC through installing Ubuntu 14.04 >>> and then obtaining and building the OPM sources. I also wrote a few shell >>> scripts to help automate the process and have confirmed it a few times with >>> clean builds. >>> >>> I would be willing to share my documents and scripts if desired. >>> >>> I'm now in the process of building OPM from source on Ubuntu 16.04. I >>> *almost* works. With a few minor changes required in dependency packages, I >>> have been able to get all the sources compiled and running. However, >>> there's a problem with FLOW - it won't recognize many of the output >>> keywords such as ECHO, NOECHO, RPTSCHED from the SPE test cases, and many >>> more in the Norne test case. I am sure it's a missing dependency in the >>> Eclipse input code, but have not yet isolated it. >>> >>> I am wondering who is currently working on compiling under Ubuntu 16.04 >>> and whether or not they would be willing to share any tips and problems >>> they may already have seen and diagnosed. I'd be very willing to contribute >>> to this process. >>> >>> Thanks in advance, and again welcome to everyone. >>> >>> -Richard Huntrods, P.Eng. >>> >>> --- >>> This email has been checked for viruses by Avast antivirus software. >>> https://www.avast.com/antivirus >>> >>> _______________________________________________ >>> Opm mailing list >>> Opm at opm-project.org >>> >>> http://opm-project.org/cgi-bin/mailman/listinfo/opm >>> >> >> >> >> >> Virus-free. >> www.avast.com >> >> > > > > > Virus-free. > www.avast.com > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From huntrods at athabascau.ca Thu Jul 14 04:46:10 2016 From: huntrods at athabascau.ca (Richard Huntrods) Date: Wed, 13 Jul 2016 21:46:10 -0700 Subject: [Opm] Greetings & compile questions In-Reply-To: References: <57866956.6090504@athabascau.ca> <5786EEBA.7050401@athabascau.ca> <57870ECD.6060707@athabascau.ca> Message-ID: <57871912.40600@athabascau.ca> Hi Liu, On 7/13/2016 9:43 PM, Ming Liu wrote: > Hi Richards, > > That would mean that if I were to build flow again on ubuntu 14.04 > (using the latest code) I would see the same error messages when I > run cases. > > Yes. > > > My most recent build on ubuntu 16.04 today, trying to use the > latest libraries was even worse. Flow did not compile (fatal > compile errors). Checking my dependencies script, I see that I > did install the latest libeigen, which the issue states does not work. > > Could you please open an issue on the related modules in the pages of > OPM project, and follow the details , that would be very helpful for > the others to solve your problem. OK. I'll have to reproduce the problems tomorrow as I deleted the virtual image. I'm trying to make everything I do repeatable. Cheers, -Richard > > > Best regards, > Liu Ming > > 2016年7月14日星期四,Richard Huntrods > 写道: > > Hi Liu, > > On 7/13/2016 6:59 PM, Ming Liu wrote: >> Hi Richard, >> >> If I understand you correctly, you have already been built and >> run FLOW, that means you don't have any issue related to the >> compile and linker. >> The only issue is that when you running flow, some messages are >> output in the terminal saying that >> " >> Error: Keyword 'NOECHO' is not supported by flow. >> In file /home/liuming/work/opm/opm-data/norne/NORNE_ATW2013.DATA, >> line 143 >> >> Error: Keyword 'SPECGRID' is not supported by flow. >> In file >> /home/liuming/work/opm/opm-data/norne/INCLUDE/GRID/IRAP_1005.GRDECL, >> line 10 >> " >> But after these keywords, flow is still running, right? > Correct. The SPE 1 & 3 case as well as Norne all ran to completion > and gave the same output as 14.04. >> >> Probably the confused thing is that these kinds of messages did >> not show before, that's because we introduce these messages early >> this week, that is this PR >> https://github.com/OPM/opm-simulators/pull/756. > OK. That makes sense. My build of flow on Ubuntu 14.04 was done > July 7 15:54 PDT. (I just checked the dates on /usr/local/bin. > > That would mean that if I were to build flow again on ubuntu 14.04 > (using the latest code) I would see the same error messages when I > run cases. That's good to know. I'll probably do that this week. :-) >> >> But regarding ubuntu 16.04, there is a potential issue could lead >> to the failure of the build process, please check issue here >> https://github.com/OPM/opm-simulators/issues/757 > > Thanks. > > My most recent build on ubuntu 16.04 today, trying to use the > latest libraries was even worse. Flow did not compile (fatal > compile errors). Checking my dependencies script, I see that I > did install the latest libeigen, which the issue states does not work. > > This is very enjoyable for me. I'm also working to convert some of > my very old datasets from other simulators to the Eclipse 100 deck > format. I do wish there was a pdf copy of the Eclipse manual > around. I looked but there's only course notes and such, unless > I've missed something. > > Seeing the issues you highlighted, I think I'll sign up to join > the github conversations tomorrow. > > Cheers, > > -Richard >> >> Best regards, >> >> Liu Ming >> >> >> 2016-07-14 9:45 GMT+08:00 Richard Huntrods >> > >: >> >> Hi Liu, >> >> I understand. >> >> I'm not talking about Eclipse keywords that are not in the >> Ubuntu 14.04 version today. I am talking about keywords >> that work today in flow compiled on ubuntu 14.04 but are >> missing when you compile the same exact source code in Ubuntu >> 16.04. Keywords like ECHO and NOECHO. >> >> Something in the ubuntu 16.04 build process isn't compiling >> or linking everything correctly. I am currently diggin deeper >> to see which dependencies have changed between 14.04 and 16.04. >> >> I do know there's an issue with libtool. It's not installed >> by default in Ubuntu 16.04 but was in Ubunty 14.04. Worse, >> when you install it in 16.04, somehow it's not where Cmake >> wants it to be, which I am sure is affecting the build / link >> process. I'm tracking that down. >> >> There are also different (newer) versions of dependencies >> between ubuntu 14.04 and ubuntu 16.04: >> libumfpack5.6.2 (now libumfpack5.7.1 in ubuntu 16.04) >> libboost1.55-dev-all (now libboost1.58-dev-all in ubuntu 16.04) >> and libsuperlu3-dev (now libsuperlu-dev in ubuntu 16.04) >> Finally, C++ is installed by default in Ubuntu 16.04 at >> version 5, not 4.7. >> >> The problem for me is that it's a very complex build process, >> and trying to figure out which new dependency library is >> causing the compile process to hiccup is difficult. However, >> I'm working away at it. >> >> Cheers, >> >> -Richard >> >> >> On 7/13/2016 5:59 PM, Ming Liu wrote: >>> Hi Richard, >>> >>> I think what kai said is very clear, recently we are working >>> on the improvement of the print file, that is .PRT file, we >>> believe this will give the user clear messages that some >>> keywords are not supported by flow currently, that's why you >>> can see lots of output. I'm sorry this output brings you >>> the trouble, but do not worry, nothing changed in the source >>> code about summary file and restart file, you can still >>> check results with any visualization tools you like, such as >>> resinsight. >>> >>> Best regards, >>> Liu Ming >>> >>> 2016-07-14 0:16 GMT+08:00 Richard Huntrods >>> >> >: >>> >>> Greetings! >>> >>> My name is Richard Huntrods, currently on Vancouver >>> Island Canada. My background is in Chemical Engineering >>> (B.Sc. & M.Eng.). I spent 5+ years in the 1980's writing >>> reservoir simulators for a few companies in Alberta, >>> Canada. Since then I moved into consulting, then >>> full-time teaching. I'm currently teaching Computer >>> Science at Athabasca University - a distance education >>> university in Alberta. >>> >>> I have always been interested in reservoir simulation, >>> and recently have begun compiling and using the FLOW >>> simulator from the OPM project. >>> >>> I have successfully compiled and used the OPM suite on >>> Ubuntu 14.04 as per the build guidelines. I also have >>> kept detailed notes of my process, from starting >>> VirtualBox on a Windows 7 PC through installing Ubuntu >>> 14.04 and then obtaining and building the OPM sources. I >>> also wrote a few shell scripts to help automate the >>> process and have confirmed it a few times with clean builds. >>> >>> I would be willing to share my documents and scripts if >>> desired. >>> >>> I'm now in the process of building OPM from source on >>> Ubuntu 16.04. I *almost* works. With a few minor changes >>> required in dependency packages, I have been able to get >>> all the sources compiled and running. However, there's >>> a problem with FLOW - it won't recognize many of the >>> output keywords such as ECHO, NOECHO, RPTSCHED from the >>> SPE test cases, and many more in the Norne test case. I >>> am sure it's a missing dependency in the Eclipse input >>> code, but have not yet isolated it. >>> >>> I am wondering who is currently working on compiling >>> under Ubuntu 16.04 and whether or not they would be >>> willing to share any tips and problems they may already >>> have seen and diagnosed. I'd be very willing to >>> contribute to this process. >>> >>> Thanks in advance, and again welcome to everyone. >>> >>> -Richard Huntrods, P.Eng. >>> >>> --- >>> This email has been checked for viruses by Avast >>> antivirus software. >>> https://www.avast.com/antivirus >>> >>> _______________________________________________ >>> Opm mailing list >>> Opm at opm-project.org >>> >>> http://opm-project.org/cgi-bin/mailman/listinfo/opm >>> >>> >> >> >> >> Virus-free. www.avast.com >> >> >> >> > > > > Virus-free. www.avast.com > > > --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -------------- next part -------------- An HTML attachment was scrubbed... URL: From liuming1035 at gmail.com Thu Jul 14 04:49:57 2016 From: liuming1035 at gmail.com (Ming Liu) Date: Thu, 14 Jul 2016 12:49:57 +0800 Subject: [Opm] Greetings & compile questions In-Reply-To: <57871912.40600@athabascau.ca> References: <57866956.6090504@athabascau.ca> <5786EEBA.7050401@athabascau.ca> <57870ECD.6060707@athabascau.ca> <57871912.40600@athabascau.ca> Message-ID: Sure, take your time. BTW, if you have any problems, please just open an issues in github. Best regards, Liu Ming 2016年7月14日星期四,Richard Huntrods > 写道: > Hi Liu, > > On 7/13/2016 9:43 PM, Ming Liu wrote: > > Hi Richards, > > That would mean that if I were to build flow again on ubuntu 14.04 (using > the latest code) I would see the same error messages when I run cases. > > Yes. > > > My most recent build on ubuntu 16.04 today, trying to use the latest > libraries was even worse. Flow did not compile (fatal compile errors). > Checking my dependencies script, I see that I did install the latest > libeigen, which the issue states does not work. > > Could you please open an issue on the related modules in the pages of OPM > project, and follow the details , that would be very helpful for the others > to solve your problem. > > OK. I'll have to reproduce the problems tomorrow as I deleted the virtual > image. I'm trying to make everything I do repeatable. > > Cheers, > > -Richard > > > > Best regards, > Liu Ming > > 2016年7月14日星期四,Richard Huntrods 写道: > >> Hi Liu, >> >> On 7/13/2016 6:59 PM, Ming Liu wrote: >> >> Hi Richard, >> >> If I understand you correctly, you have already been built and run FLOW, >> that means you don't have any issue related to the compile and linker. >> The only issue is that when you running flow, some messages are output in >> the terminal saying that >> " >> Error: Keyword 'NOECHO' is not supported by flow. >> In file /home/liuming/work/opm/opm-data/norne/NORNE_ATW2013.DATA, line >> 143 >> >> Error: Keyword 'SPECGRID' is not supported by flow. >> In file >> /home/liuming/work/opm/opm-data/norne/INCLUDE/GRID/IRAP_1005.GRDECL, line 10 >> " >> But after these keywords, flow is still running, right? >> >> Correct. The SPE 1 & 3 case as well as Norne all ran to completion and >> gave the same output as 14.04. >> >> >> Probably the confused thing is that these kinds of messages did not show >> before, that's because we introduce these messages early this week, that >> is this PR https://github.com/OPM/opm-simulators/pull/756. >> >> OK. That makes sense. My build of flow on Ubuntu 14.04 was done July 7 >> 15:54 PDT. (I just checked the dates on /usr/local/bin. >> >> That would mean that if I were to build flow again on ubuntu 14.04 (using >> the latest code) I would see the same error messages when I run cases. >> That's good to know. I'll probably do that this week. :-) >> >> >> But regarding ubuntu 16.04, there is a potential issue could lead to the >> failure of the build process, please check issue here >> >> https://github.com/OPM/opm-simulators/issues/757 >> >> >> Thanks. >> >> My most recent build on ubuntu 16.04 today, trying to use the latest >> libraries was even worse. Flow did not compile (fatal compile errors). >> Checking my dependencies script, I see that I did install the latest >> libeigen, which the issue states does not work. >> >> This is very enjoyable for me. I'm also working to convert some of my >> very old datasets from other simulators to the Eclipse 100 deck format. I >> do wish there was a pdf copy of the Eclipse manual around. I looked but >> there's only course notes and such, unless I've missed something. >> >> Seeing the issues you highlighted, I think I'll sign up to join the >> github conversations tomorrow. >> >> Cheers, >> >> -Richard >> >> >> Best regards, >> >> Liu Ming >> >> >> 2016-07-14 9:45 GMT+08:00 Richard Huntrods : >> >>> Hi Liu, >>> >>> I understand. >>> >>> I'm not talking about Eclipse keywords that are not in the Ubuntu 14.04 >>> version today. I am talking about keywords that work today in flow >>> compiled on ubuntu 14.04 but are missing when you compile the same exact >>> source code in Ubuntu 16.04. Keywords like ECHO and NOECHO. >>> >>> Something in the ubuntu 16.04 build process isn't compiling or linking >>> everything correctly. I am currently diggin deeper to see which >>> dependencies have changed between 14.04 and 16.04. >>> >>> I do know there's an issue with libtool. It's not installed by default >>> in Ubuntu 16.04 but was in Ubunty 14.04. Worse, when you install it in >>> 16.04, somehow it's not where Cmake wants it to be, which I am sure is >>> affecting the build / link process. I'm tracking that down. >>> >>> There are also different (newer) versions of dependencies between ubuntu >>> 14.04 and ubuntu 16.04: >>> libumfpack5.6.2 (now libumfpack5.7.1 in ubuntu 16.04) >>> libboost1.55-dev-all (now libboost1.58-dev-all in ubuntu 16.04) >>> and libsuperlu3-dev (now libsuperlu-dev in ubuntu 16.04) >>> Finally, C++ is installed by default in Ubuntu 16.04 at version 5, not >>> 4.7. >>> >>> The problem for me is that it's a very complex build process, and trying >>> to figure out which new dependency library is causing the compile process >>> to hiccup is difficult. However, I'm working away at it. >>> >>> Cheers, >>> >>> -Richard >>> >>> >>> On 7/13/2016 5:59 PM, Ming Liu wrote: >>> >>> Hi Richard, >>> >>> I think what kai said is very clear, recently we are working on the >>> improvement of the print file, that is .PRT file, we believe this will >>> give the user clear messages that some keywords are not supported by flow >>> currently, that's why you can see lots of output. I'm sorry this output >>> brings you the trouble, but do not worry, nothing changed in the source >>> code about summary file and restart file, you can still check results with >>> any visualization tools you like, such as resinsight. >>> >>> Best regards, >>> Liu Ming >>> >>> 2016-07-14 0:16 GMT+08:00 Richard Huntrods : >>> >>>> Greetings! >>>> >>>> My name is Richard Huntrods, currently on Vancouver Island Canada. My >>>> background is in Chemical Engineering (B.Sc. & M.Eng.). I spent 5+ years in >>>> the 1980's writing reservoir simulators for a few companies in Alberta, >>>> Canada. Since then I moved into consulting, then full-time teaching. I'm >>>> currently teaching Computer Science at Athabasca University - a distance >>>> education university in Alberta. >>>> >>>> I have always been interested in reservoir simulation, and recently >>>> have begun compiling and using the FLOW simulator from the OPM project. >>>> >>>> I have successfully compiled and used the OPM suite on Ubuntu 14.04 as >>>> per the build guidelines. I also have kept detailed notes of my process, >>>> from starting VirtualBox on a Windows 7 PC through installing Ubuntu 14.04 >>>> and then obtaining and building the OPM sources. I also wrote a few shell >>>> scripts to help automate the process and have confirmed it a few times with >>>> clean builds. >>>> >>>> I would be willing to share my documents and scripts if desired. >>>> >>>> I'm now in the process of building OPM from source on Ubuntu 16.04. I >>>> *almost* works. With a few minor changes required in dependency packages, I >>>> have been able to get all the sources compiled and running. However, >>>> there's a problem with FLOW - it won't recognize many of the output >>>> keywords such as ECHO, NOECHO, RPTSCHED from the SPE test cases, and many >>>> more in the Norne test case. I am sure it's a missing dependency in the >>>> Eclipse input code, but have not yet isolated it. >>>> >>>> I am wondering who is currently working on compiling under Ubuntu 16.04 >>>> and whether or not they would be willing to share any tips and problems >>>> they may already have seen and diagnosed. I'd be very willing to contribute >>>> to this process. >>>> >>>> Thanks in advance, and again welcome to everyone. >>>> >>>> -Richard Huntrods, P.Eng. >>>> >>>> --- >>>> This email has been checked for viruses by Avast antivirus software. >>>> https://www.avast.com/antivirus >>>> >>>> _______________________________________________ >>>> Opm mailing list >>>> Opm at opm-project.org >>>> http://opm-project.org/cgi-bin/mailman/listinfo/opm >>>> >>> >>> >>> >>> >>> Virus-free. >>> www.avast.com >>> >>> >> >> >> >> >> Virus-free. >> www.avast.com >> >> > > > > Virus-free. > www.avast.com > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From huntrods at athabascau.ca Thu Jul 14 19:29:32 2016 From: huntrods at athabascau.ca (Richard Huntrods) Date: Thu, 14 Jul 2016 12:29:32 -0700 Subject: [Opm] Greetings & compile questions In-Reply-To: References: <57866956.6090504@athabascau.ca> <5786EEBA.7050401@athabascau.ca> <57870ECD.6060707@athabascau.ca> <57871912.40600@athabascau.ca> Message-ID: <5787E81C.1050801@athabascau.ca> Hi Liu, On 7/13/2016 9:49 PM, Ming Liu wrote: > > Sure, take your time. > BTW, if you have any problems, please just open an issues in github. Thank you. I'm in the process of reading the various issues on github. One other question: do you or anyone know a way to obtain a pdf of the Eclipse 100 Reference manual? Although I used many reservoir simulators in the past, I never did use Eclipse, so don't have a manual. I have decks for other simulators that I'd like to convert but cross-referencing keywords when you don't have a manual (for Eclipse) is quite difficult. Thanks, -Richard Huntrods P.Eng. > > Best regards, > Liu Ming > 2016年7月14日星期四,Richard Huntrods > 写道: > --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -------------- next part -------------- An HTML attachment was scrubbed... URL: From JOKVA at statoil.com Mon Jul 18 11:29:11 2016 From: JOKVA at statoil.com (=?iso-8859-1?Q?J=F8rgen_Kvalsvik?=) Date: Mon, 18 Jul 2016 11:29:11 +0000 Subject: [Opm] opm-output Status of SUMMARY support Message-ID: <0DE2898B514EE542B05967D975C25F505C4FD1E8@WS343.statoil.net> Hi all, Summary support is developing rapidly. Once #65 is merged the following list of keywords can be output: CGIR FGIRH FLIR FOPRH FWPTH GLPRH GWIR WGIT WLPRH WTHP CGIT FGIT FLIT FOPT GGIR GLPT GWIRH WGITH WLPT WWCT CGPR FGITH FLPR FOPTH GGIRH GLPTH GWIT WGLR WLPTH WWCT CGPT FGLR FLPRH FWCT GGIT GOIR GWITH WGLRH WOIR WWIR COPR FGLRH FLPT FWIR GGITH GOIRH GWPR WGOR WOIRH WWIR COPT FGOR FLPTH FWIRH GGOR GOIT GWPRH WGORH WOIT WWIT CWIR FGORH FOIR FWIT GGPR GOPR GWPT WGPR WOITH WWIT CWIT FGPR FOIRH FWITH GGPRH GOPRH GWPTH WGPRH WOPR WWPR CWPR FGPRH FOIT FWPR GGPT GOPT WBHP WGPT WOPRH WWPR CWPT FGPT FOITH FWPRH GGPTH GOPTH WGIR WGPTH WOPT WWPT FGIR FGPTH FOPR FWPT GLPR GWCT WGIRH WLPR WOPTH WWPT More keywords are obviously underway, but they will probably require more thought and potentially redesign to work. Regardless, it's shaping up nicely. Please do not hesitate to report errors or shortcomings, and feel free to contribute with code, documentation or examples. #65: https://github.com/OPM/opm-output/pull/65 ------------------------------------------------------------------- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus at dr-blatt.de Wed Jul 20 17:38:39 2016 From: markus at dr-blatt.de (Markus Blatt) Date: Wed, 20 Jul 2016 19:38:39 +0200 Subject: [Opm] Greetings & compile questions In-Reply-To: <5787E81C.1050801@athabascau.ca> References: <57866956.6090504@athabascau.ca> <5786EEBA.7050401@athabascau.ca> <57870ECD.6060707@athabascau.ca> <57871912.40600@athabascau.ca> <5787E81C.1050801@athabascau.ca> Message-ID: <20160720173839.GA8993@boromir.dr-blatt.de> Hi, On Thu, Jul 14, 2016 at 12:29:32PM -0700, Richard Huntrods wrote: > > One other question: do you or anyone know a way to obtain a pdf of the > Eclipse 100 Reference manual? > You probably need to buy the software. But there is a nice description of the keywords in http://folk.uib.no/fciop/index_htm_files/ResSimNotes.pdf Markus -- Dr. Markus Blatt - HPC-Simulation-Software & Services http://www.dr-blatt.de Hans-Bunte-Str. 8-10, 69123 Heidelberg, Germany, USt-Id: DE279960836 Tel.: +49 (0) 160 97590858 From markus at dr-blatt.de Wed Jul 20 17:42:25 2016 From: markus at dr-blatt.de (Markus Blatt) Date: Wed, 20 Jul 2016 19:42:25 +0200 Subject: [Opm] Greetings & compile questions In-Reply-To: <20160720173839.GA8993@boromir.dr-blatt.de> References: <57866956.6090504@athabascau.ca> <5786EEBA.7050401@athabascau.ca> <57870ECD.6060707@athabascau.ca> <57871912.40600@athabascau.ca> <5787E81C.1050801@athabascau.ca> <20160720173839.GA8993@boromir.dr-blatt.de> Message-ID: <20160720174225.GB8993@boromir.dr-blatt.de> On Wed, Jul 20, 2016 at 07:38:39PM +0200, Markus Blatt wrote: > On Thu, Jul 14, 2016 at 12:29:32PM -0700, Richard Huntrods wrote: > > > > One other question: do you or anyone know a way to obtain a pdf of the > > Eclipse 100 Reference manual? > > > > You probably need to buy the software. But there is a nice description > of the keywords in > http://folk.uib.no/fciop/index_htm_files/ResSimNotes.pdf > Found among user useful links with https://duckduckgo.com/?q=eclipse+compdat -- Dr. Markus Blatt - HPC-Simulation-Software & Services http://www.dr-blatt.de Hans-Bunte-Str. 8-10, 69123 Heidelberg, Germany, USt-Id: DE279960836 Tel.: +49 (0) 160 97590858 From markus at dr-blatt.de Mon Jul 25 08:17:33 2016 From: markus at dr-blatt.de (Markus Blatt) Date: Mon, 25 Jul 2016 10:17:33 +0200 Subject: [Opm] How to force writing of initial state Message-ID: <20160725081733.GB1867@boromir.dr-blatt.de> Hi, I am currently failing to force flow to write the initial state of the simulation. Basically, I am forcing flow to abort after https://github.com/OPM/opm-simulators/blob/afa64d98759ec25a096acb80d6c588fc58ed1646/opm/autodiff/SimulatorBase_impl.hpp#L169-L171, but some the EclipseWriter does not create *.UNRST file. The test case that I want to run is spe9 with the following modifications $ git diff SPE9.DATAdiff --git a/spe9/SPE9.DATA b/spe9/SPE9.DATA index 97f2a11..843666c 100644 --- a/spe9/SPE9.DATA +++ b/spe9/SPE9.DATA @@ -409,7 +409,11 @@ WWPR SCHEDULE RPTRST - 'BASIC=4' / + 'BASIC=1' / + +RPTSOL + RESTART=2 / + WELSPECS -- Column 3: I-value of well head or heel -- Column 4: J-value of well head or heel $ But I do neither see any of the state variables with ResInsight nor is there a *.UNRST file created. The change concerning RPTSOL is inspired by http://ert.nr.no/ert/index.php?title=Preparing_an_ECLIPSE_reservoir_model_for_use_with_enkf&oldid=276#Output_of_inital_restart_file How do I need to change the eclipse file to get the initial state written? Cheers, Markus -- Dr. Markus Blatt - HPC-Simulation-Software & Services http://www.dr-blatt.de Hans-Bunte-Str. 8-10, 69123 Heidelberg, Germany, USt-Id: DE279960836 Tel.: +49 (0) 160 97590858 From markus at dr-blatt.de Mon Jul 25 15:29:08 2016 From: markus at dr-blatt.de (Markus Blatt) Date: Mon, 25 Jul 2016 17:29:08 +0200 Subject: [Opm] How to force writing of initial state In-Reply-To: <20160725081733.GB1867@boromir.dr-blatt.de> References: <20160725081733.GB1867@boromir.dr-blatt.de> Message-ID: <20160725152908.GD1867@boromir.dr-blatt.de> Joakim helped me this. His advice was that the RPTSOL keyword needs to be moved to the SOLUTION section (not the SCHEDULE section). Markus -- Dr. Markus Blatt - HPC-Simulation-Software & Services http://www.dr-blatt.de Hans-Bunte-Str. 8-10, 69123 Heidelberg, Germany, USt-Id: DE279960836 Tel.: +49 (0) 160 97590858 From KFLIK at statoil.com Wed Jul 27 13:11:38 2016 From: KFLIK at statoil.com (Kristian Flikka) Date: Wed, 27 Jul 2016 13:11:38 +0000 Subject: [Opm] Removing the "output_comparator" from opm-data Message-ID: Hi. With the ongoing efforts to create comparison code and applications / tests for simulator output, I believe the output_comparator folder (https://github.com/OPM/opm-data/tree/master/output_comparator) can and should be removed. Any objections? 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From paolo.orsini at gmail.com Thu Jul 28 16:01:31 2016 From: paolo.orsini at gmail.com (Paolo Orsini) Date: Thu, 28 Jul 2016 18:01:31 +0200 Subject: [Opm] parser - faults extract data data Message-ID: Hi Joakim, If I understood it right, each fault (as defined in eclipse) is a group of FaultFaces When looping on the FaultFaces, I don't see any method to get the I, J and K of the cell the face belongs to? Not even a getGlobalIndex function... How do you work out the face the multiplier should be applied to? I clearly am missing something Thanks a lot for your help Paolo -------------- next part -------------- An HTML attachment was scrubbed... URL: From joakim.hove at gmail.com Thu Jul 28 16:18:12 2016 From: joakim.hove at gmail.com (Joakim Hove) Date: Thu, 28 Jul 2016 18:18:12 +0200 Subject: [Opm] parser - faults extract data data In-Reply-To: References: Message-ID: The FaultFace has begin () and end () iterators which can be used to iterate over the indices. This (untested) should work: for (size_t g : faultface) // do something with g Hth - Joakim 28. juli 2016 18:01 skrev "Paolo Orsini" følgende: > Hi Joakim, > > If I understood it right, each fault (as defined in eclipse) is a group of > FaultFaces > When looping on the FaultFaces, I don't see any method to get the I, J > and K of the cell the face belongs to? > Not even a getGlobalIndex function... > How do you work out the face the multiplier should be applied to? > > I clearly am missing something > > Thanks a lot for your help > > Paolo > > > > _______________________________________________ > Opm mailing list > Opm at opm-project.org > http://opm-project.org/cgi-bin/mailman/listinfo/opm > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From paolo.orsini at gmail.com Thu Jul 28 16:28:33 2016 From: paolo.orsini at gmail.com (Paolo Orsini) Date: Thu, 28 Jul 2016 18:28:33 +0200 Subject: [Opm] parser - faults extract data data In-Reply-To: References: Message-ID: and "g" is the cell global index, I can use to identify the cell... right? Sorry I missed it. Are you saying "untested", because nobody is currently working with faults? However, the parser for the faults seems complete, correct? Thanks a lot Paolo On Thu, Jul 28, 2016 at 6:18 PM, Joakim Hove wrote: > The FaultFace has begin () and end () iterators which can be used to > iterate over the indices. This (untested) should work: > > for (size_t g : faultface) > // do something with g > > Hth - Joakim > 28. juli 2016 18:01 skrev "Paolo Orsini" > følgende: > >> Hi Joakim, >> >> If I understood it right, each fault (as defined in eclipse) is a group >> of FaultFaces >> When looping on the FaultFaces, I don't see any method to get the I, J >> and K of the cell the face belongs to? >> Not even a getGlobalIndex function... >> How do you work out the face the multiplier should be applied to? >> >> I clearly am missing something >> >> Thanks a lot for your help >> >> Paolo >> >> >> >> _______________________________________________ >> Opm mailing list >> Opm at opm-project.org >> http://opm-project.org/cgi-bin/mailman/listinfo/opm >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From joakim.hove at gmail.com Thu Jul 28 16:31:04 2016 From: joakim.hove at gmail.com (Joakim Hove) Date: Thu, 28 Jul 2016 18:31:04 +0200 Subject: [Opm] parser - faults extract data data In-Reply-To: References: Message-ID: The 'g' is a global cell index yes. I said untested because I had not compiled the code in the email. I consider Faults in the parser to be complete, and it is certainly used. Joakim 28. juli 2016 18:28 skrev "Paolo Orsini" følgende: > and "g" is the cell global index, I can use to identify the cell... right? > Sorry I missed it. > Are you saying "untested", because nobody is currently working with faults? > However, the parser for the faults seems complete, correct? > > Thanks a lot > > Paolo > > On Thu, Jul 28, 2016 at 6:18 PM, Joakim Hove > wrote: > >> The FaultFace has begin () and end () iterators which can be used to >> iterate over the indices. This (untested) should work: >> >> for (size_t g : faultface) >> // do something with g >> >> Hth - Joakim >> 28. juli 2016 18:01 skrev "Paolo Orsini" >> følgende: >> >>> Hi Joakim, >>> >>> If I understood it right, each fault (as defined in eclipse) is a group >>> of FaultFaces >>> When looping on the FaultFaces, I don't see any method to get the I, J >>> and K of the cell the face belongs to? >>> Not even a getGlobalIndex function... >>> How do you work out the face the multiplier should be applied to? >>> >>> I clearly am missing something >>> >>> Thanks a lot for your help >>> >>> Paolo >>> >>> >>> >>> _______________________________________________ >>> Opm mailing list >>> Opm at opm-project.org >>> http://opm-project.org/cgi-bin/mailman/listinfo/opm >>> >>> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From paolo.orsini at gmail.com Thu Jul 28 16:33:28 2016 From: paolo.orsini at gmail.com (Paolo Orsini) Date: Thu, 28 Jul 2016 18:33:28 +0200 Subject: [Opm] parser - faults extract data data In-Reply-To: References: Message-ID: All clear, thanks a lot!! On Thu, Jul 28, 2016 at 6:31 PM, Joakim Hove wrote: > The 'g' is a global cell index yes. > > I said untested because I had not compiled the code in the email. > > I consider Faults in the parser to be complete, and it is certainly used. > > Joakim > 28. juli 2016 18:28 skrev "Paolo Orsini" > følgende: > >> and "g" is the cell global index, I can use to identify the cell... right? >> Sorry I missed it. >> Are you saying "untested", because nobody is currently working with >> faults? >> However, the parser for the faults seems complete, correct? >> >> Thanks a lot >> >> Paolo >> >> On Thu, Jul 28, 2016 at 6:18 PM, Joakim Hove >> wrote: >> >>> The FaultFace has begin () and end () iterators which can be used to >>> iterate over the indices. This (untested) should work: >>> >>> for (size_t g : faultface) >>> // do something with g >>> >>> Hth - Joakim >>> 28. juli 2016 18:01 skrev "Paolo Orsini" >>> følgende: >>> >>>> Hi Joakim, >>>> >>>> If I understood it right, each fault (as defined in eclipse) is a group >>>> of FaultFaces >>>> When looping on the FaultFaces, I don't see any method to get the I, J >>>> and K of the cell the face belongs to? >>>> Not even a getGlobalIndex function... >>>> How do you work out the face the multiplier should be applied to? >>>> >>>> I clearly am missing something >>>> >>>> Thanks a lot for your help >>>> >>>> Paolo >>>> >>>> >>>> >>>> _______________________________________________ >>>> Opm mailing list >>>> Opm at opm-project.org >>>> http://opm-project.org/cgi-bin/mailman/listinfo/opm >>>> >>>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: