From markus at dr-blatt.de Fri Sep 15 11:44:36 2017 From: markus at dr-blatt.de (Markus Blatt) Date: Fri, 15 Sep 2017 13:44:36 +0200 Subject: [Opm] Who sets MODULE_ROOT when he/she calls CMake? Message-ID: <20170915114436.GA32583@boromir.dr-blatt.de> Hi, does anyone really pass MODULE_ROOT (OPM_CORE_ROOT, OPM_MATERIAL_ROOT, etc.) to CMake to tell it where the modules are located? Cheers, Markus -- Dr. Markus Blatt - HPC-Simulation-Software & Services http://www.dr-blatt.de Pedettistr. 38, 85072 Eichstätt, Germany, USt-Id: DE279960836 Tel.: +49 (0) 160 97590858 From Atgeirr.Rasmussen at sintef.no Fri Sep 15 12:25:17 2017 From: Atgeirr.Rasmussen at sintef.no (Atgeirr Rasmussen) Date: Fri, 15 Sep 2017 12:25:17 +0000 Subject: [Opm] Who sets MODULE_ROOT when he/she calls CMake? In-Reply-To: <20170915114436.GA32583@boromir.dr-blatt.de> References: <20170915114436.GA32583@boromir.dr-blatt.de> Message-ID: 15. sep. 2017 kl. 13.44 skrev Markus Blatt >: Hi, does anyone really pass MODULE_ROOT (OPM_CORE_ROOT, OPM_MATERIAL_ROOT, etc.) to CMake to tell it where the modules are located? I do. This is from my CMake options file (that I use by "cmake -C options.cmake " for each module). set(OPM_COMMON_ROOT "/Users/atgeirr/opm/opm-common" CACHE STRING "OPM build system") # set(DUNE_ROOT "/Users/atgeirr/dune" CACHE STRING "Dune core modules") I do not remember why I used to need Dune and now don't, and I am not 100% sure the OPM_COMMON_ROOT is necessary either, but I have not changed this setup in a long while… Do you want to remove this for some reason? I'm willing to test things and change my setup if necessary (as long as we always have something that works). Atgeirr -------------- next part -------------- An HTML attachment was scrubbed... URL: From abir at statoil.com Sat Sep 16 07:48:39 2017 From: abir at statoil.com (Alf Birger Rustad) Date: Sat, 16 Sep 2017 07:48:39 +0000 Subject: [Opm] Who sets MODULE_ROOT when he/she calls CMake? In-Reply-To: References: <20170915114436.GA32583@boromir.dr-blatt.de>, Message-ID: Personally I have never used OPM_COMMON_ROOT, so I am not sure exactly what it does. Hence, there may be some functionality here I am unaware of. With that disclaimer, is it not better to just use opm_common_DIR directly instead? It is a standard location variable (independent of OPM) with predictable behaviour well documented on the net, and for all I know achieves exactly the same. On the positive side, removing OPM_COMMON_ROOT will simplify our cmake set-up significantly, and hopefully make it more intuitive for us all. Cheers, Alf ________________________________ Fra: Opm på vegne av Atgeirr Rasmussen Sendt: 15. september 2017 14:25 Til: OPM Mailing List Emne: Re: [Opm] Who sets MODULE_ROOT when he/she calls CMake? 15. sep. 2017 kl. 13.44 skrev Markus Blatt >: Hi, does anyone really pass MODULE_ROOT (OPM_CORE_ROOT, OPM_MATERIAL_ROOT, etc.) to CMake to tell it where the modules are located? I do. This is from my CMake options file (that I use by "cmake -C options.cmake " for each module). set(OPM_COMMON_ROOT "/Users/atgeirr/opm/opm-common" CACHE STRING "OPM build system") # set(DUNE_ROOT "/Users/atgeirr/dune" CACHE STRING "Dune core modules") I do not remember why I used to need Dune and now don't, and I am not 100% sure the OPM_COMMON_ROOT is necessary either, but I have not changed this setup in a long while… Do you want to remove this for some reason? I'm willing to test things and change my setup if necessary (as long as we always have something that works). Atgeirr ------------------------------------------------------------------- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorized 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 Atgeirr.Rasmussen at sintef.no Fri Sep 22 09:21:07 2017 From: Atgeirr.Rasmussen at sintef.no (Atgeirr Rasmussen) Date: Fri, 22 Sep 2017 09:21:07 +0000 Subject: [Opm] Refactoring of EclipseState and Schedule Message-ID: <353FC17D-F65C-4507-993B-51FA588DC63F@sintef.no> Dear OPM community, In order to better support using Flow as a component, and gain some "scriptability", we propose to refactor the relationship between the EclipseState and Schedule classes of opm-parser. Currently the EclipseState owns the Schedule. We propose to make the Schedule class independent in the sense that it will not be owned by an EclipseState instance, although constructing it would still require an EclipseState object. This means that some methods in downstream modules will gain an additional (Schedule) parameter, for some methods a Schedule parameter will replace an existing EclipseState parameter. The end result is that it will be possible for third party developers to easily create programs that manipulate the schedule before passing it to the simulator component, such as for example NTNU's FieldOpt program. Joakim and Atgeirr From dogbe at aust.edu.ng Fri Sep 22 14:43:16 2017 From: dogbe at aust.edu.ng (David Ogbe) Date: Fri, 22 Sep 2017 15:43:16 +0100 Subject: [Opm] Compositional simulation with OPM flow Message-ID: Is it possible to run compositional model with OPM flow? Is yes, can it import an eclipse e300 deck? What is the procedure documented to use this compositional module? -------------- next part -------------- An HTML attachment was scrubbed... URL: From kelvin.loh at tno.nl Fri Sep 22 14:47:36 2017 From: kelvin.loh at tno.nl (Loh, K.K.L. (Kelvin)) Date: Fri, 22 Sep 2017 14:47:36 +0000 Subject: [Opm] Compositional simulation with OPM flow In-Reply-To: References: Message-ID: Hi David, AFAIK, the compositional model is available via the ewoms models. Not sure if flow already has them. From: Opm [mailto:opm-bounces at opm-project.org] On Behalf Of David Ogbe Sent: Friday, September 22, 2017 4:43 PM To: Opm at opm-project.org Subject: [Opm] Compositional simulation with OPM flow Is it possible to run compositional model with OPM flow? Is yes, can it import an eclipse e300 deck? What is the procedure documented to use this compositional module? This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Arne.Morten.Kvarving at sintef.no Wed Sep 27 06:36:01 2017 From: Arne.Morten.Kvarving at sintef.no (Arne Morten Kvarving) Date: Wed, 27 Sep 2017 06:36:01 +0000 Subject: [Opm] nightly ubuntu packages Message-ID: hi, nightly packages for ubuntu xenial is now operational. note that they temporarily run against my fork of libecl while waiting for my PRs to be processed. install the apt repo using 1) install key: wget http://opm-project.org/package/nightly-xenial/repokey.gpg | sudo apt-key add - 2) add repo sudo apt-add-repository http://opm-project.org/package/nightly-xenial/ 3) sudo apt-get update 4) apt-cache show libopm-simulators1-bin the repo contains the nightly build for the last seven days, the last four sundays and the first of the last five months. obviously not that populated yet, but that's the scheme. in case you do not know how to operate apt when there are several versions of a package and you want to choose a particular one, i point you to https://github.com/OPM/opm-utilities/blob/master/docker_opm_user/Dockerfile#L42 [https://avatars3.githubusercontent.com/u/1827197?v=4&s=400] OPM/opm-utilities github.com opm-utilities - A collection of utilities of interest to the opm community here opm_version is a date, e.g. 2017-09-25 sadly you have to specify for all packages, not just the top one, as apt tries to pull the newest ofupstreams, and that naturally lead to errors. arnem -------------- next part -------------- An HTML attachment was scrubbed... URL: From Arne.Morten.Kvarving at sintef.no Fri Sep 29 08:25:01 2017 From: Arne.Morten.Kvarving at sintef.no (Arne Morten Kvarving) Date: Fri, 29 Sep 2017 08:25:01 +0000 Subject: [Opm] CI system downtime Message-ID: hi, at 16:00 CET today i will take down jenkins and to do a debian distribution update. depending on how grumpy mr murphy is, it will be down anywhere from 3h to 3 days. hopefully closer to the first. arnem -------------- next part -------------- An HTML attachment was scrubbed... URL: From Arne.Morten.Kvarving at sintef.no Fri Sep 29 22:14:10 2017 From: Arne.Morten.Kvarving at sintef.no (Arne Morten Kvarving) Date: Fri, 29 Sep 2017 22:14:10 +0000 Subject: [Opm] CI system downtime In-Reply-To: References: Message-ID: murphy was surprisingly kind. ci systems now run on debian 9.1, most noteworthy changes are - jenkins 1.651 -> 2.73.1 - gcc 4.9.2 -> 6.3 - boost 1.55 -> 1.62 - openmpi 1.8 -> 2.0 - cmake 3.6.1 -> 3.7.2 - dune 2.4.1 -> 2.5.0. this is a little unfortunate since 2.4.1 is considered the minimum version and we do not get to test things. so i might have to do a backport here. plus obviously a bunch of other updates, but these should be user-facing ones. happy to report that there is not a lot of fallout. - there was some trivial build errors in ResInsight (PR submitted). - some issues in opm-upscaling and opm-simulators wrt umfpack which i took the liberty to take care of directly - an issue in opm-upscaling where gcc6 didn't like implicit casts (taken care of) - opm-grid's 'grid' test fails, likely due to dune-grid 2.5. - autodiffmatrix test in opm-simulators fails - some regression test fails in opm-simulators. fairly certain these are harmless, will investigate tmrw i have not tested the PR builders so that could be where murphy decided to bite. we will know soon enough i guess, but weekend here i come! arnem ________________________________ Fra: Opm på vegne av Arne Morten Kvarving Sendt: 29. september 2017 10:25:01 Til: opm at opm-project.org Emne: [Opm] CI system downtime hi, at 16:00 CET today i will take down jenkins and to do a debian distribution update. depending on how grumpy mr murphy is, it will be down anywhere from 3h to 3 days. hopefully closer to the first. arnem -------------- next part -------------- An HTML attachment was scrubbed... URL: