GitLab

Simon Emmert authored Mar 26, 2020 and Timo Koch committed Apr 01, 2020

Place no deprecation macros where GridView will be substituted by Grid::LeafGridView after release 3.2.

Overloading the evalFlux function for a single scvf did not have
any effect as we did not forward the call to the implementation

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

The bc types were not used anywhere and are removed from the interface.
Now they don't have to be instantiated anymore in the evalFlux_ routine which is called
by the cclocaljacobian during assembly. This commit removes this call as well.

There are a restriction of the global vector obtained
by a localView call and then bound to an element.

The global object can create an empty temporary local object that
can be bound to an element/stencil. This is closer to the
current dumux-stable implementation and still allows to switch
between global caching (for smaller problems where memory is not an issue)
and local caching (variables are precomputed for each element assemble temporarily)

Works for cc and box (in 2d). Box needs some performance improvement,
probably when creating the box geometries. But also other parts
might be possbile to optimize.

We iterate over all scvs of a fvElementGeometry like this
for (const auto& scv : scvs(fvGeometry))
This is closer to the way we speak "For each scv in all scvs of the fvElementGeometry do..."
and analogously to how we iterate over elements of a gridView.

Dennis Gläser authored Jul 05, 2016 and Timo Koch committed Nov 23, 2016

the boundary treatment is now performed after all the interior
fluxes have been calculated. This corresponds more to the previous
implementation and is assumend to be more correct for mixed BCs.

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

The volume variables caching can now be disabled in order for the
simulation to use less memory. The FVGeometry can be bound to an
element which then creates the geometries necessary for operations
on the element or the complete stencil. Several classes now need to
be friend with the model, otherwise the FVGeometry can not be bound
to the element. Maybe the bind function could return a geometry instead
of a reference, then access rights can be limited better. It would decrease
the efficiency though.

Dennis Gläser authored May 19, 2016 and Timo Koch committed Nov 23, 2016

When complex boundary handling is inactive, we only use the boundary
volume variables on pure Dirichlet boundaries. Thus, updating becomes
obsolete.