Hi, On Tuesday, March 15, 2016 08:47:52 AM Alf Birger Rustad wrote: > Today, writing results is a performance bottleneck flow.
as far as I can see, there is not much which can be done on that front if you continue to insist on using ECL compatible files for output of parallel simulations. (these are inherently sequential file formats and thus the only way to accelerate writing them is to accelerate the sequential code.) cheers Andreas > ________________________________ > From: Opm [[email protected]] on behalf of Joakim Hove > [[email protected]] Sent: Monday, March 14, 2016 6:54 PM > To: [email protected] > 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 -- Another way to put it: a team full of hammers will go around looking for nails. A team that’s a whole toolbox might figure out what really needs doing. -- Havoc Pennington
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Opm mailing list [email protected] http://opm-project.org/cgi-bin/mailman/listinfo/opm
