[Ganapathy]

Hi folks,
I have done the most difficult parts i.e. Installed OpenFoam and Paraview.
Everything is also running fine
BUT
When I use F1 or click on help for Paraview, I get a strange error
/home/dm2/henry/OpenFOAM/.................

But this is not my login nor my path for OpenFOAM.

How can I rectify this ?

[olesen]

Originally Posted by Ganapathy

Hi folks,
I have done the most difficult parts i.e. Installed OpenFoam and Paraview.
Everything is also running fine
BUT
When I use F1 or click on help for Paraview, I get a strange error
/home/dm2/henry/OpenFOAM/.................

But this is not my login nor my path for OpenFOAM.

You didn't say which OpenFOAM and paraview versions you are using.

However, there are a number of installation issues with paraview (see http://paraview.org/Bug/view.php?id=9998 for some of them). The makeParaView script in the OpenFOAM 3rdParty directory tries to rectify some of them (eg, the env path editing). It could be that it didn't fully succeed, or that there is yet another problem. Be thankful at least that your "paraview" executable seems to be finding the "paraview-real" backend correctly!

If you have a good set of nerves and a bit of time (3/4-1 hr), you could try recompiling paraview on your system. The makeParaView script is IMO the best way to go. There are options for enabling/disabling the various config and make stages. Note that the -envpath option, which is needed to replace the absolute path to gcc with the equivalent environment variables (otherwise you'd never be able to build any plugins), will prevent quick rebuilds later.

Here's a pointer to a git repo of the latest cvshead
http://github.com/Kitware/ParaView
This includes a fairly recent version of Takuya's reader and (as of yesterday) the slightly reworked wavefront OBJ reader is now activated. Since this reader version also handles point and line elements, it is a quite useful alternative to javaview for viewing debug mesh information in OpenFOAM:

For systems like openSUSE (11.1, 11.2), you'll need to install libQtWebKit-devel before compiling.

With any luck the paraview PARAVIEW_INSTALL_DEVELOPMENT cmake parameter will actually work soon! (see http://www.paraview.org/Bug/view.php?id=8712)