GitLab

They are needed for analytic assembly

Correct handling of gravitational flux contributions requires the
mpfa framework to be completely re-designed.

we now have the following levels of type tags:

- basic numerical model
- linear solver type tag
- discretization scheme-specific type tag
- physics-related type tag (e.g. pmflow)
- problem-specific type tag

TODO: implement ficks and fouriers law, as well as the interaction volume data handles
accordingly for problems involving diffusion/heat conduction

Dennis Gläser authored Feb 10, 2017 and Timo Koch committed Feb 17, 2017

[mpfa][interiorboundarydata] fix previous erroneous commit of handing in element to facetVolVars() method

Dennis Gläser authored Feb 07, 2017 and Timo Koch committed Feb 17, 2017

we do not incorporate the handling of lower dimensional elements on the facets
in the base laws etc anymore. We want to overload functionalities required to
realize the coupling in the mixeddimension-specific classes. The upwind scheme
is still to be modified!

The flux variables cache now inherits from caches defined in the different laws.
These also define a respective filler class that is called when updating the flux
variables caches. That enables us to define different caches for different laws.

Fix the flux stencil for every method independent of the stencils used
in the different flux laws. The matrix entries have to be reserved for all
possible occuring stencils if the method has parameter or solution dependent
stencils, otherwise the matrix needs to be rebuild every time. This implements
this unified flux stencil for box, cc, ccmpfa.
Remove a lot of duplicate code.
Separate the physical laws from the dicretization stencil.

Dennis Gläser authored Dec 15, 2016 and Timo Koch committed Dec 16, 2016

The laws now have a static const public variable stating which
discretization method they belong to. That makes it possible to use
the TPFA darcys law implementation in an mpfa context by changing the
MolecularDiffusionType property.

For non-zero neumann boundary conditions we did a scaling to recover
DgradU at the boundary from the prescribed flux. We don't do this anymore
and assume that when the UseTpfaBoundary property is set to false, that the
user provides -DgradU at the boundary instead of, e.g., mass fluxes.

Dennis Gläser authored Oct 12, 2016 and Timo Koch committed Nov 23, 2016

The treatment of mixed BC is questionable for cc methods. Not allowing
for it enables us to not have to store n interaction volume seeds at the boundary.