I'm currently trying it (64Bit Linux Machine, Paraview 3, compiled from the CVS). OpenFOAM-functionality is enabled via a Client-Plugin (right now the OpenFile-Dialog doesn't know OF-files).

It works fine for some cases. The problems I can put my finger on so far are:

- it is not very tolerant about the files in the time-direcotries (it allocates memory if there are any gzipped-files until the machine is completely filled). Same thing happens if there are any backup-files from the texteditor (ending with a ~)
- For some geometries I only can see the grid but can not color it with data (although the data gets recognized) I'll try to find a minimal case where that happens.

If you got a new version of vtkOpenFOAMReader that you want to have tested, I'd be more than happy to do so.

Bernhard

__________________
Note: I don't use "Friend"-feature on this forum out of principle. Ah. And by the way: I'm not on Facebook either. So don't be offended if I don't accept your invitation/friend request

*You need to create a copy of the controlDict file named "controlDict.foam" -> Paraview doesnt support opening files without extensions.

*The newest version of the reader would be in the latest release of Paraview. I would however suggest using the Paraview 2.6.2 (which also has the newest reader) not the 3 branch. I havent tested it much on 3 and there were major changes to Paraview made between those two releases.

@Gzipped data: Any plans to support that? Because having only non-zipped-data limits the usefullness for any real-life data (at least a more robust result than crashing would be cool)

Cool features (if you have too much time on your hands) would be:
- Support for Multi-region cases
- Lagrange particles

__________________
Note: I don't use "Friend"-feature on this forum out of principle. Ah. And by the way: I'm not on Facebook either. So don't be offended if I don't accept your invitation/friend request

I don't have much time to invest in the reader currently. Hopefully in the future I will have sometime to add some functionality. For the time being I am looking for any bugs in the current functionality.

Hi,
I'm now trying rather thorough bug hunting of the paraview native reader since I wrote paraFoam for Cygwin to use the native reader (afaik this is the only feasible way to realize paraFoam on Windows). Maybe I'll be posting a patch around early next week.

Although I well understand, and also would like what Bernhard suggests, the patch will exactly be focused on bugfix (most notably reported at this thread) and will include no feature enhancements, meant to serve as a basis for enhancements.

Hi,
Here's the patch for the reader included in the ParaView-2.6.2 distribution. To apply cd to ParaView-2.6.2/VTK/IO and run

patch < vtkOpenFOAMReader-20070813.diff.

If your mesh has any zones defined, extract group 0 (choose Filter->Extract Group and select group 0) to work on the dataset. Otherwise you'll see geometry but cannot colorize it (just as Bernhard pointed out above). Group 1 and above contain zone geometries.

Problems fixed:
* the reader should now work better and stably at least for most of the tutorial cases except for gzipped ones, and for other cases with relatively complex meshes/overall setups (especially ones with polyhedra/tetrahedra).

I figured that these remaining problems would be better fixed by rewriting the current line-based parser of the reader to token-based one that better emulates the one in libOpenFOAM, with gzipped stream support, as a longer-term work.

Thanks Terry, personally I think it's well worth investing some collaborative developments to improve the native reader since all VTK-based applications under all the supported platforms, not only paraview on Linux, could benefit from it, but I neither have enough time... I will post a patch again if I ever could implement those listed in my post above.

I'm currently using the OpenFOAM native reader together with the precompiled ParaView 3.3.0 you offered to download from your homepage (Thanks for that!). It runs fine, but I still have two small questions which may fit into this thread:

1.) I tried to use the ParaView filter "Surface Flow" but although I extracted the correct boundary surface the filter was not avaiable (stayed grey).
I doubt it's a bug, so maybe you can tell me whether it's simply not supported in the current version or a different procedure has to be used to make the filter available.

2.) It's an understanding question: When you refer to the performance of the reader, do you mean e. g. the playback speed of a timestep animation in ParaView? I noticed that the animation of the same case runs a bit faster and smoother when vtk-Files are used, do you know why?

1.) It looks like it's because of an incompatibility between what the reader offers as output dataset and what the filter requires as input, i.e. the Surface Flow filter doesn't seem to support composite dataset types, one of which is the type of dataset reader outputs. Other possibly incompatible filters with the same reason are Append Attributes and Append Datasets (I still haven't confirmed though). Unfortunately no quick workaround come to me.

2.) Roughly yes, I mean performance by mainly the initial loading time of a case and the playback speed of an animation. However note that
a.) I meant "better performance" by comparison to the previous versions of the reader and by no means comparison to the VTK reader.
b.) even if we make some comparisons with the VTK reader, nothing can't be said for sure without the details of the comparison, i.e. what formats (single/double-precision, text/binary formats) are used, whether patch data are also read or not, what differences are observed etc. For example if you compared the OpenFOAM reader with an ascii format case reading all internal mesh/patches and the VTK reader with single-precision binary format reading only internal mesh, and observed "only" a bit faster result with the VTK reader (which is quite a likely situation), in my view the OpenFOAM reader is doing surprisingly and unexpectedly well.

Since the OpenFOAM reader only supports double precision and foamToVTK only supports single precision as binary formats, a fair comparison will be in ascii formats (foamToVTK -ascii -noPointValues for VTK format).

First thank you for your contribution this is good stuff and I really like the new Paraview3

I downloaded the paraview-3.3.0 svn-version by end November last year. Patched up and compiled this version all the way it was described by your beautiful Release Notes. Until now everything works marvelous!

Unfortunately this version has a feature (setting the resolution, when saving pictures "Save ScreenShot"), which is added in the most reason svn version (16.01.08). Now again I patched and compiled everything without any errors, but as soon as I try to read a controlDict.foam (OFcase) I get a crash with the following error:

./bin/paraview
ERROR: In /home/klosterm/OpenFOAM/linux64/ParaView3/Servers/Common/vtkProcessModule.cxx, line 1008
vtkProcessModule (0x6ff960): Object type: vtkOpenFOAMReader, could not find requested method: "SetKeepPatches"
or the method was called with incorrect arguments.

You downloaded the latest version of Paraview 3.3.0 from the anonymous CVS right? Or is there also a parallel SVN repository?

Anyway.... was just wondering.... if you downloaded a completely new version of paraview from CVS, then this also includes the original "vtkOpenFOAMReader.cxx" and "vtkOpenFOAMReader.h" files in the "<pv3_root>/VTK/IO" directory that comes with PV3.... this version of the reader is extremely old, and is not Takuya's version.

You need to replace these two files with the version written by Takuya, and then recompile paraview.

The error that you are obtaining basically says that the XML file which configures the graphical interface has been modified to use Takuya's version, but the openfoam reader compiled into Paraview does not contain those configuration settings.