This reverts commit 4f25d438.

Merge branch 'feature/better-subdomain-handling' into 'master'

See merge request [dominic/dune-perftool!268]

  [dominic/dune-perftool!268]: Nonedominic/dune-perftool/merge_requests/268

Merge branch 'feature/lambda-generation-with-more-geometry' into 'master'

Target: normal-dependent constraints assembly.

See merge request [dominic/dune-perftool!267]

  [dominic/dune-perftool!267]: gitlab.dune-project.org/dominic/dune-perftool/merge_requests/267

Merge branch 'feature/fix-constraints-assembly-bug' into 'master'

We previously used bool() on the constraints expression to find out whether we
need to use the DIrichletConstraintsAssembler. However, UFL does the stupid
thing of evaulating

`bool(eq(x[0], 0))`

to False, because x[0] and 0 are obvioulsy not the same. Veeeery bad behaviour
for a symbolic language.

See merge request [dominic/dune-perftool!266]

  [dominic/dune-perftool!266]: gitlab.dune-project.org/dominic/dune-perftool/merge_requests/266

We previously used bool() on the constraints expression to find
out whether we need to use the DIrichletConstraintsAssembler.
However, UFL does the stupid thing of evaulating

bool(eq(x[0], 0))

to False, because x[0] and 0 are obvioulsy not the same. Veeeery
bad behaviour for a symbolic language.

Merge branch 'feature/small-fix-for-conditional' into 'master'

See merge request [dominic/dune-perftool!265]

  [dominic/dune-perftool!265]: Nonedominic/dune-perftool/merge_requests/265

Merge branch 'feature/costmodel-validation' into 'master'

The MR adds a new vectorization strategy target, which tries to find a
vectorization strategy whose cost (according to the model strategy) is as
close as possible to a given target. This allows to run several executables
and plot the cost model value against performance data. The actual plotting
work is done in dune-perftool-paperplots. The feature is very niche, and I
tried to minimize the occurence of code paths only necessary for this, but I
think the outcome is quite okay.

See merge request [dominic/dune-perftool!262]

  [dominic/dune-perftool!262]: gitlab.dune-project.org/dominic/dune-perftool/merge_requests/262

We do this from multiple subdirs

Merge branch 'feature/guard-grid-analysis' into 'master'

consistent-grid-orientation is merely a suggestion. dune-perftool should
perfectly build in its absence.

See merge request [dominic/dune-perftool!261]

  [dominic/dune-perftool!261]: gitlab.dune-project.org/dominic/dune-perftool/merge_requests/261

consistent-grid-orientation is merely a suggestion. dune-perftool
should perfectly build in its absence.

Merge branch 'bugfix/add-tensor' into 'master'

See merge request [dominic/dune-perftool!259]

  [dominic/dune-perftool!259]: Nonedominic/dune-perftool/merge_requests/259

Merge branch 'feature/sum-factorization-on-unstructered-grids' into 'master'

Make it possible to use sum factorization on unstructured grids. The main
problem are the skeleton terms. We need to make sure that we go through the
quadrature points in the same order on the two neighboring cells and that (the
jacobian of) the geometry function is applied correctly. Instead of looking at
all possible embeddings of the face and further increasing the variation we
make sure that the grid is made edge consistent. See
consistent-edge-orientation module and the paper 'On Orienting Edges of
Unstructured Two- and Three-Dimensional Meshes':

-   <https://gitlab.dune-project.org/marcel.koch/consistent-edge-orientation>
-   <https://dl.acm.org/citation.cfm?doid=3071076.3061708>

This merge request does the following:

-   make grid edge consistent
-   use sum factorization to evaluate the geometry mappings (and jacobians) of
    the cells
-   totally avoid using the geometry mapping of the interesection

Still missing:

-   Reordering of directions for 3D at intersections. This needs to be
    adjusted to make sure that we go thgrough quadrature points on self and
    neighbor in the same order. For this it would be good to have a 3D grid
    with consistent edge orientation that shows that this is necessary.
-   Vetorization is not yet implemented for GeoCornersInput. We might also
    need to adjust quadrature point vectorization.

See merge request [dominic/dune-perftool!258]

  [dominic/dune-perftool!258]: gitlab.dune-project.org/dominic/dune-perftool/merge_requests/258