Solving Engineering Tasks: SOLIDWORKS Flow Simulation 2015
Solving Engineering Tasks: SOLIDWORKS Flow Simulation 2015
ii
Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
2 Steam. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Physical model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Example of use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3 Humidity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Physical model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Example of use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
4 Real Gases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Physical model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Example of use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
5 Rotation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Physical model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Local Rotating Region(s) (Averaging) - Additional Information . . . . . . . . . . . . . 3-21
Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Global Rotating Reference Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Local Rotating Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Examples of Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Introduction
The most common problem, which almost every engineer faces every day, is to design a
device or process with the desired parameters, having only limited resources both for the
design effort itself and for the resulting device or process operation. Various tools and
methods are used to solve this problem.
Flow Simulation can help the engineer to predict and optimize fluid flows and heat
transfer in a wide variety of applications, and makes solving the engineering problems
easier and faster.
In general, there are three approaches to solving engineering problems:
• an experimental approach: a hardware rig or prototype, i.e., the full-scale object
and/or its model, is manufactured and the experiments needed for designing the
object are conducted with this hardware;
• a computational approach: the computations needed for designing the object are
performed and their results are directly used for designing the object, without
conducting any experiments;
• a computational-experimental approach combines computations and
experiments (with the manufactured full-scale object and/or its model) needed for
designing the object; their sequence and contents depend on the solved problem and
iterative procedures may be run.
Each of the first two approaches has advantages and disadvantages.
The purely experimental approach, being properly conducted, does not require additional
validation of the obtained results, but is very expensive, even if it is performed on the
object models, since testing facilities and hardware are required anyway. Moreover, if the
object models are tested, the obtained results must be scaled to the full-scale object, so
some computations are still involved.
1-2
Correspondingly, the computational codes differ from each other not only in their cost, but
also in the accuracy of the mathematical simulation of physical problems, as well as in the
procedure of specifying the initial data, in the amount of the user time needed for this
specification, in the procedure of solving a problem and the computer memory and CPU
time needed for obtaining a solution of the required accuracy, and in the procedures of
processing and visualization of the obtained results and the user time needed for that.
Naturally, a highly accurate solution requires a fine computational mesh, and,
consequently, substantial computer memory and CPU time, as well as, in some cases,
increased user time and efforts for specifying the initial data for the calculation. As the
result, if the time needed to solve an engineering problem with a computational code
exceeds some threshold time, then either the engineering problem becomes irrelevant (for
instance, because your competitors have outpaced you by that time), or alternative
approaches, which may be not so accurate, but are surely faster, are used instead to solve
the problem within given time limits.
Before getting acquainted with the recommended procedure of obtaining a reliable and
accurate solution of an engineering problem with Flow Simulation, it is expedient to
consider Flow Simulation features governing the below-described strategy of solving
engineering problems with Flow Simulation.
Since Flow Simulation is based on solving time-dependent Navier-Stokes equations,
steady-state problems are solved through a steady-state approach. To obtain the
steady-state solution quicker, a method of local time stepping is employed over the
computational domain considered. A multigrid method is used for accelerating the
solution convergence and suppressing parasitic oscillations. The computational domain is
designed as a parallelepiped enveloping the model with planes orthogonal to the axes of
the Cartesian Global coordinate system of the model. The computational mesh is built by
dividing the computational domain into parallelepiped cells with its sides orthogonal to
the Global coordinate system axes. (The cells lying outside the fluid-filled regions and
outside solids with heat conduction specified do not participate in the calculations).
Procedures of the computational mesh refinement (splitting) are used to resolve the model
features better, such as high-curvature surfaces in contact with fluid, thin walls surrounded
by fluid, narrow flow passages (gaps), and the specified insulator boundaries. During the
calculation the computational mesh can be refined additionally (if that is allowed by the
user-defined settings) to better resolve the high-gradient flow and solid regions revealed in
the calculation (Solution-Adaptive Meshing).
Since steady-state problems are solved in Flow Simulation through the steady-state
approach, it is necessary to determine the termination moment for the calculation properly.
If the calculation is finished too early, when the steady state solution has not been attained
yet, then the obtained solution can depend on the specified initial conditions and so be not
very reliable. On the contrary, if the calculation is finished too late, then some time is
wasted. To optimize the termination moment for the calculation and to determine physical
parameters of interest (such as a force acting on a model surface, or a model hydraulic
resistance) with a sufficient accuracy, you can specify them as the calculation goals.
It is necessary to remember that a fast but inaccurate beginning will cost you more efforts
and time spent not only for specifying the initial data, but, even worse, for the subsequent
calculations, until they finally become reliable. Therefore, we strongly recommend that
you carefully read this section.
1-4
example, a corrugated model surface which will result in an exceedingly large
number of mesh cells required to resolve it can be specified instead as a smooth
surface with equivalent wall roughness. If the model has narrow fluid-filled blind
holes, whose influence on the overall flow pattern is, by rough estimate, barely
perceptible, it would be better to remove these features in order to avoid the
excessive mesh splitting around them.
• to add auxiliary parts to the model such as inlet and outlet tubes for stabilization of
the flow, lids to cover the inlet and outlet openings, and parts to denote rotating
regions, local initial meshes or other areas where special conditions are applied.
All these actions, being executed properly, can be very pivotal in obtaining a reliable and
accurate solution. On the contrary, adding auxiliary parts to a model will inevitably cause
an increase of the computational mesh cells and, consequently, the required computer
memory and CPU time, therefore these parts dimensions must be adequate to the stated
problem.
If a model has not been created yet, it is expedient to consider all the above-mentioned
factors when creating it.
If all effects of these actions are not clear enough, it can be worthwhile to vary the model
parts and/or their dimensions in a series of calculations in order to determine their
influence on the obtained solution.
Then, in accordance with the problem physical features revealed and adapted to Flow
Simulation capabilities, the basic part of the Flow Simulation project is specified: the
problem type (internal or external), fluids and solids involved in the problem, physical
features considered (such as heat conduction in solids, time-dependent analysis,
gravitational effects, etc.), boundaries of the calculation domain, initial and boundary
conditions, and, if necessary, fluid subdomains, rotating regions, volume and/or surface
heat sources, fans and other features and conditions.
The specified boundary conditions, as well as heat sources, fans, and other conditions and
features must correspond to the statement of the physical problem and must not conflict
with each other.
Eventually, you specify the physical parameters of interest as the Flow Simulation project
goals. They can be local or integral, defined within the whole computational domain or in a
certain volume, on a surface or in a point. The parameters determined over some region are
expressed in the form of their minimum, or maximum, average, or bulk average values. This
allows you to increase the reliability and accuracy of determination of these parameters,
since the goal values are saved on each iteration during the calculation and can be analyzed
later. On the contrary, the convergence behavior of the parameters not specified as goals
cannot be analyzed afterwards, as they are saved only at the last iteration and, optionally, at
the user-specified iterations in transient simulations.
As soon as you have specified the basic part of the Flow Simulation project that is unlikely
to be changed in the subsequent calculations, the next step is to select the strategy of
solving the engineering problem with Flow Simulation to obtain a reliable and accurate
solution of the problem.
1-6
An additional item in this strategy of solving an engineering problem with Flow
Simulation consists in varying the auxiliary elements added to the model as needed to
solve the problem with Flow Simulation (such as inlet and outlet tubes attached to the inlet
and outlet openings, for internal problems), the dimensions of which are questionable
from the standpoint of their necessity and sufficiency. Those physical parameters of the
engineering problem, whose values are not known exactly and which, in your opinion, can
influence the problem solution, must be varied also. When performing these calculations,
there is no need to investigate the solution-vs.-mesh convergence again, since it has
already been achieved before. It is enough to just perform these calculations with the
project mesh settings that provided the solution with satisfactory accuracy during the
solution-vs.-mesh convergence investigation. The same applies also to the parametric
engineering calculations where you change the model geometry and/or flow parameters.
However, you must keep in mind the potential necessity for checking the
solution-vs.-mesh convergence, because in doubtful cases it must be checked again.
In spite of the apparent simplicity of the proposed strategy, its full implementation is
usually troublesome due to the substantial difficulties including, first of all, a dramatic
increase in the requirements for computer memory and CPU time when you substantially
increase the number of cells in the computational mesh. Since both the computer memory
and the time for which the engineering problem must be solved are usually restricted, the
specific implementation of this strategy eventually governs the accuracy of the problem
solution, whether it will be satisfactory or not. Perhaps, a further simplification of the
model and/or reducing the computational domain will be required.
Some specific description of this strategy is presented in the next sections of this
document.
Settings for Resolving the Geometrical Features of the Model and for
Obtaining the Required Solution Accuracy
The computational mesh variation described in the previous section is the key item of the
proposed strategy for solving engineering problems with Flow Simulation.
The result resolution level governs the number of basic mesh cells, the criteria for
refinement (splitting) of the basic mesh to resolve the model geometry, creating the initial
mesh, as well as the criteria for refinement (splitting) of the initial mesh during the
problem solution. The Result resolution level parameter, specified in the Wizard, defines
the following parameters in the created project: the Level of initial mesh and the Results
resolution level. The Level of initial mesh only governs the initial mesh and is accessible
(after the Wizard is finished) from the Initial Mesh dialog. The Results resolution level is
accessible from the Calculation Control Options dialog and controls the refinement of
computational mesh during the calculation and the calculation finishing conditions. The
geometry resolution options that also influence the initial mesh can be changed both in the
Wizard and on the Automatic Settings tab of the Initial Mesh and Local Initial Mesh
dialogs. The effects of the geometry resolution options can be altered on the other tabs of
these dialogs.
Before creating the initial mesh, Flow Simulation automatically determines the Minimum
gap size and the Minimum wall thickness for the walls contacting the fluid with both
sides. This is required for resolving the geometrical features of the model with the
computational mesh. Flow Simulation creates the initial mesh so that the number of the
mesh cells along the normal to the model surface must not be less than a certain number, if
the distance along this normal from this surface to the opposite wall is not less than the
minimum gap size. This insures that a flow passage or gap with the width larger than the
specified minimum gap size will be resolved with a certain number of cells across it.
The Minimum wall thickness governs the resolution of the sharp edges such as tips of
thin fins or, if the Optimize thin walls resolution option is not selected, the overall
resolution of the thin walls in the same way as the minimum gap size governs resolution of
the flow passages and gaps in the model.
In the automatic mode these mesh parameters are determined from the dimensions of the
surfaces with the boundary conditions specified, such as the model inlet and outlet
openings in an internal analysis, as well as the surfaces and volumes with the heat sources,
local initial conditions, surface and/or volume goals and some of the other conditions and
features. If you select the options to specify the Minimum gap size and the Minimum wall
thickness manually, you can see the their values determined by Flow Simulation. If these
values cannot provide an adequate resolution of the model geometry, you can change
them. At that, it is necessary to remember that the number of the computational mesh cells
generated to resolve the model geometrical features depends on the specified result
resolution level.
Evidently, when creating a Flow Simulation project, it is always worthwhile to make sure
that both the minimum gap size and the minimum wall thickness are relevant to the model
geometry. However, if the model geometry is complicated (for instance, there are
non-circular flow passages, sharp edges protruding into the stream, etc.), it can be difficult
to determine these parameters unambiguously. In this case it can be useful to perform
several calculations by varying these parameters within a reasonable range in order to
reveal their influence on the problem solution. In accordance with the strategy of solving
engineering problems, these calculations must be performed at various result resolution
levels.
The initial mesh created at the result resolution levels of 3…5 is not changed during the
calculation, so it is not adapted to the solution. Result resolution levels of 5…7 yield the
same initial mesh, but at the result resolution levels of 6 and 7 the mesh is refined during
the calculation in the regions of increased physical parameters gradients. At level 8, a finer
initial mesh is generated and refinements during calculation take place.
It makes sense to perform calculations at the result resolution level of 3 if both the model
geometry and the flow field are relatively smooth. For more complex problems we
recommend, first of all, to perform the calculation at the result resolution level of 4 or 5
(naturally, explicitly specifying the minimum gap size and minimum wall thickness).
After that, if the calculation at the result resolution level of 5 is finished properly, we
recommend, in order to ascertain the mesh convergence, to perform the calculation at the
result resolution level of 7 and, if the computer resources allow you to do this, at the result
1-8
resolution level of 8.
1-10
the corresponding test problem in addition to the practical engineering problem you are
solving (preferably before you start to solve the practical problem following the
above-mentioned strategy). This operation increases the reliability of estimating the
obtained solution of the engineering problem so substantially that the required additional
time and efforts will fully pay back later on, in particular when solving similar engineering
problems.
If after solving the test problem you see that the accuracy of its solution obtained with
Flow Simulation is not satisfactory from your standpoint, check to see that you have
properly specified the Flow Simulation project, that all substantial features of the
engineering problem hare considered, and, finally, that Flow Simulation restrictions do not
impede solving this engineering problem.
Let us consider the most common errors and improper actions that can occur when solving
engineering problems with Flow Simulation.
When Specifying Initial Data:
• not considering physical features which are important for the engineering
problem under consideration: for instance, high Mach number gas flow (it must
be considered if M>3 for steady-state and M>1 for transient problems or if the
supersonic flow occurs in about a half of the computational domain or greater),
gravitational effects (must be considered if either the fluid velocity is small, the
fluid density is temperature-dependent, and a heat source is considered, or
several fluids having substantially different densities are considered in a
gravitational field), necessity of a time-dependent analysis (for instance, at the
moderate Reynolds numbers, when unsteady vortices are generated);
• incorrectly specifying symmetry planes as the computational domain boundaries
(for instance, at the moderate Reynolds numbers, when unsteady vortices are
generated; you should keep in mind that the symmetry of model geometry and
initial and boundary conditions does not guarantee the symmetry of the flow
field);
• if you specify symmetry planes and intend to specify a mass or volume flow rate
at a model inlet or outlet opening, please do not forget to adjust the flow rate
accordingly, instead of specifying the total flow rate: for instance, if the
symmetry plane crosses the inlet opening and splits it in two halves, specify a
half of the flow rate value;
• if you specify integral boundary or volume conditions (heat transfer rates, heat
generation rate, etc.), please remember that their values specified in the Flow
Simulation dialog boxes correspond to the fraction of area or volume laying
inside the computational domain;
• if you specify a flow swirl on a model inlet or outlet opening (in the Fans or
Boundary Conditions dialogs), please do not forget to properly specify their
swirl axes and the coordinate system;
• if you specify a Unidirectional or Orthotropic porous medium, please do not
forget to specify their directions;
• please make sure that the specified boundary conditions do not conflict with each
other. For example, if you deal with gas flows and the model inlet flow is
subsonic, whereas the flow inside the model becomes supersonic, it is incorrect
to specify flow velocity or volume flow rate as the boundary condition at the
model inlet, since they are fully determined by the geometry of the model flow
passage and the fluid specific heat ratio;
• if you solve a time-dependent problem, and this problem has cyclic-in-time
boundary conditions, thus leading to a steady-state cyclic-in-time solution, to
obtain which you have to calculate the flow several times in cycle, every time
specifying the solution from the previous calculation as the initial condition for
the next calculation, there is no need to specify the boundary conditions for
several cycles. Instead it is more convenient to specify them for a cycle and
perform a series of calculations, running each calculation with the Take previous
results check box selected in the Run dialog;
• when specifying Surface Goals, Volume Goals, Point Goals or Equation
Goals, it is better to give them sensible names to identify these goals
unambiguously;
• if you want to monitor the intermediate calculation results at certain sections of
the model during the calculation, it is better to determine these sections positions
in the Global coordinate system before actually running the calculation, since
during the calculation it is more difficult;
When Monitoring a Calculation:
• when monitoring intermediate calculation results during a calculation, please do
not forget the spatial nature of the problem being solved (of course, if the
problem itself is not 2D). To take a look at the full pattern it is expedient to see
the results at least in 2 or 3 intersecting planes;
When Viewing the Obtained Solution after Finishing a Calculation:
• to view different result features in different panes simultaneously, you can
split the SOLIDWORKS graphics area into 2 or 4 panes and build different
result features in different graphical areas through their individual Cut Plots,
3D Plots, Surface Plots, Flow Trajectories, Isosurfaces defined in these
areas;
• if you intend to see integral physical parameters (such as area, mass or volume
flow rates, heat generation rates, forces, etc.) with the Surface Parameters
dialog box, please remember that:
1-12
• the shown values are determined over the parts of the surface that belong to
the computational domain;
• their determination errors include errors of representing these surfaces in
SOLIDWORKS and Flow Simulation, the latter depends on the computational
mesh;
1-14
2
Advanced Knowledge
Introduction
The present document supplies you with our experience of employing the advanced Flow
Simulation capabilities, organized in the following topics:
Manual adjustment of the initial computational mesh settings
Mesh-associated tools (viewing the mesh before and after the calculation and
advanced post-processing tools)
Calculation control options (refinement of the computational mesh during calculation,
conditions of finishing the calculation)
Flow freezing
1 Mesh - Introduction
This chapter provides the fundamentals of working with the Flow Simulation
computational mesh, describes the mesh generation procedure and explains the use of
parameters governing both automatically and manually controlled meshes.
First, let us introduce a set of definitions.
Types of Cells
Any Flow Simulation calculation is performed in a rectangular parallelepiped-shaped
computational domain which boundaries are orthogonal to the axes of the Cartesian
Global Coordinate System. A computational mesh splits the computational domain with a
set of planes orthogonal to the Cartesian Global Coordinate System's axes to form
rectangular parallelepipeds called cells. The resulting computational mesh consists of
cells of the following four types:
Partial cell
Partial cell
Solid cell
2-2
Mesh Construction Stages
Refinement is a process of splitting a rectangular computational mesh cell into eight cells
by three orthogonal planes that divide the cell's edges in halves. The non-split initial cells
that compose the basic mesh are called basic cells or zero level cells. Cells obtained by the
first splitting of the basic cells are called first level cells, the next splitting produces
second level cells, and so on. The maximum level of splitting is nine. A ninth level cell is
89 times smaller in volume than the basic cell.
Narrow channels refinement, that is the refinement of the mesh in narrow channels
taking into account the respective user-specified settings.
Refinement of all fluid, and/or solid, and/or partial mesh cells up to the user-specified
level.
After each of these stages is passed, the number of cells is increased to some extent.
In Flow Simulation you can control the following parameters and options which govern
the computational mesh:
1 Nx, the number of basic mesh cells (zero level cells) along the X axis of the Global
Coordinate System. 1 ≤ Nx ≤ 1000
2 Ny, the number of basic mesh cells (zero level cells) along the Y axis of the Global
Coordinate System. 1 ≤ Ny ≤ 1000.
3 Nz, the number of basic mesh cells (zero level cells) along the Z axis of the Global
Coordinate System. 1 ≤ Nz ≤ 1000.
4 Control planes. By adding and relocating them you can contract and/or stretch the
basic mesh in the specified directions and regions. Six control planes coincident with
the computational domain's boundaries are always present in any project.
5 Small solid features refinement level (Lb). 0 ≤ Lb ≤ 9.
6 Curvature refinement level (Lcur). 0 ≤ Lcur ≤ 9.
7 Curvature refinement criterion (Ccur). 0 ≤ Ccur ≤ .
8 Tolerance refinement level (Ltol). 0 ≤ Ltol ≤ 9.
9 Tolerance refinement criterion (Ctol). 0 ≤ C tol.
10 Narrow channels refinement: Characteristic number of cells across a narrow channel,
Narrow channels refinement level, The minimum and maximum height of narrow
channels to be refined.
These options are described in more detail below in this chapter.
Basic Mesh
The basic mesh is a mesh of zero level cells. In case of 2D calculation (i.e. if you select the
2D plane flow option in the Computational Domain dialog box) only one basic mesh cell
is generated automatically along the eliminated direction. By default Flow Simulation
constructs each cell as close to cubic shape as possible.
The number of basic mesh cells could be one or two less than the
user-defined number (Nx, Ny, Nz). There is no limitation on a cell
oblongness or aspect ratio, but you should carefully check the
calculation results in all cases for the absence of too oblong or
stretched cells.
a) 10x12x1 b) 40x36x1
2-4
Control Planes
The Control Planes option is a powerful tool for creating an optimal computational mesh,
and the user should certainly become acquainted with this tool if he is interested in
optimal meshes resulting in higher accuracy and decreasing the CPU time and required
computer memory. Control planes allow you to resolve small features, contract the basic
mesh locally to resolve a particular region by a denser mesh and stretch the basic mesh to
avoid excessively dense meshes.
Interval 2:
number of cells=12 (manual)
ratio=1
Interval 1:
number of cells=12 (automatic)
ratio=2
Use of control planes is especially recommended for external analyses, where the
computational domain may be substantially larger than the model.
2-6
Resolving Small Solid Features
The procedure of resolving small solid features refines only the cells where the solid/fluid
(solid/solid) interface curvature is too high: the maximum angle between the normals to a
solid surface inside the cell exceeds 120, i.e. the solid surface has a protrusion within the
cell.
Such cells are split until the the Small solid features refinement level of splitting mesh
cells is achieved.
Curvature Refinement
The curvature refinement level is the maximum level to which the cells will be split during
refinement of the computational mesh until the curvature of the solid/fluid interface within
the cell becomes lower than the specified curvature criterion (Ccur).
The curvature refinement procedure has the following stages:
1 Each solid surface is triangulated: Flow Simulation gets triangles that make up the
SOLIDWORKS surfaces.
2 A local (for each cell) interface curvature is determined as the maximum angle
between the normals to the triangles within the cell.
3 If this angle exceeds the specified Ccur, and the curvature refinement level is not
reached then the cell is split.
The curvature refinement is a powerful tool, so that the competent usage of it allows you
to obtain proper and optimal computational mesh. Look at the following illustrations to
the curvature refinement by the example of a sphere.
Fig.1.7 Curvature refinement level is 0; Fig.1.8 Curvature refinement level is 1;
Total number of cells is 64. Total number of cells is 120.
2-8
Tolerance Refinement
Tolerance refinement allows you to control how well (with what tolerance) mesh polygons
approximate the real interface. The tolerance refinement may affect the same cells that
were affected by the small solid features refinement and the curvature refinement. It
resolves the interface's curvature more effectively than the small solid features refinement,
and, in contrast to the curvature refinement, discerns small and large features of equal
curvature, thus avoiding refinements in regions of less importance (see images below).
Any surface is approximated by a set of polygons which vertices are surface's intersection
points with the cells' edges. This approach accurately represents flat faces though
curvature surfaces are approximated with some deviations (e.g. a circle can be
approximated by a polygon). The tolerance refinement criterion controls this deviation. A
cell will be split if the distance (h, see below) between the outermost interface's point
within the cell and the polygon approximating this interface is larger than the specified
criterion value.
2-10
Although the settings that produce an optimal mesh depends on a particular task, here are
some ’rule-of-thumb’ recommendations for narrow channel settings:
1 Set the number of cells across narrow channel to a minimum of 5.
2 Use the minimum and maximum heights of narrow channels to concentrate on the
regions of interest.
3 If possible, avoid setting high values for the narrow channels refinement level, since it
may cause a significant increase in the number of cells where it is not necessary.
Fig.1.13 Small solid features refinement level is 3; Narrow channel refinement is disabled.
Fig.1.14 Small solid features refinement level is 3; Narrow channel refinement is on: 5 cells across
narrow channels, Narrow channels refinement level is 2.
Fig.1.15 Small solid features refinement level is 3; Narrow channel refinement is on: 5 cells across
narrow channels, Narrow channels refinement level is 5.
2-12
Fig.1.16 The local mesh settings used: Two narrow channels are refined to have 10 cells across them.
2 Mesh-associated Tools
Introduction
Since the mesh settings is an indirect way of constructing the computational mesh, to
better visualize the resulting mesh various post-processing tools are offered by Flow
Simulation. In particular, these tools allow to visualize the mesh in detail before the
calculation, substantially reducing the CPU and user time.
The computational mesh constructed by Flow Simulation or other CFD codes cannot
resolve the model geometry at the mesh cell level exactly. A discrepancy can lead to
prediction errors. To facilitate an analysis of these errors and/or to avoid their appearance,
Flow Simulation offers various options for visualizing the real computational geometry
corresponding to the computational mesh used in the analysis.
Since the numerical solution is obtained inevitably in the discrete form, i.e., in the centers
of computational mesh cells, it is interpolated and extrapolated by the post-processor to
present the results in a smooth form, which is typically more convenient to the user. As a
result, some prediction errors can stem from these interpolations and extrapolations. To
facilitate an analysis of such errors and/or to prevent their appearance, Flow Simulation
offers an option to visualize the physical parameters’ values calculated at the centers of
computational mesh cells, so that when presenting results by coloring an area with a
palette, the results are considered constant within each cell.
2-14
Fig.2.1 The Basic mesh (left) and the Initial mesh (right).
To view various meshes, you must open the corresponding file via the Load results dialog
box. The calculation results, including the current computational mesh, are saved in the
.fld files, whereas the initial computational mesh is saved separately in the .cpt file. All
these files are saved in the project folder, which name (a numeric string) is formed by
Flow Simulation and must not be changed. The .cpt files and the final (i.e., with the
solution obtained at the last iteration) .fld files have the name similar to that of the project
folder, whereas the solutions obtained during the calculation at the previous iterations
(corresponding to certain physical time moments, if the problem is time-dependent) are
saved in the .fld files with names “r_<iteration number>”, e.g. the project initial data are
saved in the r_000000.fld file.
2-16
Visualizing the Real Computational Geometry
Since the SOLIDWORKS model geometry, especially its high-curvature parts, cannot be
resolved exactly at the cell level by the rectangular (parallelepiped) computational mesh,
the real computational geometry corresponding to the computational mesh used in the
analysis can be viewed after the calculation to avoid or estimate the prediction errors
stemming from this discrepancy. If no solution-adaptive meshing occurs during the
calculation, the real computational geometry can be viewed just after the mesh generation.
This option is employed by clearing the Use CAD geometry check box in Cut Plots, 3D
Plots, Surface Plots, Flow Trajectories, Point Parameters and XY Plots. The result is
especially clear when colored Contours are used to visualize a physical parameter values
(see Fig.2.3).
Fig.2.3 Cut Plots around the SOLIDWORKS model outer surface (left) and on its computational
realization (right).
This capability is especially useful for revealing important surface regions in the model,
which are inadequately resolved by the computational mesh.
On the other hand, this option may be useful when creating Surface Plots for
SOLIDWORKS models containing rippled surfaces, where ripples, which are supposed to
be not essential from the problem solution viewpoint, were not resolved by the
computational mesh. In this case, coloring of the simplified solid/fluid interface instead of
coloring the actual SOLIDWORKS model faces can lead to substantial reduction of the
CPU time and memory requirements.
2-18
Switching off the Interpolation and Extrapolation of Calculation
Results
Since the numerical solution is obtained inevitably in the discrete form, i.e., in the form of
values in the centers of the computational mesh cells in Flow Simulation, it is interpolated
and extrapolated by the post-processor to present the results in a smooth form, which is
typically more convenient to the user. As a result, prediction errors can stem from and/or
be hidden by such interpolation and extrapolation that smoothens the calculation results.
To facilitate the revealing, analysis, and elimination of such errors, Flow Simulation offers
an option to visualize the physical parameter values ’as is’, i.e. without interpolation,
when presenting calculation results in Cut Plots and Surface Plots (other result features,
namely, isolines, isosurfaces, flow streamlines and particle trajectories can not be built at
all without interpolation), so when coloring a surface with a palette, the results are
considered constant within the mesh cells (see Fig.2.4).
Since the mesh cells’ centers used in coloring the surface can lie at
different distances from the surface, this can introduce an additional
variegation into the picture, if the value of the displayed parameter
depends noticeably on this distance (see Fig.2.4).
Fig.2.4 The fluid velocity Surface Plots in the near-wall region created with the interpolation of the
calculation results (left) and without interolation (right).
Conclusion
The presented mesh-associated tools of Flow Simulation are additional tools for obtaining
reliable and accurate results with this code. These tools are summarized in the table:
Application
Flow Simulation considers the real model created in SOLIDWORKS and generates a
rectangular computational mesh automatically distinguishing the fluid and solid domains.
The corresponding computational domain is generated in the form of a rectangular
parallelepiped enclosing the model. In the mesh generation process, the computational
domain is divided into uniform rectangular parallelepiped-shaped cells, which form a
so-called basic mesh. Then, using information about the model geometry, Flow
Simulation further constructs the mesh by means of various refinements, i.e. splitting of
the basic mesh cells into smaller rectangular parallelepiped-shaped cells, thus better
representing the model and fluid regions. The mesh, which the calculation starts from,
so-called initial mesh, is fully defined by the generated basic mesh and the refinement
settings.
2-20
Each refinement has its criterion and level. The refinement criterion denotes which cells
have to be split, and the refinement level denotes the smallest size, which the cells can be
split to. Regardless of the refinement considered, the smallest cell size is always defined
with respect to the basic mesh cell size so the constructed basic mesh is of great
importance for the resulting computational mesh.
The main types of refinements are:
Small Solid Features Refinement
Curvature Refinement
Tolerance Refinement
During the calculation, the initial mesh can be refined further using the
Solution-Adaptive Refinement.
Though it depends on a refinement which criterion or level is available for user control,
we will consider all of them (except for the Solution-Adaptive Refinement) to give you a
comprehensive understanding of how the Flow Simulation meshing works.
In the chapter below the most important conclusions are marked with the blue italic font.
For abbreviation list refer to the Glossary paragraph.
The Cell Mating rule is strict and has higher priority than the other
cell operations. The rule is also enforced for the cells that are entirely
in a solid.
The mesh at this stage is called the primary mesh. The primary mesh implies the complete
basic mesh with the resolution of the solid/fluid (as well as solid/solid) interface by the
small solid features refinements and the curvature refinement also taking into account the
local mesh settings.
2-22
Narrow Channel Refinement
After the primary mesh has been created, the narrow channel refinement is put in action.
The Narrow Channels term is conventional and used for the definition of the model flow
passages which are ’narrow’ in the direction normal to the solid/fluid interface.
Regardless of the real solid curvature, the mesh approximation is that the solid boundary is
always represented by a set of flat elements, which nodes are the points where the model
intersects with the cell edges. Thus, whatever the model geometry, there is always a flat
element within a partial cell and the normal to this element denotes the direction normal to
the solid/fluid interface for this partial cell.
The narrow channel refinement operates as follows:
1 For each partial cell Flow Simulation calculates the “local” narrow channel width as
the distance between this partial cell and the next partial cell found on the line normal
to the solid/fluid interface of this cell (i.e. normal to the flat surface element located in
the cell).
If the line normal to the solid/fluid interface crosses a local initial
mesh area, then the corresponding local narrow channel refinement
settings is applied to the cells in this direction.
2 If the distance value falls within the range defined by the Minimum height of narrow
channel (NCHmin) and Maximum height of narrow channel (NCHmax) options, the
number of cells per this interval is calculated including both partial cells and taking
into account which portion of each partial cell is in fluid. [NCHmin, NCHmax].
3 More precisely, the number of cells across the channel (i.e. on the interval between the
two partial cells) is calculated as N = Nf + np1 + np2, where Nf is the number of fluid
cells on the interval, and np1 and np2 are the fluid portions of the both partial cells. This
value is compared with the specified Characteristic number of cells across a narrow
channel (CNC). If N is less than the specified CNC then the cells on this interval are
split. For example, on Fig.3.2 Nf = 2, np1 = np2 = 0.4, and N = 2+0.4+0.4 = 2.8 which is
less than the criterion. On Fig.3.3 the partial cells are split, so that the fluid portions of
the newly-formed partial cells are np1 = np2 = 9/10, and the criterion is satisfied (N >
CNC).
Fig.3.2 Fig.3.3
NCRL = 2; CNC = 3; NCRL = 3; CNC = 3;
N = 2.8 < CNC N = 3.8 > CNC
Fig.3.4 Fig.3.5
CNC = 5; NCRL = 1 CNC = 5; NCRL = 3
In Fig.3.4, the specified Characteristic number of cells across a channel is 5 but only two
cells were generated since the maximum refinement level of one allows only basic mesh
cells and first-level cells to be generated.
In Fig.3.5, the specified Narrow channel refinement level is high enough to allow five
cells to be placed across the channel.
5 Next, for all the fluid cells within the entire computational domain the following Fluid
Cell Leveling procedure is applied: if a fluid cell is located between two cells of higher
level, it is split to be equalized with the level of neighboring smaller cells.
2-24
Thin walls resolution
In contrast to the narrow channels, thin walls can be resolved without the mesh refinement
inside the wall, since the both sides of the thin wall may reside in the same cell. Therefore,
the amount of cells needed to resolve a thin wall is generally lower than the number of
cells needed to properly resolve a channel of the same width. See Fig.3.6 - 3.8 illustrating
the thin walls resolution technology and its limitations.
Solid 2 Fluid 1
Solid 1
Fluid 2
Fig.3.6
One mesh cell can contain more than one fluid and/or solid volume; during calculation
each volume has an individual set of parameters depending on its type (fluid or solid).
Fig.3.7
If the wall thickness is greater than the basic mesh cell's size across the wall or if the
wall creates only one fluid volume in the cell, then the opposite sides of the wall will not
lay within the same cell. Such walls are resolved with two or more cells across.
Trimmed edge
Trimmed cell
Fig.3.8
The edges of thin walls ending within a mesh cell may be trimmed in certain cases. These mesh cells
are called Trimmed cells.
Mesh Diagnostic
The mesh diagnostic is intended to inspect the resulting initial mesh but not to change the
total number of cells.
2-26
Small Solid Features Refinement
The small solid features refinement acts on the cells where the maximum angle between
normals to the surface-forming triangles is strictly greater than 120. To make this
120-degree criterion easier to understand, let us consider simple small solid features of
planar faces only. The normal to triangles that form the planar face is normal to the planar
face too. Therefore, instead of considering the normals to the triangles we can consider
normals to faces, or better the angle between faces.
Fig.3.9
SSFRL = 1, CRL = 0, NCRL = 0
In Fig.3.9 the cells with the cogs of 150 and 60 degrees were not split by the small solid
features refinement because the maximum angles between the faces (i.e. between normals
to the triangles enclosed by the cell) are 30 and 120, respectively. If the angle between
the normals becomes greater than 120 (121 for the 59-cog) then the cell is split. The
cell with the square spike surely has to be split because the lateral faces of the spike have
their normals at the angle of 180, thus satisfying the 120-degree criterion.
Note that rectangular corners (like in the rightmost cell) do not satisfy the criterion and
therefore will not be resolved by the small solid features refinement.
From Fig.3.10 it is clear that the cells are split by the 120-degree criterion up to the first
level, as defined by the narrow channel refinement level.
For the information about how the NCRL influences the narrow channel refinement see
the Narrow Channel Refinement paragraph.
Curvature Refinement
The curvature refinement works in the same manner as the small solid features refinement
with the difference that the critical angle between the normals can be specified by the user
(in radians) as curvature refinement criterion (CRC). Here, the smaller the criterion, the
better resolution of the solid curvature. To give more precise and descriptive explanation,
the following table presents several CRC values together with the corresponding angles
between normals and the angles between planar faces.
Table 2.1: Influence of the curvature criterion on the solid curvature resolution.
Curvature
criterion, rad 0.3176 0.4510 0.5548 0.6435 1.0472 1.5708 2.0944 3.1416
' between >19 >25 >31 >36 >60 >90 >120 180
normals, [degrees]
between faces, <161 <154 <148 <143 <120 <90 <60 0
[degrees]
The table states that if the CRC is equal to 0.4510 rad, then all the cells where the angle
between normals to the surface-forming triangles is more than 25 degrees will be split.
You can see that the curvature criterion set to 0.4510 rad splits the cells with the
150-degrees cog.
Note that the curvature refinement works exactly as the small solid
features refinement when the curvature criterion is equal to 2.0944
rad (2/3).
However, the default curvature criterion values are small enough to resolve obtuse angles
and curvature well. Increasing the curvature criterion is reasonable if you want to avoid
superfluous refinement but it is recommended that you try different criteria to find the
most appropriate one.
2-28
The curvature criterion also denotes the criterion of the Square Difference Refinement.
The square difference refinement criterion is directly proportional to the CRC, so the
smaller CRC, the smaller square difference refinement criterion, resulting in a greater
number of cells appearing after the Square Difference Refinement.
SSFRL or CRL
Why is it necessary to have two criteria? As you can see, the curvature refinement has
higher priority than the small solid features refinement if the curvature criterion is smaller
than 2/3 . Note that Flow Simulation-specified values of the curvature criterion are
always smaller than 2/3 .
In other words, if you did not set the CRC greater than 2/3 and if
the SSFRL and NCRL are smaller than the CRL, then the small solid
feature refinement would be idle.
Nevertheless, the advantage of the small solid features refinement is that being sensitive to
relatively small geometry features it does not “notice” the large-scale curvatures, thus
avoiding refinements in the entire computational domain but resolving only the areas of
small features. At the same time, the curvature refinement can be used to resolve the
large-scale curvatures. So both the refinements have their own coverage providing a
flexible tool for creating an optimal mesh.
Tolerance Refinement
Any surface is approximated by a set of polygons which vertices are the points of
intersection of this surface with the cells' edges. This approach accurately represents flat
faces though curved surfaces are represented by some approximation (e.g. as a circle can
be represented by a polygon). The tolerance refinement criterion controls the precision of
this approximation. A cell will be split if the distance between the outermost point of the
surface within the cell and the polygon approximating this surface is larger than the
specified criterion value.
Small Solid Feature Refinement Tolerance Refinement
(refinement occurs regardless of the
Tolerance criterion
feature’s size) Tolerance criterion = 0.1 = 0.08
Tolerance Refinement
Curvature Refinement Tolerance criterion = 0.1
(refinement occurs regardless of the Refines cells only if the solid part cut by Tolerance
curvature only) the polygon is large enough (h > 0.1) criterion = 0.03
2-30
The minimum level means the lower bound to which it is obligatory
to split cells, though the cells can be split further if it is required to
satisfy the other criteria such as Small solid features refinement,
Curvature refinement, Narrow channels refinement or Solid
Boundary Refinement.
If different cell types are to be refined, the refinement level of partial cells is set as the
maximum level among all selected levels.
The local mesh settings have higher priority over the initial mesh settings. Therefore, the
local mesh cells will be split to the specified local refinement levels regardless of the
general SSFRL, CRL and NCRL (specified in the Initial Mesh dialog box). This, however,
may cause refinement of cells located outside of the local region due to imposing the Cell
Mating rule.
solid/fluid
interfaces
(a) (b)
Fig.3.13
Mesh refinement around a thin wall: (a) the Optimize thin walls resolution option is switched
off, i.e. the mesh cells are split as in the previous versions of Flow Simulation; (b) the Optimize thin
walls resolution option is selected (the default state), i.e. the mesh cells are not split.
Postamble
The problem of resolving a model with the computational mesh is always model-specific.
In general, a denser mesh will provide better accuracy but you should tend to create an
optimal mesh and to avoid redundant refinement.
When performing a calculation, try different mesh settings and analyze the obtained
results carefully in order to understand whether it is necessary to refine the mesh or a
coarser resolution is acceptable for the desired accuracy.
Glossary
Nx, Ny, Nz – Number of basic mesh cells per X, Y and Z directions, respectively.
Introduction
The Calculation Control Options dialog box introduced into Flow Simulation allows you
to control:
• conditions of finishing the calculation,
• saving of the results during the calculation,
• refinement of the computational mesh during the calculation,
• freezing the flow calculation,
• time step for a time-dependent analysis,
• number of rays traced from the surface if radiating heat transfer is enabled.
2-32
This dialog box is accessible both before the calculation and during the calculation. In the
last case the new-made settings are applied to the current calculation starting from the next
iteration.
The main information on employing the options of Finishing the calculation and
Refining the computational mesh during calculation is presented in this document.
2-34
As for the automatically specified initial calculation period (measured in travels), it
depends on the problem type, the Goal type, and the specified Result resolution level.
• the manually specified analysis interval for the Goals
convergence finishing criteria must be substantially longer than
the typical period of the flow field oscillation (if it occurs);
• the Goals determined on solid/fluid interfaces or model
openings, as well as the Post-processor Surface Parameters, yield
the most accurate and correct numerical information on flow or
solid parameters, especially integral ones;
• Global Goals yield the most reliable information on flow or solid
parameters, although they may be too general;
• the CPU time depends slightly on the number of the specified
Goals, but, in some cases, vary substantially in the case of
presence of a Surface Goal;
• Surface and Volume Goals provide exactly the same information
that may be obtained via the Surface and Volume Parameters
Post-processor features, respectively.
Fig.4.1Refinement in the regions where the local initial meshes are specified.
To locate regions of the computational domain that need mesh refinement, it is necessary
to analyze the solution obtained with the mesh that existed at the last refinement cycle.
Indicator functions are used to locate regions where the solution requires a mesh
refinement to reduce the local truncation errors. The output of an indicator function is used
to determine if the mesh cell must be split or merged or is adequately resolved.
2-36
The indicator function for the momentum conservation law is defined as follows:
n n
C m , foam h S , 1 1 foam
n min n min
where S 0.5 Sij Sij is a convolution of the strain rate tensor, n is the total number of
adjacent cells, nmin is the number of the coordinate directions (plus or minus) in which at
least one cell is adjacent cell, foam is the cell level gap displacement factor, which shifts
the region where the mesh cells must be split to the area where the local truncation error is
definitely small, h is the characteristic cell size defined as follows:
u i
i j j x j
hj
h
u i
i j j x j
and the mesh refinement level is less than the current maximum refinement level.
The child mesh cells are merged if all following condition is satisfied for each child cell:
Cm merge
m
and C merge
and C e merge
e
and C y merge
y
and if the refinement level difference between the resulting merged mesh cells and their
neighbors will not exceed 1.
All limiting values (split and merge) are determined automatically at each refinement
cycle by using mesh histograms.
The solution-adaptive refinement can dramatically increase the number of cells so that the
available computer resources (physical RAM) will not be enough for running the
calculation. To limit the total number of cells the Approximate Maximum Cells value can
be specified. If the maximum cells number is exceeded, the number of cells will be limited
for the last refinement cycle in such a way that the LTE, increasing at the refinement level
gap surface, is minimized.
For a transient analysis the following three strategies are available:
• Periodic refinement;
• Tabular Refinement;
• Manual Only refinement.
In the first two strategies the refinement moment is known beforehand. The solution
gradients are analyzed over iterations belonging to the Relaxation interval, which is
calculated from the current moment rearwards. As the result, only steady-state gradients
are considered. The default length of the Relaxation interval can be adjusted manually.
On the other hand, the analysis must not continue with the same relaxation interval
defined from the start of the calculation, in order to avoid considering the initial highly
unsteady period. Therefore, a period of at least two relaxation intervals is recommended
before the first refinement. If the first assigned refinement is scheduled in a shorter term
from the beginning, the period over which the gradients are analyzed is shortened
accordingly, so that in an extreme case it can be as short as one current iteration. If you
initiate a refinement manually within this period, the gradients are analyzed in one current
iteration only. Naturally, such a short period gives not very reliable gradients and hence
may result in an inadequate solution or excessive CPU time and memory requirements.
The figure below illustrates this concept. Here, the letter r denotes the relaxation interval.
This figure involves both the Periodic and Tabular refinements. Case 1 is the
recommended normal approach. In the Case 2 the first refinement is too close to the
starting point of the calculation, so the gradients are analyzed over the shorter interval
(which could even be reduced to just one current iteration in an extreme case). Case 3 is a
particular case when the refinement is initiated manually just before a previously assigned
2-38
refinement. As the result, the manual refinement is well-defined, since the gradients have
been analyzed over almost the entire relaxation interval, but on the other hand, the
previously assigned refinement is performed on the substantially shorter interval, and
therefore its action can be incorrect. Thus, Case 3 demonstrates the possible error of
performing manual and previously assigned refinements concurrently.
Case 1
r r
Case 2 Case 3
r r1 r2
r
The mesh refinement performed during the calculation is idling and the warning messages
appear in the Monitor window in the following cases:
• Refinement canceled: the limit of maximum number of cells was achieved. This
message warns that the Approximate Maximum Cells is reached.
• Refinement canceled: refinement-unrefinement criteria is not satisfied. This
message indicates that there are no mesh cells where the conditions of splitting of
merging are satisfied.
• Refinement canceled: the limit of maximum refinement level was achieved in
field gradients. If there are mesh cells where the conditions of splitting or merging
are satisfied, but the Refinement level has been already reached, since the field
gradients have not been changed, this message appears. If the field gradients are
changed and the mesh refinement is performed again, the mesh refinement will
result in splitting or merging cells.
5 Flow Freezing
How It Works
To access the Flow Freezing option, open the Calculation Control Options dialog box,
then the Advanced tab. This option has three modes: Disabled (by default), Periodic, and
Permanent.
2-40
Flow Freezing in a Permanent Mode
As an example of applying the Flow Freezing option, let us consider a plane flow (2D)
problem of heating the vortex core in a vessel (Fig.5.1).
At the beginning the entire fluid region is filled with a cold (T=300 K) liquid. A hot
(T=400K) liquid enters the vessel through the lower channel (the upper channel is the
exit). As a result, a vortex with a cold core is developed in the vessel. The vortex core
temperature is changed mainly due to heat diffusion. To measure it, a small body is placed
at the vortex center and disabled in the Component Control dialog box, so that it is treated
by Flow Simulation as a fluid region. Its minimum temperature (i.e., the minimum fluid
temperature in this region) is the Volume Goal of the calculation.
First of all, let us consider Flow Freezing operating in the Permanent mode. The only
user-specified parameter in Permanent mode is the starting moment of enabling the Flow
Freezing option. Until this moment the calculation runs in a usual manner. After this
moment the fluid velocity field becomes frozen, i.e., it is no longer calculated, but is taken
from the last iteration performed just before the Flow Freezing Start moment. For the
remainder of the run only the equations’ terms concerning heat conduction and diffusion
are calculated. As a result, the CPU time required per iteration is reduced.
The starting moment of the Flow Freezing option should be set not too early in order to let
the flow field to fully develop. As a rule, an initial period of not less than 0.25 travels is
required to satisfy this condition. In most problems the 0.5 travel initial period is
sufficient, but there are problems that require a longer initial period.
2-42
temperatures and concentrations are calculated in each iteration. Examples include
channel flows with specified mass flow rates and pressures, so the fluid density and,
therefore, velocity depend on the fluid temperature, or flows involving free convection,
where due to the buoyancy the hot fluid rises, so the velocity field depends on the fluid
temperature.
No Freezing
Start
Iterations
Freezing
Fig.5.2
As an example, let us consider a 3D external problem of an air jet outflow from a body
face into still air (see Fig.5.3, in which the jet outflow face is marked by a red line). Here,
the wire frame is the computational domain. The other body seen in this figure is
introduced and disabled in the Component Control dialog box (so it is a fluid region) in
order to see the air temperature averaged over its face (the project Goal), depending on the
air temperature specified at the jet outflow face.
Fig.5.3 Air jet outflow from a body face into a still air.
This problem is solved in several stages. At the first stage, the calculation is performed for
the cold (T = 300 K, which is equal to the environment temperature) air jet. Then we clone
the project including copying the results. Next, we set the outlet air temperature to T = 400
K, specify the Periodic mode of the Flow Freezing option by its Start moment of 0.25
travels (in order for the heat to have time to propagate along the jet to the measuring face)
and under Duration specify 10 as both the Freezing (iterations) and No freezing
(iterations) values. Then perform the calculation on the same computational mesh with
the Take previous results option in the Run box. As a result, the calculation with flow
freezing takes less CPU time than the similar calculation without the Flow Freezing option
enabled.
2-44
3
Advanced Features Guide
This chapter gives an overview of the advanced physical simulation features available in
Flow Simulation such as Rotation, Cavitation, Steam, Humidity and Real Gases. The
provided information includes a general description of the feature, the assumptions and
limitations of the employed physical model, a full description of all interface options and
settings you need to set to include the feature into the analysis, and some examples of the
feature’s application for solving engineering problems.
1 Cavitation
Cavitation is a common problem for many engineering devices in which the fluid is in
liquid state. The deleterious effects of cavitation include: lowered performance, load
asymmetry, erosion and pitting of blade surfaces, vibration and noise, and reduction of the
overall machine life. However, cavitation is also used in some industrial processes, such
as the fuel spray formation in diesel and gasoline engines.
The following models of cavitation are available in Flow Simulation:
• Equilibrium cavitation model (for pre-defined water only):
This model employs a homogeneous equilibrium approach and is available for
pre-defined water only. It has the capability to account for the thermal effects.
• Isothermal cavitation model (for user-defined liquids only):
This model is based on the approach considering isothermal two-phase flows. Fluid
density is defined by the barotropic equation of state. The isothermal cavitation
model is only available for user-defined incompressible liquids.
Physical model
3-2
model value appropriated in most cases but it can be modified by the user in the
range of 10-2...10-6.
Interface
Isothermal cavitation model can be employed for any user-defined incompressible Liquid
in the Engineering Database by selecting the Cavitation effect check box and specifying
the Molar mass of the liquid and the Saturation pressure at the specific Temperature.
Equilibrium cavitation model becomes available when you select pre-defined Water as the
project’s Default fluid.
Cavitation option in Flow Simulation is
switched on by selecting the Cavitation
check box under Flow Characteristic
either in the Default Fluid dialog of the
Wizard or the Fluids dialog of General
Settings.
For the pre-defined water the default value of this parameter is 10-4.
This value is typical for air dissolved in water under normal conditions
and therefore is appropriate for most cases. For a user-defined liquid
the default Dissolved gas is Air and the default value of the Dissolved
gas mass fraction is 10-4. This is a typical value under normal
conditions and appropriate in most cases.
If needed, for the pre-defined water you can specify a different value of
the Dissolved gas mass fraction in the range of 10-3...10-5 and for a
user-defined liquid in the range of 10-2...10-6 for each gas which can be selected as the
dissolved gas: Air, Carbon dioxide, Helium or Methane.
Cavitation is represented in the calculation results via the following
parameters: Mass Fraction of Vapour and Volume Fraction of
Vapour, which corresponds to the local mass or volume fraction of the
vapour component. Make sure that those parameters are enabled in the
Parameter list to make them available for selection in the View
Settings dialog.
3-4
Examples of use
Rotating impeller
Water flows through a rotating impeller with five blades of a curved shape, as shown on
the picture. The aim of simulation is to predict the impeller characteristics.
Due to the pressure drop on the suction side of the impeller blades, a cavitation may
develop in these areas, which cannot but affect the impeller performance.
The appearance of the calculated cavitation area in the form of isosurfaces is shown below
on Fig.1.1.
Hydrofoil in a tunnel
A symmetric hydrofoil is placed with a non-zero
angle of attack in a sufficiently wide water-filled
tunnel. Obviously, water flow develops some
pressure drop on the upper surface of the hydrofoil,
which can lead to cavitation under certain
conditions.
Fig.1.2 contains a representation of the calculated
cavitation area visualized in terms of Volume
Fraction of Vapour.
Fig.1.2 Calculated cavitation area
Ball valve
Water flows inside an half-opened ball valve (see Fig.1.3) at the relatively low pressure
and high velocity producing cavitation.
The results visualized in the form of Cut plot with Volume Fraction of Vapour as displayed
parameter are presented on Fig.1.4. It is clearly seen that sudden expansion of the flow
produces an area of strong cavitation.
3-6
Throttle flow
Diesel fuel flows through a throttle (see Fig.1.5) under a relatively high difference
between the injection pressure and back pressure.
When a high velocity fluid passes through a contraction like a nozzle, an area of low
pressure is formed in the wake of its edge. In this wake the pressure can decrease below
the saturation pressure, and thus cause the liquid to cavitate.
Nozzle wall
The results visualized in the form of Cut plot with Volume Fraction of Vapour as displayed
parameter are presented on Fig.1.6. The red color indicates the region of high vapor
fraction.
Recommendations
• If you analyze a flow of water in some points of which the local static pressure can
reach the saturation pressure at the local temperature causing cavitation or if a
vaporization of water can occur in the water flow due to intense heating, it is
recommended to use the Equilibrium cavitation model.
• Cavitation area growths slowly during calculation and there is a risk that the
calculation will stop before the cavitation area develops completely. To avoid this,
specify Global Goal of Average Density and increase the Analysis interval on the
Finish tab of the Calculation Control Options dialog box. Also make sure that the
other finish conditions do not cause the calculation to stop before goals are
converged. The easiest way to ensure this is to select If all are satisfied in the Value
cell for the Finish conditions on the Finish tab of the Calculation Control Options
dialog box.
• The Cavitation option is not applicable if you calculate a flow in the model without
flow openings (inlet and outlet).
• The fluid region where cavitation occurs must be well resolved by the
computational mesh.
• Besides the Volume Fraction of Vapour you can also select Density as the
visualization parameter to see the cavitation areas in your simulation.
3-8
2 Steam
Physical model
Flow Simulation allows you to consider water steam among the project fluids. Like
Humidity, the Steam option may be used to analyze engineering problems concerning
water vapor and its volume condensation, along with the corresponding changes in the
physical properties of the project fluid. Steam option in Flow Simulation describes the
behavior of pure water steam or its mixtures with other gases.
Interface
Steam is treated by Flow Simulation as a
special kind of fluid and may be selected
from the Engineering Database just like
any other fluid.
Steam may be assigned for a fluid
subdomain as well as for the whole project.
Example of use
Heat exchanger
Flow Simulation calculates the equilibrium condensation in water steam as steam flows
through a cooled tube of a heat exchanger. Fig.2.1 shows cut plot of the condensate mass
fraction parameter.
Outlet
Inlet
Recommendations
• To avoid the risk of finishing the calculation before the condensation develops
completely, always specify some goal strongly dependent on condensation, for
example Global Goal of Average Density, and make sure that the calculation will
not stop before this goal is converged.
• To see the condensation areas, you may use Relative Humidity or the Condensate
Mass Fraction as the parameter for visualization.
3-10
3 Humidity
Physical model
Flow Simulation allows you to consider the relative humidity of the gas or mixture of
gases. This allows you to analyze engineering problems where the condensation of water
vapor contained in the air (or other gas), or, more generally speaking, where any
differences in physical properties of wet and dry air play an important role. Examples may
include air conditioning systems (especially in wet climate or in the places where relative
humidity is very important, e.g. libraries, art museums, etc.), tank steamers, steam turbines
and other kinds of industrial equipment. Flow Simulation can calculate equilibrium
volume (but not surface) condensation of steam into water. As a result, the local fractions
of gaseous and condensed steam are determined. In addition, the corresponding changes
of the fluid temperature, density, enthalpy, specific heat, and sonic velocity are determined
and taken into account.
Interface
Humidity option in Flow Simulation is
switched on by checking the Humidity
check box either in Wizard or in the
General Settings window. This check
box is present only if the current fluid
type is set to Gases.
The relative humidity must be specified within all boundary and initial
conditions in contact with the fluid region for which the calculation of
relative humidity is performed.
3-12
Together with the humidity value for boundary and initial
conditions you must also specify the values of Humidity
reference pressure and Humidity reference
temperature that describe the conditions under which the
relative humidity has been determined, since these values
Heat
may differ from the current pressure and temperature.
Boundary
condition
Example of use
Aircraft
An air flow around an aircraft model can be simulated with the Humidity option selected.
The examination of relative humidity distribution (Fig.3.1) reveals broad areas of more
than 80% relative humidity from above of both wings. Naturally, these areas (together
with smaller zones near the cockpit and the tail unit) are enriched with water condensate,
as it may be seen on Fig.3.2.
Recommendations
• If your analyze a flow of gas containing some amount of water vapor and the
conditions are likely to get over the dew point, it is recommended to consider
humidity in the calculation as described in this chapter.
• To avoid the risk of finishing the calculation before the condensation develops
completely, always specify some goal strongly dependent on condensation, for
example Global Goal of Average Density, and make sure that the calculation will
not stop before this goal is converged.
• To see the condensation areas, you may use Relative Humidity or the Condensate
Mass Fraction as the parameter for visualization.
3-14
4 Real Gases
Physical model
Flow Simulation has an ability to consider real gases. A wide choice of predefined real
gases is presented. The user may also create user-defined real gases by specifying their
parameters. This option may be useful in the engineering problems concerning gases at
nearly-condensation temperatures and/or at nearly-critical and supercritical pressures, i.e.
at conditions where the behavior of the gas can no longer be represented adequately by the
ideal-gas state equation.
The model of real gas implemented in Flow Simulation employs a custom modification of
the Redlich-Kwong state equation. Naturally, the equation unavoidably has certain bounds
of applicability, which are explained on the picture below:
Supercritical
Liquid
Vapor
The area of validity of the model includes zones 10, 11 and 12. (Each predefined real gas
has its own values of Pmin, Pmax, Tmin, and Tmax, and those are also to be specified for a
user-defined real gas.) If the calculated pressure and/or temperature fall outside of this
area, Flow Simulation issues a warning. The warning for zones 1 - 8 is: Real gas
parameters (pressure and/or temperature) are outside the definitional domain of
substance properties, with comment: P < Pmin, P > Pmax, T < Tmin, or T > Tmax,
depending on what has actually happen. The warning for zone 9 is: Phase transition in
the Real gas may occur.
Interface
Real gases are a special type of fluids and
may be selected from the Engineering
Database along with other fluids.
Real gas may be assigned for a fluid
subdomain as well as for the whole project.
3-16
To create a user-defined real gas,
the user must create a new item
in the corresponding folder in the
Engineering Database and
specify the following parameters:
• Molar mass;
• Critical pressure pc;
• Critical temperature Tc;
• Critical compressibility factor Zc;
• Redlich-Kwong equation type that should be used, i.e. the
original one or its modifications by Wilson, Barnes-King, or
Soave;
• Acentric factor (if applicable);
• Minimum temperature, i.e. the lower margin of validity of the model;
• Maximum temperature, i.e. the corresponding upper margin;
• Order of ideal gas heat capacity polynomial, i.e. the order of polynomial function
of temperature that defines the "ideal-gas" constituent of the real gas specific heat at
constant pressure;
• Coefficients of ideal gas heat capacity polynomial, i.e. the coefficients of the
aforementioned polynomial;
• Polarity (check if the gas in question has polar molecules);
• Vapor viscosity dependence on temperature, i.e. the coefficients a and n in the
equation describing vapor viscosity as = a·Tn;
• Vapor thermal conductivity
dependence on temperature, which
includes the coefficients a and n and the
choice of dependency type between linear = a+n·T and power-law = a·Tn
forms;
• Liquid viscosity dependence on temperature, which includes the coefficients a
and n and the choice of dependency type between power-law = a·Tn and
exponential = 10a(1/T-1/n) forms;
Example of use
Joule-Thomson effect
A flow of nitrogen through a tube containing narrow restriction is simulated. To reduce
computation time, the tube was split in halves by a symmetry plane and Symmetry
condition was applied to the corresponding boundary of the Computational Domain.
The calculation within ideal gas approximation, i.e. with nitrogen selected from Gases as
the project fluid, results in the temperature distribution shown on Fig.4.1. It is clearly seen
that the temperature of the gas, after undergoing a noticeable drop while passing through
the hole, later reinstates its initial value. This is an expected behavior of an ideal gas, as its
enthalpy does not depend on pressure.
3-18
The calculation was repeated with fluid changed to nitrogen selected from Real Gases and
all other conditions similar. Now the gas temperature at outlet is different from that at inlet
(see Fig.4.2).
Hence we may conclude that the real gas reveals a nonzero Joule-Thomson effect, as
expected.
Recommendations
• Minimum temperature for user-defined real gas should be set at least 5...10 K higher
than the triple point of the actual substance.
• Maximum temperature for user-defined real gas should be set so as to keep away
from the area of dissociation of the gas.
• The user-specified dependencies for the specific heat and transport properties of the
user-defined real gases should be valid in the whole temperature range from Tmin to
Tmax (or, as for liquid, in the whole temperature range where the liquid exists).
References
1 R.C. Reid, J.M. Prausnitz, B.E. Poling. The properties of gases and liquids, 4th edition,
McGraw-Hill Inc., NY, USA, 1987.
5 Rotation
Physical model
Flow Simulation is capable of simulating rotation of model parts and components with the
Averaging (rotating reference frame) and the Sliding approaches. Depending on the
model geometry and the incoming flow conditions, you can choose one of the following
options to simulate your rotating equipment:
• Local region(s) (Averaging) of rotation. This option allows to specify multiple
local rotating coordinate systems within the model in cases where the rotor-stator
interaction is weak. The Averaging approach assumes that the flow field is steady,
with the rotor-stator or impeller-base effects being accounted for by approximate
means. All model parts and components within the local rotating regions are
considered rotating by default. With this option you can simulate rotation of specific
model components and non-rotating model components outside rotating regions are
not required to be axisymmetrical, however, the rotor-stator interaction must be
rather weak.
• Local region(s) (Sliding) of rotation. This option allows to specify multiple local
rotating coordinate systems within the model in cases where the rotor-stator
interaction is strong. The Sliding approach assumes that the flow field is unsteady.
This assumption allows to obtain more accurate simulation than by using the
Averaging approach, however, that because this approach requires an unsteady
numerical solution, it is computationally more demanding than the Averaging
approach.
• Global rotating reference frame. With this option the model and the global
coordinate system are considered rotating with specified angular velocity. Global
rotating reference frame is applicable when all non-rotating model components are
axisymmetrical with respect to the selected rotation axis.
You can specify some model components within a global rotating
reference frame or local rotating region as non-rotating by applying the
Stator wall Boundary Condition to the components surfaces. All
non-rotating components within a rotating reference frame must be
axisymmetrical with respect to the selected rotation axis.
The Averaging (rotating reference frame) approach has the following prerequisites that
must be satisfied in order to apply it successfully and obtain reliable results:
• the supposed inlet flow field at the rotating reference frame boundaries must be
axisymmetrical with respect to the rotation axis,
• the supposed outlet flow field at the rotating reference frame boundaries must be as
close to axisymmetrical with respect to the rotation axis as possible.
The rotating reference frame boundaries are the computational domain
outer boundaries for the Global rotating option and the rotating region
outer surface for Local region(s) (Averaging) option.
3-20
Please note that even in case of time-dependent (transient) analysis by using the
Averaging approach the flow parameters within a rotating reference frame are calculated
using a steady-state approach and averaged at the rotating reference frame boundaries.
If you consider gravitational effects in your analysis, the rotation axis must be parallel to
the gravity vector.
Rotation axis
Flow parameters are
averaged over these rings
Please note that even in the case of time-dependent (transient) analysis the flow
parameters within the rotating regions are calculated using a steady-state approach and
averaged on the rotating regions' boundaries as described above.
The rotating region option is not applicable for high Mach number flows.
A rotating region is defined by adding an auxiliary component representing the rotating
region to the model and specifying the angular velocity. A component defining a rotating
region must meet the following requirements:
• the rotating component must be fully enclosed by it and the rotating component
walls must not contact or intersect the rotating region boundaries,
Interface
The rotation type is specified in the
Analysis Type dialog box of the Wizard
or General Settings by selecting the
Global rotating, Local region(s)
(Averaging) or Local region(s) (Sliding)
option.
In case of using Local region(s)
(Sliding), the Time-dependent option
must be enabled.
3-22
Local Rotating Regions
Using both the Averaging and the Sliding approaches, in the
Rotating Region dialog available under Flow Simulation >
Insert > Rotating Region, you select the model component
representing the volume, in which the local rotating reference
frame is applied, and specify Angular velocity.
The following parameters, available in the results processing tools, are useful for
analyzing the results of a calculation involving rotation:
• Axial velocity (m/s) is the fluid velocity component along the rotating coordinate
system’s rotation axis, it can be determined both in the rotating coordinate system
and in the absolute (i.e. non-rotating) one.
• Circumferential velocity (m/s) is the fluid velocity component along the rotating
coordinate system’s peripheral velocity vector relative to the Z axis of the selected
absolute (i.e. non-rotating) coordinate system.
• Circumferential velocity RRF (m/s) is the fluid velocity component along the
peripheral velocity vector relative to the Z axis of the selected rotating coordinate
system. Note that if rotation is considered in the project in the form of local rotating
regions (i.e. not as the global rotating reference frame), the values of this parameter
outside the rotating regions are determined in the absolute (i.e. non-rotating)
coordinate system.
• Peripheral velocity (m/s) is the circumferential speed of the rotating coordinate
system’s rotation: ω·r, where ω is the angular velocity at which the rotating
coordinate system rotates and r is the radius of the point under consideration in the
cylindrical coordinate system corresponding to the rotating coordinate system.
• Velocity RRF (m/s) is the fluid velocity vector and/or its absolute value in the
rotating coordinate system. Note that if rotation is considered in the project in the
form of local rotating regions (i.e. not as the global rotating reference frame), the
values of this parameter outside the rotating regions are determined in the absolute
(i.e. non-rotating) coordinate system.
Note that you may need to Enable some of those parameters in the Parameter list to make
them available for selection in the View Settings dialog.
Examples of Use
Rotating impeller
Flow through the rotating impeller of a centrifugal pump (Fig.5.2) can be simulated with
the Global rotating reference frame option since all non-rotating components of the pump
are axisymmetrical with respect to the rotation axis. The static pressure distribution in the
impeller flow passage midsection is shown on Fig.5.3.
3-24
Axial fan
An air flow in an axial fan can be simulated with the Local rotating regions option
(Fig.5.4). The rotating region encloses the fan and has a relatively simple shape.
The pressure and velocity vectors distributions are shown on Fig.5.5.
Fig.5.4 Problem statement Fig.5.5 Pressure and velocity vectors
distribution
Centrifugal pump
A water flow in a centrifugal pump can be simulated with the Local region(s) (Sliding)
option (Fig.5.7). The centrifugal pump uses a rotating impeller to increase the pressure of
the fluid to move the fluid through a piping system. The fluid enters the pump impeller
near the rotation axis and is accelerated by the impeller, flowing radially outward into the
volute chamber, from where it exits into the piping system downstream. The flow field at
the boundaries of the rotating region enclosing the impeller is not axisymmetrical, so it is
recommended to use the Sliding approach and unsteady numerical solution.
The pressure and velocity vectors distributions are shown on Fig.5.8.
Recommendations
• Choose such shape of the rotating region, that the flow direction will be as much
perpendicular to the rotating region boundary as possible.
• Local region(s) (Averaging) can be used to simulate rotation of a part or
component even if the flow field at the local rotating region boundaries is not
axisymmetrical, but you must consider how it can affect the device performance. If
you solve a problem in which the flow symmetry directly influence the device
characteristics, change the shape or position of the rotating region or make some
other modifications, if possible, to ensure that the flow at the rotating region
boundaries is axysimmetrical.
• Adjust the mesh settings to have at least 2 or 3 cells across the gaps between the
rotating region boundary and the surface of the rotating component within the
region.
• If the rotating model component is a body of revolution, use the Moving Wall
boundary condition instead of a rotating reference frame to simulate rotation of such
component.
3-26
• You can place rotating region boundary
within a solid body instead of putting it into
a narrow gap between the rotating
component and non- rotating model
geometry. This will allow you to reduce
possible negative influence of the flow
disturbances within the narrow gap on the
calculation results.
3-28