[marval]

Hi!

And thanks for the reply! I've tried to follow the steps but when I try to reinstall, the entire computer crashes (somewhere in the process, I don't know exactly where in the process since I'm away from the computer during the installation) .

I think I will start over by erasing everything and then running the script again. This time marking the other alternatives of making paraView. It will take some time but I will report how it worked out when I'm finished. Lin, my graphic card is: ATI Mobility Radeon HD3650...i think that's the answer to your question.

Oh, right. I'm using Ubuntu 10.04.

Regards, Marco

[vaina74]

Hi, Bruno.

That's me again
Today I made a fresh installation of OpenFOAM 1.6.x on another pc (32-bit, Ubuntu 10.04 LTS), with the last stable version of your script (v. 0.9). I had a (just) Paraview building error, like in post #37. Just now I read about the very last version of the script: how can I fix the problem, without launching again the whole installation process? I attach my log files.

Cheers,
Maurizio

PS I can't attach OF installation log file, it's too big.

[akidess]

For Maurizios problem, it looks like we are missing freeglut3-dev..

[vaina74]

What is freeglut3-dev? I have no idea about it
Can you help me, please? I'd like to fix the problem before office closing...

[akidess]

Hehe. Personally I'd prefer not to patch the existing paraFoam but have two scripts. Otherwise we need a runtime option to select system or of-parafoam without reinstalling. But I guess that's just a matter of taste. I like the other ideas and will try to include them in the script when I find the time, but that's probably going to be in two weeks...

Originally Posted by wyldckat

Greetings to all,
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.

[akidess]

Maurizio, freeglut is a part of the OpenGL library. Try "apt-get install freeglut3-dev", then rerunning the build script.

[vaina74]

Should I run the whole compiling process (OF, QT, etc.) - it takes hours - or maybe is it possible to run again only Paraview building with OF install script?

[wyldckat]

Greetings to all,

Originally Posted by akidess

Maurizio, freeglut is a part of the OpenGL library. Try "apt-get install freeglut3-dev", then rerunning the build script.

Anton, I have no clue as to how you figured that one out, but I've included it in the experimental script.

Originally Posted by akidess

Hehe. Personally I'd prefer not to patch the existing paraFoam but have two scripts. Otherwise we need a runtime option to select system or of-parafoam without reinstalling. But I guess that's just a matter of taste. I like the other ideas and will try to include them in the script when I find the time, but that's probably going to be in two weeks...

Uhm, good point. That way, with two scripts, one can use either the system's or OpenFOAM's versions. I now agree with you
I know it would be possible to make paraFoam to use only one of them by default (if OpenFOAM ParaView version doesn't exist, and system's version exists, use foamToVTK+system ParaView), but that would limit the user to only one ParaView version.

Originally Posted by vaina74

Should I run the whole compiling process (OF, QT, etc.) - it takes hours - or maybe is it possible to run again only Paraview building with OF install script?

Maurizio, sorry for taking so long to answer, but I had lots of stuff to do... and the answer a couple of hours ago would be: no. But right now, I've made some commits to the experimental script, so if you are willing to test it: http://openfoam-ubuntu.googlecode.co...stallOF_exp.sh
The current experimental version (as of this writing) has the following capabilities, that the current stable script doesn't have: an additional option for custom building, which gives you access to building Qt, ParaView, Gcc, change the way the OpenFOAM environment is started (always or with startFoam), build ccm26ToFoam and code documentation... all of these, without (re)building OpenFOAM itself. This is to be used ONLY after at least one "fresh install" run has been fully completed, whether with or without success. In case you do need to rebuild OpenFOAM, you should run with the "update install" option (in the "Install mode" dialog).
If the update option doesn't do the trick, it's because there is some object junk in the way, so run the following commands:

cd $WM_PROJECT_DIR
wcleanAll

Then try again running the update option.

The experimental script still doesn't have the option for using Ubuntu's ParaView with foamToVTK.


These changes haven't been pushed to the stable version, because... I haven't tested it completely and there are still some more tweaks needed to ensure a comfortable user experience Which will only be done when time is available to do so


