[haze_1986]

it isn't about the $ sign. I have tried this, if I understand correctly, the folder structure of deb install is different from the compilation. I am curious as to how to fix this as well. I can't really remember how different it is though.

[wyldckat]

Originally Posted by haze_1986

it isn't about the $ sign. I have tried this, if I understand correctly, the folder structure of deb install is different from the compilation. I am curious as to how to fix this as well. I can't really remember how different it is though.

Sorry, I don't the time to go into details, so the quickest suggestion/fix is this:

1. Uninstall the OpenFOAM Deb version you have installed.
2. Follow the instructions available here, for the Ubuntu version you've got: http://openfoamwiki.net/index.php/In...M-2.1.1/Ubuntu

Good luck!
Bruno

[haze_1986]

Originally Posted by wyldckat

Sorry, I don't the time to go into details, so the quickest suggestion/fix is this:

1. Uninstall the OpenFOAM Deb version you have installed.
2. Follow the instructions available here, for the Ubuntu version you've got: http://openfoamwiki.net/index.php/In...M-2.1.1/Ubuntu

Good luck!
Bruno

Hi, I just found that it wouldn't work as well, at least on a clean install of 12.04 LTS. Same error under view.

[haze_1986]

Happy 2013 all, would just like to bump up this thread slightly with my updates/

I have been trying to find one paraview version that fixes the problem, and it seems that 3.98.0rc3 opened fine with no problems with mouse over view.
https://launchpad.net/~gladky-anton/...+build/4013515

However, I am not sure how to integrate it into the env such that using paraFoam would allow it to load pv3.98.0 directly. Anyone can enlighten me on this?

[wyldckat]

Hi haze_1986 and Happy 2013!

It's simple:

1. Uninstall the package "paraviewopenfoam3120", if you still have it installed.
2. If you built OpenFOAM/ParaView manually, first check if the built ParaView is still available:
   

   echo $ParaView_DIR
   ls -l $ParaView_DIR

   If it's still there (if the first command outputs a path and the second tells what's inside it), run:
   

   rm -r $ParaView_DIR

3. The new version of ParaView that you wrote about is installed on the global system. Therefore, all you need to do is do a little modification in the paraFoam script, which you can find by running:
   

   which paraFoam

   Then edit this file and search for the line that 71 in it - this one https://github.com/OpenFOAM/OpenFOAM...n/paraFoam#L71 - and change:
   

   extension=OpenFOAM
   requirePV=1

   To this:
   

   extension=foam
   requirePV=0

   Save the file and close.

Best regards,
Bruno

[haze_1986]

Originally Posted by wyldckat

Hi haze_1986 and Happy 2013!

It's simple:

1. Uninstall the package "paraviewopenfoam3120", if you still have it installed.
2. If you built OpenFOAM/ParaView manually, first check if the built ParaView is still available:
   

   echo $ParaView_DIR
   ls -l $ParaView_DIR

   If it's still there (if the first command outputs a path and the second tells what's inside it), run:
   

   rm -r $ParaView_DIR

3. The new version of ParaView that you wrote about is installed on the global system. Therefore, all you need to do is do a little modification in the paraFoam script, which you can find by running:
   

   which paraFoam

   Then edit this file and search for the line that 71 in it - this one https://github.com/OpenFOAM/OpenFOAM...n/paraFoam#L71 - and change:
   

   extension=OpenFOAM
   requirePV=1

   To this:
   

   extension=foam
   requirePV=0

   Save the file and close.

Best regards,
Bruno

Thanks Bruno

[haze_1986]

Hi Bruno, just wondering, would that work for self compiled multi-installations based on this? http://www.tfd.chalmers.se/~hani/kur...OwnLaptop.html

Previously with deb installation, I downloaded the latest 3.98.0 binary from paraview site and previously just changed the path in my .bashrc with this
export PATH=/opt/ParaView-3.98.0-Linux-64bit/bin/:$PATH

However now in the .bashrc, aliases were included
alias OF21x='. /home/hei/OpenFOAM/OpenFOAM-2.1.x/etc/bashrc'
alias OF21xDebug='. /home/hei/OpenFOAM/OpenFOAM-2.1.x/etc/bashrc WM_COMPILE_OPTION=Debug'
alias OF16ext='export QT_BIN_DIR=/usr/bin;. $HOME/OpenFOAM/OpenFOAM-1.6-ext/etc/bashrc'
alias PF057='export PYTHONPATH=/home/hei/OpenFOAM/PyFoam-0.5.7/lib/python-2.7/site-packages:$PYTHONPATH; export PATH=/home/hei/OpenFOAM/PyFoam-0.5.7/bin:$PATH'

