[luckyluke]

FOAM has a solver named 'interFoam' for 2 incompressible fluids, in which the VOF method was used. Has the 'Fornt tracking method' for interface simulation been done by FOAM?

Thank you. Thank the FOAM.

[hjasak]

Yes, front tracking has been done in a recent PhD from Dr. Zeljko Tukovic at the University of Zagreb. His Thesis is currently beign translated to English and we are working on the integration of his changes into FOAM and a couple of tutorials.

The latest news I've got is that most of the work is done. The release schedule depends on tutorials/code merge, but it should be within the next version or two.

You can find the Thesis, some pictures and presentations with Zeljko's work on my private web site (this will get moved somewhere more sensible soon - apologies for the delay).

Enjoy,

Hrv

[luckyluke]

Oh my God. I was just working on my front tracking method with some new features in Fortran language and plan to do it using OpenFOAM.

Then, Jasak, when will the code provided by Dr. Zeljko Tukovic be placed into new version
of FOAM? With Zeljko's help, I will do my own job easily.

Thank FOAM.

[luckyluke]

Hi, prof. Jasak. Has the merging and breakup been considered by Dr. Zeljko Tukovic's surface tracking technique with moving meshes? It seems to be hard.

[hjasak]

Nope currently, just mesh deformation. In principle, I've got support for the detachment/reattachment algorithim for the mesh (through the morph engine) and there are people who are doing it already.

As far as I know, this reduces to the problem of automatic mesh generation and foam is a bit thin on that side at the moment. The two options are a good cut-mesh algorithm with a dynamically moving STL surface or a tet cell remeshing support (edge swap + smoothing + other stuff I know very little about). I am planning to have a go at the second one (don't hold your breath, it won't happen for at least a year) and tomorrow I am talking to some people who are already doing the first one. If we're lucky, there may be some possibilities...

Keep your fingers crossed,

Hrv

[nimasam]

hi dear jassak
im interesting to know does front tracking method finally add to open foam or not ?

[HectorRedal]

Hi,

I would like to know if front tracking code has been implemented in OpenFoam.

Do you have any information about this?

Best regards,
Hector.

[deepsterblue]

Yup. This has been done. I've extended Zeljko's stuff (freeSurface/interTrackFoam) to include mesh-motion / topology changes.

[HectorRedal]

Hello deepsterblue,

First of all, I would like to thank you for your quick response.

Also, I would like to ask you if interTrackFoam is part of the standard OpenFoan version.

Best regards,
Hector.

[deepsterblue]

It's available in 1.6-ext

[HectorRedal]

Can be 1.6-ext installed in OpenFoam realese?
Where can I find the 1.6-ext software?
Is it freeware?

Thanks.

[pbohorquez]

Just download and link it

git clone git://openfoam-extend.git.sourceforge.net/gitroot/openfoam-extend/openfoam-extend

[akidess]

Hector, also see http://openfoamwiki.net/index.php/Ma...ions_differ.3F for a quick explanation of the various versions.

[HectorRedal]

Hi,

I have managed to download OpenFoam-ext v1.6,
Previously to have downloaded OpenFoam-ext, I already have an installed version of openFoam.
The installed version is OpenFoam 1.7.1.

To install OpenFoam-ext, should I remove my previous openfoam installation?
Could I upgrade my OpenFoam version with the OpenFoam-ext version?

Is there any help guide I can use?

Thanks in advance.

Hector.

[nimasam]

you dont need to clean previous installation just change the variable source in .bashrc file

[HectorRedal]

I have changed the variable source in the the .bashrc file:

. /home/hector/OpenFOAM-1.6-ext/etc/bashrc

What's the next step I should perfom?

Should I compile it?

[nimasam]

be careful! you should make previous installation source in .bashrc deleted or commented with #
if you use the binary version you dont need to compile it , if not! you should compile it!
./Allwmake

[gwierink]

Just a simple alias in bashrc does the trick. Put the following in ~/.bashrc:

alias of16ext='. /home/hector/OpenFOAM-1.6-ext/etc/bashrc'
alias of171='. /home/hector/OpenFOAM-1.7.1/etc/bashrc'

and source it by typing

. ~/.bashrc

(note the dots!). Then, you can invoke OpenFOAM-1.6-ext by typing

of16ext

and OpenFOAM-1.7.1 by

of171

[HectorRedal]

Hi,

I would like to thank you for your help and support.

I have managed to write down all the suggestions you had made to me, and I have manage to compile OpenFoam 1.6-ext, including the third party products.

But, there is an error that appears in the compilation, that I cannot resolve.

+ wmake libso MGridGenGamgAgglomeration
SOURCE=MGridGenGAMGAgglomerate.C ; g++ -m32 -Dlinux -DWM_DP -Wall -Wextra -Wno-unused-parameter -Wold-style-cast -O3 -DNoRepository -ftemplate-depth-40 -I/home/hector/OpenFOAM-1.6-ext/src/finiteVolume/lnInclude -I/Lib -I/IMlib -IlnInclude -I. -I/home/hector/OpenFOAM-1.6-ext/src/OpenFOAM/lnInclude -I/home/hector/OpenFOAM-1.6-ext/src/OSspecific/POSIX/lnInclude -fPIC -c $SOURCE -o Make/linuxGccDPOpt/MGridGenGAMGAgglomerate.o
MGridGenGAMGAgglomerate.C:36:25: error: mgridgen.h: No existe el fichero o el directorio
MGridGenGAMGAgglomerate.C: In member function ‘Foam::tmp<Foam::Field<int> > Foam::MGridGenGAMGAgglomeration::agglomerate(Foam: :label&, Foam::label, Foam::label, const Foam::lduAddressing&, const Foam::scalarField&, const Foam::vectorField&, const Foam::scalarField&)’:
MGridGenGAMGAgglomerate.C:164: error: ‘MGridGen’ was not declared in this scope
make: *** [Make/linuxGccDPOpt/MGridGenGAMGAgglomerate.o] Error 1
+ wmake libso engine
'/home/hector/OpenFOAM-1.6-ext/lib/linuxGccDPOpt/libengine.so' is up to date.
+ wmake all solvers

Is there any thread I can take a look at, to fix this issue?

I have been looking for any one, but unsuccessfully, I didn't find anyone.

Thanks in advance,
Hector.

[HectorRedal]

Hi,

I would like to know if your implementation has followed some article: for example, a contribution to International Journal of Fluids.

I am wondering if it can be easily extended, and in such a case, I was wondering how I can contribute to this.

Thanks in advance.

Hector Redal.