July 15, 2019, 00:45
|
boundaryWallFunctionsProfile allowable modifications for generation of 'y+'
|
#1
|
Member
Ash Kotwal
Join Date: Jul 2016
Location: North Dakota, USA
Posts: 84
Rep Power: 8
|
Hello,
I'm thinking of changing the following code:
Code:
/*--------------------------------*- C++ -*----------------------------------*\
========= |
\\ / F ield | OpenFOAM: The Open Source CFD Toolbox
\\ / O peration | Website: https://openfoam.org
\\ / A nd | Version: 6
\\/ M anipulation |
\*---------------------------------------------------------------------------*/
FoamFile
{
version 2.0;
format ascii;
class volScalarField;
location "0";
object epsilon;
}
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
dimensions [0 2 -3 0 0 0 0];
internalField uniform 1e-08;
boundaryField
{
lowerWall
{
type epsilonWallFunction;
value $internalField;
}
upperWall
{
type epsilonWallFunction;
value $internalField;
}
front
{
type cyclic;
}
back
{
type cyclic;
}
defaultFaces
{
type empty;
}
}
// ************************************************************************* //
So, in the above code instead of 'cyclic' boundary conditions, is it possible to use flow velocity as inlet and outlet boundary conditions?
In other words, change the boundary conditions in U file in following way:
Code:
/*--------------------------------*- C++ -*----------------------------------*\
========= |
\\ / F ield | OpenFOAM: The Open Source CFD Toolbox
\\ / O peration | Website: https://openfoam.org
\\ / A nd | Version: 6
\\/ M anipulation |
\*---------------------------------------------------------------------------*/
FoamFile
{
version 2.0;
format ascii;
class volVectorField;
location "0";
object U;
}
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
dimensions [0 1 -1 0 0 0 0];
internalField uniform (1 0 0);
boundaryField
{
lowerWall
{
type noSlip;
}
upperWall
{
type noSlip;
}
front // so change this 'cyclic' BC to inlet and outlet velocity condition
{
type fixedValue;
value ( 1 0 0 );
}
back
{
type fixedValue;
value ( 1 0 0 );
}
defaultFaces
{
type empty;
}
}
// ************************************************************************* //
is it possible to do that?
Can anyone explain 'cyclic' boundary condition is governing the entire model?
|
|
|