From JOKVA at statoil.com Thu Jun 1 13:36:38 2017 From: JOKVA at statoil.com (=?iso-8859-1?Q?J=F8rgen_Kvalsvik?=) Date: Thu, 1 Jun 2017 13:36:38 +0000 Subject: [Opm] opm-parser makefile redesign Message-ID: Hi, opm-parser #1065 https://github.com/OPM/opm-parser/pull/1065 was just merged, which restructures the opm-parser makefiles and layout a little bit. More importantly, this makes opm-parser *completely* independent from opm-common, and uses that opportunity to use some modern(ish) cmake features, be more straight forward and robust, and obey more cmake default options. The required cmake version is now >= 2.8.12 (which ships with Ubuntu 14.04), and opm-parser is mainly intended to be found in Config mode. The Findopm-parser module in opm-common now first attempts that, before falling back to the old find logic. Please note that to better separate public and private headers, the old root/opm/parser layout has been deprecated, and directories overall have been flattened. If you're a consumer of opm-parser you hopefully shouldn't notice much of a difference, but there might be some friction if you have a semi-outdated build environment. If you have any issues, please file them on github, and we'll see what we can do. - The opm team at Statoil. ------------------------------------------------------------------- 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 joaho at statoil.com Fri Jun 2 15:10:29 2017 From: joaho at statoil.com (Joakim Hove) Date: Fri, 2 Jun 2017 15:10:29 +0000 Subject: [Opm] Build of opm-parser is broken with Boost in non-standard location. Message-ID: Since yesterday afternoon the build in opm-parser has been broken for developers who have Boost installed in a non-standard location. We have looked into for several hours this afternoon, but not yet succeeded - I therefor fear the master branch of opm-parser will remain broken over the weekend. Very sorry for the inconvenience. Joakim ------------------------------------------------------------------- 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 Tue Jun 13 07:39:56 2017 From: Atgeirr.Rasmussen at sintef.no (Atgeirr Rasmussen) Date: Tue, 13 Jun 2017 07:39:56 +0000 Subject: [Opm] Invitation to participate in a survey, MSO4SC Message-ID: <7F6BCB83-755C-4D4C-9718-3CA0198183EB@sintef.no> Dear OPM community, I am posting this on behalf of the MSO4SC project, in which we are participating, as seen in the recent news item on the OPM web page, http://opm-project.org/?p=897 Atgeirr Flø Rasmussen, SINTEF Digital +++++++++++++++++++++++++++++++++++++++ Dear Sir or Madam, Let me introduce to you MSO4SC, which is a Horizon 2020 (European Research program) project. MSO4SC is short for „Mathematical Modeling, Simulation and Optimization for Societal Challenges with Scientific Computing“. The objective to build an e-infrastructure that supports both MSO application development and HPC performance for the developed application. It will solve the conflict between fast prototyping and scalability of the resulting applications by providing a platform to support a cloud-like deployment, explicitly recognizing the HPC and big-data demands of the applications. Visit www.mso4sc.eu for further information. You can have your say in shaping the e-infrastructure by telling us about your experience, plans and/or obstacles regarding MSO-software. You will find our survey, which will take approx. 15 minutes, at https://docs.google.com/forms/d/e/1FAIpQLSeOTIIplgtMeuT-iJ2dWh_ujAXDPX64goSg0wXKeGlRWZgYEg/viewform?usp=sf_link We thank you for your time and appreciate further input and comments. Visit www.mso4sc.eu and contact F. Javier Nieto (francisco.nieto at atos.net), Zoltan Horvath (horvathz at math.sze.hu) or Esther Klann (klann at tu-berlin.de). Best regards, the MSO4SC team -------------- next part -------------- An HTML attachment was scrubbed... URL: From joakira at stud.ntnu.no Tue Jun 27 18:02:15 2017 From: joakira at stud.ntnu.no (Joakim R. Andersen) Date: Tue, 27 Jun 2017 15:02:15 -0300 Subject: [Opm] API for flow Message-ID: Hi. I am wondering if there exists an API for flow which lets you use flow as a library and not only as a program with an input file (e.g. flow_ebos norne.data). Best regards, Joakim R. Andersen -------------- next part -------------- An HTML attachment was scrubbed... URL: From abir at statoil.com Wed Jun 28 07:32:55 2017 From: abir at statoil.com (Alf Birger Rustad) Date: Wed, 28 Jun 2017 07:32:55 +0000 Subject: [Opm] API for flow In-Reply-To: References: Message-ID: Hi Joakim, There is currently no library, we have basically viewed ourselves as downstream. Still, the code that makes up the application flow is modular. We have gone through great lengths to make the various parts reusable, so to what extent you can use it for your tasks really depends on your needs. Best, Alf ________________________________ Fra: Opm på vegne av Joakim R. Andersen Sendt: 27. juni 2017 20:02 Til: opm at opm-project.org Emne: [Opm] API for flow Hi. I am wondering if there exists an API for flow which lets you use flow as a library and not only as a program with an input file (e.g. flow_ebos norne.data). Best regards, Joakim R. Andersen ------------------------------------------------------------------- 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 Wed Jun 28 07:56:19 2017 From: Atgeirr.Rasmussen at sintef.no (Atgeirr Rasmussen) Date: Wed, 28 Jun 2017 07:56:19 +0000 Subject: [Opm] API for flow In-Reply-To: References: Message-ID: <03C4247D-5118-4FA1-81AB-1A7E47BAAFAA@sintef.no> 28. jun. 2017 kl. 09.32 skrev Alf Birger Rustad >: Hi Joakim, There is currently no library, we have basically viewed ourselves as downstream. Still, the code that makes up the application flow is modular. We have gone through great lengths to make the various parts reusable, so to what extent you can use it for your tasks really depends on your needs. To customize the simulator code currently you may have to go somewhat deep into it. It is not necessarily hard, but it can be difficult to find the right place to modify. If you would like to share a little about what you want to accomplish, we could point you in the right direction! In the long term, I'd like to see a higher-level API that is well-suited to scripting, but we do not have that at the moment. Atgeirr -------------- next part -------------- An HTML attachment was scrubbed... URL: From joaho at statoil.com Wed Jun 28 11:46:34 2017 From: joaho at statoil.com (Joakim Hove) Date: Wed, 28 Jun 2017 11:46:34 +0000 Subject: [Opm] New version of libecl required Message-ID: Hello; I intend to merge: https://github.com/Statoil/libecl/pull/129 on friday. When that is merged you must have libecl updated to at least include: https://github.com/Statoil/libecl/pull/129 Joakim ------------------------------------------------------------------- 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 joaho at statoil.com Wed Jun 28 11:47:42 2017 From: joaho at statoil.com (Joakim Hove) Date: Wed, 28 Jun 2017 11:47:42 +0000 Subject: [Opm] New version of libecl required In-Reply-To: References: Message-ID: Ehh sorry - corrected message: Hello; I intend to merge: https://github.com/OPM/opm-output/pull/197 on friday. When that is merged you must have libecl updated to at least include: https://github.com/Statoil/libecl/pull/129 Joakim ------------------------------------------------------------------- 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 Wed Jun 28 12:05:33 2017 From: Atgeirr.Rasmussen at sintef.no (Atgeirr Rasmussen) Date: Wed, 28 Jun 2017 12:05:33 +0000 Subject: [Opm] Invitation to OPM meeting in Bergen Message-ID: <8CC19F10-40AB-42D0-8F23-E724B836238F@sintef.no> Dear OPM community, This year we plan to organize an OPM meeting in mid-October in Bergen. Preliminary dates are Wednesday 18th to Thursday 19th of October. Please feel free to suggest alternative dates if these doesn't fit. We will send out more information on program and venue in August. Do you have something you want to present to the community or topics for discussion? Please contact Tor Harald Sandve, tor.harald.sandve at iris.no. We hope to see many of you there! Tor Harald Sandve Atgeirr Flø Rasmussen -------------- next part -------------- An HTML attachment was scrubbed... URL: From joakira at stud.ntnu.no Wed Jun 28 13:36:38 2017 From: joakira at stud.ntnu.no (Joakim R. Andersen) Date: Wed, 28 Jun 2017 10:36:38 -0300 Subject: [Opm] API for flow In-Reply-To: <03C4247D-5118-4FA1-81AB-1A7E47BAAFAA@sintef.no> References: <03C4247D-5118-4FA1-81AB-1A7E47BAAFAA@sintef.no> Message-ID: Dear Atgeirr and Alf, Thanks for your quick response. If you are familiar with MRST I would like to have access to a function similar to runScheduleADI. Further, if possible I would like to have access or to build adjoint variables for the simulation, however I'm aware that this last functionality is not implemented yet. At the moment I would like to implement an interface to the fully-implicit simulators that given the initial states of the reservoir (pressure, saturations, rs, rv) provides the intermediate states for all the actual simulated timesteps (not only report steps) together with their Jacobians at convergence. In addition to that, I will need to build the Jacobians of the implicit steps with respect to the initial conditions and well controls settings to implement gradient-based optimization methods. I am not sure if these are readily available and not interfaced or if I have to figure out how to build them. - Joakim 2017-06-28 4:56 GMT-03:00 Atgeirr Rasmussen : > > 28. jun. 2017 kl. 09.32 skrev Alf Birger Rustad : > > Hi Joakim, > > There is currently no library, we have basically viewed ourselves as > downstream. Still, the code that makes up the application flow is modular. > We have gone through great lengths to make the various parts reusable, so > to what extent you can use it for your tasks really depends on your needs. > > > To customize the simulator code currently you may have to go somewhat deep > into it. It is not necessarily hard, but it can be difficult to find the > right place to modify. If you would like to share a little about what you > want to accomplish, we could point you in the right direction! In the long > term, I'd like to see a higher-level API that is well-suited to scripting, > but we do not have that at the moment. > > Atgeirr > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Atgeirr.Rasmussen at sintef.no Wed Jun 28 14:16:35 2017 From: Atgeirr.Rasmussen at sintef.no (Atgeirr Rasmussen) Date: Wed, 28 Jun 2017 14:16:35 +0000 Subject: [Opm] API for flow In-Reply-To: References: <03C4247D-5118-4FA1-81AB-1A7E47BAAFAA@sintef.no> Message-ID: <55CD23AB-95F7-4A42-80A9-D1465022A3E8@sintef.no> Hi Joakim, There is no function like runScheduleADI(). Adjoints are not yet supported, but we have committed to adding such support. Perhaps we should have a short video meeting to discuss these things? If so, please send me an off-list email (anyone else who would like to join the discussion is welcome, please email me). Atgeirr 28. jun. 2017 kl. 15.36 skrev Joakim R. Andersen >: Dear Atgeirr and Alf, Thanks for your quick response. If you are familiar with MRST I would like to have access to a function similar to runScheduleADI. Further, if possible I would like to have access or to build adjoint variables for the simulation, however I'm aware that this last functionality is not implemented yet. At the moment I would like to implement an interface to the fully-implicit simulators that given the initial states of the reservoir (pressure, saturations, rs, rv) provides the intermediate states for all the actual simulated timesteps (not only report steps) together with their Jacobians at convergence. In addition to that, I will need to build the Jacobians of the implicit steps with respect to the initial conditions and well controls settings to implement gradient-based optimization methods. I am not sure if these are readily available and not interfaced or if I have to figure out how to build them. - Joakim 2017-06-28 4:56 GMT-03:00 Atgeirr Rasmussen >: 28. jun. 2017 kl. 09.32 skrev Alf Birger Rustad >: Hi Joakim, There is currently no library, we have basically viewed ourselves as downstream. Still, the code that makes up the application flow is modular. We have gone through great lengths to make the various parts reusable, so to what extent you can use it for your tasks really depends on your needs. To customize the simulator code currently you may have to go somewhat deep into it. It is not necessarily hard, but it can be difficult to find the right place to modify. If you would like to share a little about what you want to accomplish, we could point you in the right direction! In the long term, I'd like to see a higher-level API that is well-suited to scripting, but we do not have that at the moment. Atgeirr -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus at dr-blatt.de Thu Jun 29 07:07:20 2017 From: markus at dr-blatt.de (Markus Blatt) Date: Thu, 29 Jun 2017 09:07:20 +0200 Subject: [Opm] New version of libecl required In-Reply-To: References: Message-ID: <20170629070720.GC9356@boromir.dr-blatt.de> Hi, Thanks for the heads up. I guess updating earlier is not a problem? 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 tobk at dtu.dk Fri Jun 30 10:34:59 2017 From: tobk at dtu.dk (Tobias Kasper Skovborg Ritschel) Date: Fri, 30 Jun 2017 10:34:59 +0000 Subject: [Opm] Dunecontrol and OPM Message-ID: Hi I'm trying to create a dune module which uses OPM functionality from opm-parser. Relevant dune models, opm-common and opm-parser are installed globally (/usr/local/lib) from source. The duneproject script is able to detect the opm-common and opm-parser modules. I'm trying to build my code with the dunecontrol script, but I can see that -Dopm-common_DIR=/usr/local while the correct path would be /usr/local/lib/dunecontrol/opm-common and similarly for opm-parser. I have attached the error messages from the dunecontrol script in err.txt. Can you help me figure out what to modify in order to be able to compile my project with dunecontrol? Best regards Tobias Ritschel Tobias Kasper Skovborg Ritschel PhD student DTU Compute Technical University of Denmark Department of Applied Mathematics and Computer Science Asmussens Allé Building 303B 2800 Kgs. Lyngby Denmark Direct +45 45255203 tobk at dtu.dk www2.compute.dtu.dk/~tobk -------------- next part -------------- An HTML attachment was scrubbed... URL: