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

[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, Michael Jackson <mike.jackson at bluequartz.net
> wrote:

> 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
> are pretty light, especially when you want to hyperslab a dataset, but you
> can get through it.
>
> Just my 2 cents.
> --
> Michael A. Jackson
> BlueQuartz Software, LLC
> [e]: mike.jackson at bluequartz.net
>
>
>
> Frederic Perez wrote:
>
>> 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 are in HDF5 and have various structures: 1D to
>> 3D vector fields, 1D to 3D scalar fields, and particle lists.
>>
>> Being new to Paraview and  VTK, I have found three options for making
>> our results usable:
>> 1) Write .xmf files that maps each of our individual pieces of data,
>> so that the XDMF reader can import them.
>> 2) Write a plugin that will convert the HDF5 files to VTK files and read.
>> 3) Use Programmable Sources that extract the HDF5 data directly to VTK
>> elements.
>>
>> Which one would you recommend? What are their qualities, especially in
>> terms of versatility and stability? In addition, are they particularly
>> hard to learn?
>>
>> Cheers
>> Fred
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensou
> rce/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170208/f31c29df/attachment.html>