[wyldckat]

Hi Bruno,

Sorry about that I noticed it myself too about an hour or so ago, and the latest version already has the fix for it.

But you no longer need to run the installOF.sh script to finalise your installation. Just follow these instructions:

1. start a terminal and activate the OpenFOAM environment - this depends on if you chose to use startFoam or not... i.e., if you chose not to use it, it should activate by itself; otherwise you must run startFoam.
2. run these commands to fix the needed Make files:

   cd $WM_THIRD_PARTY_DIR/libccmio-2.6.1/Make
   mv files.AllwmakeLibccmio files
   mv options.AllwmakeLibccmio options

3. run these commands to build ccm26ToFoam:

   cd $WM_PROJECT_DIR/applications/utilities/mesh/conversion/Optional
   ./Allwmake

4. After about 30-90 seconds, it should have built ccm26ToFoam and be ready to use

Again, my apologies for missing that detail I had completely forgotten to rename the make files to their proper names.
Hopefully these instructions I've written will do the trick and the latest script should have a slim to none chance of having bugs... alas, I'm probably just dreaming

Best regards,
Bruno Santos

[Sumontro]

The download link for the .sh file is missing. Where is place the latest version of the file can be downloaded from?

[Canesin]

The download can be made at http://code.google.com/p/openfoam-ubuntu .. in the text has an call for "DOWNLOAD - installOF - version 0.9" ..
I removed the download file because we already has two versions of the script in the branches. And doing a link direct to the repository of the stable one will make people get the latest fixes always.

The "installOF.sh" is the stable version and should always compile at least OpenFOAM with no errors.

The "installOF_exp.sh" is the experimental version where we add funcionalities and test/improve that before pushing to the principal script.

[Sumontro]

How do I download the script in sh format? Because when I click on the download link, I get the code, not the file.

[wyldckat]

Greetings Sumontro,

You have at least 3 possibilities:

1. When you are seeing the code, go to the browser menu "File->Save Page As".
2. Or, before clicking the link to the script, use right-click and choose "Save Link As".
3. Or download directly from the terminal/shell, by running:

   wget http://openfoam-ubuntu.googlecode.com/hg/installOF.sh
   chmod +x installOF.sh

   This way you get the script and make it executable

Best regards,
Bruno

[fletc900]

1 - Using Firefox:

Right click over link, then select "Save Link As...".


OR

2- Click on link, copy all of the contents of the file of the server to new text file in Gedit (or another text editor). Save your file as "installOF.sh".

THEN, to execute the script you will need to give it "executable" permission. Using the prompt/terminal, type: chmod +x installOF.sh. Then double click on script, and select "Run in Terminal"

Cheers,
Bruno F.

[fletc900]

Bruno,

I just ran your instructions to compile the CCM+ script from the prompt. It worked flawlessly! I appreciate all of your help!

Cheers,
Bruno F.

[Sumontro]

my installation is not working properly. I get this message everytime I try running commands after installing OpenFOAM.

/home/sumontro/OpenFOAM/OpenFOAM-1.6.x/tutorials

[1] + Stopped blockMesh

What should I do? There seems to be no install log.

[wyldckat]

Greetings Sumontro,

OK, you should have the following log files:

/home/sumontro/OpenFOAM/OpenFOAM-1.6.x/foamIT.log
/home/sumontro/OpenFOAM/OpenFOAM-1.6.x/make.log
/home/sumontro/OpenFOAM/ThirdParty-1.6.x/makeParaview.log

The last one depends on what options you chose and what Ubuntu version are you using, so it will only exist if you chose to build Paraview or are running Ubuntu 10.04.
Additionally, on the folder where you executed the installOF.sh script you should have a log file named installOF.log.

If you don't have any of these log files, then something very strange happened.

As for the output you are getting:

/home/sumontro/OpenFOAM/OpenFOAM-1.6.x/tutorials

[1] + Stopped blockMesh

Please follow the instructions in OpenFOAM's user guide: Chapter 2 Tutorials
If this output you've reported still occurs after following the user guide instructions, then try starting a new terminal and running startFoam (if you chose that option when installing). Then try following the user guide's instructions again. If it still doesn't work properly, then please post the logs I've written at the beginning of this post.

