Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • ParaView ParaView
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,959
    • Issues 1,959
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 96
    • Merge requests 96
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaViewParaView
  • ParaViewParaView
  • Issues
  • #19597
Closed
Open
Issue created Jan 20, 2020 by Martin Diehl@MartinDiehlReporter

XDMF+HDF5 wrong data

When using XDMF with heavy data stored in an HDF5 file, only the first cell gets a correct value. An XDMF file with embedded data works fine. Note that the Data Range is correct in both cases (1.0 to 1.0)

I am using Paraview 5.7.0 on Linux (Python 3.8). The same error occurs on Windows with Paraview 5.7.0 and 5.8 RC1. However, XMDF on Windows crashes quite often. On Linux, opening the XDMF file with heavy data in the file (no HDF5), results in an SIGABRT (Loguru caught a signal: SIGABRT).

Example files are attached

scalar_xml.xdmf

scalar_hdf5.xdmf

scalar.hdf5

scalar_xml

scalar_hdf5

Edited Jan 20, 2020 by Martin Diehl
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking