CFD Online Discussion Forums - 32bit version of 01_05

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)

- OpenFOAM Running, Solving & CFD (https://www.cfd-online.com/Forums/openfoam-solving/)

- - 32bit version of 01_05_2007 development release (https://www.cfd-online.com/Forums/openfoam-solving/58946-32bit-version-01_05_2007-development-release.html)

Hello Hrv, A Good day to yo

Hello Hrv,

A Good day to you!

Just a few days ago I upgraded my system to Fedora 7, and would like to install the latest development release of OpenFOAM 1.3.

On checking the Powerlab FTP site, I found that you have posted a development version dated 01-05-2007. Unfortunately, I have a Centrino 1.6 GHz system, and cannot use the AMD64 version available on the FTP server.

Would it be possible for you to also post the 32-bit precompiled version of this development release?

Thanks in advance, and have a lovely day!

Philippose

What's this development versio

What's this development version?

Regards,
Alberto

Hi Philiposse, I would reco

Hi Philiposse,

I would recommend you re-compile it yourself. It comes with a complete source and the actual process is not too hard.

Hrv

Alberto, if you browse here: h

Alberto, if you browse here: http://powerlab.fsb.hr/ped/kturbo/OpenFOAM/release/
you can find some develop version of OF.

Francesco

Hello again Hrv, No problem

Hello again Hrv,

No problem :-)! I was just looking for the easier way out :-)! I am sure you are quite busy with the upcoming workshop at Zagreb (Was actually considering taking part....maybe next year).

Shall recompile the development version 01/05/2007 this evening.

Have a nice day! And have a ball of a time at the workshop :-)!

Philippose

Thanks Francesco, I just want

Thanks Francesco,
I just wanted to understand how this development version is related to the official one from OpenCFD.

I saw it's still 1.3, so is it a sort of fork?

With kind regards,
Alberto

This is the development versio

This is the development version I and my colleagues and students contribute to and work on. In fundamentals it is compatible with whatever the base number is but it has got considerably expanded capabilities, it is debugged and maintained. I am currently moving the work to the 1.4 base to preserve the continuity of merging. Foir illustration, a list of additions/merges from my notes so far is:

1) Added applications:

simple solvers
- boussinesqBuoyantFoam
- barotropicCavitatingFoam
- icoFoamLagrangian
- icoMeshMotionFoam
- transientSimpleFoam
- transientSimpleOodles
- contactStressFoam (remove?)
- stressFemFoam

surfaceTracking suite
- interTrackFoam
- surfactantFoam
- sloshingInterTrackFoam
- bubbleInterTrackFoam

newStressAnalysis suite
- materialModels
- newContactStressFoam
- newStressedFoam

complete finite area library

complete FEM solver utilities

complete liftDrag implementation

2) Added utilities

interFoamPressure
simpleFoamResidual

dxFoamExec
foamToDX

liftDrag
solidStress

makeFaMesh
star4ToFoam - from user group contribution
tetDecomposition

new tutorials:

boundaryFoam/boundaryTwoWallsFlowSolution
boussinesqBuoyantFoam/heatedCavity
barotropicCavitatingFoam/nozzle (simple model)
contactStressFoam/ballAndBrick
icoDyMFoam/mixer2D
icoDyMFoam/movingConeMotion
icoDyMFoam/movingConeTopo
icoLagrangianFoam/channelParticles
interTrackFoam/hydrofoil

newContactStressFoam/ballAndBrickFriction
newStressedFoam/plateHole
scalarTransportFoam/swirlTest
stressedFoam/plateHole
stressFemFoam/plateHole
surfactantFoam/surfactantTransport
twoLiquidMixingFoam/twoStream

new classes:

dynamic meshes
- dynamicBodyFvMesh
- dynamicBoxFvMesh
- mixerGgiFvMesh
- subsetMotionSolverFvMesh

engine
- tetDecompositionEngineMesh
- simpleEngineTopoFvMesh
- engineTopoChangerMesh

fvPatch
- ggiInterfaceFvPatch

fvPatchFields
- directionMixed
- fixedMeanValue
- ggiInterfaceFvPatchField
- parabolicVelocity

discretisation
- beGaussGrad

interpolation
- pointVolInterpolation
- edgeCorrectedVolPointInterpolation

ODE
- Euler solver

OpenFOAM
- dense matrix tools

Point patch fields
- OscillatingFixedValue

