[opencfd]

ESI-OpenCFD has been continuing its work on improving post-processing.

Working together with Kitware, the VTK-native OpenFOAM reader in the freshly released ParaView 5.3.0 now includes full support of 32-bit and 64-bit binary formats, better coverage of the Lagrangian formats, and the option to skip the initial conditions directory. https://blog.kitware.com/paraview-5-3-0-release-notes/ This release also includes essential improvements for parsing STL ASCII files. (https://gitlab.kitware.com/vtk/vtk/merge_requests/2357).

At the same time, the OpenFOAM plugins for ParaView have been updated in our development line (for the upcoming 1706 release in June) to work with all recent ParaView versions. The blockMesh reader now also includes support for displaying the patch names, which allows better visualization of a blockMesh. (https://develop.openfoam.com/Develop...hics/PVReaders)

Note that the ParaView plugins supplied with OpenFOAM are now versioned according to the ParaView major version, which makes it possible to easily switch between different ParaView versions without conflicts.

[gschaider]

Originally Posted by opencfd

ESI-OpenCFD has been continuing its work on improving post-processing.

Working together with Kitware, the VTK-native OpenFOAM reader in the freshly released ParaView 5.3.0 now includes full support of 32-bit and 64-bit binary formats, better coverage of the Lagrangian formats, and the option to skip the initial conditions directory. https://blog.kitware.com/paraview-5-3-0-release-notes/ This release also includes essential improvements for parsing STL ASCII files. (https://gitlab.kitware.com/vtk/vtk/merge_requests/2357).

At the same time, the OpenFOAM plugins for ParaView have been updated in our development line (for the upcoming 1706 release in June) to work with all recent ParaView versions. The blockMesh reader now also includes support for displaying the patch names, which allows better visualization of a blockMesh. (https://develop.openfoam.com/Develop...hics/PVReaders)

Note that the ParaView plugins supplied with OpenFOAM are now versioned according to the ParaView major version, which makes it possible to easily switch between different ParaView versions without conflicts.

Nice.

Question: Whom do I contact if I find a problem with that reader? ParaView-bugtracker or yours? For instance: if I have only one non-zero data folder (for instance 0 and 42) it seems that the Time-name is not correctly display in the GUI if "Skip Zero Time" is selected. The displayed data clearly belongs to t=42 but the GUI says "Time: 0"

[olesen]

Originally Posted by gschaider

Nice.

Question: Whom do I contact if I find a problem with that reader? ParaView-bugtracker or yours? For instance: if I have only one non-zero data folder (for instance 0 and 42) it seems that the Time-name is not correctly display in the GUI if "Skip Zero Time" is selected. The displayed data clearly belongs to t=42 but the GUI says "Time: 0"

Hi Bernhard,
I would recommend the paraview bug-tracker (or the paraview mailing list). You can also put olesenm into the distributor list there too if desired.

For your reported bug: I don't really know if this is easily fixable. This seems to be a general assumption within the vtk framework - if there is only set of data, it is by definition zero and you can't change it with the spin-box. You can use the fast-forward controls (last-frame) though and "annotate time" should display the proper value.
So I'd guess this is an annoying, but partially cosmetic, corner-case not specific to the OpenFOAM reader.

One issue that has cropped up with the reader are holes in the display (when the mesh is fairly large, but no polys). I believe that someone at kitware is looking into it. I suspect something odd with the cell-matcher yielding negative tets or something.

There is a test case posted on the paraview mailing list (5.5M cells) that illustrates this problem. It does loads properly using our reader module (develop), and when converted to VTK legacy. Need to chop it down a bit and see if the problems remain, are somehow related to an overrun, or can otherwise be pinpointed.

/mark

[aerogt3]

Originally Posted by opencfd

Working together with Kitware, the VTK-native OpenFOAM reader in the freshly released ParaView 5.3.0 now includes full support of 32-bit and 64-bit binary formats,

Interestingly, I am still unable to use the "read Zones" option in paraview with binary format open foam cases. It's only possible with ASCII.

Like gschaider, I am not sure where to report this....

[olesen]

Originally Posted by aerogt3

Interestingly, I am still unable to use the "read Zones" option in paraview with binary format open foam cases. It's only possible with ASCII.

Like gschaider, I am not sure where to report this....

Do you have a case that you can share (either publicly or privately)?
It would be good so see where the problem is.

/mark