This commit moves the parseEclipseFile() function from the
upscale_relperm.cpp example to the RelPermUpscalerHelper class[%].
This, in turn, enables using the same implementation in most
relevant example utilities.
While here, also call the centralised {get,set}VoigtValue()
functions rather than local implementations.
[%] Suggested by: Arne Morten Kvarving
This commit switches function addNonStandardUpscalingKeywords() to
using a reference to a modifiable Parser rather than ParserPtr.
While here, also switch to using std::make_shared<>() when
constructing the parser object.
This means that PINCH must be used in the input deck,
whereas before, z_tolerance was available as a program
parameter (but only for some programs). A benefit is that
all programs will now uniformly accept PINCH in the input
decks.
this is currently just "RHO", an non-standard addition for
opm-upscaling and needs to be added to the Eclipse parser manually
before it is set loose on the deck file...
we need to call mpi_init when compiled against mpi (in particular mpich)
even if running with a single node.
this fixes this across all apps in a uniform way (the dune-intended approach)
The <have_boost_redef.hpp> header was introduced (commit
OPM/opm-core@82369f9) as a work-around for a particular interaction
in the Autotools-based setup of OPM-Core and the Dune core modules.
Notably, Dune's "Enable" trick for Boost failed on some older
Autoconf systems. Now that we're using CMake, however, that kluge
is no longer needed because OPM-Core always
#define HAVE_BOOST 1
i.e., as an explict true/false value.
Therefore, we need no longer include <have_boost_redef.hpp> . The
header will be removed at a later time.
The use of setPermeability did not work for upscale_perm as it did for
upscale_relperm. Deep down in ReservoirPropertyCommon it says
'use with caution', there might be something to it
