CFD Online Discussion Forums - Issue Involving Paraview

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)

- OpenFOAM (https://www.cfd-online.com/Forums/openfoam/)

- - Issue Involving Paraview (https://www.cfd-online.com/Forums/openfoam/74355-issue-involving-paraview.html)

Thanks Bruno. FoamToVTK is a little impractical with the setup I have going. After a little more digging, I found that it depends on the data fields I have loaded, some of which aren't calculated for all time steps. Therefore it seems like a plug-in bug.

Has anyone else used the vanilla ParaView 3.8.1 with OF 1.6, and if so what adjustments or tweaks have you had to make for it to work seamlessly? I like the stability of 3.8.1 in general and would like to use it as the default.

Hi Marco and Bruno,

@Marco: I see the problem with PV 3.8.1 (and only with 3.8.1, but not with 3.8.0 nor 3.9.0) too with a minor difference being I always see the problem regardless of what field I load. If we are discussing the same problem nonetheless, Merge Blocks should work.

@Bruno:

Quote:

Originally Posted by wyldckat (Post 281472)

Hi Marco,
Try using foamToVTK to generate the outputs in VTK format and see if the same problem occurs, when opening in ParaView the resulting VTK files.

If the same problem occurs, then it's a ParaView bug. If not, it's the plug-in's bug.

In fact, ParaView is a complex system thus sometimes the problem is not so bisectional. In my case, by comparing git logs of the first significant occurrence of ParaView classes in the backtrace

Code:

#28 0x00007ffff7b59e9d in pqSelectionInspectorPanel::updateSelectionGUI() ()

between PV 3.8.0/3.8.1/3.9.0, we find a commit that is in PV 3.9

Code:

commit 9cd0f355d03600e97b9b082dee0fa73ec62c4cac

Date:   Thu May 20 15:09:22 2010 -0400

    BUG: Fixed a endless loop bug with multiblock data.

but is missing from PV 3.8.1. I didn't elaborate to do a cherry-pick test for this, but since the crash is not immediate but occurs after several seconds of lockup I suspect this is most likely what fixed the problem in PV 3.9. Indeed, if I run Select Cells after running Merge Blocks to convert the multiblock reader output to a single unstructured grid, it works as expected. One may conclude this is a reader bug since the problem does not occur with the VTK data (which is of unstructured type), but was (most likely) a ParaView bug.

Takuya

Hi Takuya,

Quote:

Originally Posted by 7islands (Post 281524)

In fact, ParaView is a complex system thus sometimes the problem is not so bisectional.

:eek: I completely forgot that ParaView/VTK has multiple grid systems :( If I hadn't forgotten about it, I would have suggested that it could still be a bug in ParaView itself.
My apologies to you Takuya, for not fully thinking it through.

Best regards,
Bruno