The one place for your designs
To enable design management, you'll need to meet the requirements. If you need help, reach out to our support team for assistance.
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.