Skip to content

GitLab

  • Menu
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,841
    • Issues 1,841
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 87
    • Merge requests 87
  • 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
  • ParaView
  • ParaViewParaView
  • Issues
  • #19850
Closed
Open
Created Apr 16, 2020 by W. Alan Scott@wascottMaintainer

File output from Catalyst kills ParaView

Jeff M. wrote an exodus file from Catalyst. When we try to open this file with ParaView, it dies a horrible death. File attached.

Here's what Jeff wrote to me:

Hey Alan. To create this exodus file I ran SPARC and did a catalyst script which does an xyslice and then writes out the xy slice to a .exo file using the paraview exodus writer. I ran on 1 process to do this, so this is not a multiprocess issue.

When I try to load the file in paraview 5.8 (gui) there are a bunch of warnings about bad point ids followed by a core dump. That was on snip - a linux cluster. On my windows machine, it just hangs.

When I do something else in SPARC (extract subset with seed) and write out an exodus file, paraview 5.8 gui loads it no problem.

When I load a .cgns file from some of Watney's data into the gui, make a slice, write it out (from the gui) as an exodus file, I can load that exodus file no problem.

I have my suspicions as to why this is happening but the issue I am writing you about here is: ParaView shouldn't core dump when it tries to read this file, especially after it has already detected problems with the file.

File is UUR, under the HiFire SAND number.

exodus_output_from_xyslice1_0008.exo

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking