[wyldckat]

Hi Maurizio,

Check my blog post again! I have now updated the post to teach how to modify both OpenFOAM 1.7 and 2.0

Best regards,
Bruno

[vaina74]

Hi, Bruno.

I think there was a misunderstanding - or maybe I was not able to get the right infos from your guide about ParaView. Anyway, today I'm not working with OpenFOAM 1.5-dev and the same computer as in last days (I have it back in one week), but I've just installed OpenFOAM 1.6-ext via CAE Team PPA on a new computer and I guess the procedure could be similar - from what I need for OpenFOAM 1.5-dev on the first one. In other words, $WM_PROJECT_DIR/etc/bashrc contains this rem lines (I'm talking about OpenFOAM 1.6-ext):

# Source user setup files for optional packages
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# _foamSource $WM_PROJECT_DIR/etc/apps/paraview/bashrc
# _foamSource $WM_PROJECT_DIR/etc/apps/paraview3/bashrc
#_foamSource $WM_PROJECT_DIR/etc/apps/ensight/bashrc

Besides that, $WM_PROJECT_DIR/bin/paraFoam doesn't include any .OpenFOAM or .foam (I attach the original file). Which editing am I supposed to do with both files? As you can see, there are some differences and I'm afraid to make a mistake. My aim is a 'link' between OpenFOAM 1.6-ext (or 1.5-dev) and the last ParaView version (installed with OpenFOAM 2.0 Debian/Ubuntu packages).
Thanks again for your help and pardon for my ignorance about linux and OpenFOAM :-/

[wyldckat]

Hi Maurizio,

I'm sorry, I got lost in my own train of thought back then

OK, modifying paraFoam in 1.5-dev and 1.6-ext is not necessary at all ! It's a script originally named pvFoam, it's not the original paraFoam script So it will open .foam by default Says so on the line:

ext=foam

Now, be careful, because the next steps might blow your mind:

• Install both Deb packages for OpenFOAM 2.0.0 and ParaView 3.10.1 from www.openfoam.com.
• Then edit the bashrc files of 1.5-dev and 1.6-ext and change the line:
  

  _foamSource $WM_PROJECT_DIR/etc/apps/paraview3/bashrc

  to:
  

  _foamSource /opt/openfoam200/etc/config/paraview.sh

• Start new terminals and/or run the desired alias name(s).
• Go to the case your already ran.
• Run paraFoam. Don't worry, it will run and exit, because this script is designed to allow the user to continue having access to the terminal window, while ParaView does its thing on the back/foreground.
  A few seconds later ParaView will pop up on the foreground or in the background and ready to show you the case!

And so there you have it: the details that had gotten lost in my train of thought

Best regards,
Bruno

[vaina74]

Hi Bruno,

now my $WM_PROJECT_DIR/etc/bashrc (OpenFOAM 1.6-ext via CAE Team PPA) includes

# Source user setup files for optional packages
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# _foamSource $WM_PROJECT_DIR/etc/apps/paraview/bashrc
# _foamSource $WM_PROJECT_DIR/etc/apps/paraview3/bashrc
#_foamSource $WM_PROJECT_DIR/etc/apps/ensight/bashrc
_foamSource /opt/openfoam200/etc/config/paraview.sh

The test case is OK and I don't see ParaView run and exit - maybe it's very fast :-D
Thank you, thank you very much for your help. I owe you a dinner, when you're in Venice or Trieste (Italy) :-)

[wyldckat]

Hi Maurizio,

Originally Posted by vaina74

The test case is OK and I don't see ParaView run and exit - maybe it's very fast :-D

Well, with me it was paraFoam that started and exited right away, while ParaView took a while starting in the background.

Originally Posted by vaina74

Thank you, thank you very much for your help. I owe you a dinner, when you're in Venice or Trieste (Italy) :-)

You're very welcome I'm glad it's finally working! And thank you for the dinner offer I have no clue when I might go to Italy, but I'll try to keep in mind to ring you up when I do go to Italy

Best regards,
Bruno