Has for ParaView locking up the machines, I'm going to try to investigate if the Mesa libraries can fully replace GPU-OpenGL, thus relying in CPU-OpenGL (independent of graphic cards), but it could be a long shot
Edit: after an hour of research, I've figured out how to build ParaView with Mesa, but it require more time to implement than I have right now. It will be possible to directly link to Ubuntu's Mesa libraries, thus not requiring to do a custom build of the Mesa libraries.

Best regards,
Bruno

[vaina74]

Well, on monday I'll be your cavy
Since I think OpenFOAM, Gcc, Qt, etc. building was ok in my case and the problem was only in ParaView, I'm going to test the experimental script in order to build only Paraview.
A newbie suggestion. This incredible and growing script is fantastic (above all) for not-so-linux-experts. For this reason, if you are going to include all these customing options, it should be better to have a little readme in order to explain the options, in simple words. Otherwise one could be puzzled (too many choices!).

Thank you for your help, cheers.

Maurizio

[sda]

Dear All,

Does anyone have any experience with running the script to install OpenFOAM 1.6 on Ubuntu 10.4 with gcc 4.4.3. I am doing a test run right now and in doing a tail -F on the install.log file, I only see references to gcc 4.3.3.

I expect the worse followed by lots of fiddling about. i hope I am wrong. If anyone has any insight into this, I would appreciate your input.

Impressive work with the script by the way.

Regards,


SDA

[vaina74]

I ran installOF_exp script but something went wrong. Maybe I didn't set the right installation options:
- custom install mode
- build ParaView with(out) Qt
- build Paraview with GUI
Then I tested the OpenFOAM installation by the cavity tutorial. When I run paraFoam I obtain:

paraFoam: line 131: paraview: command not found

Why that?

[wyldckat]

Greetings to all,

Maurizio, on the dialog that has "- build Paraview with GUI", you should have read more carefully the text It says right above it "Do custom build of ParaView ?". I know, it seems misleading, but you know how quoting only some specific sentences can be misleading without knowing the whole text, right?

We haven't had time yet to write the FAQ in English, nor to write a tutorial on how to use the script and explaining each option. We've been more focused on getting the script "running to the max" and aiming to reach version 1.0. When we reach that stage, we will allocate more time to the docs


SDA, it has crossed my mind a few times to add to the script the option to also build OpenFOAM 1.6, but since 1.6.x is the state-of-the-art version of OpenFOAM, we've focused our efforts on primarily making the script fully functional, and then start adding extras. And since OpenFOAM 1.7 is just two months away, it seems to me to be a "waste of precious time" to invest in old technology

Best regards,
Bruno

[vaina74]

Hi, Bruno.

My english and linux understanding is not so good, so I don't think I can understand

on the dialog that has "- build Paraview with GUI", you should have read more carefully the text It says right above it "Do custom build of ParaView ?". I know, it seems misleading, but you know how quoting only some specific sentences can be misleading without knowing the whole text, right?

Anyway, in my linux ignorance, in the meantime I'm running the experimental script and rebuild all not-OpenFOAM stuff (Gcc, Qt, ParaView). Now the building process of ParaView seem to be going right (e.g. is very slow, at first script running it was fast in a suspicious way ).
About th FAQ, it was a suggestion for the (far) future. Your work is great and free, I know that

Thanks for your help, cheers.

Maurizio

UPDATE

It's all ok, now. It was probably enough the rebuilding of ParaView with the appropriate settings in the install script, but I got it and that matters to me. Thanks for your help again

[wyldckat]

Originally Posted by vaina74

UPDATE

It's all ok, now. It was probably enough the rebuilding of ParaView with the appropriate settings in the install script, but I got it and that matters to me. Thanks for your help again

I'm glad it's finally working! And you're welcome

[marval]

Hi!

Now I've "upgraded" to 64 bit Ubuntu and ran the script but paraview doesn't want to work this time. Everything worked fine with the 32 bit installation but not in 64 bit.