Is there anyway I can point each of the paraviews to the 3.98 version?

[wyldckat]

Hi haze_1986,

In my signature link, you would find a link to another post on details about installing ParaView. From there, you should find this post: http://www.cfd-online.com/Forums/ope...tml#post345619 post #2
And then there's this blog post as well: Using the official pre-built ParaView 3.10.1 version with OpenFOAM

Best regards,
Bruno

[haze_1986]

Hi Bruno,

following the instructions, am I supposed to apply the steps independently to OF21x and OF16ext? I was able to rm -rf $ParaView_DIR for the OF21x. After following instructions to the end, it still didn't work, even for OF21x.

[haze_1986]

Error as below:

FATAL ERROR: ParaView reader module libraries do not exist

Please build the reader module before continuing:
cd $FOAM_UTILITIES/postProcessing/graphics/PV3Readers
./Allwclean
./Allwmake

[wyldckat]

Hi Haze,

Did you follow the instructions from post #25 on this thread we're on? The instructions on that particular post will only apply to OpenFOAM 2.1 and 2.0.

Best regards,
Bruno

[haze_1986]

Hi Bruno,

Yeap that worked very well. However, on another system I am required to use 1.6 ext as well. Thus I used the Chalmer's walkthrough to build one that have multi versions. Would it be possible to use 3.98 PV for all the versions based on the chalmer's installation guide?

Your help is much appreciated, thanks.

[wyldckat]

I haven't tested this on 1.6-ext, but my guess is that the instructions from here: http://www.cfd-online.com/Forums/blo...-openfoam.html - should do the trick. More specifically, starting from point #7.

[haze_1986]

I hope to clarify some points. For a start, in my built version based on chalmer's, I am unable to rm the $Paraview_DIR. Do I have to go into OF21x and OF16ext to rm. I found that it only works for OF21x.

[wyldckat]

Hi Haze,

OK, I didn't have an 1.6-ext installation handy before, but now I do:

1. Go into the main OpenFOAM folder of 1.6-ext:
   

   cd $WM_PROJECT_DIR

2. Source the file that has ParaView environment information:
   

   . etc/apps/paraview3/bashrc

3. Go into the third party directory:
   

   cd $WM_THIRD_PARTY_DIR

4. I got the 64bit version of ParaView 3.98.0:
   

   wget http://www.paraview.org/files/v3.98/ParaView-3.98.0-Linux-64bit-glibc-2.3.6.tar.gz

5. Unpack and place where it's needed:

   mkdir -p $ParaView_DIR
   cd $ParaView_DIR
   tar -xzf $WM_THIRD_PARTY_DIR/ParaView-3.98.0-Linux-64bit-glibc-2.3.6.tar.gz
   mv ParaView-3.98.0-*/* .
   rmdir ParaView-3.98.0-*

6. Now it's time to hack the paraFoam script:
   

   sed -i -e 's=\.OpenFOAM=\.foam=' $WM_PROJECT_DIR/bin/paraFoam

7. Another hack is also need to the paraFoam script, but this one has to be manual. Edit the file "$WM_PROJECT_DIR/bin/paraFoam" and place the code in bold right after the first comment block:
   

   # Description
   #     start paraview with the OpenFOAM libraries
   #
   #------------------------------------------------------------------------------
   paraview3=`$WM_PROJECT_DIR/bin/foamEtcFile apps/paraview3/bashrc` \
       && . $paraview3
   unset paraview3
   
   usage() {

And I think that's all! It's ready to be used!

Best regards,
Bruno

[haze_1986]

Hi Bruno, after doing this. paraFoam and paraview commands still return the 3.12.0 version that I have made based on http://www.tfd.chalmers.se/~hani/kur...OwnLaptop.html

I am not sure if it is because I have several versions of OF whereas the instructions you gave are only for just 1.6ext only

[wyldckat]

Hi Haze,

Well, then it's all on your side from now on!
The instructions on that page are a bit ambiguous, because at the beginning it talks about following a set of instructions and later on it talks about another set of instructions, so I don't know what needs fixing.
You can run the following command to help you diagnose where the problem is:

echo $PATH

You probably will see two paths to different ParaView installations. The first that comes up is the one used.

Best regards and good luck!
Bruno