Good luck, best regards,
Bruno

[83_Ale_83]

Hello everybody,

I have a strange issue on ubuntu 10.04 32bit fresh installation, why everytime I have to type startFoam to start "run" or "src" command?

Thanks in advance

[wyldckat]

Greetings 83_Ale_83,

Originally Posted by 83_Ale_83

I have a strange issue on ubuntu 10.04 32bit fresh installation, why everytime I have to type startFoam to start "run" or "src" command?

Technically, it should only be needed to run startFoam every time you start a new terminal. It's a default setting in the install script, and available to the user to choose it or not, in order to maintain a clean environment whenever you start a new terminal.
This way you can more easily setup a multi-OpenFOAM environment, if you want to install OpenFOAM 1.6 or OpenFOAM-dev 1.5 on the machine.

Either way, you can change this behavior by editing the file "$HOME/.bashrc". You can:

1. always start the OpenFOAM, just by changing the line (at the end of the file):

   alias startFoam='. (...)/OpenFOAM-1.6.x/etc/bashrc'

   to

   . (...)/OpenFOAM-1.6.x/etc/bashrc

2. add another OpenFOAM environment, before or after the startFoam line:

   alias startFoam16='. (...)/OpenFOAM-1.6/etc/bashrc'

The other idea that was envisioned for this startFoam method, was to give the user the possibility of using 32 or 64 bit executables in a x86_64 machine, and/or both Single and Double Precision builds and respective environments, but that idea has been left in the freezer...

If for some reason you do need to run startFoam before running "run" or "src", even if you've already executed it in that particular terminal session... then we'll need more information, because that is a very strange behavior

Best regards,
Bruno

[83_Ale_83]

Great answer Bruno,

I have explained bad the issue, everytime I open a new terminal and type "src" ecc ecc, following your replay I have changed the bash file and everything works fine.

Great job Bruno

[Sumontro]

Thanks Bruno for your advice, typing startFoam seems to fix the difficulties I was having earlier. Also, I found all three of the logs you said to look for. I don't know what other problems are lurking so I want to post the three logs. Where should I do this?

[wyldckat]

Hi Sumontro,

Originally Posted by Sumontro

Thanks Bruno for your advice, typing startFoam seems to fix the difficulties I was having earlier. Also, I found all three of the logs you said to look for. I don't know what other problems are lurking so I want to post the three logs. Where should I do this?

OK, zip the 3 logs into one. In Ubuntu, you can copy the logs to a new folder, using Nautilus, and then right-click on the three files or the new folder, and choose "Compress". Pick ".tar.gz" or ".zip".

Now, for posting here, when you reply to this post, you have two modes for posting:

• the quick box, which has limited controls, is located on the end of this page and has a button "Go Advanced";
• the advanced, that can be reached by the "Go Advanced" button or by the "Post reply" button.

Now, on the "Advanced" mode, scroll down a bit and you will see:

Attach Files
Valid file extensions: bmp c doc f gif gz h jpe jpeg jpg patch pdf png psd txt zip
Manage Attachments

Click on the button "Manage Attachments" and a new window should pop up. Use it to attach the compressed file: choose the file and press on the Upload button next to the file address. You can now close the window.

There should be a help page for the forum, but it felt quicker to just write about it here how to do it.

Best regards,
Bruno

[marval]

Hi all!

I've installed OpenFOAM using the script and no problems there. Then I try out the first tutorial, everything works fine (even opening the postprocessor and viewing the geometry works fine! ) but when I click the "Edit Color Map..." button the program (ParaView) AND the entire computer freeze :s. Someone else experiencing something similar? Do I need to do some more steps after the script?

Ps. I'm new to Ubuntu and OpenFOAM so please take that into account if you answer to this post Ds.

[wyldckat]

Greetings marval,

Uhm, I suppose you are using Ubuntu 10.04? Unfortunately, you will have to build Qt also, along with ParaView. Ubuntu 10.04 has a Qt version too "far in the future" (Qt 4.6.2, I think) when compared with Qt 4.3.5 that OpenCFD suggest to use with ParaView 3.6.1.

