OpenFoam 1.6-ext
 

Hi Foamers

Where can I get OpenFoam 1.6-ext? Please keep me posted, I vent foamed for a while. I would like to use the new paralleled tool for dynamic meshes for engines! Has anyone some experiences so far?

Peter

Hi Peter,

it is on the public git repository of -Extend:
best regards,

Thank you for the fast response!
Peter

I think I ve succeded to compile it. I tried to compile also some solver which I made in 1.5-dev. Unfortunately it didn't work.
I guess 1.6-ext is not 100% compatible with 1.5-dev, right?

True - there are some small differences in the placement of some of the header files and some other small class differences that you'll have to reconcile. If you're stuck, you'll need to share the exact error messages.

Hi Peter,

following modifications to Make/options made my compiler happy :

* variable LIB_SRC changed to FOAM_SRC
* dynamicMesh and cousins have moved
* PolyMesh constructor needs transfer function for points

################################################## ########
# File Make/options
# modifications from OpenFOAM-1.5-dev to OpenFOAM-1.6-ext
################################################## ########
#
# OpenFOAM-1.5-dev
#
EXE_INC = \
-I$(LIB_SRC)/finiteVolume/lnInclude \
-I$(LIB_SRC)/dynamicFvMesh/lnInclude \
-I$(LIB_SRC)/dynamicMesh/lnInclude \
-I$(LIB_SRC)/meshTools/lnInclude#
################################################## ########
# OpenFOAM-1.6-ext
#
EXE_INC = \
-I$(FOAM_SRC)/finiteVolume/lnInclude \
-I$(FOAM_SRC)/dynamicMesh/dynamicFvMesh/lnInclude \
-I$(FOAM_SRC)/dynamicMesh/dynamicMesh/lnInclude \
-I$(FOAM_SRC)/meshTools/lnInclude



PolyMesh constructor changed, note the xferCopy(points):

pShapeMesh = new polyMesh
(
IOobject ....,
// ================
xferCopy(newPoints),
//================
cellShapes,
boundaryFaces,
boundaryPatchNames,
boundaryPatchTypes,
defaultFacesName,
defaultFacesType,
boundaryPatchPhysicalTypes
);


I hope this will help ...

Bandfrosch

Peter,

please let us know your results. I tried to parallelize a simple two stroke engine, but found that sliding interfaces may still not cross processor boundaries. Add/remove layers was already parallel in 1.5-dev, so for that case, I did not see any difference when it comes to parallelization.

Regards,
Kalle

Thx u for all ur replys. For the moment I am very busy. But I keep u posted about my process for sure. I hope I can do it till the weekend.

hi Kalle,
I am trying to set up a case for a simple engine with moving mesh and topological changes but have not yet succeeded, would you mind sharing your setup data? (perhaps thermophysicalProperties too since it gives me some error with not implemented thermo::e() ) I would appreciate it :D

Hi,

I only moved the mesh for this case, no CFD. I think as a start you can copy the needed thermo/transport files from some of the tutorials. Maybe from soninFoam cases? Try a few, should not be too hard to locate working files.

Good luck,
K

I have some problems during the installation of OpenFOAM-1.6-ext.
Hocw can I change the environmental variable for gcc from

usr/bin/gcc to usr/gcc ?

Thx Peter

What problems specifically? An error message would be helpful.

Around line 91 of settings.csh, do you have compilerInstall set to System?

