Académique Documents
Professionnel Documents
Culture Documents
Contents:
S.No
Topic
Page No.
10
version 2.0;
format
ascii;
class
dictionary;
object
extrudeProperties;
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
constructFrom patch;
sourceCase "$FOAM_CASE";
sourcePatches (FRONT);
exposedPatchName BACK;
extrudeModel
wedge;
sectorCoeffs
{
axisPt
axis
angle
(0 0 0.01);
(0 1 0);
1;
flipNormals false;
mergeFaces false;
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
COMMANDS:
fluent3DMeshToFoam <filename.msh>
extrudeMesh
Cons of 'extrudeMesh' utility
Creates highly non-orthogonal meshes and makes the solver crash. Not Recommended at
all.
- This is because the FRONT patch coincides exactly with coordinate plane (XY
plane, equatoion of plane is z = 0, normal vector to the plane is (0 0 1) ).
- By definition in OpenFOAM if we want axisymmetric calculations, the wedge type
patches (FRONT and BACK should straddle the coordinate plane symmetricaly ie They
have to make equal angles with the coordinate plane on either side.)
- For example, in our case we gave the wedge angle as 1 degrees. So FRONT wedge
plane should make an angle of 0.5 degrees to the coordinate plane. The BACK wedge plane
should also make 0.5 degrees with coordinate plane (on other side).
- Therefore we have to rotate the mesh. We will use 'rotateMesh' command to
achieve this.
Syntax:
rotateMesh n1
n2
n1 Current normal
n2 Normal we require
In our case
n1 = (0 0 1)
For n2 it is suggested to use the following (derived from some vector geometry)
n2 = (-sin(0.5)
0
cos(0.5))
here 0.5 degrees is half of the wedge angle (1 degree).
COMMAND:
rotateMesh (0 0 1) (-sin(0.5)
cos(0.5))
After following the procedures as in the previous section for mesh manipulation, setup the
case as above.
In the '0/T' file for temperature initial field , at the end add the following line
#includeEtc "caseDicts/setConstraintTypes"
This adds the wedge constraint for the wedge type patches.
6
'T' File
/*--------------------------------*- C++ -*----------------------------------*\
| =========
|
|
| \\
/ F ield
| OpenFOAM: The Open Source CFD Toolbox
| \\ / O peration | Version: 4.0
|
| \\ / A nd
| Web:
www.OpenFOAM.org
|
| \\/ M anipulation |
|
\*---------------------------------------------------------------------------*/
FoamFile
{
version 2.0;
format ascii;
class
volScalarField;
object
T;
}
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
dimensions
[0 0 0 1 0 0 0];
fixedValue;
uniform 300;
zeroGradient;
bottom
{
type
}
zeroGradient;
#includeEtc "caseDicts/setConstraintTypes"
}
// ************************************************************************* //
10
11
12
13
3.2 PostProcessing:
- To view results 'paraFoam' command doesn't seem to work for conjugateHeatTransfer
cases.
- We use paraview for this case.
COMMANDS
touch all.foam
paraview
// to open paraview
- In paraview interface, open the 'all.foam' file and do post processing as you wish.
14
15
Analytical Calculations
It can be seen that there is a gulf between the theoretical result of Umax and OpenFoam
result.
- The theoretical calculation assumes incompressible, non heated flow.
- But since we have heat transfer also and the use a compressible flow solver, the density of
the fluid near the walls is lowered due to heating, and hence the mass flux near the walls is
also lowered.
- To maintain continuity these mass fluxes will be pushed outward (towards the axis of
pipe), and hence the velocity near the axis increases. This explains the difference between
theoretical and analytical solution.
16
Analytical Solution:
17