[Jerome Berryhill]

Probably didn't really break it, just broke the path.
I had OpenFOAM installed, and was working with some tutorials. I came across this thread. The finite volume approach sounded promising. so I downloaded and installed foam-extend-3.0. After the usual problems due to various packages not being installed, I got it to work. I ran one of the tutorials, but when I try to look at the results, by running paraFoam, it says it can't find paraview.

If I go back into the original OpenFoam directories, I can still run paraFoam against those tutorials. So, it is likely a path issue.

I am on Debian Jessie. I used the Ubuntu install instructions.

[ Moderator note: Moved post from this thread: http://www.cfd-online.com/Forums/ope...am-extend.html ]

[wyldckat]

Quick answer: Try installing foam-extend 3.2: http://openfoamwiki.net/index.php/In...oam-extend-3.2

[Jerome Berryhill]

Ah, you have added an explanation of /path/to/qmake! I will try that now. Thanks!

[Jerome Berryhill]

The install instructions say to create directory called "foam", and operate in that directory. But when I get to source /etc/bashrc, it gives me a bunch of messages like
bash: /home/jerome/OpenFOAM/foam-extend-3.2/bin/foamGetSystemInfo: No such file or directory
bash: /home/jerome/OpenFOAM/foam-extend-3.2/bin/foamCleanPath: No such file or directory

OpenFOAM is the directory I originally installed OpenFOAM into, and I added its bashrc to my login script. It looks like they are maybe using the same environment variables, with unfortunate results? Can I just install foam-extend-3.2 in the OpenFOAM directory, instead of creating a new foam directory? Or will that cause other problems?

[Jerome Berryhill]

I undid the changes I made to my bashrc for OpenFOAM, and opened a new terminal window. Now the install seems to be running OK. I set the QT_BIN_DIR, so hopefully, it will build paraview.

[wyldckat]

Quick answer: Make sure you defined aliases for both/all versions: http://openfoamwiki.net/index.php/In...with_the_Shell
Example:

alias of240='. $HOME/OpenFOAM/OpenFOAM-2.4.0/etc/bashrc'
 
alias fe32='. $HOME/foam/foem-extend-3.0/etc/bashrc'

[Jerome Berryhill]

Here's where we stand. I downloaded extend 3.2, and set the QT_BIN_DIR envvar, and then set the DEVELOPE_WITH_NEW_BISON envvar, and Allwmake ran to completion with just a few warnings.

However, I still can't run paraview after sourcing fe32. I can run paraview after sourcing fe24.

I will look at it further in the AM, but any suggestions are welcome.

[wyldckat]

Quick answer: If you have the complete log, please compress it and attach it to your next post.
If not, then run these commands with the foam-extend 3.2 shell environment ready to be used:

foam3rdParty
./AllMake.stage4 > log.make 2>&1

gzip < log.make > log.make.gz
pwd

Then attach the file "log.make.gz" that is in the folder indicated by the last command. This way it's possible to diagnose the problem.

[Jerome Berryhill]

Here you go.

[wyldckat]

Hi Jerome,

Sigh... many thanks for the log file! I'm sighing because there is an hard-coded variable in the specification file for building ParaView that is making it always build with Python support... instead of relying on one of the options... and I don't have time to try and make a pull request for fixing this.

OK, let's solve your problem either way. I've updated the wiki page for dependencies: https://openfoamwiki.net/index.php/I...end-3.2/Ubuntu - please install the packages "python" and "python-dev":

sudo apt-get install python python-dev

Then please try again my previous post.

If ParaView builds properly this time, then also run the following commands for wrapping up the build:

cd $FOAM_UTILITIES/postProcessing/graphics/PV4FoamReader
./Allwclean
./Allwmake

If this doesn't solve the issue, I'm going to have go look for another thread where I posted a fix for an older version of foam-extend...

Best regards,
Bruno

[Jerome Berryhill]

I took a look at that log file, and it seens like it is trying to find some python files. Maybe this is a later version of paraview than the one I previously installed, and requires additional python? Anyway, I installed python-dev, and the build is running a lot longer than it did before. I will post the log if it fails.

[wyldckat]

Quick answer: Building ParaView with Python is usually optional. If you don't give the necessary build options, ParaView will not be built with Python support.

If you didn't follow the instructions given here: http://openfoamwiki.net/index.php/In...M-2.4.0/Ubuntu - then it's likely that your other ParaView build doesn't have Python support (search in the menu "Tools" for "Python Shell")... unless you installed the deb packages from here: http://www.openfoam.org/download/ubuntu.php - which does have Python support built into ParaView.

[Jerome Berryhill]

OK, I installed python-dev, and this time the build seems to have run to completion with no errors, just a couple warnings in the documentation step. But still no paraview. Here is the new log.

Ooops. "log.make.gz:
Your file of 281.6 KB bytes exceeds the forum's limit of 195.3 KB for this filetype."

Can I e-mail it somewhere?

[wyldckat]

Can you share it with DropBox or Google Drive or something like that? It would make it easier for me to not loose track of things...

If not, try:

bzip2 < log.make > log.make.bz2

[Jerome Berryhill]

bzip2 got it down to 191.

But;

log.make.bz2:
Invalid File

I don't have DropBox or google drive set up.

browse www.jJeromeBerryhill.com/Temp/log.make

[Jerome Berryhill]

Ooops, sorry, only one j;

www.JeromeBerryhill.com/Temp/log.make

[wyldckat]

Hi Jerome,

OK, installation seems to have gone well, or at least well enough. Please try a few things:

1. Start a new terminal and/or run again:
   

   fe32

2. Check if paraview is found:
   

   which paraview

3. If not, check the content of the folder where it should be installed:
   

   foam3rdParty
   ls -l packages/ParaView-4.3.1/platforms/linux64GccDPOpt/
   ls -l packages/ParaView-4.3.1/platforms/linux64GccDPOpt/bin/paraview
   ls -l packages/ParaView-4.3.1/platforms/linux64GccDPOpt/etc/

Best regards,
Bruno

[Jerome Berryhill]

Hmmm.. When I open a new terminal, and run fe32, the which command is able to find paraview, at /home/jerome/foam/foam-extend-3.2/ThirdParty/packages/ParaView-4.3.1/platforms/linux64GccDPOpt/bin/paraview.

But when I go into the bimaterials tutorial, and run Allwrun, then paraFoam, paraview starts up and gives me a message about "a reader for /yadda/yadd/.../bimaterials.OpenFOAM could not be found. Please choose one, with a long list of file types.

If, however, I start another terminal, and source the bashrc from my original OpenFOAM installation, I can then go into the bimaterials directory and paraFoam starts up paraview and it works just fine.

So, I guess I can limp along, using the extend tutorials with the old paraview. But if you want to continue trying to debug this install, I am happy to help.

[wyldckat]

I think we are almost there. If I'm not mistaken, you're only missing this:

cd $FOAM_UTILITIES/postProcessing/graphics/PV4FoamReader
./Allwclean
./Allwmake

[Jerome Berryhill]

No, that did not get it. But, I got a new error message. In addition to the thing about unable to find a reader, there is also a separate "Output Messages" box that popped up, with this in it

Generic Warning : In /home/jerome/foam-extend-3.2/ThirdParty/rpmBuild/BUILD/ParaView-3.4.1-source/Qt/Core/pqApplicationCore.cxx line 620
Readers have been changed such that the GUI definition is not needed. This should now be specified in the hints section of the XML definition.