Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • dumux dumux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 96
    • Issues 96
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 98
    • Merge requests 98
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • dumux-repositories
  • dumuxdumux
  • Issues
  • #571
Closed
Open
Created Aug 29, 2018 by Timo Koch@timokOwner

Restart from VTK looses precision because data is written in single precision floating point format

The VTKWriter in Dune currently writes all data as "Float32", that's why when restarting from a vtk file we loose precision of our results.

I was thinking of proposing to optionally pass a data type to each VTKFunction (VTKFunction already stores other useful information about each field), extend the VTKFunction interface by a function that returns the data type (options would be Float32, Float64, Int32, Int64 at least, and probably an option/function that automatically converts a C++ type into a VTK data type), and use that in the VTKDataArrayWriter (defaulting to Float32 to retain current behaviour). Any other ideas? Otherwise I would draft something for Dune, but that can take some time...

Assignee
Assign to
Time tracking