Tag DuMuX 2.10.0
DuMuX 2.10 is expected to run based on Dune 2.4.1, 2.5 and the Dune master. We will try to keep the compatibility with the Dune master as long as it is technically feasible and our resources allow it. If you want to use Dumux multidomain models, you have to stick with the Dune 2.4 core and specific versions of other modules, see
DuMuX 2.10 requires at least GCC 4.9 or Clang 3.5 in their C++-14 mode.
For employing corner-point grids by means of opm-grid (former dune-cornerpoint), the OPM release 2016.04 has to be used.
IMPROVEMENTS and ENHANCEMENTS:
Two new fully-implicit models have been added:
TwoPOneC. The first one admits two components water and oil that may be present in two liquid and one gaseous phase, see
test/porousmediumflow/3pwateroil/implicitfor details. The second one is dedicated to one generic component that may be present in liquid and gaseous state, see
test/porousmediumflow/2p1c/implicitfor an example.
Numbering of the VTK files starts with
Using the geostatistical tool gstat for generating random fields has been facilitated. See
test/porousmediumflow/1p/implicit. This tool can be installed using the
bin/installexternal.shscript. If cmake does not find gstat, one has to specify the GSTAT_ROOT variable, see the standard optim.opts or debug.opts.
The multidomain models should now run with all compilers without segfaults, both with optimization and debug options.
Computation for two-dimensional fracture networks in three-dimensional space has been fixed and is tested now in
binfolder containing various helper scripts has been restructured. For example, the scripts
runtest.pyare now contained in the subfolder
Two new scripts
extractpointdataovertime.pyhave been added to
bin/postprocessing. They realize what their names suggest.
The computation of the tortuosity tau with the Millington-Quirk model has been optimized. Tests show a speedup of up to 5% for a 2p2c simulation.
The fully-implicit box scheme now fully supports prism-shaped elements.
Convenience functions for reading values from a file to a container and for writing values to a file from a container have been added, see
IMMEDIATE INTERFACE CHANGES not allowing/requiring a deprecation period:
- The problem class interface needs to provide the method maxTimeStepSize().
This is important if you implement problem classes not deriving from the base
problem classes in Dumux (
- All name-related methods that previously returned / received
const char*do now use the type-safe alternative
std::string. An example is
FluidSystem::componentName(). If you need a
const char*for special operation use the string member
- The problem class interface needs to provide the method maxTimeStepSize(). This is important if you implement problem classes not deriving from the base problem classes in Dumux (
Deprecated PROPERTY and PARAMETER NAMES, to be removed after 2.10: BEWARE: The compiler will not print any warning if a deprecated property or parameter name is used. If possible, a run-time warning will appear in the summary lines after the corresponding run.
- The pure run-time parameter
tauhas been renamed to the property and run-time parameter
TauTortuosity. For the models 1p2c, 2p2c, 3p3c it got the default value 0.5.
- The pure run-time parameter
Deprecated CLASSES/FILES, to be removed after 2.10:
DiffusivityConstantTau<TypeTag, Scalar>was renamed to
DiffusivityConstant<TypeTag>and is located in a according new header. The old class, its header and the property
PointSourceHelper<TypeTag>has been deprecated. Use
Dumux::Liquid/GasPhase<Scalar, Component>have been moved to the namespace
Deprecated MEMBER FUNCTIONS, to be removed after 2.10:
checkEffectiveSaturationof the classes
concentrationGradof the class
moleFractionGradinstead, with the obviously different physical meaning.
DELETED classes/files, property names, constants/enums, member functions, which have been deprecated in DuMuX 2.9:
- Everything listed as deprecated below has been removed.