[MikeWallis]

Hi,

Newbie question.

I'm compiling up 2.1.1 for a HPC system where we already have a version of ParaView installed. How do I configure parafoam to use this version, instead of having to compile the version that's in ThirdParty?

Thanks,

Mike.

[lovecraft22]

I don't have a direct answer to your question… but… what I usually do is to create a .foam file within the case folder and then open it in paraview. It is almost the same as running paraFoam.

[wyldckat]

Greetings to all!

@Mike: it depends on the ParaView version you've got on your HPC system. Was it a custom build or did it come with the installed Linux distribution?

As lovecraft22 indicated, you can use the internal reader, by using the file extension ".foam". If you want this by default, edit the file paraFoam and change the line:

# reader extension
extension=OpenFOAM

To:

# reader extension
extension=foam

To know where paraFoam is located:

which paraFoam

In case you have a custom build of ParaView and still have the development files around (preferably installed as well), then edit the file "etc/config/paraview.sh" in OpenFOAM's folder.

Best regards,
Bruno

[olesen]

Everything else is good, but I'd make a slight improvement here:

Originally Posted by wyldckat

...
In case you have a custom build of ParaView and still have the development files around (preferably installed as well), then edit the file "etc/config/paraview.sh" in OpenFOAM's folder.

The preferred solution is given indicated in the etc/config/example/paraview.sh file. You'd make a copy of this in your site-wide or user-specific OPENFOAM directory (see "foamEtcFile -list")

Your modified version hooks into the shipped version:

foamFile=$($WM_PROJECT_DIR/bin/foamEtcFile -mode o config/paraview.sh 2>/dev/null) && . $foamFile ParaView_VERSION=3.9.0
unset foamFile

This makes it easier to carry across your modifications to a newer OPENFOAM version (if needed) and avoids needing to touch the shipped files at all.

[MikeWallis]

Thanks, everybody! The point of all this is so that I can build and deploy OpenFOAM as a module for multiple users on the cluster, and there are users of ParaView on the system who don't use OpenFOAM so I'd like to keep the two applications as separated as possible.

You've been really helpful and I really appreciate it.

[GLfast80]

Originally Posted by olesen

Everything else is good, but I'd make a slight improvement here:


The preferred solution is given indicated in the etc/config/example/paraview.sh file. You'd make a copy of this in your site-wide or user-specific OPENFOAM directory (see "foamEtcFile -list")

Your modified version hooks into the shipped version:

foamFile=$($WM_PROJECT_DIR/bin/foamEtcFile -mode o config/paraview.sh 2>/dev/null) && . $foamFile ParaView_VERSION=3.9.0
unset foamFile

This makes it easier to carry across your modifications to a newer OPENFOAM version (if needed) and avoids needing to touch the shipped files at all.

This is interesting. One question, where do you have to place this file exactly?