From rlwalker at usc.edu Mon Aug 8 18:18:32 2016 From: rlwalker at usc.edu (Robert Walker) Date: Mon, 8 Aug 2016 11:18:32 -0700 Subject: [Opm] ECLIPSE Keywords Supported Message-ID: Hello, Is there a listing of what ECLIPSE keywords are supported by which OPM simulator? I imagine there exists a file for FLOW somewhere within the code, but I thought I would ask before diving headlong. Thank you, Robert 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From joaho at statoil.com Tue Aug 9 06:20:45 2016 From: joaho at statoil.com (Joakim Hove) Date: Tue, 9 Aug 2016 06:20:45 +0000 Subject: [Opm] ECLIPSE Keywords Supported In-Reply-To: References: Message-ID: Whether a keyword is supported in flow is not really that clear cut; in my opinion it is meaningful to talk of two main levels of support: 1. Read support: The parser can read the keyword, and the content of the keyword is properly internalized in the Deck datatructure during the parse process. All the keywords in the https://github.com/OPM/opm-parser/tree/master/opm/parser/share/keywords directory are supported in this way. 2. Full support: Flow actually takes the keyword into account, and behaves correctly according to the values in the keyword. The explicit list of keywords with full support like this does not exist. In addition there is list of keywords which are partially supported, in the sense that some of the item/values are supported, but not all of them. When running flow on a deck it will print a warning for keywords which are read but not supported, or keywords which are only partially supported. This list is a bit extensive. ________________________________ From: Opm on behalf of Robert Walker Sent: Monday, August 8, 2016 8:18:32 PM To: opm at opm-project.org Subject: [Opm] ECLIPSE Keywords Supported Hello, Is there a listing of what ECLIPSE keywords are supported by which OPM simulator? I imagine there exists a file for FLOW somewhere within the code, but I thought I would ask before diving headlong. Thank you, Robert 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 ------------------------------------------------------------------- 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 liuming1035 at gmail.com Tue Aug 9 06:28:59 2016 From: liuming1035 at gmail.com (Ming Liu) Date: Tue, 9 Aug 2016 14:28:59 +0800 Subject: [Opm] ECLIPSE Keywords Supported In-Reply-To: References: Message-ID: Actually the partially supported keywords PR have not been merged yet, so running flow, unsupported keyword in the deck will not be printed. Check this pull request for your reference. https://github.com/OPM/opm-simulators/pull/762 Best regards, Liu Ming 2016年8月9日星期二,Joakim Hove 写道: > Whether a keyword is supported in flow is not really that clear cut; in my > opinion it is meaningful to talk of two main levels of support: > > > 1. Read support: The parser can read the keyword, and the content of the > keyword is properly internalized in the Deck datatructure during the parse > process. All the keywords in the https://github.com/OPM/ > opm-parser/tree/master/opm/parser/share/keywords directory are supported > in this way. > > > 2. Full support: Flow actually takes the keyword into account, and behaves > correctly according to the values in the keyword. The explicit list of > keywords with full support like this does not exist. > > > In addition there is list of keywords which are partially supported, in > the sense that some of the item/values are supported, but not all of them. > When running flow on a deck it will print a warning for keywords which are > read but not supported, or keywords which are only partially supported. > This list is a bit extensive. > > > > > > > > ------------------------------ > *From:* Opm > on behalf > of Robert Walker > > *Sent:* Monday, August 8, 2016 8:18:32 PM > *To:* opm at opm-project.org > > *Subject:* [Opm] ECLIPSE Keywords Supported > > Hello, > > Is there a listing of what ECLIPSE keywords are supported by which OPM > simulator? I imagine there exists a file for FLOW somewhere within the > code, but I thought I would ask before diving headlong. > > Thank you, > > Robert > > > 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 > > > ------------------------------------------------------------------- > 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 > -- Best regards, Liu Ming -------------- next part -------------- An HTML attachment was scrubbed... URL: From KFLIK at statoil.com Wed Aug 10 13:06:54 2016 From: KFLIK at statoil.com (Kristian Flikka) Date: Wed, 10 Aug 2016 13:06:54 +0000 Subject: [Opm] Testing mail from Statoil Message-ID: This is just a test, we've had some problems with the mails from statoil.com addresses to the opm-project list. Sorry for the inconvenience. 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 wang.xyun at gmail.com Thu Aug 11 05:36:50 2016 From: wang.xyun at gmail.com (XiaoYun Wang) Date: Thu, 11 Aug 2016 13:36:50 +0800 Subject: [Opm] ERT cmake problem Message-ID: Hi I try to install ERT.ecl in my PC, redhat 6.4 with cmake 3.6.1 After I download ert-master, mkdir build cmake ../devel there something wrong with [root at shltd-s1 build]# pwd /software/OPM/ert-master/build [root at shltd-s1 build]# cmake ../devel CMake Error at src/CMakeLists.txt:195 (set_target_properties): set_target_properties called with incorrect number of arguments. fatal: Not a git repository (or any of the parent directories): .git CMake Warning (dev) in CMakeLists.txt: No cmake_minimum_required command is present. A line of code such as cmake_minimum_required(VERSION 3.6) should be added at the top of the file. The version specified may be lower if you wish to support older CMake versions for this project. For more information run "cmake --help-policy CMP0000". This warning is for project developers. Use -Wno-dev to suppress it. -- Configuring incomplete, errors occurred! See also "/software/OPM/ert-master/devel/CMakeFiles/CMakeOutput.log". [root at shltd-s1 build]# Would you please help me, many thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From JOKVA at statoil.com Thu Aug 11 06:39:43 2016 From: JOKVA at statoil.com (=?iso-8859-1?Q?J=F8rgen_Kvalsvik?=) Date: Thu, 11 Aug 2016 06:39:43 +0000 Subject: [Opm] ERT cmake problem In-Reply-To: References: Message-ID: You need to 'cd' into the build directory: mkdir build cd build cmake ../devel ________________________________ From: Opm on behalf of XiaoYun Wang Sent: Thursday, August 11, 2016 7:36:50 AM To: opm at opm-project.org Subject: [Opm] ERT cmake problem Hi I try to install ERT.ecl in my PC, redhat 6.4 with cmake 3.6.1 After I download ert-master, mkdir build cmake ../devel there something wrong with [root at shltd-s1 build]# pwd /software/OPM/ert-master/build [root at shltd-s1 build]# cmake ../devel CMake Error at src/CMakeLists.txt:195 (set_target_properties): set_target_properties called with incorrect number of arguments. fatal: Not a git repository (or any of the parent directories): .git CMake Warning (dev) in CMakeLists.txt: No cmake_minimum_required command is present. A line of code such as cmake_minimum_required(VERSION 3.6) should be added at the top of the file. The version specified may be lower if you wish to support older CMake versions for this project. For more information run "cmake --help-policy CMP0000". This warning is for project developers. Use -Wno-dev to suppress it. -- Configuring incomplete, errors occurred! See also "/software/OPM/ert-master/devel/CMakeFiles/CMakeOutput.log". [root at shltd-s1 build]# Would you please help me, many thanks. ------------------------------------------------------------------- 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 and at poware.org Thu Aug 11 10:01:17 2016 From: and at poware.org (Andreas Lauser) Date: Thu, 11 Aug 2016 12:01:17 +0200 Subject: [Opm] ERT cmake problem In-Reply-To: References: Message-ID: <2893138.ToXbR3Cmlr@heuristix> Hi, On Thursday, August 11, 2016 06:39:43 AM Jørgen Kvalsvik wrote: > You need to 'cd' into the build directory: > > mkdir build > > cd build > > cmake ../devel the repository layout of ERT is quite weird in my opinion (in the sense that it is non-standard), and when I first tried to compile it, I also fell on my nose because of it. Question: are there objections to switch to the standard directory structure? (basically this means moving everything in the 'devel' directory to the top level of the repository.) I volunteer to do the patch. cheers Andreas > ________________________________ > From: Opm on behalf of XiaoYun Wang > Sent: Thursday, August 11, 2016 7:36:50 AM > To: opm at opm-project.org > Subject: [Opm] ERT cmake problem > > Hi > > I try to install ERT.ecl in my PC, redhat 6.4 with cmake 3.6.1 > > After I download ert-master, > > mkdir build > cmake ../devel > > there something wrong with > [root at shltd-s1 build]# pwd > /software/OPM/ert-master/build > [root at shltd-s1 build]# cmake ../devel > CMake Error at src/CMakeLists.txt:195 (set_target_properties): > set_target_properties called with incorrect number of arguments. > > > fatal: Not a git repository (or any of the parent directories): .git > CMake Warning (dev) in CMakeLists.txt: > No cmake_minimum_required command is present. A line of code such as > > cmake_minimum_required(VERSION 3.6) > > should be added at the top of the file. The version specified may be > lower if you wish to support older CMake versions for this project. For > more information run "cmake --help-policy CMP0000". > This warning is for project developers. Use -Wno-dev to suppress it. > > -- Configuring incomplete, errors occurred! > See also "/software/OPM/ert-master/devel/CMakeFiles/CMakeOutput.log". > [root at shltd-s1 build]# > > Would you please help me, many thanks. -- Measuring programming progress by lines of code is like measuring aircraft building progress by weight. -- Bill Gates -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: This is a digitally signed message part. URL: From joaho at statoil.com Thu Aug 11 10:05:27 2016 From: joaho at statoil.com (Joakim Hove) Date: Thu, 11 Aug 2016 10:05:27 +0000 Subject: [Opm] ERT cmake problem In-Reply-To: <2893138.ToXbR3Cmlr@heuristix> References: , <2893138.ToXbR3Cmlr@heuristix> Message-ID: > are there objections to switch to the standard directory structure? (basically this means moving everything in the 'devel' directory to the top level of the repository.) I volunteer to do the patch. There are no objections to this - on the contrary the patch would be welcome. What has been on my list for a long time, but never got enough priority was: 1. Move the top level CMakeLists.txt out of the devel/ directory and one level to become more standard. 2. Rename the directory devel/ to src/ ________________________________ From: Opm on behalf of Andreas Lauser Sent: Thursday, August 11, 2016 12:01:17 PM To: opm at opm-project.org Subject: Re: [Opm] ERT cmake problem Hi, On Thursday, August 11, 2016 06:39:43 AM Jørgen Kvalsvik wrote: > You need to 'cd' into the build directory: > > mkdir build > > cd build > > cmake ../devel the repository layout of ERT is quite weird in my opinion (in the sense that it is non-standard), and when I first tried to compile it, I also fell on my nose because of it. Question: are there objections to switch to the standard directory structure? (basically this means moving everything in the 'devel' directory to the top level of the repository.) I volunteer to do the patch. cheers Andreas > ________________________________ > From: Opm on behalf of XiaoYun Wang > Sent: Thursday, August 11, 2016 7:36:50 AM > To: opm at opm-project.org > Subject: [Opm] ERT cmake problem > > Hi > > I try to install ERT.ecl in my PC, redhat 6.4 with cmake 3.6.1 > > After I download ert-master, > > mkdir build > cmake ../devel > > there something wrong with > [root at shltd-s1 build]# pwd > /software/OPM/ert-master/build > [root at shltd-s1 build]# cmake ../devel > CMake Error at src/CMakeLists.txt:195 (set_target_properties): > set_target_properties called with incorrect number of arguments. > > > fatal: Not a git repository (or any of the parent directories): .git > CMake Warning (dev) in CMakeLists.txt: > No cmake_minimum_required command is present. A line of code such as > > cmake_minimum_required(VERSION 3.6) > > should be added at the top of the file. The version specified may be > lower if you wish to support older CMake versions for this project. For > more information run "cmake --help-policy CMP0000". > This warning is for project developers. Use -Wno-dev to suppress it. > > -- Configuring incomplete, errors occurred! > See also "/software/OPM/ert-master/devel/CMakeFiles/CMakeOutput.log". > [root at shltd-s1 build]# > > Would you please help me, many thanks. -- Measuring programming progress by lines of code is like measuring aircraft building progress by weight. -- Bill Gates ------------------------------------------------------------------- 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 joaho at statoil.com Mon Aug 22 10:01:29 2016 From: joaho at statoil.com (Joakim Hove) Date: Mon, 22 Aug 2016 10:01:29 +0000 Subject: [Opm] ERT repo layout changed Message-ID: Hello; after request the layout of the ert repository has changed to become more standard compliant, and in particular agree with the opm modules. After you have updated you must: 1. Wipe the build directory. 2. Invoke cmake with the updated path to the root CMakeLists.txt - i.e. without the offending devel/ directory. Joakim https://github.com/OPM/opm-common/pull/167 https://github.com/Ensembles/ert/pull/1196 ------------------------------------------------------------------- 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 Fri Aug 26 05:24:57 2016 From: yli15 at uwyo.edu (Ye Li) Date: Fri, 26 Aug 2016 05:24:57 +0000 Subject: [Opm] Where to start to learn the OPM FLOW 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. best regards, Rick -------------- next part -------------- An HTML attachment was scrubbed... URL: From Atgeirr.Rasmussen at sintef.no Fri Aug 26 07:57:16 2016 From: Atgeirr.Rasmussen at sintef.no (Atgeirr Rasmussen) Date: Fri, 26 Aug 2016 07:57:16 +0000 Subject: [Opm] Where to start to learn the OPM FLOW code ? In-Reply-To: References: Message-ID: <8EC313F7-FAB6-4719-B257-828FCBF6A6C0@sintef.no> 26. aug. 2016 kl. 07.24 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. Thanks for your kind words, and welcome to the Opm community! The code is, as you have found out, spread out over several modules. I'll try to give a brief overview of the most important parts of the simulator, and where to find the code that is used. Be aware that we are continuously refactoring and changing the code to improve performance or extensibility, or to add features. 0. Startup The actual main() function of the simulator is rather small. Most of the actual setup is done in the class FlowMain in opm-simulators. After setup, it calls the run() method of a simulator class, see the SimulatorBase class to see how it works. 1. Input There are two sources of input: the command line (or parameter file) and a simulation deck in Eclipse format. The most important is the deck, and if you don't need or want to change any of the defaults you can do with just the deck. The opm-parser module handles the deck input. The classes Parser and Deck read, parse and store the deck. In order to access the content of the deck we prefer to use the EclipseState class rather than the Deck directly, this is because the EclipseState provides the final state of important properties like pore volumes etc. If we were to use the Deck directly we would have to account for all kinds of manipulation with multipliers and BOX keywords, but the EclipseState already does all of that. (You can think of a deck as a state machine, and the EclipseState provides the final state after all manipulations.) The EclipseState also provides the Schedule class, which contains the well schedule and properties. The command line parameters are handled by the ParameterGroup class from opm-core. 2. Properties The opm-material module provides the low-level fluid properties, both saturation properties like relative permeability and capillary pressure, and pvt properties like viscosity and formation volume factors. For pvt the important class is FluidSystems::Blackoil (found in BlackoilFluidSystem.hpp), which provides the features needed (saturated and unsaturated property values for example). The Flow simulator accesses these properties through a facade class. This is in opm-simulators and is called BlackoilPropsAdFromDeck. 3. Initialization For Flow, this is done by the initStateEquil() function in opm-core. It is a rather complicated system though, and we'd like to simplify this. 4. Solving All of this is in the opm-simulators module. The basic nonlinear solver machinery is in the class NonlinearSolver, but this class leaves great freedom to the model class used (by calling its nonlinearIteration() method). The current class implementing the blackoil model is the BlackoilModel class. However, in order to support extensions to the usual model all the important stuff is actually in the BlackoilModelBase class (extensions include polymer and solvent). This class is one of the largest in OPM, but if you want to take a look at the assembly process you could read the assemble() function and see what it calls (or even better: step through it in a debugger), most of it is quite straightforward. This class uses automatic differentiation (AD) to automatically assemble the Jacobian matrices as we compute the nonlinear residual. The AD capability is provided by the AutoDiffBlock class. Finally (in each nonlinear iteration) the residual and Jacobians are passed to a customized linear solvers. The main one currently used is the class NewtonIterationBlackoilInterleaved, which structures the linear system in such a way that all unknowns associated with a cell are clustered together. 5. Output Result output is provided by the opm-output module, especially the EclipseWriter class that provides Eclipse-standard binary output of summary and restart files. This facility is being worked on quite heavily right now, with the goal of providing a very flexible output capability, which is completely configurable from the deck. Log output (to the terminal and log files) is provided by the OpmLog facility, which is implemented in the opm-common module. You will see some output to the terminal, some more to a .PRT file and if you are really curious you can look at the (hidden to avoid confusion for regular users) debug output file named .CASENAME.DEBUG — notice the period at the start of the name. I hope that gets you started. If you have any further questions, feel free to ask. Good luck! Atgeirr -------------- next part -------------- An HTML attachment was scrubbed... URL: