Re: [Paraview] Best way to make a code's output Paraview-ready

2017-02-08 Thread Samuel Key
Fred, Useful simulation results formats for ParaView depend on the size of the datum set. Here are two formats. For medium to very large massively parallel datum sets, the ExodusII format works. The ExodusII format is binary, current, and well supported in ParaView. It is a no-cost,

Re: [Paraview] Best way to make a code's output Paraview-ready

2017-02-08 Thread Andy Smith
I will second that recommendation. I've used XDMF in this way (writing the HDF5 and XML parts manually) with multiple CFD codes. You may also want to checkout the XDMF API as I'm sure they've made improvements since I started using XDMF 6 or 7 years ago. -Andy On Wed, Feb 8, 2017 at 7:52 AM,

Re: [Paraview] Best way to make a code's output Paraview-ready

2017-02-08 Thread Michael Jackson
For our project (http://www.github.com/bluequartzsoftware/simpl) we write .xdmf files that reference the hdf5 files that we natively write. We just rolled our own XDMF writer as it is just xml and we knew which of our datasets we wanted to expose in the XDMF file. The docs for the xdmf format

[Paraview] Best way to make a code's output Paraview-ready

2017-02-08 Thread Frederic Perez
Hi all, I am part of a development team for a scientific code, and we would like to make our code's output readable by Paraview. Unfortunately, there is no reasonable way we could have our code directly output to VTK formats for various reasons (performance, memory, etc.). Currently, the outputs