Having a look into the new sol
 

Having a look into the new solver interDyMFoam of OF-1.5, I have just realised that the effective viscosity muEff in the UEqn.H file has not been defined according to twoPhaseProperties.muf() + fvc::interpolate(rho*turbulence->nut()).

Should we replace the UEqn.H file in interDyMFoam with the one in rasInterFoam and recompile the solver?

Cheers, Patricio

interDyMFoam is setup for lami
 

interDyMFoam is setup for laminar flow. If you want to use it for turbulent flow simply transfer the turbulence model parts from either rasInterFoam for RAS or lesInterFoam for LES.

H

Thanks for the explanation Hen
 

Thanks for the explanation Henry, and for the new release OF-1.5.

(The following lines in interDyMFoam.C were confusing me
#include "incompressible/RASModel/RASModel.H"
turbulence->correct();)

Good point, thanks for bringin
 

Good point, thanks for bringing it to my attention. This application was in a state of flux before release and we have been developing a better version which will be included in the next OpenFOAM release. For now I agree with your proposal of adding the turbulent part of the viscosity in UEqn.H and then switch to the "laminar" turbulence model to run laminar. I will make this change here also.

Thanks again

H

hello, everyone. i have a q
 

hello, everyone.

i have a question that how the variables are updated when the dynamic mesh is changed.

in the dynamic mesh solver "icoDyFoam.C", after the mesh is changed, the code calls the following commands:


bool meshChanged = mesh.update();

if (meshChanged)
{
........
# include "correctPhi.H"
........
}

in the "correctPhi.H", a Poission equation of pcorr is defined as the following:

fvScalarMatrix pcorrEqn
(
fvm::laplacian(rUA, pcorr) == fvc::div(phi)
);

I know that the phi has been made the flux absolute before the mesh is updated, and made the flux relative after the mesh is updated.

My question is about the rUA in the left hand of this equation. I think that the rUA was calculated from the "UEqn.H" at the last time step. if so, where has the rUA been updated after the mesh is changed. If the new cells happened due to the mesh motion, what is the rUA at the new cells?

I hope someone can help me even if this is a stupid question.

by the way, I am also troubling with the mechnism for the phi update. someone can suggest me the references about the dynamics mesh?


Thanks!

ZHAO

rUA only needs to be approxima
 

rUA only needs to be approximate for pcorr, in fact choosing 1 will also work fine. If the mesh moves without topology change rUA is unchanged but with topology change it is mapped automatically to the new mesh.

H

Thanks you very much,Henry.
 

Thanks you very much,Henry.

Another question for icoDyMFoam.C in OF-1.5. in gammaEqn.H, there are the following commands:

