[Opm] New opm-repo

[Alf Birger Rustad]

Thanks for the announcement! There is one issue that I hope everybody with informed opinions can contribute to. Today, writing results is a performance bottleneck flow. Hence, we should find a way for flow to write results asynchronously, i.e., the simulator should not need to wait computing the next timestep while the results are written. It has been suggested to split out the writing in a separate process to accomplish this, but I am not sure how this could be done in a good way. Implementing the writer as a server seems like over-engineering, and we probably do not want to mandate MPI to run the simulator. The simplest option I can think of is splitting the writing to a new thread with openmp.

Your thoughts are welcome!
Alf

________________________________
From: Opm [opm-bounces at opm-project.org] on behalf of Joakim Hove [joakim.hove at gmail.com]
Sent: Monday, March 14, 2016 6:54 PM
To: opm at opm-project.org
Subject: [Opm] New opm-repo

Hello;

we have just created a new repository: opm-output: https://github.com/OPM/opm-output - the new repository should contain routines for generating output from opm simulators. Currently there is zero actual code in the repository, but the necessary (absolute) minimum cmake support is in there already.

With this PR: https://github.com/OPM/opm-common/pull/86 opm-autodiff will depend on the new repository. I encourage you all to fork, clone and "build" the opm-output repo asap; then I guess we will merge build system change actually creating a dependency in a couple of days?


The initial plan is to move the outputwriter code from opm-core, and then take it from there.


Joakim




-------------------------------------------------------------------
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: <//opm-project.org/pipermail/opm/attachments/20160315/b45a53bb/attachment.html>