[Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some weird visualization issues.

Mark Olesen Mark.Olesen at esi-group.com
Thu Mar 16 06:44:38 EDT 2017


Hi Tom,

Sorry, no answers - only questions/ideas:

Is decompose polyhedral on or off? How do things look using the other setting?
If the number of cells corresponds to checkMesh - then you either have no polyhedra, or decompose polyhedral is off.
If you use foamToVTK (with and without -poly) and then read the VTK file back in, how does that compare?
Using foamToEnsight could be yet another check, but without the option to decompose polyhedra.

In most paraview versions I've had issues with slicing through polyhedron (eg, from the motorBike tutorial).
The symptoms are either holes in the visual (like you have) or crashing the program. I haven't checked if this is better/worse in 5.3.0.

Cheers,
/mark
________________________________________
From: ParaView <paraview-bounces at paraview.org> on behalf of Tom Fahner <tom.fahner at gmail.com>
Sent: Thursday, March 16, 2017 9:39:49 AM
To: ParaView
Subject: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some weird visualization issues.

Dear all,

Please find attached two images that show my OpenFOAM model in ParaView 5.3.0. It was the standard Binary Installers package downloaded from the website for 64 bit linux (OpenSUSE Leap 42.1).

The correct number of cells is reported in the information tab (when compared to OpenFOAM's checkMesh result). The patches are
all rendered nicely, but it looks like some cells are missing in the domain/volume.

Is there some setting that I need to apply?

Please note that the mesh has about 25.8 million cells, for smaller meshes this was not a problem. A colleague had similar issues.
ParaView version 5.1.2 did not have this problem, ParaView 5.2 was not able to open the OpenFOAM files at all.

Best regards,
Tom

--
T.C. Fahner
e: tom.fahner at gmail.com<mailto:tom.fahner at gmail.com>



More information about the ParaView mailing list