Hi,
I think we have set up (but not activated) Flyspray on
opm-project.orghttp://opm-project.org. I am reluctant to start using it, since
I feel that github's issue system so far has been reasonably usable. I agree
that it is more geared towards bugs than features, but I think that can be
… in opm-core, opm-polymer, dune-cornerpoint, opm-porsol and opm-upscaling.
The actual tag is release/2013.03/rc2 (even though only opm-core had an rc1
tag).
We'll now make available binary packages as they are built. When they are
tested, we'll tag everything with release/2013.03/final (which
Den 23. aug. 2013 kl. 12:06 skrev Andreas Lauser:
[...]
(for example, a Newton solver not converging is not an exceptional thing).
That's a thing I see quite differently. The reason is that there are about a
million things which could go wrong that make the newton solver diverge. If
any and all
Den 26. aug. 2013 kl. 17:20 skrev Andreas Lauser:
Hi All,
On Monday 26 August 2013 14:20:18 Atgeirr Rasmussen wrote:
Den 23. aug. 2013 kl. 12:06 skrev Andreas Lauser:
[...]
(for example, a Newton solver not converging is not an exceptional thing).
That's a thing I see quite differently
Dear OPM community!
We are now in September, and since we have planned to do a 2013.09 release, we
should agree on how to do it. The following are some suggestions.
1. Each maintainer (as given on
http://www.opm-project.org/wiki/index.php/Main_Page near the bottom) is
responsible for
Thank you, Roland!
It will be a great help for the other maintainers.
Atgeirr
Den 24. sep. 2013 kl. 00:49 skrev Roland Kaufmann:
On 2013-09-23 03:12, Arne Morten Kvarving wrote:
@rolk can push [build system changes] directly, once they have been
reviewed and merged elsewhere
But I
Dear OPM community,
We are now tagging the module repositories that are part of the upcoming opm
release.
The tag is release/2013.10/rc2.
We expect that a release will be made fully available and announced on the
website in the near future,
unless there are unexpected regressions or other
Dear OPM community,
Release candidate binary packages for Ubuntu 12.04 are now available.
Please see the news item on
http://opm-project.org
for a list of modules and some information on how to install or upgrade.
We would appreciate any testing and feedback concerning these packages,
Welcome to the community Yuhe, and thank you for taking the effort to introduce
yourself.
I would also be interested in knowing what you are working on, and what you are
interested in.
Feel free to ask questions to the mailing list and post issues on github, we
will try to answer you
as well
Hi,
As long as a function is declared with a C link interface by using extern it
can be called from C.
It can be implemented in C++, but then of course must be compiled by a C++
compiler, and
have a C++ extension such as .cpp.
Atgeirr
21. feb. 2014 kl. 14:09 skrev Markus Blatt
Hi Markus!
Your observation is correct. The normals in the UnstructuredGrid are required
to have length equal to the
area of the corresponding face (see the Doxygen doc for UnstructuredGrid).
The reason for this is compatibility with MRST, which has the same convention.
In particular some of
Dear Liu Ming,
It is good to hear that your work has progressed. We very much appreciate your
contribution to OPM, and I will take a look at your pull request for the
implicit two-phase simulator shortly.
Regarding your polymer simulator, I am ok with making opm-polymer require
opm-autodiff,
11. mars 2014 kl. 12:02 skrev Markus Blatt mar...@dr-blatt.de:
Hi,
I guess this place is still wrong for the parallel case and I am
currently struggeling to fix it.
On Fri, Jan 24, 2014 at 11:58:18AM +, Atgeirr Rasmussen wrote:
See the docs for the field face_cells. For a face f
11. mars 2014 kl. 13:10 skrev Markus Blatt mar...@dr-blatt.de:
On Tue, Mar 11, 2014 at 11:25:07AM +, Atgeirr Rasmussen wrote:
11. mars 2014 kl. 12:02 skrev Markus Blatt mar...@dr-blatt.de:
CpGrid: [a] - UnstruncturedGrid [a, -1] as you say.
But [~a] - [-1, a] instead (letting
Thank you for this utility, it really helped me debug the summary output!
Atgeirr
27. mars 2014 kl. 18:05 skrev Joakim Hove jo...@statoil.com:
I have added a section on the Wiki about viewing ECLIPSE summary files.
Hi Markus,
I guess you could try to delete some of the keywords that create trouble, if
they are unneeded and not too many.
If this applies to a large amount of keywords I'd be surprised.
I'll follow this up in a private mail to you.
Atgeirr
28. mars 2014 kl. 09:08 skrev Markus Blatt
Dear OPM community,
Last year we had two OPM releases, 2013.03 and 2013.10. At the time, I and
others expected that the next opm release would be 2014.04. However, April is
here, and we have not started the release process. With easter holidays
approaching for some of us, I doubt we can make a
Hello James,
Thank you for your interest in OPM!
Gentoo: I do not know anyone working on OPM with this distro. We provide
packages for Ubuntu and some other distros, but not Gentoo. The OPM developers
use a quite wide variety of systems, though: Ubuntu, RHEL, Suse, Mac OS X at
least, so
Thank you Roland!
I am not sure what these things require though: are they stand-alone scripts
that only need virtualbox, or are they using a something like vagrant?
Atgeirr
11. aug. 2014 kl. 08:49 skrev Roland Kaufmann roland.kaufm...@uni.no:
Due to the recent release of RHEL7 as well as
27. aug. 2014 kl. 10:03 skrev robert.kloefk...@iris.no:
Hi all,
The first is what has been the main focus for the black-oil simulator,
the second was made to enable parallel MPI simulations with Dune
solvers. The two codes have been diverging lately (some code for
transmissibility
28. okt. 2014 kl. 12:14 skrev Jørgen Kvalsvik jorge...@stud.ntnu.no:
Hi,
I am a student at NTNU http://www.ntnu.no/, and my pre-master project is
modularizing OPM by implementing (at least trying to) support for using more
linear solvers. There is some code available, see the
Hi everyone!
First, on the original topic of this thread: I think the new repo is fine, it
may be a useful alternative to consider placing such things in a utilities/
directory on opm-core instead to reduce the number of repositories though.
Second, about gentoo, development platforms etc.:
Hi!
We have now started a process to make a new OPM release. Our last release was
in October 2013, which is a very long time ago!
At some point it was decided to postpone the release, waiting for the fully
implicit black-oil simulator (which now is named Flow) to mature.
While that allowed us
Thank you very much for this, it will make it easier to catch mistakes before
they are merged rather than after!
Atgeirr
14. apr. 2015 kl. 08:10 skrev Christine Fløysand ch...@statoil.com:
Hi!
A Jenkins job for building and running tests for multiple pull requests are
now available on the
Thank you very much, Arne Morten!
I will be testing these on Ubuntu 14.04 (trusty). I would appreciate it if
someone could test the 12.04 (precise) packages as well.
At this point we consider 10.04 too old to support, it would have required
significant extra work to pacakge for it.
Atgeirr
Hi!
We have not yet implemented the adjoint method in OPM.
We do indeed use Automatic Differentiation (AD) which should make it
relatively easy (compared to without AD) to implement adjoints. If you'd
implement this I would certainly be interested!
It should also be noted that if you have access
Subject line so it is more specific
than Re: Contents of Opm digest...
Today's Topics:
1. Derivatives from solvers in opm-autodiff (Tobias Ritschel)
2. Re: Derivatives from solvers in opm-autodiff (Atgeirr Rasmussen
20. mai 2015 kl. 12:06 skrev Tobias Ritschel tobiasritsc...@gmail.com:
These sound like just the solvers and preconditioners that I need. Does this
also mean that flow is able to run in parallel?
No, it is not. But a variant (flow_cp) is, however it is still in heavy
development and
21. mai 2015 kl. 10:25 skrev Tobias Ritschel tobiasritsc...@gmail.com:
Thanks for the great feedback. I will proceed with the DUNE solvers and I
might compare to the Eigen solvers for a simple setup.
I also considered PETSc as I use TAO (part of PETSc) to carry out
optimization, though I
21. mai 2015 kl. 09:58 skrev Joakim Hove jo...@statoil.com:
Hello;
thank you for your input.
What, specifically, do you mean by remove sibling build feature?
With that I mean that when searching for opm libraries and header files the
build system will not use heuristics to look in
I use a similar setup as Bård, and I am also reluctant to abandon the so-called
sibling builds.
Having heard that various meta-project will solve the same, I am willing to try
them out, what
should I be using instead?
My main concerns are that:
- it must not be too hard to make a developer's
Dear OPM community,
We have been considering how to best refactor the (huge) class
FullyImplicitBlackoilSolver
in such a manner that it can be more easily be extended with new options and
functionality
without copying the whole class (as is currently done to implement the
flow_polymer variant
22. mai 2015 kl. 13:46 skrev Joakim Hove jo...@statoil.com:
Could code generation be a third alternative?
You could think of templates as a form of structured code generation happening
inside
the C++ language. I think we want to keep this inside C++, since we are not
talking
about 100s of
Dear OPM community,
There are now binary packages available for testing the 2015.10 OPM release.
The major features of this release are:
* Significantly improved performance for Flow, the fully implicit black-oil
reservoir simulator.
* An experimental black-oil + solvent simulator
Dear OPM community,
We have two major news items today!
1. Our new website is available.
Found at the same address as before (opm-project.org), we hope that the new
site will
serve the community well, and provide all the information you need. For the
moment,
we are still in a transitional
Dear OPM community,
There are now updated (rc2) binary packages available for testing the 2015.10
OPM release.
The information posted in the first round (quoted below) is still valid (no
feature changes since rc1).
Atgeirr Flø Rasmussen
28. okt. 2015 kl. 09:06 skrev Atgeirr Rasmussen
Dear OPM community,
Many of us feel that our current module/repository structure is a little
confusing and should be improved.
For example, from the name, one would expect that opm-core would be the single
module on which all
others depend, but that is not the case.
We should move forward one
28. aug. 2015 kl. 11.34 skrev Roland Kaufmann roland.kaufm...@uni.no:
On 28. Aug. 2015 at 11:10, Atgeirr Rasmussen wrote:
I propose the following small change to start off: rename opm-cmake
to opm-common. ... It will grow (primarily by moving code there from
other modules)
One question
28. aug. 2015 kl. 11.46 skrev Roland Kaufmann roland.kaufm...@uni.no:
On 28. aug. 2015 at 11.34, Roland Kaufmann wrote:
One question: Are you moving the HEAD version of the files, or the
entire history?
On 28. Aug. 2015 at 11:42, Atgeirr Rasmussen wrote:
I imagine that we would
Dear OPM community,
As announced earlier, we have now renamed the opm-cmake repository to
opm-common. This is the first step of renaming.
It only changes the *location* of the repo, not the *module name* as referred
to in the other modules.
You can change the location of the remote repo in
Dear OPM community,
We have now completed the second step of renaming opm-cmake -> opm-common.
Now the module name is changed throughout the build system.
1. If you have not already done so, you should now rename your github fork (if
you have one) of opm-common
from opm-cmake to opm-common.
2.
> 3. des. 2015 kl. 13.33 skrev Atgeirr Rasmussen <atgeirr.rasmus...@sintef.no>:
>
> If no-one objects I intend to do the reorganization early next week.
This has now been done, and all contents of opm-polymer is now in opm-autodiff.
Special thanks to Arne Morten Kvarving who man
Congratulations Jørgen! And thanks for sharing with us.
Atgeirr
___
Opm mailing list
Opm@opm-project.org
http://opm-project.org/cgi-bin/mailman/listinfo/opm
Dear OPM community,
Yesterday a new version of Dune was released (2.4.1) and I had some problems
compiling OPM after updating.
However, the fix is simple: delete your build directories (for opm modules
depending on Dune modules, which are
almost all opm modules except opm-common and opm-parser)
The repository has now been renamed on github. The old URL will still work for
a long time (half a year I think) so no-one need to do anything right now.
The next step is creating PRs with the required changes. This is underway.
Atgeirr
___
Opm
Dear OPM community,
We have now completed renaming dune-cornerpoint -> opm-grid. Now the module
name is changed throughout the system.
1. If you have not already done so, you should now rename your github fork (if
you have one) from dune-cornerpoint to opm-grid.
2. You should rename your
Hi,
As Arne Morten said, the prerequisites must be in place before you build OPM.
However the build order part of the page you refer to was outdated after our
recent
reorganization efforts. I have updated this to show the correct order.
Atgeirr
8. apr. 2016 kl. 00.07 skrev Ibrahem Atef
Dear OPM community,
We would like to invite you to participate in the 2016 OPM Meeting on June 1-2
in Oslo! We hope to welcome anybody who
wants to come, please contact Atgeirr Flø Rasmussen or Tor
Harald Sandve
if you want to join. Please tell us
Dear OPM community,
The program for the OPM meeting is ready, and can be viewed at
http://opm-project.org/?p=664
Please direct any questions to me or Tor Harald Sandve.
Atgeirr
___
Opm mailing list
Opm@opm-project.org
Dear OPM community,
A new release is soon due, and I must ask all contributors who wants a feature
to be included
in the release to submit their pull requests, or at the very least, tell us
about it!
We hope to have the release ready by the end of the month. The release will be
coordinated by
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.
The perfRates() vector contains *reservoir volume* total rates at the
perforations, while the perfPhaseRates() vector contain
*surface volume* rates per phase. So it is not a direct sum.
Atgeirr
26. sep. 2016 kl. 14.10 skrev Jørgen Kvalsvik
>:
Hi,
Hi Bernd,
This is not something we have given very much attention. Basically our
assumption has been
that ensuring the releases are solid is enough. However, as maturity increases
in general,
and people come to rely on the code we should do something more about this.
The only place such
Dear OPM community,
We are pleased to announce the availability of OPM release 2016.10!
This is the second release this year, the previous release was 2016.04. The
next release
is expected to be 2017.04.
The release brings major improvements to the output capabilities of Flow, the
fully
Dear OPM community,
A release candidate is ready for testing. There are binary packages available
for 64-bit Ubuntu 14.04, Ubuntu 16.04 and RHEL 6.
For those building from source, the relevant branch is called release/2016.10
in each repository. There is a single change to the
module structure
Markus,
Thank you for taking the initiative on this, and my apologies for not replying
sooner!
I think the abstract is good, and I'll of course contribute to the content of
the poster.
Best,
Atgeirr
___
Opm mailing list
Opm@opm-project.org
Hi again,
The problem has been identified, and fixed in opm-simulators#987:
https://github.com/OPM/opm-simulators/pull/987
If you are building from source, it should be sufficient to pull/update from
github and recompile.
Thanks to André for fixing!
Atgeirr
> 22. des. 2016 kl. 22.39 skrev Markus Blatt :
>
> Hi,
>
> and here comes the first Christmas present:
>
> The poster has already been accepted.
Great!
A merry Christmas to you all!
Atgeirr
___
Opm mailing list
Dear OPM community,
A new tutorial has been made available, explaining how to run the Norne
benchmark case with Flow:
http://opm-project.org/?page_id=780
If you have feedback on the tutorial, in particular if there are errors or
unclear parts, please tell us!
Atgeirr Flø Rasmussen
Hi Bob,
I can reproduce your error (with SPE1CASE2.DATA). Interestingly the
region-based report looks correct:
Field:
===
:
Dear OPM community,
I thought I should let you know that we have just changed the default output
directory for the Flow family of simulators.
Instead of by default writing to the current directory, it now writes to the
directory containing the data deck. If you have scripts depending on this
Hello Andres!
I checked-out on 63b7cf6febf3f41e59b8803c06994e12a550c46a (which is earlier
than the one above), and continued with a successful installation.
Good to hear!
I realized that you are pushing new commits every few hours to the master
branch of all the opm-modules. I guess these
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
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
<atgeirr.rasm
Dear Kang,
If you follow the instructions for Mac OS X on this page:
http://opm-project.org/?page_id=239
you should be able to build with MPI, although it has not been tested with the
latest version of macOS. However, you will then only get a very basic
partitioning scheme. To get a good
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
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
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
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
Dear OPM community,
A reference manual has been created for OPM Flow, the fully implicit reservoir
simulator program. The manual describes the structure and keywords of the input
deck format, how to run Flow, and its command line parameters. We hope that it
will be useful!
The manual can be
https://www.scandichotels.no/hotell/norge/bergen/scandic-ornen
Please send an email to
tor.harald.san...@iris.no<mailto:tor.harald.san...@iris.no> for a registration
code. Unfortunately you will have to pay for your stay at the hotel yourself.
Kind regards
Atgeirr Rasmussen and Tor H
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
This invitation was posted earlier this summer, I am repeating it as some may
not have had the time or
Hi all,
I am afraid that tutorial needs to be updated.
About updating the tutorial: the "python-ert.ecl" should be replaced with
"python-ecl", that has been changed on the website.
Are there other changes that need to be done to make it work? Artyom, I think
your errors look a little like
Dear OPM community,
We have created an update for the 2017.10 release. It fixes a few bugs in Flow
that could affect simulation results slightly and also lead to very bad
performance when running Flow in parallel using MPI. The effect was most
pronounced when running with more than 4 MPI
Dear OPM community,
Binary packages for redhat are now available with mpi support using openmpi.
They are built according to redhat standards, i.e., there are separate packages
with the mpi support.
To install the serial 'flow', you do as usual: "yum install opm-simulators-bin".
To install the
Dear Mr. Salem,
Thanks for bringing this to our attention. I have updated the repository at
Dockerhub, and it should now be possible to refer to the "2018.04" version
explicitly, also the "latest" tag now points to that version.
Atgeirr
Frå: Opm på vegne
Hello,
Thanks for the tutorial Carl Fredrik, I linked to it from the installation page
on opm-project.org, I hope that is OK!
Atgeirr
Frå: Opm på vegne av c berg
Sendt: tysdag 29. mai 2018 19:42
Til: Arne Morten Kvarving; opm@opm-project.org
Emne: Re:
Hi Rodrigo,
Thanks for your kind words!
The problem you describe looks interesting, and I hope that we can help you
towards a solution.
First I must admit that I have very limited experience with solving eigenvalue
problems numerically
(I have not done that in 20 years…) which limits how
Dear OPM community,
As part of ongoing work to simplify and reorganize the module structure, the
opm-core module has now been removed. Most of the classes and functions have
been moved to opm-simulators, with a few exceptions.
Build instructions have been updated.
Atgeirr
Hi,
I have tried to reproduce your problem with a clean Ubuntu 16.04 VM, but all
installation steps succeed for me. Unfortunately, I do not know the packaging
system well enough to know what could possibly go wrong. You will therefore
probably have to wait until after New Year before we can
Dear Mr. Abdelmoumen,
I recommend that you try running OPM Flow on HPC systems using the Singularity
container system. You should ask your HPC maintainer if Singularity is
supported. If not, Docker containers are also available, but will probably not
be able to exploit the special hardware
delmoumen-bacetti-01a46b138/> &
Researchgate<https://www.researchgate.net/profile/Abdelmoumen_Bacetti2>
On Fri, Apr 13, 2018 at 8:24 AM, Atgeirr Rasmussen
<atgeirr.rasmus...@sintef.no<mailto:atgeirr.rasmus...@sintef.no>> wrote:
Dear Mr. Abdelmoumen,
I recommend that you try r
Hi Manoel,
I am not aware of any such software that is free or open source, unfortunately.
Atgeirr
Frå: Opm på vegne av Manoel Farias
Sendt: fredag 19. oktober 2018 21:10
Til: opm@opm-project.org
Emne: [Opm] Multiphase flow Tables App
Hi,
Does anybody know
Hi Alan,
TNO has also implemented Fetkovich aquifers. I am not aware of any
further plans regarding numerical or analytical aquifers, perhaps somebody
from TNO (Wessel, Rohith, Frank or Kelvin) can comment on this?
Atgeirr
Frå: Opm på vegne av Alan King
___
Opm mailing list
Opm@opm-project.org
https://opm-project.org/cgi-bin/mailman/listinfo/opm
Hello Andy,
I am not aware of anyone using OPM Flow on unconventional fields, but for all I
know there could be someone using it for that.
What features do you think would be the most important for such usage?
Atgeirr
Frå: Opm på vegne av Andrei Austin
Hi,
I just run the provided deck (but without the "extra line" in GCONINJE) to see
if I could reproduce your problem,
but I am not sure what to look for. What are the pressure values you expect for
the (0.9, 1.0, 1.1) cases?
In any case, I get different behaviour from the simulator from
Dear all,
In preparation for the upcoming 2019.10 release, the module "ewoms" has been
renamed "opm-models". The repository on github has been renamed, but the old
name will continue to work for some time.
Atgeirr
___
Opm mailing list
Hello Patricia,
Did you successfully install an Ubuntu VM? Verify by starting the VM (using
"vagrant ssh" if you used vagrant to create it) and running the "uname -a"
command, on my computer I get the output
Linux ubuntu-cosmic 4.18.0-17-generic #18-Ubuntu SMP Wed Mar 13 14:34:40 UTC
2019
Hi Ogi,
The application "ecl_summary" is from the libecl library, which is no longer a
prerequisite for OPM Flow (since the latest release). You can still install
libecl and get the application, or use the new "summary" application suggested
by Torbjørn.
Atgeirr
The web site was stating that 18.10 was supported with binary packages, which
is not true for the latest release for the reason stated by Arne Morten. The
information on the web site has been corrected. I am sorry for any confusion
this caused!
Atgeirr
Frå:
Hi all,
I agree that we should do this (unless other disadvantages come to light).
I'd say that the loss of Ubuntu 18.04 LTS as a supported target is less of
a problem than it appears, since that version provides a faulty MPI
implementation so we cannot provide MPI packages for it anyway.
Are
Hi!
I support increasing the Dune dependency to 2.6.
With a minimum GCC version of 8.3 we can adopt C++17 and drop several boost
libraries, but not yet all.
Atgeirr
Frå: Opm på vegne av Alf Birger Rustad
Sendt: tysdag 28. januar 2020 09:13
Til:
Despite what I initially wrote (that I want to increase the requirements), if
we turn away potential users by this, that would be a good reason to NOT bump
the requirements.
Arne Morten's message implies that we can still provide binary packages for new
releases (i.e. 2020.04 and 2020.10 etc.)
Dear OPM community,
At the recent OPM meeting, it was decided to require newer versions of some
libraries and compilers for building OPM Flow going forward. The new
requirements are:
- C++ compiler with C++17 support (gcc minimum version 7).
- Dune version 2.6 or newer.
These requirements
Hi Yogi,
Lots of things have changed in Flow for the initialization in parallel
recently. Could you try to check out the previous release (2019.10) and check
if you see the same problems?
Atgeirr
Frå: Opm på vegne av Markus Blatt
Sendt: onsdag 11. mars 2020
Dear all,
I would just say thank you to Joakim for his effort in managing the release!
Atgeirr
___
Opm mailing list
Opm@opm-project.org
https://opm-project.org/cgi-bin/mailman/listinfo/opm
Alf,
My initial thoughts on the issues you raise are:
1. (Post-processor compatibility.) A new format could be implemented in both
OPM Flow and Resinsight, making it useful rather quickly.
2. (Write only at end of run.) I assume this can be resolved by wasting a
little space: initially
Hi Antoine!
Our partitioning scheme starts with the whole graph on a single process, so
indeed this would be a "bad" starting partition. The partitioning we end up
with does not seem any worse though, although for very large process counts,
this could become a bottleneck.
I am a little
Hi Antoine,
For OPM Flow, the computational mesh is always generated based on the DATA
file. We support both simple cartesian grids as you have observed, and more
complex corner-point grids. There is a very brief explanation on page 277 of
the OPM Flow reference manual (2020.04 version). (See
1 - 100 of 120 matches
Mail list logo