Meshes
- ggiInterfacePointPatch
- regionCouplePointPatch

- ggiInterfacePolyPatch
- regionCouplePolyPatch

Thermophysical
- physical constants

topoChangerFvMesh
- attachDetachFvMesh

This should give you a basic idea of what's going on - more on the Workshop in Zagreb.

Hrv

Thanks for your answer Hrvoje.

Thanks for your answer Hrvoje.

There's a lot of interesting stuff there!

What I don't understand is why there are two separate development trees and there's not a unified SVN archive for example at SourceForge, where also external contribution can be submitted.

In this way OpenCFD and you (it seems you're not working together anymore, right?) could merge the different contributions in a easier way, and also users would have a single reference site.

Just my opinion.

With kind regards,
Alberto

Hrv: If I want to simulate

Hrv:

If I want to simulate 3D bubble rise in a channel, would I use the interTrackFoam or the bubbleInterTrackFoam solver? Basically, what is the difference between the two?

Thanks!

Heya, The basic algorithm b

Heya,

The basic algorithm between the two is the same. the bubbleInterTrackFoam has got some additional features necessary for the bubble simulation:

handling for a non-inertial reference frame for ths similation: the mesh moves with the bubble centroid, which needs to be accounted for in various forces
handling of the inlet boundary condition; same as above
special correction for closed domains: you have to preserve the bubble fluid mass to machine tolerance; otherwise the pressure equation has no solution

Hope this helps,

Hrv

Thanks Hrv. Is there are sampl

Thanks Hrv. Is there are sample tutorial for the bubbleInterTrackFoam solver. I could not find one in the devel-release. Thanks again for your help.

Hrv: Can I get a copy of the m

Hrv: Can I get a copy of the mrfproperties file that is needed when I try to run bubbleInterTrackFoam.

Also, why does transientSimpleFoam need a PISO entry in the fvSolution dictionary?

Hello Srinath, A Good eveni

Hello Srinath,

A Good evening to you!

I dont know if you have already found the answer to your question as to why "transientSimpleFoam" needs the PISO entry in the fvSolution dictionary instead of the SIMPLE entry.

Basically, if you look into the code of the transientSimpleFoam solver, you find that it performs a corrector loop, which requires the number of correctors to be obtained from the user.

Now... if you look at the "readPISOControls.H" and the "readSIMPLEControls.H" files, you see that "readPISOControls.H" is basically a superset of "readSIMPLEControls.H"..... it looks up all the values which the SIMPLE solver needs, and in addition, also reads in the number of correctors (along with some more stuff).

One other thing you need to add to the fvSolution file for a case solved using the "transientSimpleFoam" solver, would be the sub-dictionary for the relaxation factors.

Enjoy!

Philippose

Thanks for the explanation Phi

Thanks for the explanation Philippose. But doesn't SIMPLE use just one corrector? Or are you referring to non-orthogonal correctors? BTW how is turbForceFoam shaping up?

It's just a naming problem. tr

It's just a naming problem. transientSimpleFoam just re-uses the original readPISOControls.H so that it is possible to set nCorr, which is the maximum number of iterations for each time step.

Håkan.

Hi, Håkan Nilsson: I just w

Hi, Håkan Nilsson:

I just wonder should the nCorr be the same value (which is 2) as the PISO solver? Is the maximum number of iterations for each time step = 2?

Hi Hrvoje Where can i find

Hi Hrvoje

Where can i find the sources for foamToDx...?

I can't find them inside OpenFOAM-1.4.1-dev install...

Alex

Check this: ~/OpenFOAM-1.4.1-d

Check this:

~/OpenFOAM-1.4.1-dev/applications/utilities/postProcessing/dataConversion/foamTo DX

Dragos

Both are in the SVN: dxFoam

Ok Hrv, here it is... I cha

Ok Hrv, here it is...

I changed to ~/OpenFOAM/OpenFOAM-1.4.1-dev/applications/utilities/postProcessing/dataConversi on/foamToDX

%wmake&&wclean
%cd $FOAM_RUN
%ls -l

drwxr-xr-x 16 root root 4096 2008-04-18 13:30 simpleV33M_HF3
drwxr-xr-x 8 root root 4096 2008-04-17 23:26 simpleV33M_HS5c
drwxr-xr-x 55 root root 4096 2008-04-10 02:04 tutorials

%foamToDX . simpleV33M_HF3

ends like this

/*---------------------------------------------------------------------------*\
| ========= | |
| \ / F ield | OpenFOAM: The Open Source CFD Toolbox |
| \ / O peration | Version: 1.4.1-dev |
| \ / A nd | Web: http://www.openfoam.org |
| \/ M anipulation | |
\*---------------------------------------------------------------------------*/

Exec : foamToDX . simpleV33M_HF3
Date : Apr 18 2008
Time : 13:30:41
Host : iskandhar
PID : 15617
Root : /root/OpenFOAM/root-1.4.1-dev/run
Case : simpleV33M_HF3
Nprocs : 1
Create time

Create mesh for time = 6

--> FOAM FATAL ERROR : Wrong number of vertices in cell
expected 4,5,6,7 or 8, found 0

From function foamToDX
in file writeDXgrid.H at line 89.

FOAM aborting

Aborted (core dumped)

The prob seems to be in writeDXgrid.H, or in some dependency before...

The mesh is a small one, just to test simpleFoam fvSolution settings for convergence in a difficult case; it was created in Harpoon, Hexahedral dominated mesh, meaning cells with 4 and 6 nodes, with fast expansion ratio.

%checkMesh . simpleV33M_HF3

/*---------------------------------------------------------------------------*\
| ========= | |
| \ / F ield | OpenFOAM: The Open Source CFD Toolbox |
| \ / O peration | Version: 1.4.1-dev |
| \ / A nd | Web: http://www.openfoam.org |
| \/ M anipulation | |
\*---------------------------------------------------------------------------*/

Exec : checkMesh . simpleV33M_HF3
Date : Apr 18 2008
Time : 13:40:45
Host : iskandhar
PID : 15654
Root : /root/OpenFOAM/root-1.4.1-dev/run
Case : simpleV33M_HF3
Nprocs : 1
Create time

Create polyMesh for time = constant

Time = constant

Mesh stats
points: 169325
edges: 491479
faces: 473517
internal faces: 437339
cells: 151364
boundary patches: 7
point zones: 0
face zones: 0
cell zones: 0

Number of cells of each type:
hexahedra: 118879
prisms: 4318
wedges: 0
pyramids: 11383
tet wedges: 0
tetrahedra: 6337
polyhedra: 10447

Checking topology...
Boundary definition OK.
Point usage OK.
Upper triangular ordering OK.
Topological cell zip-up check OK.
Face vertices OK.
Face-face connectivity OK.
Number of regions: 1 (OK).

Checking patch topology for multiply connected surfaces ...
Patch Faces Points Surface
ascii 27399 25675 ok (not multiply connected)
Farfield_maxx 169 196 ok (not multiply connected)
Farfield_minx 169 196 ok (not multiply connected)
Farfield_maxy 702 770 ok (not multiply connected)
Farfield_miny 3140 3382 ok (not multiply connected)
Farfield_maxz 702 770 ok (not multiply connected)
Farfield_minz 3897 4473 ok (not multiply connected)

Checking geometry...
Boundary openness (3.33821e-17 -6.19233e-16 2.64655e-16) OK.
This is a 3-D mesh
Domain bounding box: (-9.99999 -0.694117 0) (9.99999 4.01176 4.70588)
Max cell openness = 2.11652e-16 OK.
Max aspect ratio = 17.6831 OK.
Minumum face area = 3.24275e-05. Maximum face area = 0.195367. Face area magnitudes OK.
Min volume = 1.12067e-07. Max volume = 0.0711076. Total volume = 440.802. Cell volumes OK.
Mesh non-orthogonality Max: 82.6217 average: 9.61819
*Number of severely non-orthogonal faces: 6.
Non-orthogonality check OK.
<<Writing 6 non-orthogonal faces to set nonOrthoFaces
Face pyramids OK.
Max skewness = 1.42469 OK.
Min/max edge length = 0.00518645 0.536765 OK.
All angles in faces OK.
Face flatness (1 = flat, 0 = butterfly) : average = 0.999956 min = 0.970839
All face flatness OK.

Mesh OK.

End

Obs. I will buy this tiny little book called c++ for dummies..( that is what i am ... :-) ) just to see if i can start understanding the inner works of OpenFOAM...

It is a powerfull and user friendly tool, but it chooses carefully who its friends are... :-D and i am not (yet) a c++ guru... :-)

in the mean time what can i do to get foamToDX to work?

Do i need to change some c file, use a different mesh ( pure tetrahedrical ) ?

Thanks in advance

Alex