Strange. I don’t get the garbled mess when I threshold on volume fraction in paraview.
In any case, it sounds like we may run into issues at some point using cell based data within an image data object. Our filtering needs are pretty simple – threshold and various clipping are the most commonly used ones. We’ve been using paraview for years without much issue anyway with this format.
That said we do tend to merge and convert the cell data to point data for smoother images when using paraview. In our CFD solver, each process writes out its own vti file. In paraview, we merge the data to prevent discontinuities from appearing across interfaces. For some users this “reassembly” can present an issue, and we provide scripts to help with that workflow step. If there is a more natural way to represent this data in vtk I would be interested in suggestions.