So, hopefully the following steps will work:

1. Don't erase your current OpenFOAM installation.
2. Run the installOF.sh script again and follow the same steps you followed the first time...
3. But this time, when it asks what options to use to build ParaView, pick Qt and ParaView. Also, since you are going to rebuild ParaView, might as well pick "With Python" option too, since you might need Python scripting in ParaView too, and this way you wont need to rebuild it once again.

Hopefully these steps wont mess up your current installation, and should build a bit faster OpenFOAM itself, since not much has changed.

After it is finished building, please test again and tell us if it now works or if it still doesn't work. Because if it works, we will set Qt 4.3.5 as standard for building in Ubuntu 10.04.

Best regards,
Bruno

[lin]

I have ever met the same issue, namely, paraview freeze the PC. I have tried to solve it but fail. From my opinion, this is due to the incompatibility between the intel graphic card 4 series and the driver on my laptop.

Do you have the same hardware?

[akidess]

Just an idea I got: We could add an option to the buildscript to use system paraview which would then create it's own paraFoam script doing the following:

foamToVTK [options]
paraview --data VTK/datafile.vtk

What do you think?

[wyldckat]

Greetings to all,

Originally Posted by akidess

Just an idea I got: We could add an option to the buildscript to use system paraview which would then create it's own paraFoam script doing the following:

foamToVTK [options]
paraview --data VTK/datafile.vtk

What do you think?

Looks and sounds great. And I raise you (playing poker with "idea chips" ) the following ideas:

• integrate a detection mechanism in the paraFoam script to either use foamToVTK+system or the usual OpenFOAM ParaView build;
• add an option to installOF.sh to either use the system ParaView or the usual building of ParaView+PV3FoamReader;
• add an option to build ParaView straight of the ParaView's Git repository, which apparently now has Takuya's vtkOpenFOAMReader which enables a more native reader for OpenFOAM files.
• add an option to include pvFoam... although I've never used it and I don't know if it will quell the freezing issues.

My current problem is the lack of time on my hands for the next few weeks


But the freezing problems remains somewhat unanswered: what is the specific reason for the freeze?
I assumed it was a Qt problem, but without access to a computer that exhibits the same problems, I can't isolate the problem myself

So, here is the list of possibilities that comes to mind, also based on other threads I've read in the past:

• Qt issue: try building ParaView with Qt 4.3.5. The installOF.sh script already does have that option.
• PV3FoamReader may be an incomplete plugin: in other words, the OpenFOAM plugin for ParaView might be missing some pieces of code that are required for specific operations, such as the "editing colors". So, try running the following commands, with the OpenFOAM environment activated, to remove the built plugins:

  rm "$FOAM_LIBBIN/libvtkPV3Foam.so"
  rm "$FOAM_LIBBIN/libPV3FoamReader.so"
  rm "$FOAM_LIBBIN/libPV3FoamReader_SM.so"

  Then go to the case you were running that froze up the computer, and run:

  foamToVTK
  cd VTK
  paraview

  And open the vtk files. (Or use the commands that Anton wrote) Then try again to freeze up the computer, by doing the same steps you did before last time it froze.
• Could be a bad build of ParaView, for some strange reason. If so, run (with the OpenFOAM environment up and running):

  rm -rf $ParaView_DIR

  And install Ubuntu's ParaView version:

  sudo apt-get install paraview

  Then try to use the vtk files generated in the previous possibility.
• Bad drivers: yes, if your graphics card isn't properly installed in Ubuntu, then it could lead to these problems with ParaView crashing and freezing the computer

And right now... I'm all out of more ideas....

So, marval and lin, if you still have problems with ParaView locking up the computer, please try these possibilities above and tell us if any of them worked. If not, we'll try to conjure up some more ideas

Best regards and good luck!
Bruno

[lin]

Thanks wyldckat for your advice.

I have the freezing problem some time ago when I use a laptop with intel 4 series graphic card, and Fedora 12 as OS.

I have tried all your suggestions at that time and still fail. My suspect is the intel 4 series graphic card, because I do not have any problem with others. This is just for reference, now I change to a PC and am not bothered by that.