Implement a grid manager class that creates grids and a grid data object. The new class
is no longer a singleton. It is instantiated by the user. It is possible to get a
shared_ptr to the grid data to pass it on to e.g. problem / spatial parameter classes.

* No longer sets the overlap automatically (overlap to be checked by the grid geometry)
* Does not depend on discretization method or TypeTag anymore

Joint work with Kilian Weishaupt <kilian.weishaupt@iws.uni-stuttgart.de>

Improve harmonic mean to have less divisions

See merge request !1038

Melanie Lipp authored 6 years ago and Melanie Lipp committed 6 years ago

Change harmonic mean to a formulation which is more consistent with the old one (without weighting factors). One advantage of this formulation is that there are less divisions necessary.

[liquidphase2c] fluid system is not miscible

See merge request !1035

Fix/gridcreator gmsh parameters

See merge request !185

Bernd Flemisch authored 6 years ago and Timo Koch committed 6 years ago

The distribution of a grid over several cores can be system-dependent,
rendering the direct comparison of resulting parallel vtk files
impossible. To enable a comparison, convert the parallel files into
sequential ones in the fuzzycompare Python script. With this approach,
it is possible to compare the parallel output against the sequential
one. Adapt the gridcreator tests correspondingly.

Concerning the converted vtk files, a few difficulties had to be
handled:
* The files usually have duplicated vertices at the process borders.
  Eliminate the duplicated entries.

* The files can have an empty `PointData` section yielding to problems
  since the number of children differs. Eliminate the empty section
  from the files.

* The attributes may be different for each node: the
  `NumberOfComponents` isn't stated explicity if it is equal to `1`.
  On the other hand, the minimum and maximum values are provided
  which is not the case for the original vtk output. Eliminate the
  check of the attributes if a conversion from pvd has happened.

Enhance the gridcreator tests using boundary markers with an
additional synchronization step for those markers in the parallel
regime.

Bernd Flemisch authored 6 years ago and Timo Koch committed 6 years ago

Make the tests more flexible by passing a bool to refine or not.
Don't refine in the case of the ALUGrid 3d test, since apparently
the boundary parametrization isn't handled correctly during
refinement. Adapt the reference solutions.

Bernd Flemisch authored 6 years ago and Timo Koch committed 6 years ago

Only one marker per entity is communicated.

Bernd Flemisch authored 6 years ago and Timo Koch committed 6 years ago

Realize boundary marker load balancing for ALUGrid. To achieve this, adapt
the data handle such that also the boundary markers are balanced. Since
the data handle works on faces rather than intersections, transfer first
the vector that is given in terms of boundary segments to a vector holding
a parameter value for each mesh face. After balancing, transfer the data
back to a boundary segment vector.

Restructure the tests and add more tests. Both UG and ALU are now tested
for Gmsh 2/3d and DGF 2d. The ALU tests for Gmsh 3d still need to be
worked on.

Bernd Flemisch authored 6 years ago and Timo Koch committed 6 years ago

Use a special data handle for load balancing a UGGrid that has been
read with the GmshReader. Hopefully an intermediate solution that can be
combined with the already existing data handle.

Gmsh data for Alugrid and ug needs to be manually loadbalances. Sadly, ug
doesn't implement parameter load balancing for elements at the moment (only vertices).
It might be possbile to have all parameters on all processes.

Use always level 0 entities. This is for user convenience. The data was always
only available for level 0. Now the gridcreator also checks this and if not we take
the level 0 father instead to evaluate the parameter - more robust.

This test should also work in parallel now and a parallel test is added

We now get the parameter using the insertion index because that's the index
used by the factory in the gmsh reader. This also fixes how UG and ALU handle
reading gmsh files differently in parallel again.

Unfortunately the gmsh reader doesn't provide any load balancing features for the
parameters so that they might not always work in parallel

We now get the parameter using the insertion index because that's the index
used by the factory in the gmsh reader. This also fixes how UG and ALU handle
reading gmsh files differently in parallel again.

Unfortunately the gmsh reader doesn't provide any load balancing features for the
parameters so that they might not always work in parallel?

Fix/lowrekepsilon

See merge request !1031

Cleanup/component co2

Closes #489

See merge request !1034

[components][simpleco2] remove simpleco2 as it is not used anywhere and can be replaced by C02.hh when the correct table is used

Freeflow/kepsilon improvements

See merge request !1029