............
surfaceScalarField phiGamma =
fvc::flux
(
phi,
gamma,
gammaScheme
)
+ fvc::flux
(
-fvc::flux(-phir, scalar(1) - gamma, gammarScheme),
gamma,
gammarScheme
.............

I think that the fvc::flux(phi, gamma, gammaScheme) is obtained from the old ( the last time step) gamma field at the center of the changed mesh. Is it right?

I am wondering whether this old gamma at the center of the changed mesh is unchanged when the mesh moves without topology change, and it is mapped automatically to the new mesh with topology change.

If a scalar or vector field is defined similarly to the gamma or velocity field in the createFields.H, this user-defined field is also mapped automatically to the new mesh with topology change?

Thanks!

ZHAO

All fields registered with the
 

All fields registered with the database are automatically mapped to the new mesh following mesh topology change and are unchanged without topology change as required by the Lagrangian-Eulerian time-space discretization used for moving meshes.

H

Hello All: I am trying to r
 

Hello All:

I am trying to run the tank sloshing 2D case under interDymFoam. Is any documentation available like the other tutorials. There isnt one with the documentation for OpenFOAM 1.5.

Thanks

Musaddeque: (and OpenCFD folks
 

Musaddeque: (and OpenCFD folks!)

The Allrun script in the sloshingTank2D tutorial contains the commands needed to make the case run.

Problem is that the m4 template blockMeshDict.m4 is broken: "format" is probably a reserved word (?) in m4, and needs to be quoted in line 11! Note the shape of the quotes: `format' (see m4 manual for details...)

With this fixed, I could run the tutorial using the Allrun script.

/Ola

PS: corrected blockMeshDict.m4 is attached...

http://www.cfd-online.com/OpenFOAM_D...hment_icon.gif blockMeshDict.m4

Ola: What does the ".m4" ex
 

Ola:

What does the ".m4" extension at the end of the blockMeshDict.m4 imply? Is this specific to OpenFOAM? or do I need something else. Sorry for being so ignorant.

Musa

Hi Musa! The .m4 means that
 

Hi Musa!

The .m4 means that you should replace it with the corresponding .m4 in that tutorial case. If you have a look at the Allrun-file in that case and then type "man m4" on your command line the purpose of this file should become obvious. And "No": m4 is not OpenFOAM-specific. Unless the classic sendmail is also part of OpenFOAM

Ola, Over the many years I
 

Ola,

Over the many years I have been using m4 with blockMesh I have never come across the problem you are seeing with the "format" keyword. I need to investigate this further before making the change you suggest in all the .m4 files in the tutorials.

Which OS are you running on?
Which version of m4?

Thanks
H

Hi Henry, The server runs S
 

Hi Henry,

The server runs SUSE Linux Enterprise Server 10, SP2. GNU m4 version is 1.4.4.

I enclose the blockMeshDict of the slochingTank2D tutorial, produced before my extra quotes. I also enclose the output from the dumpdef command in m4. "format" is defined there, from where I don't know.

Please keep me posted on your conclusions.

Best regards,
Ola

http://www.cfd-online.com/OpenFOAM_D...hment_icon.gif blockMeshDict.org
http://www.cfd-online.com/OpenFOAM_D...s/mime_txt.gif dumpdef.txt

Hi again, The m4 'format' b
 

Hi again,

The m4 'format' built-in is described in the manual for GNU m4 1.4.6. It is described in Section 15.1 as a GNU extension to m4. It also says that all GNU extensions can be suppressed with the '-G' option to m4.

I wouldn't be surprised if the GNU extensions can be suppressed already at compilation of m4, which would explain why it's distro specific.

/Ola

I am running GNU m4 1.4.6 on S
 

I am running GNU m4 1.4.6 on SuSE 10.2 and at appears that the -G option is set by default, well at least the blockMeshDict of the slochingTank2D tutorial runs through correctly.

However if using `format' will allow the .m4 files in OpenFOAM to operate correctly with the GNU extensions I am happy to make the change and will push the updated files into our git repository.

H

Ola: Many thanks for your r
 

Ola:

Many thanks for your response. I ran the Allrun for tank sloshing problem for 2D and 3d and things worked ok - even paraview didnt crash!. I did not have to replace the blockMeshDict file with the one you sent. I am running OpenFoam 1.5 on Suse 11.

Musa

I would appreciate it if someo
 

I would appreciate it if someone could tell me how to provide a sinusiodal swaying to the 2d tank sloshing problem. I am trying to model a case where a tank of fluid is subject to some oscillation Asin(2*pi8t/T). Does OpenFoam have a facility where the since wave source can be plugged in and processed for the solvers to pick up.

Musa

Have you looked at the slos
 

Have you looked at the

sloshingTank2D
sloshingTank2D3DoF
sloshingTank3D
sloshingTank3D3DoF

tutorial cases?

H

Henry: I looked at the slos
 

Henry:

I looked at the sloshingTank2D case and tried to modify the control dictionary such that there is only swaying and no roll or heave, thus:

// Centre of gravity
CofG (0 0 0);

// Model scale ratio
// lamda 50;
lamda 50;

// Max roll amplitude [rad]
//rollAmax 0.22654;
rollAmax 0.0;

// Min roll amplitude [rad]
//rollAmin 0.10472;
rollAmin 0.0;

// Heave amplitude [m]
//heaveA 3.79;
heaveA 0.0;

// Sway amplitude [m]
//swayA 2.34;
swayA 2.5;

// Damping Coefficient [-]
Q 0.010;

// Time Period for liquid [sec]
Tp 1.27;

// Natural Period of Ship [sec]
Tpn 11.93;

// Reference time step [sec]
dTi 0.059;

// Incr. in Tp/unit 'dTi'[-]
dTp -0.001;
I left the other parameters intact. The solution ran for 3 hours before I terminated the process. Any suggestions as to how I can do that? I look forward to your response.