------------------------------------------------------
Build ParaView:
Build process didn't finished with success. Please check the log file for more information:
/home/marco/OpenFOAM/ThirdParty-1.6.x/build_ParaView.log
You can post it at this forum thread:
http://www.cfd-online.com/Forums/ope...er-ubuntu.html

You can also verify that thread for other people who might have had the same problems.
------------------------------------------------------
------------------------------------------------------
ParaView isn't available where it is expected:
/home/marco/OpenFOAM/ThirdParty-1.6.x/paraview-3.6.1/platforms/linux64Gcc/bin/paraview
Therefore it isn't possible to proceed with building the plugin PV3FoamReader.
------------------------------------------------------

I attached the log file for this. By the way, it didn't work out the freezing problems for me before (in 32 bit Ubuntu 10.04). I suspect it is, as many already said, the graphics card (hardware problem/incompatibility).

Regards Marco

[wyldckat]

Greetings Marco,

Can you test the experimental script (see post #68) to build again ParaView? Use the new "custom" option instead of the "fresh" install option, and try to build ParaView again, but this time without the "OSMesa" build option.

OSMesa is useful only for off-screen rendering. Instructions here: Setting up a ParaView Server
This option hasn't been fully tested yet, so as far as I know, it should work, but it might not work

Best regards,
Bruno

[marval]

Thanks alot Bruno!

Everything (!) is working fine for the moment. Even the freezing problem is gone! I don't know if it have anything to do about switching to 64 bit. Now, something strange happened, when I did NOT (not yet) update the drivers for my graphic card. Paraview worked fine. THEN, when I updated it I got segmentation error when trying to open paraview . After that I thought: "What the heck!" and "un-updated" my drivers and then tried to run paraview. Guess what happened, it worked! . I thinks that's very peculiar to say the least. Maybe a pure coincidence I don't know...

Regards Marco

[wyldckat]

Hi Marco,

That's good news
As for the drivers, I'm almost betting that if you'd had gone to the previous version of the drivers in the 32bit version, the same would have happened.

The thing is, as far as I know, proprietary drivers like NVidia and ATI's, have one serious problem with their source code: they aren't even privately open (i.e., any changes by others would be automatically theirs), they are fully closed to the general public and when they release a new update, it's just as prone to error as GPL software, but has a tendency of taking far longer to be fixed. My assumption is that the team that works on the Windows version of the drivers is far larger than the team that works on the Linux version.

Best regards,
Bruno

[akidess]

I googled "OPENGL_INCLUDE_DIR (ADVANCED)" and the most likely answer was the missing freeglut package. No black magic here

I have the feeling using Mesa will be really slow so it might not even be that helpful. But it's worth trying if you find the time...

- Anton

Originally Posted by wyldckat

Greetings to all,

Anton, I have no clue as to how you figured that one out, but I've included it in the experimental script.

Uhm, good point. That way, with two scripts, one can use either the system's or OpenFOAM's versions. I now agree with you
I know it would be possible to make paraFoam to use only one of them by default (if OpenFOAM ParaView version doesn't exist, and system's version exists, use foamToVTK+system ParaView), but that would limit the user to only one ParaView version.

[...]

As for ParaView locking up the machines, I'm going to try to investigate if the Mesa libraries can fully replace GPU-OpenGL, thus relying in CPU-OpenGL (independent of graphic cards), but it could be a long shot
Edit: after an hour of research, I've figured out how to build ParaView with Mesa, but it require more time to implement than I have right now. It will be possible to directly link to Ubuntu's Mesa libraries, thus not requiring to do a custom build of the Mesa libraries.

Best regards,
Bruno

[Canesin]

Mesa is f***ing slow against OpenGL in rendering.. when you are dealing with small meshes and fields maps you don't notice it a lot but when you need an cluster almost the size of the compute-cluster just to post-process you start to understand why is a good design choice to include one rendering node in your farm... Has some LLVM work with translation GL whith a JIT for CPU rendering, using Gallium3D ... has some benchmark here : http://www.phoronix.com/scan.php?pag...llvmpipe&num=1

But, GPU will always be better for the job.