|
[Sponsors] |
December 11, 2009, 14:34 |
ParaFoam Installation
|
#181 |
Senior Member
Phoevos
Join Date: Mar 2009
Posts: 104
Rep Power: 17 |
Hi everyone,
I have already installed OpenFoam 1.6 and been using it without problems, apart from the paraFoam command. Till now I was transforming the 0,1,2-.... folders to VTK files using foamToVTK and then I have been using paraview for visualisation. I was unable to proceed with the following procedure : cd $FOAM_UTILITIES/postProcessing/graphics/PV3FoamReader ./Allwclean ./Allwmake The make procedure starts but approximately at 33% it halts giving the following error message : make[2]: *** No rule to make target `/usr/lib64/libGL.so', needed by `/home/fivos/OpenFOAM/OpenFOAM-1.6.x/lib/linux64GccDPOpt/libPV3FoamReader.so'. Stop. make[1]: *** [CMakeFiles/PV3FoamReader.dir/all] Error 2 make: *** [all] Error 2 I initially thought that this was a problem of incompatibility with cmake, because I am using Ubuntu 8.10 64-bit (and I have read in other forums about issues on 64-bit ubuntu, cmake and parafoam) . But I have seen that some people in this thread, have managed to use it on 64-bit machines. So I have tried the sudo apt-get cmake, described by akidess, but I get the message that my cmake is up-to-date. Trying to make gives tha same error again. Any ideas about that ? Thanks in advance. |
|
December 11, 2009, 15:13 |
|
#182 | |
Member
Alessandro
Join Date: Nov 2009
Posts: 67
Rep Power: 16 |
Quote:
__________________
|
||
December 11, 2009, 17:40 |
|
#183 |
Senior Member
Phoevos
Join Date: Mar 2009
Posts: 104
Rep Power: 17 |
It seems Alessandro that we have some problem with the cmake and that is why the paraFoam loader cannot be built. At least we have a workaround using the foamToVTK. Lets hope that someone who has some more experience on the issue would be able to help us.
Anyway an other question regarding the script and the OpenMPI installation : The script automatically installs OpenMPI and configures it to use g++ and gcc as the desired compilers. However I need to use OpenMPI with icc,icpc and ifort (they are the Intel compilers for C,C++ and fortran respectively) for some other programs that I need to build from source. After the installation, OpenMPI cannot be configured (or at least I dont know a way to do so and I would prefer to avoid using makefiles during the compilation of my programs). So what I did is to install OpenMPI again, at a different folder, configured it properly and linked it with my compilers and added it to PATH and the LD_LIBRARY_PATH. Also in order to avoid conflicts with the first OpenMPI installation (made for OpenFOAM) I commented line 105 at bashrc located at .../OpenFOAM/OpenFOAM-1.6.x/etc/. This setup allows me to compile and run my programs but I can't run OpenFoam solvers in parallel. In order to run in parallel OpenFoam I have to un-comment the aforementioned line in bashrc at .../OpenFOAM/OpenFOAM-1.6.x/etc/. Is there an easier way to do that (swithcing OpenMPI installations) without needing to comment/un-comment lines in bashrc and the consequent sourcing of bashrc? Thanks in advance. |
|
December 13, 2009, 12:40 |
|
#184 | ||
New Member
okke bronkhorst
Join Date: Dec 2009
Posts: 2
Rep Power: 0 |
Hello there,
I am new to OpenFOAM and Linux, I have followed the cookbook (by copy-pasting line per line), but ran into trouble at the following line: Quote:
Quote:
Okke |
|||
December 13, 2009, 12:43 |
|
#185 | |
New Member
okke bronkhorst
Join Date: Dec 2009
Posts: 2
Rep Power: 0 |
the file the terminal is talking about is:
Quote:
|
||
December 14, 2009, 03:27 |
|
#186 |
Senior Member
Phoevos
Join Date: Mar 2009
Posts: 104
Rep Power: 17 |
Ignore the post, it was wrong. How can I delete it ?
QUOTE=okkebrokke;239859] Last edited by fivos; December 14, 2009 at 03:58. |
|
December 14, 2009, 13:14 |
|
#187 |
New Member
sachin
Join Date: Dec 2009
Posts: 3
Rep Power: 16 |
./Allwmake >make.log 2>&1
does this takes time? |
|
December 14, 2009, 13:33 |
|
#188 |
Senior Member
Mads Reck
Join Date: Aug 2009
Location: Copenhagen, Denmark
Posts: 177
Rep Power: 18 |
Sachin, takes time? If you mean if it takes a long time to complete, then yes :-) it can take from around half an hour to several hours. I have tried to implement parallel compilation (which is quite simple) but to keep the script as robust as possible I've stayed with sequential compilation...:-/
/Mads
__________________
Online free airfoil-mesher for OpenFOAM here |
|
December 14, 2009, 13:48 |
|
#189 | |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,982
Blog Entries: 45
Rep Power: 128 |
Greetings,
Quote:
Code:
# # Set the number of cores to build on # WM_NCOMPPROCS=1 if [ -r /proc/cpuinfo ] then WM_NCOMPPROCS=$(egrep "^processor" /proc/cpuinfo | wc -l) [ $WM_NCOMPPROCS -le 8 ] || WM_NCOMPPROCS=8 fi echo "Building on " $WM_NCOMPPROCS " cores" I've been meaning to give you guys a tested and tweaked version, but I haven't had the time yet Best regards, Bruno |
||
December 14, 2009, 19:00 |
|
#190 |
New Member
Jon Mita
Join Date: Nov 2009
Posts: 8
Rep Power: 17 |
Hello all,
When trying to run the installation script, I get the following: mstfl@mstfl-desktop:~$ ./installOF bash: ./installOF: Permission denied This is on a brand new install of Ubuntu 9.10 32bit. Any ideas? Thanks, Jon |
|
December 15, 2009, 02:19 |
|
#191 |
Member
Wolfram Kretzschmar
Join Date: Dec 2009
Posts: 71
Rep Power: 16 |
Jon,
please post the result of Code:
mstfl@mstfl-desktop:~$ ls -l Cheers Wolle Last edited by Wolle; December 15, 2009 at 02:37. |
|
December 15, 2009, 02:22 |
|
#192 | |
Member
Wolfram Kretzschmar
Join Date: Dec 2009
Posts: 71
Rep Power: 16 |
Quote:
for your paraFoam command issue, have a look at this: http://www.cfd-online.com/Forums/ope...tml#post239591 Maybe this could make your compilation needless? Cheers Wolle |
||
December 15, 2009, 02:38 |
|
#193 | |
Senior Member
Phoevos
Join Date: Mar 2009
Posts: 104
Rep Power: 17 |
Quote:
Thank you for your response Wolle, I will try adding export LC_ALL=C In the paraFoam script located at : $HOME/OpenFOAM/OpenFOAM-1.6.x/bin/paraFoam and see what happens. Regards |
||
December 15, 2009, 04:40 |
|
#194 |
Member
Alessandro
Join Date: Nov 2009
Posts: 67
Rep Power: 16 |
It works!!!
__________________
|
|
December 15, 2009, 05:58 |
|
#195 | |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,982
Blog Entries: 45
Rep Power: 128 |
Hi Jon,
Quote:
Code:
chmod 744 installOF Best, Bruno |
||
December 15, 2009, 10:04 |
|
#196 |
Senior Member
Phoevos
Join Date: Mar 2009
Posts: 104
Rep Power: 17 |
Well unfortunately it didn't work for me .
- If I use the command paraFoam in a directory with the 0,constant, system folders, I get the message : created temporary 'damBreakWithObstacle.OpenFOAM' /home/fivos/OpenFOAM/ThirdParty-1.6/paraview-3.6.1/platforms/linux64Gcc/bin/paraview-real: symbol lookup error: /home/fivos/OpenFOAM/ThirdParty-1.6/paraview-3.6.1/platforms/linux64Gcc/bin/libvtkQtChart.so.pv3.6: undefined symbol: _ZN14QGraphicsScene11eventFilterEP7QObjectP6QEvent - If I try to compile the PV3 foam reader at : /home/fivos/OpenFOAM/OpenFOAM-1.6.x/applications/utilities/postProcessing/graphics/PV3FoamReader with allwmake I still get stuck at the same point. Is there any case my attempts for building paraview from source would ruin the paraview files that were installed by the tar files (I am especially concerned about ./Allwclean)? Something else that I have found is that, if I comment line 241 in bashrc located at : /home/fivos/OpenFOAM/OpenFOAM-1.6.x/etc (line is : _foamSource $WM_PROJECT_DIR/etc/apps/paraview3/bashrc) and add my own paraview installation in the default directory bashrc, then the paraFoam command opens the paraview program, but when I select to open openFoam files it closes. Wolle could you please explain what do you mean with "make your compilation needless"? Where can I find the executables? As I said above I tried using a separate installation of paraview (which I am currently using to open the VTK files generated by foamToVTK) but paraFoam does not work. Any ideas ? Thanks in advance |
|
December 15, 2009, 10:24 |
|
#197 |
Member
Wolfram Kretzschmar
Join Date: Dec 2009
Posts: 71
Rep Power: 16 |
Hi all,
Fivos, at the moment I'm working with a binary version of ParaView, though I intend to make my own builds in the future. The binary versions of ParaView (corresponding to your CPUs architecture) are available through the Third-Party packages here: http://www.opencfd.co.uk/openfoam/do....html#download (CHOSE PLATFORM!!!) Once, you install those versions (I don't know, whether you can make your own OF build use the third party binaries or whether this works only with the binary version of OF too), ParaView is likely to work, paraFoam sometimes doesn't, but at least, there's the workaround using foamToVTK. The reason, why paraFoam sometimes wont work, is a thing called "LOCALES". The locales on your machine are characteristic for type setting, spelling, encoding, date and clock format etc. according to your language. Other language settings than English (as for me: German, as for Alessandro: French as it seems) obviously confuse the paraFoam script. So by adding the afore mentioned line in the beginning (I chose the first uncommented line, as the effect takes place immediately when the script reaches this line!) of the script, you suspend your local LOCALES settings (lasting for the duration of the paraFoam script execution and its child processes). As you understand, this ONLY affects the execution (and result, of course) of the paraFoam script. It wont have any effect concerning your compilation issues! The error message you get when executing the paraFoam script seems to result from your defective compilation. So using your working copy of ParaView with the modified version of paraFoam script should work. It's not so easy to explain, because I'm not a professional in this area and no English native speaker too. So if you didn't understand something, feel free to ask again... Cheers Wolle |
|
December 15, 2009, 10:59 |
|
#198 | ||
Member
Alessandro
Join Date: Nov 2009
Posts: 67
Rep Power: 16 |
In my case (Ubuntu 9.10 x64) I have followed the script made by Mads and I change the script like CedricVH and also I have used http instead of git.
Regarding openFoam I have only added the line at the beginning of the parafoam script located at Quote:
Quote:
__________________
|
|||
December 15, 2009, 11:05 |
|
#199 |
Senior Member
Phoevos
Join Date: Mar 2009
Posts: 104
Rep Power: 17 |
Wolle and Alessandro thank you for your quick answers. I understand that the local language settings might be an issue for the paraFoam application (I think that I have read something about messing with '','' and ''.''). Something else, have you (or anyone else) ever encountered the following message when using paraFoam :
Read float past end of buffer Read float past end of buffer Read float past end of buffer Read float past end of buffer Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must reimplement QApplication::notify() and catch all exceptions there. terminate called after throwing an instance of 'std::length_error' what(): basic_string::_S_create Aborted Thanks. If everything else fails I'll stick with the foamToVTK |
|
December 15, 2009, 11:57 |
|
#200 | |
Member
Alessandro
Join Date: Nov 2009
Posts: 67
Rep Power: 16 |
Quote:
Maybe you don't have all the QT packages to run QT correctly
__________________
|
||
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
install OpenFoam 1.6 by building source: how? | niudie | OpenFOAM Installation | 13 | April 26, 2011 01:48 |
How to Install OpenFOAM on 64 Ubuntu 9.04 | hansel | OpenFOAM Installation | 62 | March 19, 2010 15:43 |
install openfoam 1.6 on opensuse 11.0 | andresbh | OpenFOAM Installation | 8 | September 30, 2009 01:48 |
Install openFOAM 1.6 on debian 32bit - blockMesh: command not found | fossy | OpenFOAM Installation | 1 | August 28, 2009 05:06 |
Install of OpenFOAM 1.6 Error 1 Error 2 & run tutorial | potac | OpenFOAM Installation | 3 | August 27, 2009 10:04 |