Please see attached the output of the log file.
I compiled paraview and all the other 4 stages of the thirdparty tool. Seems to work. Also I can open paraview and use paraFOAM.
When I open old cases made with 1.5-dev i can visualize it.
BUT
When I try to visualize a tutorial made by 1.6-ext it is not working :(
I tried to postprocess the icoFoam tutorial (cavity) The solver runs but it is not possible to see anything by opening with paraFoam.

Yes. It is compilerInstall set to System.

I really don't think the foamInstallationTest warnings about gcc having anything to do with your paraFoam problems. But since you have System compiler set, it looks to me like WM_COMPILER_DIR is never set. Try setting it yourself to be /usr and maybe foamInstallationTest will be happier. It will still complain about your version not matching the supplied version, but it's not clear to me why it even checks that if you have a system compiler. Anyway, like I said, I don't think that has anything to do with your paraFoam problem.

As far as your paraFoam problem, you need to tell us more than "it doesn't work". Do you get error messages? Does it crash?

The weird thing is. I don t get any error. I simply don t see my grid when I try to open the cavity case. I can see all the variables, nothing else more.
When I open a case which was made with 1.5-dev, I can see it with the 1.6-ext version (paraFoam). Probably all my versions are mixed up ?

I will reinstall my system. It s mixed up with all the the openFoam versions.. I will install Suse 11.3. I ll keep u posted about my process.

I refreshed my system. I installed Suse11.3 64 bit version.
I have a problem with stage4 of the thirdparty tools. The installaion of paraview doesn t start. I have a problem with the environmental variables. I don t know how to change the path of them.
Thx Peter

Do you have qt installed? What do you get from a 'which qmake' ? If it's /usr/bin/qmake, then you would need 'setenv QT_BIN_DIR /usr'

Hello Peter, I had a similar problem with stage4 and openSuse 11.2.

The stage4 script has commented the line to compile the qt. If this is your case, you should use the system qt, but I could not use the system version in suse, so I uncommented that line and compile qt from ThirdParty.

The compiling takes too long, but when it finish you should get the issue about the QT_DIR again. I solved it restarting the terminal and commenting again the line in stage4 script.

I hope this will help you, regards

Pablo

Hi boger.

For 'which qmake' I get /usr/bin/qmake. What do you mean by I need 'setenv QT_BIN_DIR /usr. Shall I write it in the console? If yes, I doesn't work. I don t have setenv (opensuse 11.3). I looked for it in the respiratory, but I couldn't find it, nor in the net :(

@pcaron
I know about this issue, I did one week ago. Yesterday, I have downloaded 1.6-ext again and the Allmake.stage4 seems to differ slightly. Correct me if I am wrong.

Cheers
Peter

ok, I figured out that setenv doesn t work for bash shell, so I switched to csh. When I write 'setenv QT_BIN_DIR /usr' in the csh shell nothing happens. Still not able to compile paraview. I checked the last Allmake.stage4 file and indeed it changed. There is now an if statement for the qt files. I do not want to compile it again since I have qt installed on my system. I really don t get it to set environmental variables properly.

I'd go back to your bash shell and add

export QT_BIN_DIR=/usr

to your .bashrc file, which sets the environment variable QT_BIN_DIR. After that, open a new terminal window (to be sure the environment variable gets added) and try your stage4 again. If it doesn't work, please let us know exactly what error message you get.

Out of curiosity, which version of Qt do you have? ("qmake --version" should tell you.)

I still get the same output as before, that the environmental variable QT_BIN_USR is not set properly

my version is:

QMake version 2.01a
Using Qt version 4.6.3 in /usr/lib64

Peter

I'm sorry: try

export QT_BIN_DIR=/usr/bin

Here we go :)
Thank you very much!!!!
Now it s compiling. I let u know about my progress.

Unfortunately an error occurred

Installing 'libQtWebKit4-32bit' solved that problem.

Hi Peter, I agree with you the script is slightly different. I recopiled 1.6-ext yesterday using an updated git version. To enable the ThirdParty Qt, as I did before, you must set a new variable. I typed this before execute stage4 script.
Then I could compile ThirdParty-QT. But you find out how to use the system QT, so I think this info is not relevant now ;)

Regards

Pablo

I have some troubles compiling Openfoam. Which compiler version do u use of gcc. Do you use ur system compiler or one from the ThirdParty package?

cheers
Peter

It is always better to tell us exactly what "troubles" you have run into. Do you get an error message?

Whether or not you can use your system version of gcc probably depends most on what version of gcc you have on your system. What does "gcc --version" tell you?

for foamInstallationTest, I got this


Unfortunately I ve deleted openfoam already. I am going to compile everything again. But it had same warnings concerning paraview, that some variables haven t been set properly.
What is the best way to save the output? when I simply write .Allwmake > log, i don t save all the output from the screen in it. Any suggestions.
Sorry for the poor error message. I will compile it again and change to compiler set by OpenFoam.

Didn't we already discuss this same point in a previous post? The warning you got looks like just that to me - a warning. Based on that warning, there was no reason to delete OpenFOAM.

Maybe it depends on the shell, but something like "Allwmake >& log" or "Allwmake |& tee log" should save the error messages that are written to stderr.

I recompiled everything. OpenFoam is running, paraview and paraFoam,too.
Nevertheless, I am no able to see something when I load a case (icoFoam). In the end of stage4 I got an error. Maybe this could be the reason. I don t know how to treat it..

> Nevertheless, I am no able to see something when I load a case (icoFoam).

This is rather vague....

What is the error message generated by paraview/paraFoam when you load your case?

What is the output of the following command: wmakePrintBuild

Martin

This is my output for 'wmakePrintBuild'
I dont get any error when I open paraview or load a case with paraFoam. I can enter ther GUI of paraview with both cases, but I am not able to see the grid. When I close paraview I get than

Any Idea?

I'm pretty sure this is a bug in glibc. Are you using a gcc-4.5.1 / openSuse combo?

Yes. I am using opensuse 11.3 but gcc gcc-4.5.0.
What is that mean?

Yeah.. It's a general problem with glibc and gcc-4.5.x. The shared libraries aren't unloaded properly by certain class destructors, and so the assertion gets triggered. It doesn't seem to be a major issue, if you're willing to ignore the assertion warning.

I downgraded to gcc-4.4.x, and the problem doesn't exist there. I'll go back up once they fix the issue.

Thank you very much. How can I downgrade my compiler? Just delete this one and install with yast an older one?