Sign in


DuMux is short for "DUNE for Multi-{Phase, Component, Scale, Physics, …} flow and transport in porous media". It is an open-source simulator and research code in modern C++. It provides a framework for the implementation and application of porous media model concepts and constitutive relations.

Get started
16508 commits | Last commit 11 hours ago

What DuMux can do for you

What is DuMux?

DuMux is a simulation framework with a focus on finite volume discretization methods, model coupling for multi-physics applications, and flow and transport applications in porous media.

DuMux is based on the DUNE framework from which it uses the versatile grid interface, vector and matrix types, geometry and local basis functions, and linear solvers. DuMux then provides

  • Finite volume discretizations (Tpfa, Mpfa, Staggered) and control-volume finite element discretization schemes
  • A flexible system matrix assembler and approximation of the Jacobian matrix by numeric differentation
  • A customizable Newton method implementation including line search and various stopping criteria
  • Many preimplemented models (Darcy-scale porous media flow, Navier-Stokes, Geomechanics, Pore network models, Shallow water equations) and constitutive models
  • A multi-domain framework for model coupling suited to couple subproblems with different discretizations/domains/physics/dimensions/... and create monolithic solvers

DuMux has been applied to model complex and non-linear phenomena, such as CO2 sequestration, soil remediation, reactive transport and precipitaion phenomena, drug delivery in cancer therapy, flow in micro-fluidics, root-soil interaction, flow in fractured porous media, atmosphere-soil flow interaction, evaporation and more. Please have a look at our journal publications for a more detailed description of the goals the development history and motivations behind DuMux.

Project Status: Active – The project has reached a stable, usable state and is being actively developed.


The following resources are useful to get started with DuMux:

Some helpful code snippets are available in the Wiki.

Automated testing of installation: installation testing pipeline


REUSE status

DuMux is licensed under the terms and conditions of the GNU General Public License (GPL) version 3 or - at your option - any later version. The GPL can be read online or in the file provided in the topmost directory of the DuMux source code tree.

Please note that DuMux' license, unlike DUNE's, does not feature a template exception to the GNU General Public License. This means that you must publish any source code which uses any of the DuMux header files if you want to redistribute your program to third parties. If this is unacceptable to you, please contact us for a commercial license.

See the file for copying permissions. For a curated list of contributors see If you notice that a contributor is missing on the list, please contact us or open a merge request adding the name.

Automated Testing / Test suite

  • Latest release (3.8): release build badge
  • Master branch (development / unstable): master build badge

DuMux features many tests (some unit tests and test problems) that are continuously and automatically tested in the GitLab-CI framework (see badges). The test suite is based on CTest and can also be built and run manually

make -j8 build_tests && ctest -j8

The tests are labelled (see CMakeLists.txt of each individual test for its labels). You can build and run tests of a specific label (e.g. 2p for two-phase flow porous medium model tests) like this

make -j8 build_2p_tests && ctest -j8 -L ^2p$

Running individual tests

To find out how to build a test inspect the CMakeLists.txt file in the respective test folder.

The dumux_add_test command specifies some important parameters: NAME sets the name of the test. There is either SOURCES or TARGET specified. If SOURCES is specified NAME, corresponds to the build target, otherwise TARGET is the build target.

You can build the test by running make REPLACE_BY_NAME_OF_BUILD_TARGET (when using GNU Makefiles (default) this is possible within the test folder in the build directory, for ninja it has to be executed in the top-most build folder level).

Some tests may depend on additional optional dependencies. You can find this by inspecting the argument CMAKE_GUARD, e.g. HAVE_UMFPACK means UMFPack is required (via installing Suitesparse), or ( "dune-foamgrid_FOUND" AND "dune-alugrid_FOUND" ) means that the test requires the additional Dune modules dune-foamgrid and dune-alugrid. For installing external dependencies, have a look at the documentation and the script dumux/bin/

Test coverage

coverage report

A weekly coverage report of the test suite is created by gcovr/gcov. The report currently doesn't include non-instantiated code, so the real coverage is likely lower. However, only a few lines of code are never instantiated in the comprehensive test suite.


Contributions are highly welcome. Please ask questions over the mailing list. Please review the contribution guidelines before opening issues and merge requests.

Bug/issue reports or vulnerabilities

For bug reports or to report any detected security vulnerabilities contact us over the mailing list, or file an issue. For bug fixes, feature implementations open a merge request or send us formatted patches.

Releases and backwards compatibility policy

For a detailed description of the backwards compatibility policy, please see contribution guidelines.

DuMux releases are split into major (e.g. 2.0, 3.0) and minor (e.g. 3.1, 3.2, 3.3) releases. Major releases are not required to maintain backwards compatibility (see below), but would provide a detailed guide on how to update dependent modules. For each minor release, maintaining backwards compatibility is strongly encouraged and recommended.

Despite the goal of maintaining backwards compatibility across minor releases, for more complicated changes, this is decided upon on a case to case basis, due to limited developer resources. In the case that implementing full backwards compatibility for an update is not feasible, or would require unreasonable resources, the degree of backwards compatibility be decided by a vote in one of the monthly core developer meetings.

Logo of DuMux
Programming languages
  • C++ 93%
  • CMake 3%
  • Hack 2%
  • Python 2%
  • C 0%
  • GPL-3.0-or-later
</>Source code

Participating organisations

University of Stuttgart


Bernd Flemisch