1. 07 Dec, 2018 1 commit
  2. 06 Dec, 2018 2 commits
  3. 04 Dec, 2018 1 commit
  4. 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
  5. 27 Nov, 2018 5 commits
  6. 26 Nov, 2018 3 commits
  7. 25 Nov, 2018 5 commits
    • Timo Koch's avatar
      d0486276
    • Timo Koch's avatar
      [vtk] Add optional precision interface to VTKFunction · d50daa0e
      Timo Koch authored
      * Allow VTKFunctions to state precision other than float
      * Allow user to pass precision via the simple addVertex/CellData
      interfaces
      d50daa0e
    • Timo Koch's avatar
      [vtk] Enable variable precision in VTK output · d660048b
      Timo Koch authored
      * Enable the data array writer to write four specific types
        int, unsigned int, float, double in the right precision.
      
      * Enable passing the precision via the field info into vtk writer
      
      * Enable changing precision of the coordinate output
      
      * The DataArrayWriter seems to be less generic now because it only
        works for 4 types, however it is actually more versatile now
        because the type doesn't have to be fixed at compile time which
        allows to write each field with individual precision provided by
        the user. The type cannot be determined at compile time as the
        passed in functions are type-erased.
      d660048b
    • Timo Koch's avatar
      [vtk] Add precision field to VTK::FieldInfo · 648a19c6
      Timo Koch authored
      648a19c6
    • Timo Koch's avatar
      [vtk] Add enum class for variable output precision · 96592808
      Timo Koch authored
      * Add an enum class Precision that determines with which
        precision a field should be written to VTK file,
        int32 (int), uint32 (unsigned int), float32 (float), float64 (double)
      
      * Add precision types that were previously in use
      
      * Add helper function that converts a precision to a VTK field type
      string
      
      * Add helper function that converts a precision to the byte size
      96592808
  8. 20 Nov, 2018 3 commits
  9. 14 Nov, 2018 5 commits
  10. 08 Nov, 2018 2 commits
    • Steffen Müthing's avatar
      [!300] Make UG message buffer work with aligned types · 26e75d93
      Steffen Müthing authored
      Merge branch 'bug/ug-messagebuffer-fails-for-aligned-types' into 'master'
      
      ref:core/dune-grid We stumbled over a problem when trying to communicate
      dense, fixed-size Eigen matrices:
      
      The UG message buffer calls the copy assignment operator on all communicated
      data to copy it into its internal void* buffer. This can fail for types that
      assume alignment during copy operations, as there are no alignment guarantees
      on the internal buffer.
      
      The implementation only works for POD types anyway (as their raw memory
      representation is communicated via MPI), so we just do the same when writing
      to and reading from the buffer, which solves the problem.
      
      See merge request [core/dune-grid!300]
      
        [core/dune-grid!300]: gitlab.dune-project.org/core/dune-grid/merge_requests/300
      26e75d93
    • Robert K's avatar
      [!292] [cmake.modules.FindAlberta] two small fixes · 953a9547
      Robert K authored
      Merge branch 'findalbertafix' into 'master'
      
      ref:core/dune-grid Two small fixes for FindAlberta.cmake:
      
      1.  Do not add ${ALBERTA_UTIL_LIB} to the required libraries if it is set to
          NOTFOUND. This made cmake fail for me with icc, other compilers do not
          seem to be affected.
      2.  fix typo (length -\> _length)
      
      See merge request [core/dune-grid!292]
      
        [core/dune-grid!292]: gitlab.dune-project.org/core/dune-grid/merge_requests/292
      953a9547
  11. 07 Nov, 2018 1 commit
  12. 23 Sep, 2018 1 commit
    • Oliver Sander's avatar
      [!307] Make Coordinates constructors take domain size instead of element size · 8bb63866
      Oliver Sander authored
      Merge branch 'coordinates-constructors-should-take-domain-size' into 'master'
      
      This patch changes the semantics of the constructors of EquidistantCoordinates
      and EquidistantOffsetCoordinates. Whereas previously they took the element
      size, with the patch they now take the upper right corner of the domain.
      
      Rationale: as of 067abb55 , Coordinates
      objects can be used to construct YaspGrid objects. However, YaspGrid
      constructors expect the upper right domain corner rather than the element
      size. I think being consistent here will help to avoid many mistakes.
      
      Technically, this commit is an interface change. However, I propose to
      fast-track it because while users could use the constructors of the
      Coordinates objects before 067abb55 , they
      couldn't actually do anything with these objects. Therefore I argue that the
      constructors are not really public API after all.
      
      See merge request [core/dune-grid!307]
      
        [core/dune-grid!307]: gitlab.dune-project.org/core/dune-grid/merge_requests/307
      8bb63866
  13. 06 Sep, 2018 1 commit
  14. 05 Sep, 2018 2 commits
  15. 30 Aug, 2018 3 commits
    • Oliver Sander's avatar
      Make Coordinates constructors take domain size instead of element size · 33718576
      Oliver Sander authored
      This patch changes the semantics of the constructors of
      EquidistantCoordinates and EquidistantOffsetCoordinates.  Whereas
      previously they took the element size, with the patch they now
      take the upper right corner of the domain.
      
      Rationale: as of 067abb55 ,
      Coordinates objects can be used to construct YaspGrid objects.
      However, YaspGrid constructors expect the upper right domain
      corner rather than the element size.  I think being consistent
      here will help to avoid many mistakes.
      
      Technically, this commit is an interface change.  However,
      I propose to fast-track it because while users could use the
      constructors of the Coordinates objects before
      067abb55 ,
      they could actually do anything with these objects.  Therefore
      I argue that the constructors are not really public API
      after all.
      33718576
    • Oliver Sander's avatar
      [!144] Introduce constructor that takes a Coordinates object · 411048af
      Oliver Sander authored
      Merge branch 'introduce-generic-yaspgrid-constructor' into 'master'
      
      This constructor then takes the domain size and the number of elements from
      this coordinate object.
      
      See merge request [core/dune-grid!144]
      
        [core/dune-grid!144]: gitlab.dune-project.org/core/dune-grid/merge_requests/144
      411048af
    • Oliver Sander's avatar
      067abb55
  16. 13 Aug, 2018 4 commits