Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • VTK VTK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 830
    • Issues 830
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 241
    • Merge requests 241
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTKVTK
  • VTKVTK
  • Issues
  • #18081
Closed
Open
Issue created Jan 12, 2021 by olesen@olesenDeveloper

openfoam reader ignores embedded 32/64-bit information

The additional arch information in FoamFile header provides information about the precision of the contents (integer and floats). However, most of the reader doesn't handle this properly and blindly applies the values from the GUI in various places. For mixed workflows this becomes as complete disaster (ie, SEGFAULT).

For an example of a "mixed workflow":

  • surface preparation and meshing (snappyHexMesh) with 64-bit labels and double precision
  • initial calculation with the same settings
  • restart and run calculation with mixed precision - field storage in single precision, with the linear solver running in double precision.

Since the internal file representation changes between time steps, there is no GUI setting that works.

Assignee
Assign to
Time tracking