1. 17 May, 2019 2 commits
  2. 04 Apr, 2019 1 commit
    • Carsten Gräser's avatar
      [!330] Avoid unused variable warning without MPI · 0500649f
      Carsten Gräser authored
      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
      0500649f
  3. 03 Apr, 2019 2 commits
  4. 29 Mar, 2019 1 commit
  5. 26 Mar, 2019 1 commit
  6. 25 Mar, 2019 1 commit
    • Robert K's avatar
      [!325] Distributed boundary segments. · 8fe069ca
      Robert K authored
      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
      8fe069ca
  7. 22 Mar, 2019 1 commit
  8. 19 Mar, 2019 1 commit
  9. 18 Mar, 2019 2 commits
  10. 19 Feb, 2019 1 commit
  11. 18 Feb, 2019 12 commits
  12. 12 Feb, 2019 2 commits
  13. 11 Feb, 2019 2 commits
  14. 21 Jan, 2019 2 commits
  15. 07 Dec, 2018 1 commit
  16. 06 Dec, 2018 2 commits
  17. 04 Dec, 2018 1 commit
  18. 03 Dec, 2018 1 commit
    • Jö Fahlke's avatar
      [!315] Feature/vtk variable output precision · a5cf355a
      Jö Fahlke authored
      Merge branch 'feature/vtk-variable-output-precision' into 'master'
      
      ref:core/dune-grid
      
      -   Allow to write every field and the coordinated in a custom precision
      -   Allow VTKFunctions to state precision other than float
      -   Allow user to pass precision via the simple addVertex/CellData interfaces
      -   Enable passing the precision via the field info into vtk writer
      -   Enable changing precision of the coordinate output
      -   Add an enum class Precision that determines with which precision a field
          should be written to VTK file, int32 (std::int32_t), uint8 (std::uint8_t),
          uint32 (std::uint32_t), float32 (float), float64 (double)
      -   Add helper function that converts a precision to a VTK field type string
      -   Add helper function that converts a precision to the byte size
      -   Decouples VTK types from C++ types
      -   Use fixed size C++ integer types to make sure we always have a format
          conforming VTK file
      
      I measured runtimes for outputs with a single field + coords for 1000 to 10Mio
      cells, by running 10 consecutive writes in a loop measuring with Dune::Timer,
      and I couldn't detect any performance penalty.
      
      ToDos:
      
      -   \[x\] Add entry to changelog
      
      See merge request [!315]
      
        [!315]: gitlab.dune-project.org/core/dune-grid/merge_requests/315
      a5cf355a
  19. 27 Nov, 2018 4 commits