Merge branch 'update-uggridfactory-documentation' into 'master'

ref:core/dune-grid The return value of createGrid should nowadays be captured
by a std::unique_ptr or std::shared_ptr.

See merge request [!344]

  [!344]: gitlab.dune-project.org/core/dune-grid/merge_requests/344

The return value of createGrid should nowadays be captured
by a std::unique_ptr or std::shared_ptr.

Merge branch 'uggrid-heapSize-Wundefined-var-template' into 'master'

ref:core/dune-grid Closes: [#91]

WIP:

-   [x] Manually verify in job trace the warning is gone (the remaining
    instances of the same error seem Alberta-related)

See merge request [!343]

  [#91]: gitlab.dune-project.org/NoneNone/issues/91
  [!343]: gitlab.dune-project.org/core/dune-grid/merge_requests/343


Closes #91

Closes: #91

Merge branch 'santiago.ospina/dune-grid-feature/change-type-of-volume-method-to-typedef' into 'master'

ref:core/dune-grid This is a rebased version of [!305] \-\-- I seem unable to
rebase that one in situ.

See merge request [!342]

  [!305]: gitlab.dune-project.org/NoneNone/merge_requests/305
  [!342]: gitlab.dune-project.org/core/dune-grid/merge_requests/342

Test User authored 6 years ago and Oliver Sander committed 5 years ago

Previously this was 'ctype', but grids may care about proper
dimensions.  In that case, a volume is not the same as a
coordinate, and a separate type for volumes is necessary.

The interface class does not hard-wire any type but rather exports
the type used by the Geometry implementation class.  That type
is determined by introspection, there is no need to adapt
downstream grid implementations.

Merge branch 'fix/gcc-9-warnings' into 'master'

ref:core/dune-grid Indicated by GCC 9's -Wpessimizing-move

See merge request [!341]

  [!341]: gitlab.dune-project.org/core/dune-grid/merge_requests/341

Indicated by GCC 9's -Wpessimizing-move

Merge branch 'issue/alberta_backuprestore_warning' into 'master'

ref:core/dune-grid

### Summary

Remove the usage of writeGridXdr and readGridXdr in AlbertaGrid since is
produces a deprecated warning.

### Details

The functions writeGridXdr and readGridXdr were simplified to writeGrid and
readGrid some time ago, but used in the backup-restore facilities of the
AlbertaGrid. This emits a deprecated warning all the time. This MR, replaces
the old functions with the new ones.

See merge request [!338]

  [!338]: gitlab.dune-project.org/core/dune-grid/merge_requests/338

Merge branch 'issue/geometrygrid_backuprestore_coordfunction' into 'master'

ref:core/dune-grid

### Summary

Changes GeometryGrid capabilities to be true for hasBackupRestoreFacilities
only if the CoordFunction is default constructible

### Details

Instantiating the BackupRestoreFacilities::restore for
`GeometryGrid<HostGrid, CoordFunction>` with a CoordFunction that is not
default constructible leads to an error. This is in contrast to the capability
hasBackupRestoreFacilities that returns true for this grid.

This MR updates the capabilities to be false if the CoordsFunction is not
default constructible and adds a tag-dispatching with a runtime-error in case
someone instantiates the BackupRestoreFacilities with such a CoordsFunction
nevertheless.

So, the BackupRestoreFacilities can be instantiated without a compile-time
error and one can use the hasBackupRestoreFacilities for a compile-time check
whether this should work or not.

### See Also

Some discussions about how to restore a non-default-constructible
CoordFunction can be found in [!339]

See merge request [!340]

  [!339]: gitlab.dune-project.org/NoneNone/merge_requests/339
  [!340]: gitlab.dune-project.org/core/dune-grid/merge_requests/340

changed geometrygrid capabilities to be true for backup-restore only if coordfunction is default constructible

Merge branch 'use-No_Comm-tag-for-CollectiveCommunication' into 'master'

ref:core/dune-grid Using No_Comm means there is just one dummy communication
type instead of different types for different grids.

See merge request [!337]

  [!337]: gitlab.dune-project.org/core/dune-grid/merge_requests/337

Using `No_Comm` means there is just one dummy communication type
instead of different types for different grids.

Merge branch 'do-not-use-cubetopology' into 'master'

ref:core/dune-grid The new GeometryTypes interface is much nicer.

See merge request [!336]

  [!336]: gitlab.dune-project.org/core/dune-grid/merge_requests/336

The new GeometryTypes interface is much nicer.

Merge branch 'fix-typos' into 'master'

See merge request [!335]

  [!335]: Nonecore/dune-grid/merge_requests/335

Merge branch 'feature/yaspgrid-avoid-unused-variable' into 'master'

ref:core/dune-grid Whatever the mysterious meaning of the mysteryFactor is,
it's only used in the `#if HAVE_MPI` branch. Hence we should move it there to
avoid unused variable warnings.

See merge request [!330]

  [!330]: gitlab.dune-project.org/core/dune-grid/merge_requests/330

Merge branch 'fix-warnings' into 'master'

ref:core/dune-grid silences a compiler warning
\[-Winconsistent-missing-override\]

See merge request [!331]

  [!331]: gitlab.dune-project.org/core/dune-grid/merge_requests/331

silences a compiler warning [-Winconsistent-missing-override]

Merge branch 'document-vtk-writing-of-functions' into 'master'

ref:core/dune-grid

-   Describe object life-times of the method arguments
-   Mention in the change log that globally defined functions can now be
    written

See merge request [!329]

  [!329]: gitlab.dune-project.org/core/dune-grid/merge_requests/329

Whatever the mysterious meaning of the `mysteryFactor` is,
it's only used in the `#if HAVE_MPI` branch. Hence we should
move it there to avoid unused variable warnings.

Merge branch 'feature/distributed-boundary-segments' into 'master'

ref:core/dune-grid This MR implements a missing feature in the grid interface,
the possibility to distribute boundary segments during load balancing. This
create a problem, because grid readers such as GmshReader only read grid on
rank 0, and thus boundary segments only exist on that rank. So far there was
not possibility to re-distribute these segments leading to false boundary
projections in parallel computations. This MR implements this by providing a
BoundarySegmentBackupRestore class that allows to re-create a boundary segment
from a stringstream (char buffer). This requires the registry of a static
function that can restore the correct object from the stream. The factory is
necessary because of the type erasure when passing pointers of BoundarySegment
to the GridFactory. This also means a slight interface change for GmshReader.
The methods of GmshReader, such as GmshReader::read have to be called on all
ranks, because the correct BoundarySegment factory methods have to be
registered on all cores. As before reading is only done on core 0 which
already was checked in GmshReader before. The other implementation concerns
the DGF::ProjectionBlock where the boundary projections are now also
distributable.

Testing has been done with a corresponding branch on dune-alugrid.

See merge request [!325]

  [!325]: gitlab.dune-project.org/core/dune-grid/merge_requests/325

* Describe object life-times of the method arguments
* Mention in the change log that globally defined functions
  can now be written

Merge branch 'feature/implement-vtk-writing-of-c++-functions' into 'master'

ref:core/dune-grid Previously, only grid functions were supported.

See merge request [!327]

  [!327]: gitlab.dune-project.org/core/dune-grid/merge_requests/327

This namespace is almost empty and not used anywhere.
I think it ended up in the code by accident.

Previously, only grid functions were supported.

boundary segment objects. Also, restore returns unique_ptr instead of
raw pointer.

store class name for checking upon restore.

GmshReaderQuadraticBoundarySegment default implementation.

restore.

ProjectionBlock.

const Expression* to shared_ptr< Expression > to avoid memory leaks.

missing.