https://www.cfd-online.com/W/index.php?title=Special:Contributions/Frmonto&feed=atom&limit=50&target=Frmonto&year=&month=CFD-Wiki - User contributions [en]2017-09-25T19:24:19ZFrom CFD-WikiMediaWiki 1.16.5https://www.cfd-online.com/Wiki/Best_practice_guidelines_for_turbomachinery_CFDBest practice guidelines for turbomachinery CFD2013-08-23T10:27:49Z<p>Frmonto: /* References */</p>
<hr />
<div>This article contains a summary of the most important knowledge and experience a CFD engineer needs in order to perform CFD simulations of turbomachinery components. The guide is mainly aimed at axial turbomachinery. The goal is to give a CFD engineer, who has just started working with turbomachinery simulations, a head start and avoid some of the most difficult pit-falls. Experienced turbomachinery CFD engineers can also use the guidelines in order to learn what other experts consider best practice. The intended audience is expected to know basic CFD terminology and have a basic turbomachinery knowledge, but no detailed knowledge about CFD for turbomachinery is needed. <br />
<br />
== Deciding what type of simulation to do ==<br />
<br />
Before starting a new turbomachinery simulation it is wise to think carefully of what it is that should be predicted and what physical phenomena that affect the results. This chapter contains a brief overview of the various types of simulations and some hints of what can be predicted with them.<br />
<br />
=== 2D, Quasi-3D or 3D ===<br />
<br />
2D simulations are often used in the early design phase in order to obtain a typical 2D section of a blade. For cases with many long blades or vanes, like low-pressure turbines, a 2D simulation can also provide reasonable results. If the area of the flow-path changes significantly in the axial direction it might be necessary to instead make a quasi-3D simulation. A quasi-3D simulation is a 2D simulation in which extra source terms are used to account for the acceleration/deceleration caused by a changing channel height or growing end-wall boundary layers. Codes focused on turbomachinery applications often have the possibility to perform quasi-3D simulations, but most general purpose CFD codes can not do this type of simulations, or require user coding to implement the correct source terms in the equations. Please contact your software distributor if your code does not have the quasi-3d possibility and you require it. Many codes require special routines or hidden commands to enable this feature.<br />
<br />
Full 3D simulations are necessary if a true 3D geometry is needed to obtain correct secondary flows and/or shock locations. For low-aspect-ratio cases with only a few short blades, like for example structurally loaded turbine outlet guide vanes, the secondary flow development is important and a 3D simulation is often necessary in order to obtain reasonable results. For applications where the end-wall boundary layers grow very quickly and interact with a large part of the flow-field it is necessary to perform a full 3D simulation. This is often the case in compressors and fans, where the negative pressure gradients make the boundary layers grow much quicker than what they do in for example turbines. For cases where the shock location is very critical, like in transonic compressors, it is also often necessary to perform a 3D simulation in order to obtain reasonable shock locations.<br />
<br />
=== Inviscid or viscid ===<br />
<br />
For attached flows close to the design point and without any large separations it is often sufficient with an inviscid Euler simulation in order to obtain reasonable blade loadings and pressure distributions. Note that inviscid Euler simulations should only be used if the boundary layers are judged to not have a significant effect on the global flow-field. A viscid Navier-Stokes simulation is necessary in order to predict losses, secondary flows and separations. As soon as separations are of interest it is of course also necessary to do a viscid simulation. Note that with todays computers it is often not time and resources that make users run inviscid Euler simulations. Running viscid Navier-Stokes simulations is now so quick that it is not a time problem any more. Euler simulations are still interesting though, since with an inviscid Euler simulation you don't have to worry about wall resolutions, y+ values, turbulence modeling errors etc.<br />
<br />
=== Transient or Stationary ===<br />
<br />
Most turbomachinery simulations are performed as stationary simulations. Transient simulations are done when some kind of transient flow behaviour has a strong influence on the global flow field. Examples of transient simulations are detailed simulations of rotor-stator interaction effects, simulations of large unsteady separations etc. Sometimes when you perform a steady stationary simulation you can see tendencies of unsteady behaviour like for example periodic vortex shedding behind blunt trailing edges. This is often first seen as periodical variations of the residuals. If the unsteady tendencies are judged to not affect the overall simulation results it might be necessary to coarsen the mesh close to the vortex shedding or run a different turbulence model in order to make the simulation converge. Sometimes you are still forced to run a transient simulation and average the results if you don't obtain a converged steady solution.<br />
<br />
== Meshing ==<br />
<br />
In turbomachinery applications structured multi-block hexahedral meshes are most often used for flow-path simulations. In most solvers a structured grid requires less memory, provides superior accuracy and allows a better boundary-layer resolution than an unstructured grid. By having cells with a large aspect ratio around sharp leading and trailing edges a structured grid also provides a better resolution of these areas. Many companies have automatic meshing tools that automatically mesh blade sections with a structured mesh without much user intervention.<br />
<br />
Unstructured meshes are used for more complex and odd geometries where a structured mesh is difficult to create. Typical examples where unstructured meshes are often used are blade tip regions, areas involving leakage flows and secondary air systems, film cooling ducts etc.<br />
<br />
When meshing avoid to create large jumps in cell sizes. Typically the cell size should not change with more than a factor of 1.25 between neighbouring cells. For structured meshes also try to create fairly continous mesh lines and avoid discontinuities where the cell directions suddenly change. For multi-block structured meshes avoid placing the singular points where blocks meet in regions with strong flow gradients since most schemes have a lower accuracy in these singular points.<br />
<br />
=== Mesh size guidelines ===<br />
<br />
It is difficult to define, a priori, the mesh size. The required mesh size depends on the purpose of the simulation. <br />
<br />
If the main goal is to obtain static pressure forces a coarse mesh is often able to obtain a good solution, especially when an accurate resolution of the boundary layers is not required. For 2D inviscid simulations of one blade a mesh with say 3,000 cells is most often sufficient. For 3D inviscid blade simulations a mesh size of about 40,000 cells is usually sufficient. On inviscid Euler simulations the cells should be fairly equal in size and no boundary layer resolution should be present. Avoid having too skewed cells.<br />
<br />
For loss predictions and cases where boundary layer development and separation is important the mesh needs to have a boundary layer resolution. The boundary layer resolution can either be coarse and suitable for a [[Wall functions|wall function]] simulation or very fine and suitable for a [[Low-Re resolved boundary layers|low-Re]] simulation. For further information about selecting the near-wall turbulence model please see the [[#Turbulence modeling|turbulence modeling]] section. In 3D single-blade simulations a decent wall-function mesh typically has around 100,000 cells. This type of mesh size is suitable for quick design iterations where it is not essential to resolve all secondary flows and vortices. A good 3D wall-function mesh of a blade section intended to resolve secondary flows well should have at least 400,000 cells . A good low-Re mesh with resolved boundary layers typically has around 1,000,000 cells. <br />
<br />
In 2D blade simulations a good wall-function mesh has around 20,000 cells and a good low-Re mesh with resolved boundary layers has around 50,000 cells.<br />
<br />
Along the suction and pressure surfaces it is a good use about 100 cells in the streamwise direction. In the radial direction a good first approach is to use something like 30 cells for a wall-function mesh and 100 cells for a low-Re mesh.<br />
<br />
It is important to resolve leading and trailing edges well. Typically at least 10 cells, preferably 20 should be used around the leading and trailing edges. For very blunt and large leading edges, like those commonly found on HP turbine blades, 30 or more cells can be necessary.<br />
<br />
Cases which are difficult to converge with a steady simulation and which show tendencies of periodic vortex shedding from the trailing edge, can sometimes be "tamed" by using a coarse mesh around the trailing edge. This, of course, reduces the accuracy but can be a trick to obtain a converged solution if time and computer resources does not allow a transient simulation to be performed.<br />
<br />
=== Boundary layer mesh ===<br />
<br />
For design iteration type of simulations where a [[Wall functions|wall function]] approach is sufficient [[Dimensionless wall distance (y plus) | y+]] for the first cell should be somewhere between 20 and 200. The outer limit is dependent on the actual Re number of the simulations. For cases with fairly low Re numbers make sure to keep the maximum y+ as low as possible. For more accurate simulations with resolved boundary layers the mesh should have a y+ for the first cell which is below 1. Some new codes are now using a hybrid wall treatment that allows a smooth transition from a coarse wall-function mesh to a resolved low-Re mesh. Use some extra care when using this type of hybrid technique since it is still fairly new and unproven.<br />
<br />
Outside of the first cell at a wall a good rule of thumb is to use a growth ratio normal to the wall in the boundary layer of maximum 1.25. For a low-Re mesh this usually gives around 40 cells in the boundary layer whereas a wall-function mesh does not require more than 10 cells in the boundary layer.<br />
<br />
If you are uncertain of which wall distance to mesh with you can use a [http://www.cfd-online.com/Links/tools.html#yplus y+ estimation tool] to estitmate the distance needed to obtain the desired y+. These estimation tools are ''very handy'' if you have not done any previous similar simulations. <br />
<br />
As a rule of thumb a wall-function mesh typically requires areound 5 to 10 cells in the boundary layer whereas a resolved low-Re mesh requires about 40 cells in the boundary layer.<br />
<br />
== Boundary conditions ==<br />
<br />
Describe different types of boundary conditions and when they should be used:<br />
<br />
* Total pressure in, static pressure out<br />
* Absorbing boundary conditions<br />
* ...<br />
<br />
There are different types of boundary conditions you can use:<br />
*Mass flow inlet, static pressure outlet.<br />
To put this BC you must allocate inlet surface enough far away from the turbomachine impeller. The velocity distribution is not<br />
constant over all the surface. If you put this "lie" away from your problem it works well.<br />
<br />
<br />
=== Turbulence inlet conditions ===<br />
<br />
Prescribing realistic turbulence inlet conditions is important and usually difficult. For two-equation turbulence models two different turbulence values need to be specified on the inlet. The most common way of specifying the inlet turbulence variables is to give an inlet [[Turbulence intensity|turbulence level]] and [[Turbulence length scale|length-scale]]. For simulations where the incoming boundary layers are estimated to not have any significant effect on the secondary flows and global flow-field downstream it is usually sufficient to specify a constant incoming turbulence level and length-scale.<br />
<br />
The incoming [[Turbulence intensity|turbulence level]] is dependent on which component is analyzed. Best is of course to have measurments from a similar application in order to be able to prescribe a fairly realistic value. Without measurements it is necessary to make an educated guess. Simulations with very complex and turbulence-generating components upstream will have a very high incoming turbulence level. For example, a high-pressure turbine just downstream of a turbulence generating combustor might have incoming turbulence levels up to 20%. Fans and low-pressure compressors with not many components upstream might have as low incoming turbulence level as 1%. For components between these two extreme examples, like high-pressure compressors, low-pressure turbines etc. a turbulence level of around 5% might be realistic. If you do not have any measurements and are unsure about which incoming turbulence level to prescribe it is always a good idea to run a few different simulations with say one half and one double incoming turbulence level in order to estimate how important it is for the simulation results.<br />
<br />
The incoming [[Turbulence length scale|turbulence length-scale]] is often even more difficult to guess than the incoming turbulence level. Measurements might sometimes include the incoming turbulence level, but very seldom also include the incoming turbulent length-scale. The best way of guessing a realistic incoming length-scale is to use the geometrical properties of the upstream components. The incoming turbulence length-scale can be estimated as say the thickness of upstream blades or somewhere between 2% and 20% of the incoming channel heigth. Fortunately the incoming turbulence length-scale is usually not that important for the end results. However, some k-omega models can have an unrelisticly strong influence on the incoming turbulence length-scale. Hence, be extra carefull about the length-scale when using k-omega models. Note that the [[SST k-omega model]] does not have this unrealistic sensitivity to the inlet turbulence length-scale.<br />
<br />
Instead of specifying an incoming turbulence length-scale it is sometimes more convenient to specify an incoming [[Eddy viscosity ratio|eddy viscosity ratio]]. For low-turbulence cases with no well-specified turbulence generating components upstream it can be difficult to estimate a turbulence length-scale. Specifying an eddy viscosity ratio instead gives a more direct control over how large the effect of the incoming turbulence is. The eddy viscosity ratio describes how large the turbulence viscosity is related to the molecular viscosity. In turbomachinery the eddy viscosity ratio can vary from say 10 in low-turbulence components like fans up to say 1,000 or in rare cases even 10,000 in high-turbulence components like high-pressure turbines. In components between these extremes a typical eddy viscosity ration might be about 200. Even if specifying an inlet turbulence length scale it can still be good to compute what eddy viscosity ratio this corresponds to in order to estimate if it sounds reasonable.<br />
<br />
== Turbulence modeling ==<br />
<br />
Selecting a suitable turbulence model for turbomachinery simulations can be a challenging task. There is no single model which is suitable for all types of simulations. Which turbulence model CFD engineers use has as much to do with beliefs and traditions as with knowledge and facts. There are many different schools. However, below follows some advices that most CFD engineers in the turbomachinery field tend to agree upon.<br />
<br />
For attached flows close to the design point a simple algebraic model like the [[Baldwin-Lomax model]] can be used. Another common choice for design-iteration type of simulations is the one-equation model by [[Spalart-Allmaras model | Spalart-Allmaras]]. This model has become more popular in the last years due to the many inherent problems in more refined two-equation models. The big advantage with both the [[Baldwin-Lomax model]] and the [[Spalart-Allmaras model]] over more advanced models is that they are very robust to use and rarely produce completely unphysical results.<br />
<br />
In order to accurately predict more difficult cases, like separating flows, rotating flows, flows strongly affected by secondary flows etc. it is often necessary to use a more refined turbulence model. Common choices are two-equation models like the <math>k-\epsilon</math> model.<br />
<br />
Two-equation models are based on the [[Boussinesq eddy viscosity assumption]] and this often leads to an over-production of turbulent energy in regions with strong acceleration or deceleration, like in the leading edge region, regions around shocks and in the suction peak on the suction side of a blade. To reduce this problems it is common to use a special model variant using, for example, [[Durbin's realizability constraint]] or the [[Kato-Launder modification]]. Note that different two-equation models behave differently in these problematic stagnation and acceleration regions. Worst is probably the standard <math>k-\epsilon</math> model. <math>k-\omega</math> model are slightly better but still do not behave well. More modern variants like Menter's [[SST k-omega model]] also has problems, wheras the [[V2-f models|v2f model ]] by Durbin behaves better.<br />
<br />
=== Near-wall treatment ===<br />
<br />
For on-design simulations without any large separated regions it is often sufficient to use a [[wall-function model]] close to the wall, preferably with some form of non-equilibrium wall-function that is sensitised to streamwise pressure gradients.<br />
<br />
For off-design simulation, or simulations involving complex secondary flows and separations, it is often necessary to use a [[low-Re model]]. There exist many low-Re models that have been used with success in turbomachinery simulations. A robust and often good choice is to use a one-equation model, like for example the [[Wolfstein model]], in the inner parts of the boundary layer. There are also several Low-Re <math>k-\epsilon</math> models that work well. Just make sure they don't suffer from the problem with overproduction of turbulent energy in regions with strong acceleration or deceleration. In the last few years Menter's low-Re <math>SST k-\omega</math> model has gained increased popularity.<br />
<br />
=== Transition prediction ===<br />
<br />
Transition refers to the process when a laminar boundary layer becomes unstable and transitions to a turbulent boundary layer. There are two types of transition - natural transition, where inherent instabilities in the boundary layer cause the transition and by-pass transition, where convection and diffusion of turbulence from the free-stream into the boundary layer cause the transition. Most transitions in turbomachinery are by-pass transitions caused by free-stream turbulence and other external disturbances like wakes, vortices and surface defects.<br />
<br />
Simulating transition in a CFD code accurately is very difficult. Often a separate transition model needs to be solved in order to specify the transition location and length. Predicting natural transition in a pure CFD code is not possible. Predicting by-pass transition in a pure CFD code is almost impossible, although there are people who claim to be able to predict by-pass transition with low-Re two-equation models. However, this is usually on special test cases and with simulations that have been tuned for these special cases, see for example [Saville 2002]. In reality transition is a very complex and sensitive process where disturbances like incoming wakes and vortices from previous stages, surface roughness effects and small steps or gaps in the surfaces play a significant role. <br />
<br />
The turbomachinery codes that have transition prediction models often use old ad-hoc models like the Abu-Ghannam and Shaw model [Abu-Ghannam 1980] or the Mayle model [Mayle 1991]. These models can be quite reliable if they have been validated and tuned for a similar application. Do not trust your transition predictions without having some form of experimental validation. Menter has also recently developed a new form of transition model that might work fairly well, but it is still too new and untested.<br />
<br />
For some turbomachinery applications, like modern high-lift low-pressure turbines, transition is critical. For these applications a CFD code with a transition model that has been tuned for this type of applications should be used.<br />
<br />
== Numerical considerations ==<br />
<br />
Use at least a second order accurate scheme for the flow variables. Some codes require a first order scheme for the turbulent variables (<math>k</math> and <math>\epsilon</math>) in order to converge well. It might be sufficient with a first order scheme only on the turbulence variables, but a second order scheme is of course preferable.<br />
<br />
=== Convergence criteria ===<br />
<br />
To know when a solution is converged is not always that easy. You need some prior experience of your CFD code and your application to judge when a simulation is converged. For normal pure aero simulations without resolved walls, i.e. with wall functions or inviscid Euler simulations, convergence can most often be estimated just by looking at the residuals. Exactly what the residuals should be is not possible to say, it all depends on how your particular code computes and scales the residuals. Hence, make sure to read the manuals and plot the convergence of a few global parameters before you decide what the residuals should be for a solution to converge. Note also that many manuals for genereal purpose CFD codes list overly aggressive convergence criteria that often produce unconverged results. <br />
For simulations with resolved walls it is good to look at the convergence of some global properties, like total pressure losses from the inlet to the outlet. For heat transfer simulations it is even more tricky since the aerodynamic field can look almost converged although the thermal field is not converged at all. If doing heat transfer simulations make sure to plot the heat-transfer, run for some time, and plot it again to make sure that it doesn't change anymore. With very well resolved walls and heat transfer it can sometimes take 10 times longer for the thermal field to converge.<br />
<br />
=== Single or double precision ===<br />
<br />
With todays computers and cheap memory prices it often does not cost much extra to run in double precision. Before using single precision you should first investigate how your software and hardware works with double precision. If the extra time and memory needed for double precision is negligible you should of course always run in double precision. With double precision you never have to worry about round-off errors. Always using double precision is one way of avoiding one type of pit-falls in the complex world of CFD simulations. Use double precision when you have resolved boundary layers (Y+ around 1) and when you use advanced physical models like combustion, free-surface simulations, spray and transient simulations with quick mesh motions.<br />
<br />
== Multi-stage analysis ==<br />
<br />
Multi-stage analysis can be done in different ways:<br />
<br />
* Steady mixing-plane simulations<br />
* Frozen rotor simulations<br />
* Unsteady sliding-mesh stator-rotor simulations<br />
* Hybrid steady-unsteady stator-rotor simulations<br />
* Other '''advanced''' multi-stage methods<br />
<br />
=== Steady mixing-plane simulations ===<br />
<br />
Since the mixing-plane method was first introduced in 1979 [Denton & Singh 1979] it has become the industry standard type of rotor-stator simulations. A mixing-plane simulation is steady and only requires one rotor blade and one stator blade per stage. Between the rotating blade passage and the steady vane passage the flow properties are circumferentially averaged in a so-called mixing-plane interface. This will of course remove all transient rotor-stator interactions, but it still gives fairly representative results. In some commercial codes (CFX for example) mixing-plane interfaces are also called stage-interfaces.<br />
<br />
=== Frozen rotor simulations ===<br />
<br />
In a frozen rotor simulation the rotating and the stationary parts have a fixed relative position. A frame transformation is done to include the rotating effect on the rotating sections. This will give a steady flow and no transient effects are included. With a frozen-rotor simulation rotating wakes, secondary flows, leading edge pressure increases etc. will always stay in exactly the same positions. This makes a frozen rotor simulation very dependent on exactly how the rotors and the stators are positioned. Most often a mixing-plane simulation gives better results. Frozen rotor simulations are mainly performed to obtain a good starting flow-field before doing a transient sliding-mesh simulation.<br />
<br />
=== Unsteady sliding-mesh stator-rotor simulations ===<br />
<br />
This is the most complete type of stator-rotor simulation. In most engines the number of stators and rotors do not have a common denominator (to avoid instabilities caused by resonance between different rings). Hence, to make a full unsteady sliding-mesh computation it is necessary to have a mesh which includes the full wheel with all stators vanes and all rotor blades. This is often not possible, instead it is necessary to reduce the number of vanes and blades by finding a denominator that is '''almost''' common and then scale the geometry slightly circumferentially. Here is an example:<br />
<br />
*Real engine: 36 stator vanes, 41 rotor blades<br />
*Approximated engine: 41 stator vanes, 41 rotor blades, making it possible to simulate only 1 stator vane and 1 rotor blade<br />
*Scaling of stator: All stator vanes are scaled by 36/41 = 0.8780 circumferentially.<br />
<br />
<br />
=== Hybrid steady-unsteady stator-rotor simulations ===<br />
<br />
Hybrid steady-unsteady methods have been proposed in literature (Montomoli et al. 2011) in order to have an unsteady simulation embedded in a multistage steady study. <br />
There are several advantages related to this method: mainly grid size and number of iterations.<br />
<br />
=== Other '''advanced''' multi-stage methods ===<br />
<br />
Time-inclinded, Adamszyk stresses ...<br />
<br />
== Heat transfer predictions ==<br />
<br />
Besides listing the general heat transfer mechanisms involved <br />
(namely conduction, convection, radiation)<br />
heat transfer prediction in CFD may be seen as or split into two cases. <br />
<br />
'''Mesh consists of fluid domain(s)''': <br />
you want to know how heat inserted into the fluid domain (e.g. via the flowing medium) changes the temperature field along the flow path. Be it a steady or transient run, a fluid which enters with a given temperature will usually experience temperature variations, for instance, caused by convective boundary conditions, prescribed temperature profiles at flow obstacles etc. <br />
<br />
'''Mesh consists of fluid and solid domain(s)''': <br />
additionally to the above, you want info too wrt the (spatial, temporal or even spectral) temperature field distribution in surrounding, confining or immersed solids like channel walls or heat exchanger tubes. This is also called conjugate heattransfer CHT in the CFD context. CHT requires a good boundary layer resolution, usually the wall mesh needs to be rather refined, to obtain realistic heatflux results at the fluid/solid interface. Flow and heat transfer convergence require different time step settings, to properly capture changes in flow and heat quantities respectively. <br />
<br />
<br />
In either case, verify (strict necessity depends on CFD code used, CFX for instance checks and assists in regard) that model dimensions, boundary conditions and properties are in consistent units, hold appropriate values. Check temperature-dependence of properties and other numbers before the run.<br />
<br />
In heat transfer predictions (depending on the CFD code in use) <br />
besides the flow solver, you may have to activate the thermal solver too, <br />
as a job specification.<br />
<br />
== Acoustics and noise ==<br />
<br />
A whole separate research subject, difficult. <br />
<br />
Tone noise possible. Often run with linearzised solvers in the frequency domain.<br />
<br />
Jet noise possible. Often run with LES or DES simulations that either also resolve the sound waves or couples to a separate acoustic solver.<br />
<br />
Turbomachinery broadband noise not possible yet, or at least a great challenge.<br />
<br />
== Errors and uncertainties ==<br />
<br />
CFD is still a tool which requires that a user has a good understanding of uncertainties and errors that might spoil a CFD similation. There exists no error control in CFD and any CFD simulation must be interpreted by an expirenced user to have some credibility. Without some knowledge about possible errors and how they can be handled a CFD simulation can not be trusted. Errors can occur at different places:<br />
<br />
* Definition of the problem - What needs to be analyzed?<br />
* Selection of the solution strategy - What physical models and what numerical tools should be used?<br />
* Development of the computational model - How should the geometry and the numerical tools be set up?<br />
* Analysis and interpretation of the results - How should the model be analyzed and the results be interpreted?<br />
<br />
There exists many different definitions on errors. In this guide the errors are classified into four types of errors: problem definition errors, model errors, numerical errors and user and code errors. The chapters below describe these errors and give some guidelines on how to avoid them.<br />
<br />
=== Problem definition errors ===<br />
<br />
Problem definition errors are the most basic form of errors. In order to obtain usefull results a CFD simulation must of course analyze the correct problem, have suitable boundary contions and be based on a relevant geometry.<br />
<br />
==== Wrong type of simulation ====<br />
<br />
It is essential to have an overview of the physics involved and how the problem can best be analyzed. Running a 2D simulation in order to understand secondary flows or running a steady simulation in order to understand transient behaviour is of course no use. When assessing a CFD simulation the first thing to consider is what physical phenomena are important for the results and if the selected type of simulation is suitable to resolve this type of phenomena. For further information about selecting the most suitable type of simulation please see the previous chapter on [[#Deciding what type of simulation to do|deciding what type of simulation to perform]].<br />
<br />
==== Incorrect or uncertain boundary conditions ====<br />
<br />
A common source of errors is that incorrect boundary conditions are used. The boundary conditions must be specified in enough detail in order to resolve all the important physical features in the problem. For further information about specifying boundary conditions please see the previous chapter on [[#Boundary conditions|boundary conditions]].<br />
<br />
==== Geometrical errors ====<br />
<br />
It is almost always necessary to simplify the geometry in some form. When assessing a CFD simulation one should consider how the geometrical simplifications can affect the interesting physical phenomena. Typical geometrical errors are:<br />
<br />
*Simplifications<br />
:Small geometrical features like fillets, small steps or gaps etc. can often be disregarded. When disregarding this type of features one should consider if they might affect the important physics. For example, a very large fillet on the suction-side of a vane might affect corner separations near the end-walls. A large tip-leakage might affect the flow physics significantly in the upper part of a compressor.<br />
*Tolerances and manufacturing discrepancies<br />
:If the geometry has very large tolerances or is manufactured in a way which might produce a non-ideal shape or position it might be necessary to perform additional CFD simulations in order to cover the whole span of possible real geometries.<br />
*Surface conditions - roughness, welds, steps, gaps etc.<br />
:Often CFD simulations assume a perfectly smooth surface. A non-smooth surface which might have welds, steps or even gaps will of course produce different results. If the physical phenomena of interest might depend on the surface conditions these should of course be condidered. Typical phenomena that might be dependent on this type of errors are transition prediction, leakage flows etc.<br />
<br />
More recently Uncertainty Quantification techniques have been applied to turbomachinery to model real geometries considering their stochastic variations [Montomoli et al. 2013]<br />
<br />
=== Model errors ===<br />
<br />
Errors related to the computational model.<br />
<br />
==== Wrong physical models ====<br />
<br />
Once the type of simulation has been selected the next step is to select what type of physical models the simulation should use. The following points should be considered:<br />
<br />
* Gas data (incompressible/compressible, perfect gas/real gas, ...)<br />
* Turbulence modeling (type of model, type of near-wall treatment, ...)<br />
* Other models (combustion, sprays, ...)<br />
<br />
When assessing model related errors it is important to know the features of the selected model and think carefully how these features and possible short comings might affect the predicted physical behaviour. Using the wrong turbulence model or combustion model can completely destroy the results of a CFD simulation.<br />
<br />
=== Numerical errors ===<br />
<br />
Errors related to the numerical solution of the developed model. Typical examples of numerical errors are discretization errors, convergence errors and round-off errors.<br />
<br />
==== Discretization errors ====<br />
<br />
Discretization errors can either be spatial errors in space or temporal errors in time.<br />
<br />
Spatial discretization errors are what people normally call discretization errors. These errors are due to the difference between the exact solution and the numerical representation of the solution in space. Describing exactly what discretization different codes use and what errors this might lead to is not possible here. Instead some general rules to avoid these errors can be summarized as:<br />
* Use at least a 2nd order accurate scheme, preferably a 3rd order accurate scheme. Some general purpose codes have a 1st order upwind scheme as default, this is a very diffusives schemes that often gives too smooth results.<br />
* For new applications always run a simulation with a finer mesh to see how grid independent your solution is.<br />
* Be aware of checker-board errors. Checker-board errors occur close to strong shocks and other large discontinuities and can be seen as a wavy pattern with a wavelength of two cells. Some schemes, especially those who behave like central differencing schemes, are more prone to checker-board errors. Upwind schemes are a bit better and schemes like TVD or chock-capturing schemes are even better.<br />
<br />
Temporal discretization errors mainly effect transient simulations. However, some codes use a time-marching method also for steady simulations and then a temporal discretization error might affect the final steady solution slightly. The discretization in time can be done with 1st or 2nd order schemes or a Runge-Kutta method, which is more accurate and saves memory. Some codes can adapt the time-step, but often it is necessary to prescribe a time-step in advance. Think of the time-step as your grid in time and make sure that the grid-resolution in time is fine enough to resolve the highest frequencies. To avoid problems with temporal discretization errors the following should be considered:<br />
* Use at least a 2nd order scheme in time.<br />
* Do a physical estimation of the typical frequencies in time of the phenomena that you are interested in and select a time-step which is fine enough to resolve these frequencies well. After the simulation also look at the frequencies captured and make sure that they are well resolved by the chosen time-step.<br />
* For new applications try a finer time-step to ensure that your solution in time is fairly grid independent in time.<br />
<br />
==== Convergence errors ====<br />
<br />
To judge when a CFD simulation is converged is not always that easy. Different codes and different applications behave very differently. For a pure aero-simulation on a fairly coarse grid convergence is easy to judge, but for more complex simulations involving resolved boundary layers, heat transfer, combustion etc. convergence can be very tricky. Aside from looking at residuals one should always also look at how global parameters like static pressure distributions, total pressure losses, skin friction, heat transfer etc. change in time.<br />
For more information about how to avoid convergence errors see the previous chapter about [[#Convergence criteria]].<br />
<br />
==== Round-off errors ====<br />
<br />
When using single precision care needs to be taken to avoid round-off errors. Inviscid Euler simulations and simulations using wall-function meshes can most often be performed in single precision. For well resolved boundary layers with Y plus close to 1 it is often necessary to use double precision. If using double precision for very fine mesh resolutions make sure that you also create the mesh in double precision and not just run the solver in double precision. Sometimes a single precision solver converges slower than a double precision solver due to numerical errors caused by round-off errors. When using advanced physical models like combustion, free-surface simulations, spray and transient simulations with quick mesh motions it is also often necessary to use double precision.<br />
<br />
=== User and code errors ===<br />
<br />
Errors related to bugs in the code used or mistakes made by the CFD engineer.<br />
<br />
=== What to trust and what not to trust ===<br />
<br />
CFD is generally quite good at predicting surface static pressure distributions. With care CFD can also be used to predict performance, total-pressure losses and blade turning. <br />
<br />
Predicting separation, stall and off-design performance can be a challenge and results with non-attached flows should be interpreted with care. <br />
<br />
Heat transfer is often very difficult to predict accurately and it is common to obtain heat-transfer coefficients that are 100% wrong or more. Validation data is critical in order to be able to trust heat transfer simulations.<br />
<br />
Transition is almost impossible to predict accurately in general. However, there exist models that have been tuned to predict transition and these tend to give acceptable results for cases close to the ones they were tuned for.<br />
<br />
== References ==<br />
<br />
* {{reference-paper|author=Abu-Ghannam, B.J. and Shaw, R.|year=1980|title=Natural Transition of Boundary Layers - the Effects of Turbulence, Pressure Gradient, and Flow History|rest=Journal of Mech. Eng. Science, vol. 22, no. 5, pp. 213–228}}<br />
<br />
* {{reference-paper|author=Adamczyk, J. J.|year=1985|title=Model Equation for Simulating Flows in Multistage Turbomachinery|rest=ASME Paper 85-GT-226, also NASA TM-86869}}<br />
<br />
* {{reference-paper|author=Adamczyk, J. J.|year=1999|title=Aerodynamic Analysis of Multistage Turbomachinery Flows in Support of Aerodynamic Design|rest=ASME Paper 99-GT-80.}}<br />
<br />
* {{reference-paper|author=Baldwin, B. S. and Lomax, H.|year=1978|title=Thin Layer Approximation and Algebraic Model for Separated Turbulent Flows|rest=AIAA Paper 78-257}}<br />
<br />
* {{reference-paper|author=Chen, J. P. and Barter, J. W.|year=1998|title=Comparison of Time-Accurate Calculations for the Unsteady Interaction in Turbomachinery Stage|rest=AIAA Paper 98-3292}}<br />
<br />
* {{reference-paper|author=Denton, J. and Singh, U.|year=1979|title=Time Marching Methods for Turbomachinery Flow Calculations|rest=VKI Lecture Series 1979-7, von Karman Institute}}<br />
<br />
* {{reference-paper|author=Erdos, J., Alzner, E. and McNally, W.|year=1977|title=Numerical Solution of Periodic Transonic Flow Through a Transonic Fan Stage|rest=AIAA Journal, vol. 15, no. 11, pp. 1559-1568}}<br />
<br />
* {{reference-paper|author=Gerolymos, G., Vinteler, D., Haugeard, R., Tsange, G. and Vallet, I.|year=1996|title=On the Computation of Unsteady Turbomachinery Flows – Part II – Rotor/Stator Interaction using Euler Equations|rest=AGARD Report CP-571}}<br />
<br />
* {{reference-paper|author=Giles, M. B.|year=1990|title=Stator/Rotor Interaction in a Transonic Turbine|rest=AIAA Journal of Propulsion and Power, vol. 6, no. 5}}<br />
<br />
* {{reference-paper|author=He, L, and Ning, W.|year=1998|title=Efficient Approach for Analysis of Unsteady Viscous Flows in Turbomachines|rest=AIAA Journal, vol. 36, no. 11, pp. 2005-2012}}<br />
<br />
* {{reference-paper|author=Mayle, R. E.|year=1991|title=The Role of Laminar-Turbulent Transition in Gas Turbine Engines|rest=ASME Journal of Turbomachinery, vol. 113, pp. 509-537}}<br />
<br />
* {{reference-paper|author=Menter, F.R. |year=1994|title=Two-equation eddy-viscosity turbulence models for engineering applications|rest=AIAA Journal, vol. 32, pp. 269-289}}<br />
<br />
* {{reference-paper|author= Montomoli, F., Hodson,H.P, Lapworth, L. |year=2011|title=RANS-URANS in axial compressors, a design methodology|rest=Journal of Power and Energy, 225 (A3), pp. 363-374}}<br />
<br />
* {{reference-paper|author= Montomoli, F., D'Ammaro,A., Uchida, S. |year=2013|title=Uncertainty Quantification and Conjugate Heat Transfer: a Stochastic Analysis|rest=Journal of Turbomachinery, 135(3), 031014}}<br />
<br />
* {{reference-paper|author=Savill, M., Dick, E., Hanjalić, K. and Voke, P.|year=2002|title=Synthesis Report of the ERCOFTAC Transition Modeling – TRANSPRETURB Thematic Network Activities 1998-2002|rest=Ecoftac Bulletin 54, September 2002, pp. 5-16}}<br />
<br />
* {{reference-paper|author=Wang, X. and Chen J.|year=2004|title=A Post-Processor to Render Turbomachinery Flows Using Phase-Lag Simulations|rest=AIAA Paper 04-615}}<br />
<br />
== External links ==<br />
<br />
* [https://pronet.wsatkins.co.uk/marnet/guidelines/guide.html MARNET-CFD Best Practice Guidelines for Marine Applications of CFD]<br />
* [http://www.stanford.edu/group/ctr/ResBriefs/temp05/weide.pdf On Large Scale Turbomachinery Computations, by E. van der Weide et. al., Center for Turbulence Research, Annual Research Briefs 2005]</div>Frmontohttps://www.cfd-online.com/Wiki/Best_practice_guidelines_for_turbomachinery_CFDBest practice guidelines for turbomachinery CFD2013-08-23T10:25:13Z<p>Frmonto: /* Geometrical errors */</p>
<hr />
<div>This article contains a summary of the most important knowledge and experience a CFD engineer needs in order to perform CFD simulations of turbomachinery components. The guide is mainly aimed at axial turbomachinery. The goal is to give a CFD engineer, who has just started working with turbomachinery simulations, a head start and avoid some of the most difficult pit-falls. Experienced turbomachinery CFD engineers can also use the guidelines in order to learn what other experts consider best practice. The intended audience is expected to know basic CFD terminology and have a basic turbomachinery knowledge, but no detailed knowledge about CFD for turbomachinery is needed. <br />
<br />
== Deciding what type of simulation to do ==<br />
<br />
Before starting a new turbomachinery simulation it is wise to think carefully of what it is that should be predicted and what physical phenomena that affect the results. This chapter contains a brief overview of the various types of simulations and some hints of what can be predicted with them.<br />
<br />
=== 2D, Quasi-3D or 3D ===<br />
<br />
2D simulations are often used in the early design phase in order to obtain a typical 2D section of a blade. For cases with many long blades or vanes, like low-pressure turbines, a 2D simulation can also provide reasonable results. If the area of the flow-path changes significantly in the axial direction it might be necessary to instead make a quasi-3D simulation. A quasi-3D simulation is a 2D simulation in which extra source terms are used to account for the acceleration/deceleration caused by a changing channel height or growing end-wall boundary layers. Codes focused on turbomachinery applications often have the possibility to perform quasi-3D simulations, but most general purpose CFD codes can not do this type of simulations, or require user coding to implement the correct source terms in the equations. Please contact your software distributor if your code does not have the quasi-3d possibility and you require it. Many codes require special routines or hidden commands to enable this feature.<br />
<br />
Full 3D simulations are necessary if a true 3D geometry is needed to obtain correct secondary flows and/or shock locations. For low-aspect-ratio cases with only a few short blades, like for example structurally loaded turbine outlet guide vanes, the secondary flow development is important and a 3D simulation is often necessary in order to obtain reasonable results. For applications where the end-wall boundary layers grow very quickly and interact with a large part of the flow-field it is necessary to perform a full 3D simulation. This is often the case in compressors and fans, where the negative pressure gradients make the boundary layers grow much quicker than what they do in for example turbines. For cases where the shock location is very critical, like in transonic compressors, it is also often necessary to perform a 3D simulation in order to obtain reasonable shock locations.<br />
<br />
=== Inviscid or viscid ===<br />
<br />
For attached flows close to the design point and without any large separations it is often sufficient with an inviscid Euler simulation in order to obtain reasonable blade loadings and pressure distributions. Note that inviscid Euler simulations should only be used if the boundary layers are judged to not have a significant effect on the global flow-field. A viscid Navier-Stokes simulation is necessary in order to predict losses, secondary flows and separations. As soon as separations are of interest it is of course also necessary to do a viscid simulation. Note that with todays computers it is often not time and resources that make users run inviscid Euler simulations. Running viscid Navier-Stokes simulations is now so quick that it is not a time problem any more. Euler simulations are still interesting though, since with an inviscid Euler simulation you don't have to worry about wall resolutions, y+ values, turbulence modeling errors etc.<br />
<br />
=== Transient or Stationary ===<br />
<br />
Most turbomachinery simulations are performed as stationary simulations. Transient simulations are done when some kind of transient flow behaviour has a strong influence on the global flow field. Examples of transient simulations are detailed simulations of rotor-stator interaction effects, simulations of large unsteady separations etc. Sometimes when you perform a steady stationary simulation you can see tendencies of unsteady behaviour like for example periodic vortex shedding behind blunt trailing edges. This is often first seen as periodical variations of the residuals. If the unsteady tendencies are judged to not affect the overall simulation results it might be necessary to coarsen the mesh close to the vortex shedding or run a different turbulence model in order to make the simulation converge. Sometimes you are still forced to run a transient simulation and average the results if you don't obtain a converged steady solution.<br />
<br />
== Meshing ==<br />
<br />
In turbomachinery applications structured multi-block hexahedral meshes are most often used for flow-path simulations. In most solvers a structured grid requires less memory, provides superior accuracy and allows a better boundary-layer resolution than an unstructured grid. By having cells with a large aspect ratio around sharp leading and trailing edges a structured grid also provides a better resolution of these areas. Many companies have automatic meshing tools that automatically mesh blade sections with a structured mesh without much user intervention.<br />
<br />
Unstructured meshes are used for more complex and odd geometries where a structured mesh is difficult to create. Typical examples where unstructured meshes are often used are blade tip regions, areas involving leakage flows and secondary air systems, film cooling ducts etc.<br />
<br />
When meshing avoid to create large jumps in cell sizes. Typically the cell size should not change with more than a factor of 1.25 between neighbouring cells. For structured meshes also try to create fairly continous mesh lines and avoid discontinuities where the cell directions suddenly change. For multi-block structured meshes avoid placing the singular points where blocks meet in regions with strong flow gradients since most schemes have a lower accuracy in these singular points.<br />
<br />
=== Mesh size guidelines ===<br />
<br />
It is difficult to define, a priori, the mesh size. The required mesh size depends on the purpose of the simulation. <br />
<br />
If the main goal is to obtain static pressure forces a coarse mesh is often able to obtain a good solution, especially when an accurate resolution of the boundary layers is not required. For 2D inviscid simulations of one blade a mesh with say 3,000 cells is most often sufficient. For 3D inviscid blade simulations a mesh size of about 40,000 cells is usually sufficient. On inviscid Euler simulations the cells should be fairly equal in size and no boundary layer resolution should be present. Avoid having too skewed cells.<br />
<br />
For loss predictions and cases where boundary layer development and separation is important the mesh needs to have a boundary layer resolution. The boundary layer resolution can either be coarse and suitable for a [[Wall functions|wall function]] simulation or very fine and suitable for a [[Low-Re resolved boundary layers|low-Re]] simulation. For further information about selecting the near-wall turbulence model please see the [[#Turbulence modeling|turbulence modeling]] section. In 3D single-blade simulations a decent wall-function mesh typically has around 100,000 cells. This type of mesh size is suitable for quick design iterations where it is not essential to resolve all secondary flows and vortices. A good 3D wall-function mesh of a blade section intended to resolve secondary flows well should have at least 400,000 cells . A good low-Re mesh with resolved boundary layers typically has around 1,000,000 cells. <br />
<br />
In 2D blade simulations a good wall-function mesh has around 20,000 cells and a good low-Re mesh with resolved boundary layers has around 50,000 cells.<br />
<br />
Along the suction and pressure surfaces it is a good use about 100 cells in the streamwise direction. In the radial direction a good first approach is to use something like 30 cells for a wall-function mesh and 100 cells for a low-Re mesh.<br />
<br />
It is important to resolve leading and trailing edges well. Typically at least 10 cells, preferably 20 should be used around the leading and trailing edges. For very blunt and large leading edges, like those commonly found on HP turbine blades, 30 or more cells can be necessary.<br />
<br />
Cases which are difficult to converge with a steady simulation and which show tendencies of periodic vortex shedding from the trailing edge, can sometimes be "tamed" by using a coarse mesh around the trailing edge. This, of course, reduces the accuracy but can be a trick to obtain a converged solution if time and computer resources does not allow a transient simulation to be performed.<br />
<br />
=== Boundary layer mesh ===<br />
<br />
For design iteration type of simulations where a [[Wall functions|wall function]] approach is sufficient [[Dimensionless wall distance (y plus) | y+]] for the first cell should be somewhere between 20 and 200. The outer limit is dependent on the actual Re number of the simulations. For cases with fairly low Re numbers make sure to keep the maximum y+ as low as possible. For more accurate simulations with resolved boundary layers the mesh should have a y+ for the first cell which is below 1. Some new codes are now using a hybrid wall treatment that allows a smooth transition from a coarse wall-function mesh to a resolved low-Re mesh. Use some extra care when using this type of hybrid technique since it is still fairly new and unproven.<br />
<br />
Outside of the first cell at a wall a good rule of thumb is to use a growth ratio normal to the wall in the boundary layer of maximum 1.25. For a low-Re mesh this usually gives around 40 cells in the boundary layer whereas a wall-function mesh does not require more than 10 cells in the boundary layer.<br />
<br />
If you are uncertain of which wall distance to mesh with you can use a [http://www.cfd-online.com/Links/tools.html#yplus y+ estimation tool] to estitmate the distance needed to obtain the desired y+. These estimation tools are ''very handy'' if you have not done any previous similar simulations. <br />
<br />
As a rule of thumb a wall-function mesh typically requires areound 5 to 10 cells in the boundary layer whereas a resolved low-Re mesh requires about 40 cells in the boundary layer.<br />
<br />
== Boundary conditions ==<br />
<br />
Describe different types of boundary conditions and when they should be used:<br />
<br />
* Total pressure in, static pressure out<br />
* Absorbing boundary conditions<br />
* ...<br />
<br />
There are different types of boundary conditions you can use:<br />
*Mass flow inlet, static pressure outlet.<br />
To put this BC you must allocate inlet surface enough far away from the turbomachine impeller. The velocity distribution is not<br />
constant over all the surface. If you put this "lie" away from your problem it works well.<br />
<br />
<br />
=== Turbulence inlet conditions ===<br />
<br />
Prescribing realistic turbulence inlet conditions is important and usually difficult. For two-equation turbulence models two different turbulence values need to be specified on the inlet. The most common way of specifying the inlet turbulence variables is to give an inlet [[Turbulence intensity|turbulence level]] and [[Turbulence length scale|length-scale]]. For simulations where the incoming boundary layers are estimated to not have any significant effect on the secondary flows and global flow-field downstream it is usually sufficient to specify a constant incoming turbulence level and length-scale.<br />
<br />
The incoming [[Turbulence intensity|turbulence level]] is dependent on which component is analyzed. Best is of course to have measurments from a similar application in order to be able to prescribe a fairly realistic value. Without measurements it is necessary to make an educated guess. Simulations with very complex and turbulence-generating components upstream will have a very high incoming turbulence level. For example, a high-pressure turbine just downstream of a turbulence generating combustor might have incoming turbulence levels up to 20%. Fans and low-pressure compressors with not many components upstream might have as low incoming turbulence level as 1%. For components between these two extreme examples, like high-pressure compressors, low-pressure turbines etc. a turbulence level of around 5% might be realistic. If you do not have any measurements and are unsure about which incoming turbulence level to prescribe it is always a good idea to run a few different simulations with say one half and one double incoming turbulence level in order to estimate how important it is for the simulation results.<br />
<br />
The incoming [[Turbulence length scale|turbulence length-scale]] is often even more difficult to guess than the incoming turbulence level. Measurements might sometimes include the incoming turbulence level, but very seldom also include the incoming turbulent length-scale. The best way of guessing a realistic incoming length-scale is to use the geometrical properties of the upstream components. The incoming turbulence length-scale can be estimated as say the thickness of upstream blades or somewhere between 2% and 20% of the incoming channel heigth. Fortunately the incoming turbulence length-scale is usually not that important for the end results. However, some k-omega models can have an unrelisticly strong influence on the incoming turbulence length-scale. Hence, be extra carefull about the length-scale when using k-omega models. Note that the [[SST k-omega model]] does not have this unrealistic sensitivity to the inlet turbulence length-scale.<br />
<br />
Instead of specifying an incoming turbulence length-scale it is sometimes more convenient to specify an incoming [[Eddy viscosity ratio|eddy viscosity ratio]]. For low-turbulence cases with no well-specified turbulence generating components upstream it can be difficult to estimate a turbulence length-scale. Specifying an eddy viscosity ratio instead gives a more direct control over how large the effect of the incoming turbulence is. The eddy viscosity ratio describes how large the turbulence viscosity is related to the molecular viscosity. In turbomachinery the eddy viscosity ratio can vary from say 10 in low-turbulence components like fans up to say 1,000 or in rare cases even 10,000 in high-turbulence components like high-pressure turbines. In components between these extremes a typical eddy viscosity ration might be about 200. Even if specifying an inlet turbulence length scale it can still be good to compute what eddy viscosity ratio this corresponds to in order to estimate if it sounds reasonable.<br />
<br />
== Turbulence modeling ==<br />
<br />
Selecting a suitable turbulence model for turbomachinery simulations can be a challenging task. There is no single model which is suitable for all types of simulations. Which turbulence model CFD engineers use has as much to do with beliefs and traditions as with knowledge and facts. There are many different schools. However, below follows some advices that most CFD engineers in the turbomachinery field tend to agree upon.<br />
<br />
For attached flows close to the design point a simple algebraic model like the [[Baldwin-Lomax model]] can be used. Another common choice for design-iteration type of simulations is the one-equation model by [[Spalart-Allmaras model | Spalart-Allmaras]]. This model has become more popular in the last years due to the many inherent problems in more refined two-equation models. The big advantage with both the [[Baldwin-Lomax model]] and the [[Spalart-Allmaras model]] over more advanced models is that they are very robust to use and rarely produce completely unphysical results.<br />
<br />
In order to accurately predict more difficult cases, like separating flows, rotating flows, flows strongly affected by secondary flows etc. it is often necessary to use a more refined turbulence model. Common choices are two-equation models like the <math>k-\epsilon</math> model.<br />
<br />
Two-equation models are based on the [[Boussinesq eddy viscosity assumption]] and this often leads to an over-production of turbulent energy in regions with strong acceleration or deceleration, like in the leading edge region, regions around shocks and in the suction peak on the suction side of a blade. To reduce this problems it is common to use a special model variant using, for example, [[Durbin's realizability constraint]] or the [[Kato-Launder modification]]. Note that different two-equation models behave differently in these problematic stagnation and acceleration regions. Worst is probably the standard <math>k-\epsilon</math> model. <math>k-\omega</math> model are slightly better but still do not behave well. More modern variants like Menter's [[SST k-omega model]] also has problems, wheras the [[V2-f models|v2f model ]] by Durbin behaves better.<br />
<br />
=== Near-wall treatment ===<br />
<br />
For on-design simulations without any large separated regions it is often sufficient to use a [[wall-function model]] close to the wall, preferably with some form of non-equilibrium wall-function that is sensitised to streamwise pressure gradients.<br />
<br />
For off-design simulation, or simulations involving complex secondary flows and separations, it is often necessary to use a [[low-Re model]]. There exist many low-Re models that have been used with success in turbomachinery simulations. A robust and often good choice is to use a one-equation model, like for example the [[Wolfstein model]], in the inner parts of the boundary layer. There are also several Low-Re <math>k-\epsilon</math> models that work well. Just make sure they don't suffer from the problem with overproduction of turbulent energy in regions with strong acceleration or deceleration. In the last few years Menter's low-Re <math>SST k-\omega</math> model has gained increased popularity.<br />
<br />
=== Transition prediction ===<br />
<br />
Transition refers to the process when a laminar boundary layer becomes unstable and transitions to a turbulent boundary layer. There are two types of transition - natural transition, where inherent instabilities in the boundary layer cause the transition and by-pass transition, where convection and diffusion of turbulence from the free-stream into the boundary layer cause the transition. Most transitions in turbomachinery are by-pass transitions caused by free-stream turbulence and other external disturbances like wakes, vortices and surface defects.<br />
<br />
Simulating transition in a CFD code accurately is very difficult. Often a separate transition model needs to be solved in order to specify the transition location and length. Predicting natural transition in a pure CFD code is not possible. Predicting by-pass transition in a pure CFD code is almost impossible, although there are people who claim to be able to predict by-pass transition with low-Re two-equation models. However, this is usually on special test cases and with simulations that have been tuned for these special cases, see for example [Saville 2002]. In reality transition is a very complex and sensitive process where disturbances like incoming wakes and vortices from previous stages, surface roughness effects and small steps or gaps in the surfaces play a significant role. <br />
<br />
The turbomachinery codes that have transition prediction models often use old ad-hoc models like the Abu-Ghannam and Shaw model [Abu-Ghannam 1980] or the Mayle model [Mayle 1991]. These models can be quite reliable if they have been validated and tuned for a similar application. Do not trust your transition predictions without having some form of experimental validation. Menter has also recently developed a new form of transition model that might work fairly well, but it is still too new and untested.<br />
<br />
For some turbomachinery applications, like modern high-lift low-pressure turbines, transition is critical. For these applications a CFD code with a transition model that has been tuned for this type of applications should be used.<br />
<br />
== Numerical considerations ==<br />
<br />
Use at least a second order accurate scheme for the flow variables. Some codes require a first order scheme for the turbulent variables (<math>k</math> and <math>\epsilon</math>) in order to converge well. It might be sufficient with a first order scheme only on the turbulence variables, but a second order scheme is of course preferable.<br />
<br />
=== Convergence criteria ===<br />
<br />
To know when a solution is converged is not always that easy. You need some prior experience of your CFD code and your application to judge when a simulation is converged. For normal pure aero simulations without resolved walls, i.e. with wall functions or inviscid Euler simulations, convergence can most often be estimated just by looking at the residuals. Exactly what the residuals should be is not possible to say, it all depends on how your particular code computes and scales the residuals. Hence, make sure to read the manuals and plot the convergence of a few global parameters before you decide what the residuals should be for a solution to converge. Note also that many manuals for genereal purpose CFD codes list overly aggressive convergence criteria that often produce unconverged results. <br />
For simulations with resolved walls it is good to look at the convergence of some global properties, like total pressure losses from the inlet to the outlet. For heat transfer simulations it is even more tricky since the aerodynamic field can look almost converged although the thermal field is not converged at all. If doing heat transfer simulations make sure to plot the heat-transfer, run for some time, and plot it again to make sure that it doesn't change anymore. With very well resolved walls and heat transfer it can sometimes take 10 times longer for the thermal field to converge.<br />
<br />
=== Single or double precision ===<br />
<br />
With todays computers and cheap memory prices it often does not cost much extra to run in double precision. Before using single precision you should first investigate how your software and hardware works with double precision. If the extra time and memory needed for double precision is negligible you should of course always run in double precision. With double precision you never have to worry about round-off errors. Always using double precision is one way of avoiding one type of pit-falls in the complex world of CFD simulations. Use double precision when you have resolved boundary layers (Y+ around 1) and when you use advanced physical models like combustion, free-surface simulations, spray and transient simulations with quick mesh motions.<br />
<br />
== Multi-stage analysis ==<br />
<br />
Multi-stage analysis can be done in different ways:<br />
<br />
* Steady mixing-plane simulations<br />
* Frozen rotor simulations<br />
* Unsteady sliding-mesh stator-rotor simulations<br />
* Hybrid steady-unsteady stator-rotor simulations<br />
* Other '''advanced''' multi-stage methods<br />
<br />
=== Steady mixing-plane simulations ===<br />
<br />
Since the mixing-plane method was first introduced in 1979 [Denton & Singh 1979] it has become the industry standard type of rotor-stator simulations. A mixing-plane simulation is steady and only requires one rotor blade and one stator blade per stage. Between the rotating blade passage and the steady vane passage the flow properties are circumferentially averaged in a so-called mixing-plane interface. This will of course remove all transient rotor-stator interactions, but it still gives fairly representative results. In some commercial codes (CFX for example) mixing-plane interfaces are also called stage-interfaces.<br />
<br />
=== Frozen rotor simulations ===<br />
<br />
In a frozen rotor simulation the rotating and the stationary parts have a fixed relative position. A frame transformation is done to include the rotating effect on the rotating sections. This will give a steady flow and no transient effects are included. With a frozen-rotor simulation rotating wakes, secondary flows, leading edge pressure increases etc. will always stay in exactly the same positions. This makes a frozen rotor simulation very dependent on exactly how the rotors and the stators are positioned. Most often a mixing-plane simulation gives better results. Frozen rotor simulations are mainly performed to obtain a good starting flow-field before doing a transient sliding-mesh simulation.<br />
<br />
=== Unsteady sliding-mesh stator-rotor simulations ===<br />
<br />
This is the most complete type of stator-rotor simulation. In most engines the number of stators and rotors do not have a common denominator (to avoid instabilities caused by resonance between different rings). Hence, to make a full unsteady sliding-mesh computation it is necessary to have a mesh which includes the full wheel with all stators vanes and all rotor blades. This is often not possible, instead it is necessary to reduce the number of vanes and blades by finding a denominator that is '''almost''' common and then scale the geometry slightly circumferentially. Here is an example:<br />
<br />
*Real engine: 36 stator vanes, 41 rotor blades<br />
*Approximated engine: 41 stator vanes, 41 rotor blades, making it possible to simulate only 1 stator vane and 1 rotor blade<br />
*Scaling of stator: All stator vanes are scaled by 36/41 = 0.8780 circumferentially.<br />
<br />
<br />
=== Hybrid steady-unsteady stator-rotor simulations ===<br />
<br />
Hybrid steady-unsteady methods have been proposed in literature (Montomoli et al. 2011) in order to have an unsteady simulation embedded in a multistage steady study. <br />
There are several advantages related to this method: mainly grid size and number of iterations.<br />
<br />
=== Other '''advanced''' multi-stage methods ===<br />
<br />
Time-inclinded, Adamszyk stresses ...<br />
<br />
== Heat transfer predictions ==<br />
<br />
Besides listing the general heat transfer mechanisms involved <br />
(namely conduction, convection, radiation)<br />
heat transfer prediction in CFD may be seen as or split into two cases. <br />
<br />
'''Mesh consists of fluid domain(s)''': <br />
you want to know how heat inserted into the fluid domain (e.g. via the flowing medium) changes the temperature field along the flow path. Be it a steady or transient run, a fluid which enters with a given temperature will usually experience temperature variations, for instance, caused by convective boundary conditions, prescribed temperature profiles at flow obstacles etc. <br />
<br />
'''Mesh consists of fluid and solid domain(s)''': <br />
additionally to the above, you want info too wrt the (spatial, temporal or even spectral) temperature field distribution in surrounding, confining or immersed solids like channel walls or heat exchanger tubes. This is also called conjugate heattransfer CHT in the CFD context. CHT requires a good boundary layer resolution, usually the wall mesh needs to be rather refined, to obtain realistic heatflux results at the fluid/solid interface. Flow and heat transfer convergence require different time step settings, to properly capture changes in flow and heat quantities respectively. <br />
<br />
<br />
In either case, verify (strict necessity depends on CFD code used, CFX for instance checks and assists in regard) that model dimensions, boundary conditions and properties are in consistent units, hold appropriate values. Check temperature-dependence of properties and other numbers before the run.<br />
<br />
In heat transfer predictions (depending on the CFD code in use) <br />
besides the flow solver, you may have to activate the thermal solver too, <br />
as a job specification.<br />
<br />
== Acoustics and noise ==<br />
<br />
A whole separate research subject, difficult. <br />
<br />
Tone noise possible. Often run with linearzised solvers in the frequency domain.<br />
<br />
Jet noise possible. Often run with LES or DES simulations that either also resolve the sound waves or couples to a separate acoustic solver.<br />
<br />
Turbomachinery broadband noise not possible yet, or at least a great challenge.<br />
<br />
== Errors and uncertainties ==<br />
<br />
CFD is still a tool which requires that a user has a good understanding of uncertainties and errors that might spoil a CFD similation. There exists no error control in CFD and any CFD simulation must be interpreted by an expirenced user to have some credibility. Without some knowledge about possible errors and how they can be handled a CFD simulation can not be trusted. Errors can occur at different places:<br />
<br />
* Definition of the problem - What needs to be analyzed?<br />
* Selection of the solution strategy - What physical models and what numerical tools should be used?<br />
* Development of the computational model - How should the geometry and the numerical tools be set up?<br />
* Analysis and interpretation of the results - How should the model be analyzed and the results be interpreted?<br />
<br />
There exists many different definitions on errors. In this guide the errors are classified into four types of errors: problem definition errors, model errors, numerical errors and user and code errors. The chapters below describe these errors and give some guidelines on how to avoid them.<br />
<br />
=== Problem definition errors ===<br />
<br />
Problem definition errors are the most basic form of errors. In order to obtain usefull results a CFD simulation must of course analyze the correct problem, have suitable boundary contions and be based on a relevant geometry.<br />
<br />
==== Wrong type of simulation ====<br />
<br />
It is essential to have an overview of the physics involved and how the problem can best be analyzed. Running a 2D simulation in order to understand secondary flows or running a steady simulation in order to understand transient behaviour is of course no use. When assessing a CFD simulation the first thing to consider is what physical phenomena are important for the results and if the selected type of simulation is suitable to resolve this type of phenomena. For further information about selecting the most suitable type of simulation please see the previous chapter on [[#Deciding what type of simulation to do|deciding what type of simulation to perform]].<br />
<br />
==== Incorrect or uncertain boundary conditions ====<br />
<br />
A common source of errors is that incorrect boundary conditions are used. The boundary conditions must be specified in enough detail in order to resolve all the important physical features in the problem. For further information about specifying boundary conditions please see the previous chapter on [[#Boundary conditions|boundary conditions]].<br />
<br />
==== Geometrical errors ====<br />
<br />
It is almost always necessary to simplify the geometry in some form. When assessing a CFD simulation one should consider how the geometrical simplifications can affect the interesting physical phenomena. Typical geometrical errors are:<br />
<br />
*Simplifications<br />
:Small geometrical features like fillets, small steps or gaps etc. can often be disregarded. When disregarding this type of features one should consider if they might affect the important physics. For example, a very large fillet on the suction-side of a vane might affect corner separations near the end-walls. A large tip-leakage might affect the flow physics significantly in the upper part of a compressor.<br />
*Tolerances and manufacturing discrepancies<br />
:If the geometry has very large tolerances or is manufactured in a way which might produce a non-ideal shape or position it might be necessary to perform additional CFD simulations in order to cover the whole span of possible real geometries.<br />
*Surface conditions - roughness, welds, steps, gaps etc.<br />
:Often CFD simulations assume a perfectly smooth surface. A non-smooth surface which might have welds, steps or even gaps will of course produce different results. If the physical phenomena of interest might depend on the surface conditions these should of course be condidered. Typical phenomena that might be dependent on this type of errors are transition prediction, leakage flows etc.<br />
<br />
More recently Uncertainty Quantification techniques have been applied to turbomachinery to model real geometries considering their stochastic variations [Montomoli et al. 2013]<br />
<br />
=== Model errors ===<br />
<br />
Errors related to the computational model.<br />
<br />
==== Wrong physical models ====<br />
<br />
Once the type of simulation has been selected the next step is to select what type of physical models the simulation should use. The following points should be considered:<br />
<br />
* Gas data (incompressible/compressible, perfect gas/real gas, ...)<br />
* Turbulence modeling (type of model, type of near-wall treatment, ...)<br />
* Other models (combustion, sprays, ...)<br />
<br />
When assessing model related errors it is important to know the features of the selected model and think carefully how these features and possible short comings might affect the predicted physical behaviour. Using the wrong turbulence model or combustion model can completely destroy the results of a CFD simulation.<br />
<br />
=== Numerical errors ===<br />
<br />
Errors related to the numerical solution of the developed model. Typical examples of numerical errors are discretization errors, convergence errors and round-off errors.<br />
<br />
==== Discretization errors ====<br />
<br />
Discretization errors can either be spatial errors in space or temporal errors in time.<br />
<br />
Spatial discretization errors are what people normally call discretization errors. These errors are due to the difference between the exact solution and the numerical representation of the solution in space. Describing exactly what discretization different codes use and what errors this might lead to is not possible here. Instead some general rules to avoid these errors can be summarized as:<br />
* Use at least a 2nd order accurate scheme, preferably a 3rd order accurate scheme. Some general purpose codes have a 1st order upwind scheme as default, this is a very diffusives schemes that often gives too smooth results.<br />
* For new applications always run a simulation with a finer mesh to see how grid independent your solution is.<br />
* Be aware of checker-board errors. Checker-board errors occur close to strong shocks and other large discontinuities and can be seen as a wavy pattern with a wavelength of two cells. Some schemes, especially those who behave like central differencing schemes, are more prone to checker-board errors. Upwind schemes are a bit better and schemes like TVD or chock-capturing schemes are even better.<br />
<br />
Temporal discretization errors mainly effect transient simulations. However, some codes use a time-marching method also for steady simulations and then a temporal discretization error might affect the final steady solution slightly. The discretization in time can be done with 1st or 2nd order schemes or a Runge-Kutta method, which is more accurate and saves memory. Some codes can adapt the time-step, but often it is necessary to prescribe a time-step in advance. Think of the time-step as your grid in time and make sure that the grid-resolution in time is fine enough to resolve the highest frequencies. To avoid problems with temporal discretization errors the following should be considered:<br />
* Use at least a 2nd order scheme in time.<br />
* Do a physical estimation of the typical frequencies in time of the phenomena that you are interested in and select a time-step which is fine enough to resolve these frequencies well. After the simulation also look at the frequencies captured and make sure that they are well resolved by the chosen time-step.<br />
* For new applications try a finer time-step to ensure that your solution in time is fairly grid independent in time.<br />
<br />
==== Convergence errors ====<br />
<br />
To judge when a CFD simulation is converged is not always that easy. Different codes and different applications behave very differently. For a pure aero-simulation on a fairly coarse grid convergence is easy to judge, but for more complex simulations involving resolved boundary layers, heat transfer, combustion etc. convergence can be very tricky. Aside from looking at residuals one should always also look at how global parameters like static pressure distributions, total pressure losses, skin friction, heat transfer etc. change in time.<br />
For more information about how to avoid convergence errors see the previous chapter about [[#Convergence criteria]].<br />
<br />
==== Round-off errors ====<br />
<br />
When using single precision care needs to be taken to avoid round-off errors. Inviscid Euler simulations and simulations using wall-function meshes can most often be performed in single precision. For well resolved boundary layers with Y plus close to 1 it is often necessary to use double precision. If using double precision for very fine mesh resolutions make sure that you also create the mesh in double precision and not just run the solver in double precision. Sometimes a single precision solver converges slower than a double precision solver due to numerical errors caused by round-off errors. When using advanced physical models like combustion, free-surface simulations, spray and transient simulations with quick mesh motions it is also often necessary to use double precision.<br />
<br />
=== User and code errors ===<br />
<br />
Errors related to bugs in the code used or mistakes made by the CFD engineer.<br />
<br />
=== What to trust and what not to trust ===<br />
<br />
CFD is generally quite good at predicting surface static pressure distributions. With care CFD can also be used to predict performance, total-pressure losses and blade turning. <br />
<br />
Predicting separation, stall and off-design performance can be a challenge and results with non-attached flows should be interpreted with care. <br />
<br />
Heat transfer is often very difficult to predict accurately and it is common to obtain heat-transfer coefficients that are 100% wrong or more. Validation data is critical in order to be able to trust heat transfer simulations.<br />
<br />
Transition is almost impossible to predict accurately in general. However, there exist models that have been tuned to predict transition and these tend to give acceptable results for cases close to the ones they were tuned for.<br />
<br />
== References ==<br />
<br />
* {{reference-paper|author=Abu-Ghannam, B.J. and Shaw, R.|year=1980|title=Natural Transition of Boundary Layers - the Effects of Turbulence, Pressure Gradient, and Flow History|rest=Journal of Mech. Eng. Science, vol. 22, no. 5, pp. 213–228}}<br />
<br />
* {{reference-paper|author=Adamczyk, J. J.|year=1985|title=Model Equation for Simulating Flows in Multistage Turbomachinery|rest=ASME Paper 85-GT-226, also NASA TM-86869}}<br />
<br />
* {{reference-paper|author=Adamczyk, J. J.|year=1999|title=Aerodynamic Analysis of Multistage Turbomachinery Flows in Support of Aerodynamic Design|rest=ASME Paper 99-GT-80.}}<br />
<br />
* {{reference-paper|author=Baldwin, B. S. and Lomax, H.|year=1978|title=Thin Layer Approximation and Algebraic Model for Separated Turbulent Flows|rest=AIAA Paper 78-257}}<br />
<br />
* {{reference-paper|author=Chen, J. P. and Barter, J. W.|year=1998|title=Comparison of Time-Accurate Calculations for the Unsteady Interaction in Turbomachinery Stage|rest=AIAA Paper 98-3292}}<br />
<br />
* {{reference-paper|author=Denton, J. and Singh, U.|year=1979|title=Time Marching Methods for Turbomachinery Flow Calculations|rest=VKI Lecture Series 1979-7, von Karman Institute}}<br />
<br />
* {{reference-paper|author=Erdos, J., Alzner, E. and McNally, W.|year=1977|title=Numerical Solution of Periodic Transonic Flow Through a Transonic Fan Stage|rest=AIAA Journal, vol. 15, no. 11, pp. 1559-1568}}<br />
<br />
* {{reference-paper|author=Gerolymos, G., Vinteler, D., Haugeard, R., Tsange, G. and Vallet, I.|year=1996|title=On the Computation of Unsteady Turbomachinery Flows – Part II – Rotor/Stator Interaction using Euler Equations|rest=AGARD Report CP-571}}<br />
<br />
* {{reference-paper|author=Giles, M. B.|year=1990|title=Stator/Rotor Interaction in a Transonic Turbine|rest=AIAA Journal of Propulsion and Power, vol. 6, no. 5}}<br />
<br />
* {{reference-paper|author=He, L, and Ning, W.|year=1998|title=Efficient Approach for Analysis of Unsteady Viscous Flows in Turbomachines|rest=AIAA Journal, vol. 36, no. 11, pp. 2005-2012}}<br />
<br />
* {{reference-paper|author=Mayle, R. E.|year=1991|title=The Role of Laminar-Turbulent Transition in Gas Turbine Engines|rest=ASME Journal of Turbomachinery, vol. 113, pp. 509-537}}<br />
<br />
* {{reference-paper|author=Menter, F.R. |year=1994|title=Two-equation eddy-viscosity turbulence models for engineering applications|rest=AIAA Journal, vol. 32, pp. 269-289}}<br />
<br />
* {{reference-paper|author= Montomoli, F., Hodson,H.P, Lapworth, L. |year=2011|title=RANS-URANS in axial compressors, a design methodology|rest=Journal of Power and Energy, 225 (A3), pp. 363-374}}<br />
<br />
* {{reference-paper|author=Savill, M., Dick, E., Hanjalić, K. and Voke, P.|year=2002|title=Synthesis Report of the ERCOFTAC Transition Modeling – TRANSPRETURB Thematic Network Activities 1998-2002|rest=Ecoftac Bulletin 54, September 2002, pp. 5-16}}<br />
<br />
* {{reference-paper|author=Wang, X. and Chen J.|year=2004|title=A Post-Processor to Render Turbomachinery Flows Using Phase-Lag Simulations|rest=AIAA Paper 04-615}}<br />
<br />
== External links ==<br />
<br />
* [https://pronet.wsatkins.co.uk/marnet/guidelines/guide.html MARNET-CFD Best Practice Guidelines for Marine Applications of CFD]<br />
* [http://www.stanford.edu/group/ctr/ResBriefs/temp05/weide.pdf On Large Scale Turbomachinery Computations, by E. van der Weide et. al., Center for Turbulence Research, Annual Research Briefs 2005]</div>Frmontohttps://www.cfd-online.com/Wiki/Best_practice_guidelines_for_turbomachinery_CFDBest practice guidelines for turbomachinery CFD2013-08-23T10:20:07Z<p>Frmonto: /* References */</p>
<hr />
<div>This article contains a summary of the most important knowledge and experience a CFD engineer needs in order to perform CFD simulations of turbomachinery components. The guide is mainly aimed at axial turbomachinery. The goal is to give a CFD engineer, who has just started working with turbomachinery simulations, a head start and avoid some of the most difficult pit-falls. Experienced turbomachinery CFD engineers can also use the guidelines in order to learn what other experts consider best practice. The intended audience is expected to know basic CFD terminology and have a basic turbomachinery knowledge, but no detailed knowledge about CFD for turbomachinery is needed. <br />
<br />
== Deciding what type of simulation to do ==<br />
<br />
Before starting a new turbomachinery simulation it is wise to think carefully of what it is that should be predicted and what physical phenomena that affect the results. This chapter contains a brief overview of the various types of simulations and some hints of what can be predicted with them.<br />
<br />
=== 2D, Quasi-3D or 3D ===<br />
<br />
2D simulations are often used in the early design phase in order to obtain a typical 2D section of a blade. For cases with many long blades or vanes, like low-pressure turbines, a 2D simulation can also provide reasonable results. If the area of the flow-path changes significantly in the axial direction it might be necessary to instead make a quasi-3D simulation. A quasi-3D simulation is a 2D simulation in which extra source terms are used to account for the acceleration/deceleration caused by a changing channel height or growing end-wall boundary layers. Codes focused on turbomachinery applications often have the possibility to perform quasi-3D simulations, but most general purpose CFD codes can not do this type of simulations, or require user coding to implement the correct source terms in the equations. Please contact your software distributor if your code does not have the quasi-3d possibility and you require it. Many codes require special routines or hidden commands to enable this feature.<br />
<br />
Full 3D simulations are necessary if a true 3D geometry is needed to obtain correct secondary flows and/or shock locations. For low-aspect-ratio cases with only a few short blades, like for example structurally loaded turbine outlet guide vanes, the secondary flow development is important and a 3D simulation is often necessary in order to obtain reasonable results. For applications where the end-wall boundary layers grow very quickly and interact with a large part of the flow-field it is necessary to perform a full 3D simulation. This is often the case in compressors and fans, where the negative pressure gradients make the boundary layers grow much quicker than what they do in for example turbines. For cases where the shock location is very critical, like in transonic compressors, it is also often necessary to perform a 3D simulation in order to obtain reasonable shock locations.<br />
<br />
=== Inviscid or viscid ===<br />
<br />
For attached flows close to the design point and without any large separations it is often sufficient with an inviscid Euler simulation in order to obtain reasonable blade loadings and pressure distributions. Note that inviscid Euler simulations should only be used if the boundary layers are judged to not have a significant effect on the global flow-field. A viscid Navier-Stokes simulation is necessary in order to predict losses, secondary flows and separations. As soon as separations are of interest it is of course also necessary to do a viscid simulation. Note that with todays computers it is often not time and resources that make users run inviscid Euler simulations. Running viscid Navier-Stokes simulations is now so quick that it is not a time problem any more. Euler simulations are still interesting though, since with an inviscid Euler simulation you don't have to worry about wall resolutions, y+ values, turbulence modeling errors etc.<br />
<br />
=== Transient or Stationary ===<br />
<br />
Most turbomachinery simulations are performed as stationary simulations. Transient simulations are done when some kind of transient flow behaviour has a strong influence on the global flow field. Examples of transient simulations are detailed simulations of rotor-stator interaction effects, simulations of large unsteady separations etc. Sometimes when you perform a steady stationary simulation you can see tendencies of unsteady behaviour like for example periodic vortex shedding behind blunt trailing edges. This is often first seen as periodical variations of the residuals. If the unsteady tendencies are judged to not affect the overall simulation results it might be necessary to coarsen the mesh close to the vortex shedding or run a different turbulence model in order to make the simulation converge. Sometimes you are still forced to run a transient simulation and average the results if you don't obtain a converged steady solution.<br />
<br />
== Meshing ==<br />
<br />
In turbomachinery applications structured multi-block hexahedral meshes are most often used for flow-path simulations. In most solvers a structured grid requires less memory, provides superior accuracy and allows a better boundary-layer resolution than an unstructured grid. By having cells with a large aspect ratio around sharp leading and trailing edges a structured grid also provides a better resolution of these areas. Many companies have automatic meshing tools that automatically mesh blade sections with a structured mesh without much user intervention.<br />
<br />
Unstructured meshes are used for more complex and odd geometries where a structured mesh is difficult to create. Typical examples where unstructured meshes are often used are blade tip regions, areas involving leakage flows and secondary air systems, film cooling ducts etc.<br />
<br />
When meshing avoid to create large jumps in cell sizes. Typically the cell size should not change with more than a factor of 1.25 between neighbouring cells. For structured meshes also try to create fairly continous mesh lines and avoid discontinuities where the cell directions suddenly change. For multi-block structured meshes avoid placing the singular points where blocks meet in regions with strong flow gradients since most schemes have a lower accuracy in these singular points.<br />
<br />
=== Mesh size guidelines ===<br />
<br />
It is difficult to define, a priori, the mesh size. The required mesh size depends on the purpose of the simulation. <br />
<br />
If the main goal is to obtain static pressure forces a coarse mesh is often able to obtain a good solution, especially when an accurate resolution of the boundary layers is not required. For 2D inviscid simulations of one blade a mesh with say 3,000 cells is most often sufficient. For 3D inviscid blade simulations a mesh size of about 40,000 cells is usually sufficient. On inviscid Euler simulations the cells should be fairly equal in size and no boundary layer resolution should be present. Avoid having too skewed cells.<br />
<br />
For loss predictions and cases where boundary layer development and separation is important the mesh needs to have a boundary layer resolution. The boundary layer resolution can either be coarse and suitable for a [[Wall functions|wall function]] simulation or very fine and suitable for a [[Low-Re resolved boundary layers|low-Re]] simulation. For further information about selecting the near-wall turbulence model please see the [[#Turbulence modeling|turbulence modeling]] section. In 3D single-blade simulations a decent wall-function mesh typically has around 100,000 cells. This type of mesh size is suitable for quick design iterations where it is not essential to resolve all secondary flows and vortices. A good 3D wall-function mesh of a blade section intended to resolve secondary flows well should have at least 400,000 cells . A good low-Re mesh with resolved boundary layers typically has around 1,000,000 cells. <br />
<br />
In 2D blade simulations a good wall-function mesh has around 20,000 cells and a good low-Re mesh with resolved boundary layers has around 50,000 cells.<br />
<br />
Along the suction and pressure surfaces it is a good use about 100 cells in the streamwise direction. In the radial direction a good first approach is to use something like 30 cells for a wall-function mesh and 100 cells for a low-Re mesh.<br />
<br />
It is important to resolve leading and trailing edges well. Typically at least 10 cells, preferably 20 should be used around the leading and trailing edges. For very blunt and large leading edges, like those commonly found on HP turbine blades, 30 or more cells can be necessary.<br />
<br />
Cases which are difficult to converge with a steady simulation and which show tendencies of periodic vortex shedding from the trailing edge, can sometimes be "tamed" by using a coarse mesh around the trailing edge. This, of course, reduces the accuracy but can be a trick to obtain a converged solution if time and computer resources does not allow a transient simulation to be performed.<br />
<br />
=== Boundary layer mesh ===<br />
<br />
For design iteration type of simulations where a [[Wall functions|wall function]] approach is sufficient [[Dimensionless wall distance (y plus) | y+]] for the first cell should be somewhere between 20 and 200. The outer limit is dependent on the actual Re number of the simulations. For cases with fairly low Re numbers make sure to keep the maximum y+ as low as possible. For more accurate simulations with resolved boundary layers the mesh should have a y+ for the first cell which is below 1. Some new codes are now using a hybrid wall treatment that allows a smooth transition from a coarse wall-function mesh to a resolved low-Re mesh. Use some extra care when using this type of hybrid technique since it is still fairly new and unproven.<br />
<br />
Outside of the first cell at a wall a good rule of thumb is to use a growth ratio normal to the wall in the boundary layer of maximum 1.25. For a low-Re mesh this usually gives around 40 cells in the boundary layer whereas a wall-function mesh does not require more than 10 cells in the boundary layer.<br />
<br />
If you are uncertain of which wall distance to mesh with you can use a [http://www.cfd-online.com/Links/tools.html#yplus y+ estimation tool] to estitmate the distance needed to obtain the desired y+. These estimation tools are ''very handy'' if you have not done any previous similar simulations. <br />
<br />
As a rule of thumb a wall-function mesh typically requires areound 5 to 10 cells in the boundary layer whereas a resolved low-Re mesh requires about 40 cells in the boundary layer.<br />
<br />
== Boundary conditions ==<br />
<br />
Describe different types of boundary conditions and when they should be used:<br />
<br />
* Total pressure in, static pressure out<br />
* Absorbing boundary conditions<br />
* ...<br />
<br />
There are different types of boundary conditions you can use:<br />
*Mass flow inlet, static pressure outlet.<br />
To put this BC you must allocate inlet surface enough far away from the turbomachine impeller. The velocity distribution is not<br />
constant over all the surface. If you put this "lie" away from your problem it works well.<br />
<br />
<br />
=== Turbulence inlet conditions ===<br />
<br />
Prescribing realistic turbulence inlet conditions is important and usually difficult. For two-equation turbulence models two different turbulence values need to be specified on the inlet. The most common way of specifying the inlet turbulence variables is to give an inlet [[Turbulence intensity|turbulence level]] and [[Turbulence length scale|length-scale]]. For simulations where the incoming boundary layers are estimated to not have any significant effect on the secondary flows and global flow-field downstream it is usually sufficient to specify a constant incoming turbulence level and length-scale.<br />
<br />
The incoming [[Turbulence intensity|turbulence level]] is dependent on which component is analyzed. Best is of course to have measurments from a similar application in order to be able to prescribe a fairly realistic value. Without measurements it is necessary to make an educated guess. Simulations with very complex and turbulence-generating components upstream will have a very high incoming turbulence level. For example, a high-pressure turbine just downstream of a turbulence generating combustor might have incoming turbulence levels up to 20%. Fans and low-pressure compressors with not many components upstream might have as low incoming turbulence level as 1%. For components between these two extreme examples, like high-pressure compressors, low-pressure turbines etc. a turbulence level of around 5% might be realistic. If you do not have any measurements and are unsure about which incoming turbulence level to prescribe it is always a good idea to run a few different simulations with say one half and one double incoming turbulence level in order to estimate how important it is for the simulation results.<br />
<br />
The incoming [[Turbulence length scale|turbulence length-scale]] is often even more difficult to guess than the incoming turbulence level. Measurements might sometimes include the incoming turbulence level, but very seldom also include the incoming turbulent length-scale. The best way of guessing a realistic incoming length-scale is to use the geometrical properties of the upstream components. The incoming turbulence length-scale can be estimated as say the thickness of upstream blades or somewhere between 2% and 20% of the incoming channel heigth. Fortunately the incoming turbulence length-scale is usually not that important for the end results. However, some k-omega models can have an unrelisticly strong influence on the incoming turbulence length-scale. Hence, be extra carefull about the length-scale when using k-omega models. Note that the [[SST k-omega model]] does not have this unrealistic sensitivity to the inlet turbulence length-scale.<br />
<br />
Instead of specifying an incoming turbulence length-scale it is sometimes more convenient to specify an incoming [[Eddy viscosity ratio|eddy viscosity ratio]]. For low-turbulence cases with no well-specified turbulence generating components upstream it can be difficult to estimate a turbulence length-scale. Specifying an eddy viscosity ratio instead gives a more direct control over how large the effect of the incoming turbulence is. The eddy viscosity ratio describes how large the turbulence viscosity is related to the molecular viscosity. In turbomachinery the eddy viscosity ratio can vary from say 10 in low-turbulence components like fans up to say 1,000 or in rare cases even 10,000 in high-turbulence components like high-pressure turbines. In components between these extremes a typical eddy viscosity ration might be about 200. Even if specifying an inlet turbulence length scale it can still be good to compute what eddy viscosity ratio this corresponds to in order to estimate if it sounds reasonable.<br />
<br />
== Turbulence modeling ==<br />
<br />
Selecting a suitable turbulence model for turbomachinery simulations can be a challenging task. There is no single model which is suitable for all types of simulations. Which turbulence model CFD engineers use has as much to do with beliefs and traditions as with knowledge and facts. There are many different schools. However, below follows some advices that most CFD engineers in the turbomachinery field tend to agree upon.<br />
<br />
For attached flows close to the design point a simple algebraic model like the [[Baldwin-Lomax model]] can be used. Another common choice for design-iteration type of simulations is the one-equation model by [[Spalart-Allmaras model | Spalart-Allmaras]]. This model has become more popular in the last years due to the many inherent problems in more refined two-equation models. The big advantage with both the [[Baldwin-Lomax model]] and the [[Spalart-Allmaras model]] over more advanced models is that they are very robust to use and rarely produce completely unphysical results.<br />
<br />
In order to accurately predict more difficult cases, like separating flows, rotating flows, flows strongly affected by secondary flows etc. it is often necessary to use a more refined turbulence model. Common choices are two-equation models like the <math>k-\epsilon</math> model.<br />
<br />
Two-equation models are based on the [[Boussinesq eddy viscosity assumption]] and this often leads to an over-production of turbulent energy in regions with strong acceleration or deceleration, like in the leading edge region, regions around shocks and in the suction peak on the suction side of a blade. To reduce this problems it is common to use a special model variant using, for example, [[Durbin's realizability constraint]] or the [[Kato-Launder modification]]. Note that different two-equation models behave differently in these problematic stagnation and acceleration regions. Worst is probably the standard <math>k-\epsilon</math> model. <math>k-\omega</math> model are slightly better but still do not behave well. More modern variants like Menter's [[SST k-omega model]] also has problems, wheras the [[V2-f models|v2f model ]] by Durbin behaves better.<br />
<br />
=== Near-wall treatment ===<br />
<br />
For on-design simulations without any large separated regions it is often sufficient to use a [[wall-function model]] close to the wall, preferably with some form of non-equilibrium wall-function that is sensitised to streamwise pressure gradients.<br />
<br />
For off-design simulation, or simulations involving complex secondary flows and separations, it is often necessary to use a [[low-Re model]]. There exist many low-Re models that have been used with success in turbomachinery simulations. A robust and often good choice is to use a one-equation model, like for example the [[Wolfstein model]], in the inner parts of the boundary layer. There are also several Low-Re <math>k-\epsilon</math> models that work well. Just make sure they don't suffer from the problem with overproduction of turbulent energy in regions with strong acceleration or deceleration. In the last few years Menter's low-Re <math>SST k-\omega</math> model has gained increased popularity.<br />
<br />
=== Transition prediction ===<br />
<br />
Transition refers to the process when a laminar boundary layer becomes unstable and transitions to a turbulent boundary layer. There are two types of transition - natural transition, where inherent instabilities in the boundary layer cause the transition and by-pass transition, where convection and diffusion of turbulence from the free-stream into the boundary layer cause the transition. Most transitions in turbomachinery are by-pass transitions caused by free-stream turbulence and other external disturbances like wakes, vortices and surface defects.<br />
<br />
Simulating transition in a CFD code accurately is very difficult. Often a separate transition model needs to be solved in order to specify the transition location and length. Predicting natural transition in a pure CFD code is not possible. Predicting by-pass transition in a pure CFD code is almost impossible, although there are people who claim to be able to predict by-pass transition with low-Re two-equation models. However, this is usually on special test cases and with simulations that have been tuned for these special cases, see for example [Saville 2002]. In reality transition is a very complex and sensitive process where disturbances like incoming wakes and vortices from previous stages, surface roughness effects and small steps or gaps in the surfaces play a significant role. <br />
<br />
The turbomachinery codes that have transition prediction models often use old ad-hoc models like the Abu-Ghannam and Shaw model [Abu-Ghannam 1980] or the Mayle model [Mayle 1991]. These models can be quite reliable if they have been validated and tuned for a similar application. Do not trust your transition predictions without having some form of experimental validation. Menter has also recently developed a new form of transition model that might work fairly well, but it is still too new and untested.<br />
<br />
For some turbomachinery applications, like modern high-lift low-pressure turbines, transition is critical. For these applications a CFD code with a transition model that has been tuned for this type of applications should be used.<br />
<br />
== Numerical considerations ==<br />
<br />
Use at least a second order accurate scheme for the flow variables. Some codes require a first order scheme for the turbulent variables (<math>k</math> and <math>\epsilon</math>) in order to converge well. It might be sufficient with a first order scheme only on the turbulence variables, but a second order scheme is of course preferable.<br />
<br />
=== Convergence criteria ===<br />
<br />
To know when a solution is converged is not always that easy. You need some prior experience of your CFD code and your application to judge when a simulation is converged. For normal pure aero simulations without resolved walls, i.e. with wall functions or inviscid Euler simulations, convergence can most often be estimated just by looking at the residuals. Exactly what the residuals should be is not possible to say, it all depends on how your particular code computes and scales the residuals. Hence, make sure to read the manuals and plot the convergence of a few global parameters before you decide what the residuals should be for a solution to converge. Note also that many manuals for genereal purpose CFD codes list overly aggressive convergence criteria that often produce unconverged results. <br />
For simulations with resolved walls it is good to look at the convergence of some global properties, like total pressure losses from the inlet to the outlet. For heat transfer simulations it is even more tricky since the aerodynamic field can look almost converged although the thermal field is not converged at all. If doing heat transfer simulations make sure to plot the heat-transfer, run for some time, and plot it again to make sure that it doesn't change anymore. With very well resolved walls and heat transfer it can sometimes take 10 times longer for the thermal field to converge.<br />
<br />
=== Single or double precision ===<br />
<br />
With todays computers and cheap memory prices it often does not cost much extra to run in double precision. Before using single precision you should first investigate how your software and hardware works with double precision. If the extra time and memory needed for double precision is negligible you should of course always run in double precision. With double precision you never have to worry about round-off errors. Always using double precision is one way of avoiding one type of pit-falls in the complex world of CFD simulations. Use double precision when you have resolved boundary layers (Y+ around 1) and when you use advanced physical models like combustion, free-surface simulations, spray and transient simulations with quick mesh motions.<br />
<br />
== Multi-stage analysis ==<br />
<br />
Multi-stage analysis can be done in different ways:<br />
<br />
* Steady mixing-plane simulations<br />
* Frozen rotor simulations<br />
* Unsteady sliding-mesh stator-rotor simulations<br />
* Hybrid steady-unsteady stator-rotor simulations<br />
* Other '''advanced''' multi-stage methods<br />
<br />
=== Steady mixing-plane simulations ===<br />
<br />
Since the mixing-plane method was first introduced in 1979 [Denton & Singh 1979] it has become the industry standard type of rotor-stator simulations. A mixing-plane simulation is steady and only requires one rotor blade and one stator blade per stage. Between the rotating blade passage and the steady vane passage the flow properties are circumferentially averaged in a so-called mixing-plane interface. This will of course remove all transient rotor-stator interactions, but it still gives fairly representative results. In some commercial codes (CFX for example) mixing-plane interfaces are also called stage-interfaces.<br />
<br />
=== Frozen rotor simulations ===<br />
<br />
In a frozen rotor simulation the rotating and the stationary parts have a fixed relative position. A frame transformation is done to include the rotating effect on the rotating sections. This will give a steady flow and no transient effects are included. With a frozen-rotor simulation rotating wakes, secondary flows, leading edge pressure increases etc. will always stay in exactly the same positions. This makes a frozen rotor simulation very dependent on exactly how the rotors and the stators are positioned. Most often a mixing-plane simulation gives better results. Frozen rotor simulations are mainly performed to obtain a good starting flow-field before doing a transient sliding-mesh simulation.<br />
<br />
=== Unsteady sliding-mesh stator-rotor simulations ===<br />
<br />
This is the most complete type of stator-rotor simulation. In most engines the number of stators and rotors do not have a common denominator (to avoid instabilities caused by resonance between different rings). Hence, to make a full unsteady sliding-mesh computation it is necessary to have a mesh which includes the full wheel with all stators vanes and all rotor blades. This is often not possible, instead it is necessary to reduce the number of vanes and blades by finding a denominator that is '''almost''' common and then scale the geometry slightly circumferentially. Here is an example:<br />
<br />
*Real engine: 36 stator vanes, 41 rotor blades<br />
*Approximated engine: 41 stator vanes, 41 rotor blades, making it possible to simulate only 1 stator vane and 1 rotor blade<br />
*Scaling of stator: All stator vanes are scaled by 36/41 = 0.8780 circumferentially.<br />
<br />
<br />
=== Hybrid steady-unsteady stator-rotor simulations ===<br />
<br />
Hybrid steady-unsteady methods have been proposed in literature (Montomoli et al. 2011) in order to have an unsteady simulation embedded in a multistage steady study. <br />
There are several advantages related to this method: mainly grid size and number of iterations.<br />
<br />
=== Other '''advanced''' multi-stage methods ===<br />
<br />
Time-inclinded, Adamszyk stresses ...<br />
<br />
== Heat transfer predictions ==<br />
<br />
Besides listing the general heat transfer mechanisms involved <br />
(namely conduction, convection, radiation)<br />
heat transfer prediction in CFD may be seen as or split into two cases. <br />
<br />
'''Mesh consists of fluid domain(s)''': <br />
you want to know how heat inserted into the fluid domain (e.g. via the flowing medium) changes the temperature field along the flow path. Be it a steady or transient run, a fluid which enters with a given temperature will usually experience temperature variations, for instance, caused by convective boundary conditions, prescribed temperature profiles at flow obstacles etc. <br />
<br />
'''Mesh consists of fluid and solid domain(s)''': <br />
additionally to the above, you want info too wrt the (spatial, temporal or even spectral) temperature field distribution in surrounding, confining or immersed solids like channel walls or heat exchanger tubes. This is also called conjugate heattransfer CHT in the CFD context. CHT requires a good boundary layer resolution, usually the wall mesh needs to be rather refined, to obtain realistic heatflux results at the fluid/solid interface. Flow and heat transfer convergence require different time step settings, to properly capture changes in flow and heat quantities respectively. <br />
<br />
<br />
In either case, verify (strict necessity depends on CFD code used, CFX for instance checks and assists in regard) that model dimensions, boundary conditions and properties are in consistent units, hold appropriate values. Check temperature-dependence of properties and other numbers before the run.<br />
<br />
In heat transfer predictions (depending on the CFD code in use) <br />
besides the flow solver, you may have to activate the thermal solver too, <br />
as a job specification.<br />
<br />
== Acoustics and noise ==<br />
<br />
A whole separate research subject, difficult. <br />
<br />
Tone noise possible. Often run with linearzised solvers in the frequency domain.<br />
<br />
Jet noise possible. Often run with LES or DES simulations that either also resolve the sound waves or couples to a separate acoustic solver.<br />
<br />
Turbomachinery broadband noise not possible yet, or at least a great challenge.<br />
<br />
== Errors and uncertainties ==<br />
<br />
CFD is still a tool which requires that a user has a good understanding of uncertainties and errors that might spoil a CFD similation. There exists no error control in CFD and any CFD simulation must be interpreted by an expirenced user to have some credibility. Without some knowledge about possible errors and how they can be handled a CFD simulation can not be trusted. Errors can occur at different places:<br />
<br />
* Definition of the problem - What needs to be analyzed?<br />
* Selection of the solution strategy - What physical models and what numerical tools should be used?<br />
* Development of the computational model - How should the geometry and the numerical tools be set up?<br />
* Analysis and interpretation of the results - How should the model be analyzed and the results be interpreted?<br />
<br />
There exists many different definitions on errors. In this guide the errors are classified into four types of errors: problem definition errors, model errors, numerical errors and user and code errors. The chapters below describe these errors and give some guidelines on how to avoid them.<br />
<br />
=== Problem definition errors ===<br />
<br />
Problem definition errors are the most basic form of errors. In order to obtain usefull results a CFD simulation must of course analyze the correct problem, have suitable boundary contions and be based on a relevant geometry.<br />
<br />
==== Wrong type of simulation ====<br />
<br />
It is essential to have an overview of the physics involved and how the problem can best be analyzed. Running a 2D simulation in order to understand secondary flows or running a steady simulation in order to understand transient behaviour is of course no use. When assessing a CFD simulation the first thing to consider is what physical phenomena are important for the results and if the selected type of simulation is suitable to resolve this type of phenomena. For further information about selecting the most suitable type of simulation please see the previous chapter on [[#Deciding what type of simulation to do|deciding what type of simulation to perform]].<br />
<br />
==== Incorrect or uncertain boundary conditions ====<br />
<br />
A common source of errors is that incorrect boundary conditions are used. The boundary conditions must be specified in enough detail in order to resolve all the important physical features in the problem. For further information about specifying boundary conditions please see the previous chapter on [[#Boundary conditions|boundary conditions]].<br />
<br />
==== Geometrical errors ====<br />
<br />
It is almost always necessary to simplify the geometry in some form. When assessing a CFD simulation one should consider how the geometrical simplifications can affect the interesting physical phenomena. Typical geometrical errors are:<br />
<br />
*Simplifications<br />
:Small geometrical features like fillets, small steps or gaps etc. can often be disregarded. When disregarding this type of features one should consider if they might affect the important physics. For example, a very large fillet on the suction-side of a vane might affect corner separations near the end-walls. A large tip-leakage might affect the flow physics significantly in the upper part of a compressor.<br />
*Tolerances and manufacturing discrepancies<br />
:If the geometry has very large tolerances or is manufactured in a way which might produce a non-ideal shape or position it might be necessary to perform additional CFD simulations in order to cover the whole span of possible real geometries.<br />
*Surface conditions - roughness, welds, steps, gaps etc.<br />
:Often CFD simulations assume a perfectly smooth surface. A non-smooth surface which might have welds, steps or even gaps will of course produce different results. If the physical phenomena of interest might depend on the surface conditions these should of course be condidered. Typical phenomena that might be dependent on this type of errors are transition prediction, leakage flows etc.<br />
<br />
=== Model errors ===<br />
<br />
Errors related to the computational model.<br />
<br />
==== Wrong physical models ====<br />
<br />
Once the type of simulation has been selected the next step is to select what type of physical models the simulation should use. The following points should be considered:<br />
<br />
* Gas data (incompressible/compressible, perfect gas/real gas, ...)<br />
* Turbulence modeling (type of model, type of near-wall treatment, ...)<br />
* Other models (combustion, sprays, ...)<br />
<br />
When assessing model related errors it is important to know the features of the selected model and think carefully how these features and possible short comings might affect the predicted physical behaviour. Using the wrong turbulence model or combustion model can completely destroy the results of a CFD simulation.<br />
<br />
=== Numerical errors ===<br />
<br />
Errors related to the numerical solution of the developed model. Typical examples of numerical errors are discretization errors, convergence errors and round-off errors.<br />
<br />
==== Discretization errors ====<br />
<br />
Discretization errors can either be spatial errors in space or temporal errors in time.<br />
<br />
Spatial discretization errors are what people normally call discretization errors. These errors are due to the difference between the exact solution and the numerical representation of the solution in space. Describing exactly what discretization different codes use and what errors this might lead to is not possible here. Instead some general rules to avoid these errors can be summarized as:<br />
* Use at least a 2nd order accurate scheme, preferably a 3rd order accurate scheme. Some general purpose codes have a 1st order upwind scheme as default, this is a very diffusives schemes that often gives too smooth results.<br />
* For new applications always run a simulation with a finer mesh to see how grid independent your solution is.<br />
* Be aware of checker-board errors. Checker-board errors occur close to strong shocks and other large discontinuities and can be seen as a wavy pattern with a wavelength of two cells. Some schemes, especially those who behave like central differencing schemes, are more prone to checker-board errors. Upwind schemes are a bit better and schemes like TVD or chock-capturing schemes are even better.<br />
<br />
Temporal discretization errors mainly effect transient simulations. However, some codes use a time-marching method also for steady simulations and then a temporal discretization error might affect the final steady solution slightly. The discretization in time can be done with 1st or 2nd order schemes or a Runge-Kutta method, which is more accurate and saves memory. Some codes can adapt the time-step, but often it is necessary to prescribe a time-step in advance. Think of the time-step as your grid in time and make sure that the grid-resolution in time is fine enough to resolve the highest frequencies. To avoid problems with temporal discretization errors the following should be considered:<br />
* Use at least a 2nd order scheme in time.<br />
* Do a physical estimation of the typical frequencies in time of the phenomena that you are interested in and select a time-step which is fine enough to resolve these frequencies well. After the simulation also look at the frequencies captured and make sure that they are well resolved by the chosen time-step.<br />
* For new applications try a finer time-step to ensure that your solution in time is fairly grid independent in time.<br />
<br />
==== Convergence errors ====<br />
<br />
To judge when a CFD simulation is converged is not always that easy. Different codes and different applications behave very differently. For a pure aero-simulation on a fairly coarse grid convergence is easy to judge, but for more complex simulations involving resolved boundary layers, heat transfer, combustion etc. convergence can be very tricky. Aside from looking at residuals one should always also look at how global parameters like static pressure distributions, total pressure losses, skin friction, heat transfer etc. change in time.<br />
For more information about how to avoid convergence errors see the previous chapter about [[#Convergence criteria]].<br />
<br />
==== Round-off errors ====<br />
<br />
When using single precision care needs to be taken to avoid round-off errors. Inviscid Euler simulations and simulations using wall-function meshes can most often be performed in single precision. For well resolved boundary layers with Y plus close to 1 it is often necessary to use double precision. If using double precision for very fine mesh resolutions make sure that you also create the mesh in double precision and not just run the solver in double precision. Sometimes a single precision solver converges slower than a double precision solver due to numerical errors caused by round-off errors. When using advanced physical models like combustion, free-surface simulations, spray and transient simulations with quick mesh motions it is also often necessary to use double precision.<br />
<br />
=== User and code errors ===<br />
<br />
Errors related to bugs in the code used or mistakes made by the CFD engineer.<br />
<br />
=== What to trust and what not to trust ===<br />
<br />
CFD is generally quite good at predicting surface static pressure distributions. With care CFD can also be used to predict performance, total-pressure losses and blade turning. <br />
<br />
Predicting separation, stall and off-design performance can be a challenge and results with non-attached flows should be interpreted with care. <br />
<br />
Heat transfer is often very difficult to predict accurately and it is common to obtain heat-transfer coefficients that are 100% wrong or more. Validation data is critical in order to be able to trust heat transfer simulations.<br />
<br />
Transition is almost impossible to predict accurately in general. However, there exist models that have been tuned to predict transition and these tend to give acceptable results for cases close to the ones they were tuned for.<br />
<br />
== References ==<br />
<br />
* {{reference-paper|author=Abu-Ghannam, B.J. and Shaw, R.|year=1980|title=Natural Transition of Boundary Layers - the Effects of Turbulence, Pressure Gradient, and Flow History|rest=Journal of Mech. Eng. Science, vol. 22, no. 5, pp. 213–228}}<br />
<br />
* {{reference-paper|author=Adamczyk, J. J.|year=1985|title=Model Equation for Simulating Flows in Multistage Turbomachinery|rest=ASME Paper 85-GT-226, also NASA TM-86869}}<br />
<br />
* {{reference-paper|author=Adamczyk, J. J.|year=1999|title=Aerodynamic Analysis of Multistage Turbomachinery Flows in Support of Aerodynamic Design|rest=ASME Paper 99-GT-80.}}<br />
<br />
* {{reference-paper|author=Baldwin, B. S. and Lomax, H.|year=1978|title=Thin Layer Approximation and Algebraic Model for Separated Turbulent Flows|rest=AIAA Paper 78-257}}<br />
<br />
* {{reference-paper|author=Chen, J. P. and Barter, J. W.|year=1998|title=Comparison of Time-Accurate Calculations for the Unsteady Interaction in Turbomachinery Stage|rest=AIAA Paper 98-3292}}<br />
<br />
* {{reference-paper|author=Denton, J. and Singh, U.|year=1979|title=Time Marching Methods for Turbomachinery Flow Calculations|rest=VKI Lecture Series 1979-7, von Karman Institute}}<br />
<br />
* {{reference-paper|author=Erdos, J., Alzner, E. and McNally, W.|year=1977|title=Numerical Solution of Periodic Transonic Flow Through a Transonic Fan Stage|rest=AIAA Journal, vol. 15, no. 11, pp. 1559-1568}}<br />
<br />
* {{reference-paper|author=Gerolymos, G., Vinteler, D., Haugeard, R., Tsange, G. and Vallet, I.|year=1996|title=On the Computation of Unsteady Turbomachinery Flows – Part II – Rotor/Stator Interaction using Euler Equations|rest=AGARD Report CP-571}}<br />
<br />
* {{reference-paper|author=Giles, M. B.|year=1990|title=Stator/Rotor Interaction in a Transonic Turbine|rest=AIAA Journal of Propulsion and Power, vol. 6, no. 5}}<br />
<br />
* {{reference-paper|author=He, L, and Ning, W.|year=1998|title=Efficient Approach for Analysis of Unsteady Viscous Flows in Turbomachines|rest=AIAA Journal, vol. 36, no. 11, pp. 2005-2012}}<br />
<br />
* {{reference-paper|author=Mayle, R. E.|year=1991|title=The Role of Laminar-Turbulent Transition in Gas Turbine Engines|rest=ASME Journal of Turbomachinery, vol. 113, pp. 509-537}}<br />
<br />
* {{reference-paper|author=Menter, F.R. |year=1994|title=Two-equation eddy-viscosity turbulence models for engineering applications|rest=AIAA Journal, vol. 32, pp. 269-289}}<br />
<br />
* {{reference-paper|author= Montomoli, F., Hodson,H.P, Lapworth, L. |year=2011|title=RANS-URANS in axial compressors, a design methodology|rest=Journal of Power and Energy, 225 (A3), pp. 363-374}}<br />
<br />
* {{reference-paper|author=Savill, M., Dick, E., Hanjalić, K. and Voke, P.|year=2002|title=Synthesis Report of the ERCOFTAC Transition Modeling – TRANSPRETURB Thematic Network Activities 1998-2002|rest=Ecoftac Bulletin 54, September 2002, pp. 5-16}}<br />
<br />
* {{reference-paper|author=Wang, X. and Chen J.|year=2004|title=A Post-Processor to Render Turbomachinery Flows Using Phase-Lag Simulations|rest=AIAA Paper 04-615}}<br />
<br />
== External links ==<br />
<br />
* [https://pronet.wsatkins.co.uk/marnet/guidelines/guide.html MARNET-CFD Best Practice Guidelines for Marine Applications of CFD]<br />
* [http://www.stanford.edu/group/ctr/ResBriefs/temp05/weide.pdf On Large Scale Turbomachinery Computations, by E. van der Weide et. al., Center for Turbulence Research, Annual Research Briefs 2005]</div>Frmontohttps://www.cfd-online.com/Wiki/Best_practice_guidelines_for_turbomachinery_CFDBest practice guidelines for turbomachinery CFD2013-08-23T10:19:33Z<p>Frmonto: /* Hybrid steady-unsteady stator-rotor simulations */</p>
<hr />
<div>This article contains a summary of the most important knowledge and experience a CFD engineer needs in order to perform CFD simulations of turbomachinery components. The guide is mainly aimed at axial turbomachinery. The goal is to give a CFD engineer, who has just started working with turbomachinery simulations, a head start and avoid some of the most difficult pit-falls. Experienced turbomachinery CFD engineers can also use the guidelines in order to learn what other experts consider best practice. The intended audience is expected to know basic CFD terminology and have a basic turbomachinery knowledge, but no detailed knowledge about CFD for turbomachinery is needed. <br />
<br />
== Deciding what type of simulation to do ==<br />
<br />
Before starting a new turbomachinery simulation it is wise to think carefully of what it is that should be predicted and what physical phenomena that affect the results. This chapter contains a brief overview of the various types of simulations and some hints of what can be predicted with them.<br />
<br />
=== 2D, Quasi-3D or 3D ===<br />
<br />
2D simulations are often used in the early design phase in order to obtain a typical 2D section of a blade. For cases with many long blades or vanes, like low-pressure turbines, a 2D simulation can also provide reasonable results. If the area of the flow-path changes significantly in the axial direction it might be necessary to instead make a quasi-3D simulation. A quasi-3D simulation is a 2D simulation in which extra source terms are used to account for the acceleration/deceleration caused by a changing channel height or growing end-wall boundary layers. Codes focused on turbomachinery applications often have the possibility to perform quasi-3D simulations, but most general purpose CFD codes can not do this type of simulations, or require user coding to implement the correct source terms in the equations. Please contact your software distributor if your code does not have the quasi-3d possibility and you require it. Many codes require special routines or hidden commands to enable this feature.<br />
<br />
Full 3D simulations are necessary if a true 3D geometry is needed to obtain correct secondary flows and/or shock locations. For low-aspect-ratio cases with only a few short blades, like for example structurally loaded turbine outlet guide vanes, the secondary flow development is important and a 3D simulation is often necessary in order to obtain reasonable results. For applications where the end-wall boundary layers grow very quickly and interact with a large part of the flow-field it is necessary to perform a full 3D simulation. This is often the case in compressors and fans, where the negative pressure gradients make the boundary layers grow much quicker than what they do in for example turbines. For cases where the shock location is very critical, like in transonic compressors, it is also often necessary to perform a 3D simulation in order to obtain reasonable shock locations.<br />
<br />
=== Inviscid or viscid ===<br />
<br />
For attached flows close to the design point and without any large separations it is often sufficient with an inviscid Euler simulation in order to obtain reasonable blade loadings and pressure distributions. Note that inviscid Euler simulations should only be used if the boundary layers are judged to not have a significant effect on the global flow-field. A viscid Navier-Stokes simulation is necessary in order to predict losses, secondary flows and separations. As soon as separations are of interest it is of course also necessary to do a viscid simulation. Note that with todays computers it is often not time and resources that make users run inviscid Euler simulations. Running viscid Navier-Stokes simulations is now so quick that it is not a time problem any more. Euler simulations are still interesting though, since with an inviscid Euler simulation you don't have to worry about wall resolutions, y+ values, turbulence modeling errors etc.<br />
<br />
=== Transient or Stationary ===<br />
<br />
Most turbomachinery simulations are performed as stationary simulations. Transient simulations are done when some kind of transient flow behaviour has a strong influence on the global flow field. Examples of transient simulations are detailed simulations of rotor-stator interaction effects, simulations of large unsteady separations etc. Sometimes when you perform a steady stationary simulation you can see tendencies of unsteady behaviour like for example periodic vortex shedding behind blunt trailing edges. This is often first seen as periodical variations of the residuals. If the unsteady tendencies are judged to not affect the overall simulation results it might be necessary to coarsen the mesh close to the vortex shedding or run a different turbulence model in order to make the simulation converge. Sometimes you are still forced to run a transient simulation and average the results if you don't obtain a converged steady solution.<br />
<br />
== Meshing ==<br />
<br />
In turbomachinery applications structured multi-block hexahedral meshes are most often used for flow-path simulations. In most solvers a structured grid requires less memory, provides superior accuracy and allows a better boundary-layer resolution than an unstructured grid. By having cells with a large aspect ratio around sharp leading and trailing edges a structured grid also provides a better resolution of these areas. Many companies have automatic meshing tools that automatically mesh blade sections with a structured mesh without much user intervention.<br />
<br />
Unstructured meshes are used for more complex and odd geometries where a structured mesh is difficult to create. Typical examples where unstructured meshes are often used are blade tip regions, areas involving leakage flows and secondary air systems, film cooling ducts etc.<br />
<br />
When meshing avoid to create large jumps in cell sizes. Typically the cell size should not change with more than a factor of 1.25 between neighbouring cells. For structured meshes also try to create fairly continous mesh lines and avoid discontinuities where the cell directions suddenly change. For multi-block structured meshes avoid placing the singular points where blocks meet in regions with strong flow gradients since most schemes have a lower accuracy in these singular points.<br />
<br />
=== Mesh size guidelines ===<br />
<br />
It is difficult to define, a priori, the mesh size. The required mesh size depends on the purpose of the simulation. <br />
<br />
If the main goal is to obtain static pressure forces a coarse mesh is often able to obtain a good solution, especially when an accurate resolution of the boundary layers is not required. For 2D inviscid simulations of one blade a mesh with say 3,000 cells is most often sufficient. For 3D inviscid blade simulations a mesh size of about 40,000 cells is usually sufficient. On inviscid Euler simulations the cells should be fairly equal in size and no boundary layer resolution should be present. Avoid having too skewed cells.<br />
<br />
For loss predictions and cases where boundary layer development and separation is important the mesh needs to have a boundary layer resolution. The boundary layer resolution can either be coarse and suitable for a [[Wall functions|wall function]] simulation or very fine and suitable for a [[Low-Re resolved boundary layers|low-Re]] simulation. For further information about selecting the near-wall turbulence model please see the [[#Turbulence modeling|turbulence modeling]] section. In 3D single-blade simulations a decent wall-function mesh typically has around 100,000 cells. This type of mesh size is suitable for quick design iterations where it is not essential to resolve all secondary flows and vortices. A good 3D wall-function mesh of a blade section intended to resolve secondary flows well should have at least 400,000 cells . A good low-Re mesh with resolved boundary layers typically has around 1,000,000 cells. <br />
<br />
In 2D blade simulations a good wall-function mesh has around 20,000 cells and a good low-Re mesh with resolved boundary layers has around 50,000 cells.<br />
<br />
Along the suction and pressure surfaces it is a good use about 100 cells in the streamwise direction. In the radial direction a good first approach is to use something like 30 cells for a wall-function mesh and 100 cells for a low-Re mesh.<br />
<br />
It is important to resolve leading and trailing edges well. Typically at least 10 cells, preferably 20 should be used around the leading and trailing edges. For very blunt and large leading edges, like those commonly found on HP turbine blades, 30 or more cells can be necessary.<br />
<br />
Cases which are difficult to converge with a steady simulation and which show tendencies of periodic vortex shedding from the trailing edge, can sometimes be "tamed" by using a coarse mesh around the trailing edge. This, of course, reduces the accuracy but can be a trick to obtain a converged solution if time and computer resources does not allow a transient simulation to be performed.<br />
<br />
=== Boundary layer mesh ===<br />
<br />
For design iteration type of simulations where a [[Wall functions|wall function]] approach is sufficient [[Dimensionless wall distance (y plus) | y+]] for the first cell should be somewhere between 20 and 200. The outer limit is dependent on the actual Re number of the simulations. For cases with fairly low Re numbers make sure to keep the maximum y+ as low as possible. For more accurate simulations with resolved boundary layers the mesh should have a y+ for the first cell which is below 1. Some new codes are now using a hybrid wall treatment that allows a smooth transition from a coarse wall-function mesh to a resolved low-Re mesh. Use some extra care when using this type of hybrid technique since it is still fairly new and unproven.<br />
<br />
Outside of the first cell at a wall a good rule of thumb is to use a growth ratio normal to the wall in the boundary layer of maximum 1.25. For a low-Re mesh this usually gives around 40 cells in the boundary layer whereas a wall-function mesh does not require more than 10 cells in the boundary layer.<br />
<br />
If you are uncertain of which wall distance to mesh with you can use a [http://www.cfd-online.com/Links/tools.html#yplus y+ estimation tool] to estitmate the distance needed to obtain the desired y+. These estimation tools are ''very handy'' if you have not done any previous similar simulations. <br />
<br />
As a rule of thumb a wall-function mesh typically requires areound 5 to 10 cells in the boundary layer whereas a resolved low-Re mesh requires about 40 cells in the boundary layer.<br />
<br />
== Boundary conditions ==<br />
<br />
Describe different types of boundary conditions and when they should be used:<br />
<br />
* Total pressure in, static pressure out<br />
* Absorbing boundary conditions<br />
* ...<br />
<br />
There are different types of boundary conditions you can use:<br />
*Mass flow inlet, static pressure outlet.<br />
To put this BC you must allocate inlet surface enough far away from the turbomachine impeller. The velocity distribution is not<br />
constant over all the surface. If you put this "lie" away from your problem it works well.<br />
<br />
<br />
=== Turbulence inlet conditions ===<br />
<br />
Prescribing realistic turbulence inlet conditions is important and usually difficult. For two-equation turbulence models two different turbulence values need to be specified on the inlet. The most common way of specifying the inlet turbulence variables is to give an inlet [[Turbulence intensity|turbulence level]] and [[Turbulence length scale|length-scale]]. For simulations where the incoming boundary layers are estimated to not have any significant effect on the secondary flows and global flow-field downstream it is usually sufficient to specify a constant incoming turbulence level and length-scale.<br />
<br />
The incoming [[Turbulence intensity|turbulence level]] is dependent on which component is analyzed. Best is of course to have measurments from a similar application in order to be able to prescribe a fairly realistic value. Without measurements it is necessary to make an educated guess. Simulations with very complex and turbulence-generating components upstream will have a very high incoming turbulence level. For example, a high-pressure turbine just downstream of a turbulence generating combustor might have incoming turbulence levels up to 20%. Fans and low-pressure compressors with not many components upstream might have as low incoming turbulence level as 1%. For components between these two extreme examples, like high-pressure compressors, low-pressure turbines etc. a turbulence level of around 5% might be realistic. If you do not have any measurements and are unsure about which incoming turbulence level to prescribe it is always a good idea to run a few different simulations with say one half and one double incoming turbulence level in order to estimate how important it is for the simulation results.<br />
<br />
The incoming [[Turbulence length scale|turbulence length-scale]] is often even more difficult to guess than the incoming turbulence level. Measurements might sometimes include the incoming turbulence level, but very seldom also include the incoming turbulent length-scale. The best way of guessing a realistic incoming length-scale is to use the geometrical properties of the upstream components. The incoming turbulence length-scale can be estimated as say the thickness of upstream blades or somewhere between 2% and 20% of the incoming channel heigth. Fortunately the incoming turbulence length-scale is usually not that important for the end results. However, some k-omega models can have an unrelisticly strong influence on the incoming turbulence length-scale. Hence, be extra carefull about the length-scale when using k-omega models. Note that the [[SST k-omega model]] does not have this unrealistic sensitivity to the inlet turbulence length-scale.<br />
<br />
Instead of specifying an incoming turbulence length-scale it is sometimes more convenient to specify an incoming [[Eddy viscosity ratio|eddy viscosity ratio]]. For low-turbulence cases with no well-specified turbulence generating components upstream it can be difficult to estimate a turbulence length-scale. Specifying an eddy viscosity ratio instead gives a more direct control over how large the effect of the incoming turbulence is. The eddy viscosity ratio describes how large the turbulence viscosity is related to the molecular viscosity. In turbomachinery the eddy viscosity ratio can vary from say 10 in low-turbulence components like fans up to say 1,000 or in rare cases even 10,000 in high-turbulence components like high-pressure turbines. In components between these extremes a typical eddy viscosity ration might be about 200. Even if specifying an inlet turbulence length scale it can still be good to compute what eddy viscosity ratio this corresponds to in order to estimate if it sounds reasonable.<br />
<br />
== Turbulence modeling ==<br />
<br />
Selecting a suitable turbulence model for turbomachinery simulations can be a challenging task. There is no single model which is suitable for all types of simulations. Which turbulence model CFD engineers use has as much to do with beliefs and traditions as with knowledge and facts. There are many different schools. However, below follows some advices that most CFD engineers in the turbomachinery field tend to agree upon.<br />
<br />
For attached flows close to the design point a simple algebraic model like the [[Baldwin-Lomax model]] can be used. Another common choice for design-iteration type of simulations is the one-equation model by [[Spalart-Allmaras model | Spalart-Allmaras]]. This model has become more popular in the last years due to the many inherent problems in more refined two-equation models. The big advantage with both the [[Baldwin-Lomax model]] and the [[Spalart-Allmaras model]] over more advanced models is that they are very robust to use and rarely produce completely unphysical results.<br />
<br />
In order to accurately predict more difficult cases, like separating flows, rotating flows, flows strongly affected by secondary flows etc. it is often necessary to use a more refined turbulence model. Common choices are two-equation models like the <math>k-\epsilon</math> model.<br />
<br />
Two-equation models are based on the [[Boussinesq eddy viscosity assumption]] and this often leads to an over-production of turbulent energy in regions with strong acceleration or deceleration, like in the leading edge region, regions around shocks and in the suction peak on the suction side of a blade. To reduce this problems it is common to use a special model variant using, for example, [[Durbin's realizability constraint]] or the [[Kato-Launder modification]]. Note that different two-equation models behave differently in these problematic stagnation and acceleration regions. Worst is probably the standard <math>k-\epsilon</math> model. <math>k-\omega</math> model are slightly better but still do not behave well. More modern variants like Menter's [[SST k-omega model]] also has problems, wheras the [[V2-f models|v2f model ]] by Durbin behaves better.<br />
<br />
=== Near-wall treatment ===<br />
<br />
For on-design simulations without any large separated regions it is often sufficient to use a [[wall-function model]] close to the wall, preferably with some form of non-equilibrium wall-function that is sensitised to streamwise pressure gradients.<br />
<br />
For off-design simulation, or simulations involving complex secondary flows and separations, it is often necessary to use a [[low-Re model]]. There exist many low-Re models that have been used with success in turbomachinery simulations. A robust and often good choice is to use a one-equation model, like for example the [[Wolfstein model]], in the inner parts of the boundary layer. There are also several Low-Re <math>k-\epsilon</math> models that work well. Just make sure they don't suffer from the problem with overproduction of turbulent energy in regions with strong acceleration or deceleration. In the last few years Menter's low-Re <math>SST k-\omega</math> model has gained increased popularity.<br />
<br />
=== Transition prediction ===<br />
<br />
Transition refers to the process when a laminar boundary layer becomes unstable and transitions to a turbulent boundary layer. There are two types of transition - natural transition, where inherent instabilities in the boundary layer cause the transition and by-pass transition, where convection and diffusion of turbulence from the free-stream into the boundary layer cause the transition. Most transitions in turbomachinery are by-pass transitions caused by free-stream turbulence and other external disturbances like wakes, vortices and surface defects.<br />
<br />
Simulating transition in a CFD code accurately is very difficult. Often a separate transition model needs to be solved in order to specify the transition location and length. Predicting natural transition in a pure CFD code is not possible. Predicting by-pass transition in a pure CFD code is almost impossible, although there are people who claim to be able to predict by-pass transition with low-Re two-equation models. However, this is usually on special test cases and with simulations that have been tuned for these special cases, see for example [Saville 2002]. In reality transition is a very complex and sensitive process where disturbances like incoming wakes and vortices from previous stages, surface roughness effects and small steps or gaps in the surfaces play a significant role. <br />
<br />
The turbomachinery codes that have transition prediction models often use old ad-hoc models like the Abu-Ghannam and Shaw model [Abu-Ghannam 1980] or the Mayle model [Mayle 1991]. These models can be quite reliable if they have been validated and tuned for a similar application. Do not trust your transition predictions without having some form of experimental validation. Menter has also recently developed a new form of transition model that might work fairly well, but it is still too new and untested.<br />
<br />
For some turbomachinery applications, like modern high-lift low-pressure turbines, transition is critical. For these applications a CFD code with a transition model that has been tuned for this type of applications should be used.<br />
<br />
== Numerical considerations ==<br />
<br />
Use at least a second order accurate scheme for the flow variables. Some codes require a first order scheme for the turbulent variables (<math>k</math> and <math>\epsilon</math>) in order to converge well. It might be sufficient with a first order scheme only on the turbulence variables, but a second order scheme is of course preferable.<br />
<br />
=== Convergence criteria ===<br />
<br />
To know when a solution is converged is not always that easy. You need some prior experience of your CFD code and your application to judge when a simulation is converged. For normal pure aero simulations without resolved walls, i.e. with wall functions or inviscid Euler simulations, convergence can most often be estimated just by looking at the residuals. Exactly what the residuals should be is not possible to say, it all depends on how your particular code computes and scales the residuals. Hence, make sure to read the manuals and plot the convergence of a few global parameters before you decide what the residuals should be for a solution to converge. Note also that many manuals for genereal purpose CFD codes list overly aggressive convergence criteria that often produce unconverged results. <br />
For simulations with resolved walls it is good to look at the convergence of some global properties, like total pressure losses from the inlet to the outlet. For heat transfer simulations it is even more tricky since the aerodynamic field can look almost converged although the thermal field is not converged at all. If doing heat transfer simulations make sure to plot the heat-transfer, run for some time, and plot it again to make sure that it doesn't change anymore. With very well resolved walls and heat transfer it can sometimes take 10 times longer for the thermal field to converge.<br />
<br />
=== Single or double precision ===<br />
<br />
With todays computers and cheap memory prices it often does not cost much extra to run in double precision. Before using single precision you should first investigate how your software and hardware works with double precision. If the extra time and memory needed for double precision is negligible you should of course always run in double precision. With double precision you never have to worry about round-off errors. Always using double precision is one way of avoiding one type of pit-falls in the complex world of CFD simulations. Use double precision when you have resolved boundary layers (Y+ around 1) and when you use advanced physical models like combustion, free-surface simulations, spray and transient simulations with quick mesh motions.<br />
<br />
== Multi-stage analysis ==<br />
<br />
Multi-stage analysis can be done in different ways:<br />
<br />
* Steady mixing-plane simulations<br />
* Frozen rotor simulations<br />
* Unsteady sliding-mesh stator-rotor simulations<br />
* Hybrid steady-unsteady stator-rotor simulations<br />
* Other '''advanced''' multi-stage methods<br />
<br />
=== Steady mixing-plane simulations ===<br />
<br />
Since the mixing-plane method was first introduced in 1979 [Denton & Singh 1979] it has become the industry standard type of rotor-stator simulations. A mixing-plane simulation is steady and only requires one rotor blade and one stator blade per stage. Between the rotating blade passage and the steady vane passage the flow properties are circumferentially averaged in a so-called mixing-plane interface. This will of course remove all transient rotor-stator interactions, but it still gives fairly representative results. In some commercial codes (CFX for example) mixing-plane interfaces are also called stage-interfaces.<br />
<br />
=== Frozen rotor simulations ===<br />
<br />
In a frozen rotor simulation the rotating and the stationary parts have a fixed relative position. A frame transformation is done to include the rotating effect on the rotating sections. This will give a steady flow and no transient effects are included. With a frozen-rotor simulation rotating wakes, secondary flows, leading edge pressure increases etc. will always stay in exactly the same positions. This makes a frozen rotor simulation very dependent on exactly how the rotors and the stators are positioned. Most often a mixing-plane simulation gives better results. Frozen rotor simulations are mainly performed to obtain a good starting flow-field before doing a transient sliding-mesh simulation.<br />
<br />
=== Unsteady sliding-mesh stator-rotor simulations ===<br />
<br />
This is the most complete type of stator-rotor simulation. In most engines the number of stators and rotors do not have a common denominator (to avoid instabilities caused by resonance between different rings). Hence, to make a full unsteady sliding-mesh computation it is necessary to have a mesh which includes the full wheel with all stators vanes and all rotor blades. This is often not possible, instead it is necessary to reduce the number of vanes and blades by finding a denominator that is '''almost''' common and then scale the geometry slightly circumferentially. Here is an example:<br />
<br />
*Real engine: 36 stator vanes, 41 rotor blades<br />
*Approximated engine: 41 stator vanes, 41 rotor blades, making it possible to simulate only 1 stator vane and 1 rotor blade<br />
*Scaling of stator: All stator vanes are scaled by 36/41 = 0.8780 circumferentially.<br />
<br />
<br />
=== Hybrid steady-unsteady stator-rotor simulations ===<br />
<br />
Hybrid steady-unsteady methods have been proposed in literature (Montomoli et al. 2011) in order to have an unsteady simulation embedded in a multistage steady study. <br />
There are several advantages related to this method: mainly grid size and number of iterations.<br />
<br />
=== Other '''advanced''' multi-stage methods ===<br />
<br />
Time-inclinded, Adamszyk stresses ...<br />
<br />
== Heat transfer predictions ==<br />
<br />
Besides listing the general heat transfer mechanisms involved <br />
(namely conduction, convection, radiation)<br />
heat transfer prediction in CFD may be seen as or split into two cases. <br />
<br />
'''Mesh consists of fluid domain(s)''': <br />
you want to know how heat inserted into the fluid domain (e.g. via the flowing medium) changes the temperature field along the flow path. Be it a steady or transient run, a fluid which enters with a given temperature will usually experience temperature variations, for instance, caused by convective boundary conditions, prescribed temperature profiles at flow obstacles etc. <br />
<br />
'''Mesh consists of fluid and solid domain(s)''': <br />
additionally to the above, you want info too wrt the (spatial, temporal or even spectral) temperature field distribution in surrounding, confining or immersed solids like channel walls or heat exchanger tubes. This is also called conjugate heattransfer CHT in the CFD context. CHT requires a good boundary layer resolution, usually the wall mesh needs to be rather refined, to obtain realistic heatflux results at the fluid/solid interface. Flow and heat transfer convergence require different time step settings, to properly capture changes in flow and heat quantities respectively. <br />
<br />
<br />
In either case, verify (strict necessity depends on CFD code used, CFX for instance checks and assists in regard) that model dimensions, boundary conditions and properties are in consistent units, hold appropriate values. Check temperature-dependence of properties and other numbers before the run.<br />
<br />
In heat transfer predictions (depending on the CFD code in use) <br />
besides the flow solver, you may have to activate the thermal solver too, <br />
as a job specification.<br />
<br />
== Acoustics and noise ==<br />
<br />
A whole separate research subject, difficult. <br />
<br />
Tone noise possible. Often run with linearzised solvers in the frequency domain.<br />
<br />
Jet noise possible. Often run with LES or DES simulations that either also resolve the sound waves or couples to a separate acoustic solver.<br />
<br />
Turbomachinery broadband noise not possible yet, or at least a great challenge.<br />
<br />
== Errors and uncertainties ==<br />
<br />
CFD is still a tool which requires that a user has a good understanding of uncertainties and errors that might spoil a CFD similation. There exists no error control in CFD and any CFD simulation must be interpreted by an expirenced user to have some credibility. Without some knowledge about possible errors and how they can be handled a CFD simulation can not be trusted. Errors can occur at different places:<br />
<br />
* Definition of the problem - What needs to be analyzed?<br />
* Selection of the solution strategy - What physical models and what numerical tools should be used?<br />
* Development of the computational model - How should the geometry and the numerical tools be set up?<br />
* Analysis and interpretation of the results - How should the model be analyzed and the results be interpreted?<br />
<br />
There exists many different definitions on errors. In this guide the errors are classified into four types of errors: problem definition errors, model errors, numerical errors and user and code errors. The chapters below describe these errors and give some guidelines on how to avoid them.<br />
<br />
=== Problem definition errors ===<br />
<br />
Problem definition errors are the most basic form of errors. In order to obtain usefull results a CFD simulation must of course analyze the correct problem, have suitable boundary contions and be based on a relevant geometry.<br />
<br />
==== Wrong type of simulation ====<br />
<br />
It is essential to have an overview of the physics involved and how the problem can best be analyzed. Running a 2D simulation in order to understand secondary flows or running a steady simulation in order to understand transient behaviour is of course no use. When assessing a CFD simulation the first thing to consider is what physical phenomena are important for the results and if the selected type of simulation is suitable to resolve this type of phenomena. For further information about selecting the most suitable type of simulation please see the previous chapter on [[#Deciding what type of simulation to do|deciding what type of simulation to perform]].<br />
<br />
==== Incorrect or uncertain boundary conditions ====<br />
<br />
A common source of errors is that incorrect boundary conditions are used. The boundary conditions must be specified in enough detail in order to resolve all the important physical features in the problem. For further information about specifying boundary conditions please see the previous chapter on [[#Boundary conditions|boundary conditions]].<br />
<br />
==== Geometrical errors ====<br />
<br />
It is almost always necessary to simplify the geometry in some form. When assessing a CFD simulation one should consider how the geometrical simplifications can affect the interesting physical phenomena. Typical geometrical errors are:<br />
<br />
*Simplifications<br />
:Small geometrical features like fillets, small steps or gaps etc. can often be disregarded. When disregarding this type of features one should consider if they might affect the important physics. For example, a very large fillet on the suction-side of a vane might affect corner separations near the end-walls. A large tip-leakage might affect the flow physics significantly in the upper part of a compressor.<br />
*Tolerances and manufacturing discrepancies<br />
:If the geometry has very large tolerances or is manufactured in a way which might produce a non-ideal shape or position it might be necessary to perform additional CFD simulations in order to cover the whole span of possible real geometries.<br />
*Surface conditions - roughness, welds, steps, gaps etc.<br />
:Often CFD simulations assume a perfectly smooth surface. A non-smooth surface which might have welds, steps or even gaps will of course produce different results. If the physical phenomena of interest might depend on the surface conditions these should of course be condidered. Typical phenomena that might be dependent on this type of errors are transition prediction, leakage flows etc.<br />
<br />
=== Model errors ===<br />
<br />
Errors related to the computational model.<br />
<br />
==== Wrong physical models ====<br />
<br />
Once the type of simulation has been selected the next step is to select what type of physical models the simulation should use. The following points should be considered:<br />
<br />
* Gas data (incompressible/compressible, perfect gas/real gas, ...)<br />
* Turbulence modeling (type of model, type of near-wall treatment, ...)<br />
* Other models (combustion, sprays, ...)<br />
<br />
When assessing model related errors it is important to know the features of the selected model and think carefully how these features and possible short comings might affect the predicted physical behaviour. Using the wrong turbulence model or combustion model can completely destroy the results of a CFD simulation.<br />
<br />
=== Numerical errors ===<br />
<br />
Errors related to the numerical solution of the developed model. Typical examples of numerical errors are discretization errors, convergence errors and round-off errors.<br />
<br />
==== Discretization errors ====<br />
<br />
Discretization errors can either be spatial errors in space or temporal errors in time.<br />
<br />
Spatial discretization errors are what people normally call discretization errors. These errors are due to the difference between the exact solution and the numerical representation of the solution in space. Describing exactly what discretization different codes use and what errors this might lead to is not possible here. Instead some general rules to avoid these errors can be summarized as:<br />
* Use at least a 2nd order accurate scheme, preferably a 3rd order accurate scheme. Some general purpose codes have a 1st order upwind scheme as default, this is a very diffusives schemes that often gives too smooth results.<br />
* For new applications always run a simulation with a finer mesh to see how grid independent your solution is.<br />
* Be aware of checker-board errors. Checker-board errors occur close to strong shocks and other large discontinuities and can be seen as a wavy pattern with a wavelength of two cells. Some schemes, especially those who behave like central differencing schemes, are more prone to checker-board errors. Upwind schemes are a bit better and schemes like TVD or chock-capturing schemes are even better.<br />
<br />
Temporal discretization errors mainly effect transient simulations. However, some codes use a time-marching method also for steady simulations and then a temporal discretization error might affect the final steady solution slightly. The discretization in time can be done with 1st or 2nd order schemes or a Runge-Kutta method, which is more accurate and saves memory. Some codes can adapt the time-step, but often it is necessary to prescribe a time-step in advance. Think of the time-step as your grid in time and make sure that the grid-resolution in time is fine enough to resolve the highest frequencies. To avoid problems with temporal discretization errors the following should be considered:<br />
* Use at least a 2nd order scheme in time.<br />
* Do a physical estimation of the typical frequencies in time of the phenomena that you are interested in and select a time-step which is fine enough to resolve these frequencies well. After the simulation also look at the frequencies captured and make sure that they are well resolved by the chosen time-step.<br />
* For new applications try a finer time-step to ensure that your solution in time is fairly grid independent in time.<br />
<br />
==== Convergence errors ====<br />
<br />
To judge when a CFD simulation is converged is not always that easy. Different codes and different applications behave very differently. For a pure aero-simulation on a fairly coarse grid convergence is easy to judge, but for more complex simulations involving resolved boundary layers, heat transfer, combustion etc. convergence can be very tricky. Aside from looking at residuals one should always also look at how global parameters like static pressure distributions, total pressure losses, skin friction, heat transfer etc. change in time.<br />
For more information about how to avoid convergence errors see the previous chapter about [[#Convergence criteria]].<br />
<br />
==== Round-off errors ====<br />
<br />
When using single precision care needs to be taken to avoid round-off errors. Inviscid Euler simulations and simulations using wall-function meshes can most often be performed in single precision. For well resolved boundary layers with Y plus close to 1 it is often necessary to use double precision. If using double precision for very fine mesh resolutions make sure that you also create the mesh in double precision and not just run the solver in double precision. Sometimes a single precision solver converges slower than a double precision solver due to numerical errors caused by round-off errors. When using advanced physical models like combustion, free-surface simulations, spray and transient simulations with quick mesh motions it is also often necessary to use double precision.<br />
<br />
=== User and code errors ===<br />
<br />
Errors related to bugs in the code used or mistakes made by the CFD engineer.<br />
<br />
=== What to trust and what not to trust ===<br />
<br />
CFD is generally quite good at predicting surface static pressure distributions. With care CFD can also be used to predict performance, total-pressure losses and blade turning. <br />
<br />
Predicting separation, stall and off-design performance can be a challenge and results with non-attached flows should be interpreted with care. <br />
<br />
Heat transfer is often very difficult to predict accurately and it is common to obtain heat-transfer coefficients that are 100% wrong or more. Validation data is critical in order to be able to trust heat transfer simulations.<br />
<br />
Transition is almost impossible to predict accurately in general. However, there exist models that have been tuned to predict transition and these tend to give acceptable results for cases close to the ones they were tuned for.<br />
<br />
== References ==<br />
<br />
* {{reference-paper|author=Abu-Ghannam, B.J. and Shaw, R.|year=1980|title=Natural Transition of Boundary Layers - the Effects of Turbulence, Pressure Gradient, and Flow History|rest=Journal of Mech. Eng. Science, vol. 22, no. 5, pp. 213–228}}<br />
<br />
* {{reference-paper|author=Adamczyk, J. J.|year=1985|title=Model Equation for Simulating Flows in Multistage Turbomachinery|rest=ASME Paper 85-GT-226, also NASA TM-86869}}<br />
<br />
* {{reference-paper|author=Adamczyk, J. J.|year=1999|title=Aerodynamic Analysis of Multistage Turbomachinery Flows in Support of Aerodynamic Design|rest=ASME Paper 99-GT-80.}}<br />
<br />
* {{reference-paper|author=Baldwin, B. S. and Lomax, H.|year=1978|title=Thin Layer Approximation and Algebraic Model for Separated Turbulent Flows|rest=AIAA Paper 78-257}}<br />
<br />
* {{reference-paper|author=Chen, J. P. and Barter, J. W.|year=1998|title=Comparison of Time-Accurate Calculations for the Unsteady Interaction in Turbomachinery Stage|rest=AIAA Paper 98-3292}}<br />
<br />
* {{reference-paper|author=Denton, J. and Singh, U.|year=1979|title=Time Marching Methods for Turbomachinery Flow Calculations|rest=VKI Lecture Series 1979-7, von Karman Institute}}<br />
<br />
* {{reference-paper|author=Erdos, J., Alzner, E. and McNally, W.|year=1977|title=Numerical Solution of Periodic Transonic Flow Through a Transonic Fan Stage|rest=AIAA Journal, vol. 15, no. 11, pp. 1559-1568}}<br />
<br />
* {{reference-paper|author=Gerolymos, G., Vinteler, D., Haugeard, R., Tsange, G. and Vallet, I.|year=1996|title=On the Computation of Unsteady Turbomachinery Flows – Part II – Rotor/Stator Interaction using Euler Equations|rest=AGARD Report CP-571}}<br />
<br />
* {{reference-paper|author=Giles, M. B.|year=1990|title=Stator/Rotor Interaction in a Transonic Turbine|rest=AIAA Journal of Propulsion and Power, vol. 6, no. 5}}<br />
<br />
* {{reference-paper|author=He, L, and Ning, W.|year=1998|title=Efficient Approach for Analysis of Unsteady Viscous Flows in Turbomachines|rest=AIAA Journal, vol. 36, no. 11, pp. 2005-2012}}<br />
<br />
* {{reference-paper|author=Mayle, R. E.|year=1991|title=The Role of Laminar-Turbulent Transition in Gas Turbine Engines|rest=ASME Journal of Turbomachinery, vol. 113, pp. 509-537}}<br />
<br />
* {{reference-paper|author=Menter, F.R. |year=1994|title=Two-equation eddy-viscosity turbulence models for engineering applications|rest=AIAA Journal, vol. 32, pp. 269-289}}<br />
<br />
* {{reference-paper|author= Montomoli, F., Hodson,H.P, Lapworth, L. |year=2009|title=RANS-URANS in axial compressors, a design methodology|rest=Journal of Power and Energy, 225 (A3), pp. 363-374 (2011)}}<br />
<br />
* {{reference-paper|author=Savill, M., Dick, E., Hanjalić, K. and Voke, P.|year=2002|title=Synthesis Report of the ERCOFTAC Transition Modeling – TRANSPRETURB Thematic Network Activities 1998-2002|rest=Ecoftac Bulletin 54, September 2002, pp. 5-16}}<br />
<br />
* {{reference-paper|author=Wang, X. and Chen J.|year=2004|title=A Post-Processor to Render Turbomachinery Flows Using Phase-Lag Simulations|rest=AIAA Paper 04-615}}<br />
<br />
== External links ==<br />
<br />
* [https://pronet.wsatkins.co.uk/marnet/guidelines/guide.html MARNET-CFD Best Practice Guidelines for Marine Applications of CFD]<br />
* [http://www.stanford.edu/group/ctr/ResBriefs/temp05/weide.pdf On Large Scale Turbomachinery Computations, by E. van der Weide et. al., Center for Turbulence Research, Annual Research Briefs 2005]</div>Frmontohttps://www.cfd-online.com/Wiki/Best_practice_guidelines_for_turbomachinery_CFDBest practice guidelines for turbomachinery CFD2013-08-23T10:18:20Z<p>Frmonto: /* References */</p>
<hr />
<div>This article contains a summary of the most important knowledge and experience a CFD engineer needs in order to perform CFD simulations of turbomachinery components. The guide is mainly aimed at axial turbomachinery. The goal is to give a CFD engineer, who has just started working with turbomachinery simulations, a head start and avoid some of the most difficult pit-falls. Experienced turbomachinery CFD engineers can also use the guidelines in order to learn what other experts consider best practice. The intended audience is expected to know basic CFD terminology and have a basic turbomachinery knowledge, but no detailed knowledge about CFD for turbomachinery is needed. <br />
<br />
== Deciding what type of simulation to do ==<br />
<br />
Before starting a new turbomachinery simulation it is wise to think carefully of what it is that should be predicted and what physical phenomena that affect the results. This chapter contains a brief overview of the various types of simulations and some hints of what can be predicted with them.<br />
<br />
=== 2D, Quasi-3D or 3D ===<br />
<br />
2D simulations are often used in the early design phase in order to obtain a typical 2D section of a blade. For cases with many long blades or vanes, like low-pressure turbines, a 2D simulation can also provide reasonable results. If the area of the flow-path changes significantly in the axial direction it might be necessary to instead make a quasi-3D simulation. A quasi-3D simulation is a 2D simulation in which extra source terms are used to account for the acceleration/deceleration caused by a changing channel height or growing end-wall boundary layers. Codes focused on turbomachinery applications often have the possibility to perform quasi-3D simulations, but most general purpose CFD codes can not do this type of simulations, or require user coding to implement the correct source terms in the equations. Please contact your software distributor if your code does not have the quasi-3d possibility and you require it. Many codes require special routines or hidden commands to enable this feature.<br />
<br />
Full 3D simulations are necessary if a true 3D geometry is needed to obtain correct secondary flows and/or shock locations. For low-aspect-ratio cases with only a few short blades, like for example structurally loaded turbine outlet guide vanes, the secondary flow development is important and a 3D simulation is often necessary in order to obtain reasonable results. For applications where the end-wall boundary layers grow very quickly and interact with a large part of the flow-field it is necessary to perform a full 3D simulation. This is often the case in compressors and fans, where the negative pressure gradients make the boundary layers grow much quicker than what they do in for example turbines. For cases where the shock location is very critical, like in transonic compressors, it is also often necessary to perform a 3D simulation in order to obtain reasonable shock locations.<br />
<br />
=== Inviscid or viscid ===<br />
<br />
For attached flows close to the design point and without any large separations it is often sufficient with an inviscid Euler simulation in order to obtain reasonable blade loadings and pressure distributions. Note that inviscid Euler simulations should only be used if the boundary layers are judged to not have a significant effect on the global flow-field. A viscid Navier-Stokes simulation is necessary in order to predict losses, secondary flows and separations. As soon as separations are of interest it is of course also necessary to do a viscid simulation. Note that with todays computers it is often not time and resources that make users run inviscid Euler simulations. Running viscid Navier-Stokes simulations is now so quick that it is not a time problem any more. Euler simulations are still interesting though, since with an inviscid Euler simulation you don't have to worry about wall resolutions, y+ values, turbulence modeling errors etc.<br />
<br />
=== Transient or Stationary ===<br />
<br />
Most turbomachinery simulations are performed as stationary simulations. Transient simulations are done when some kind of transient flow behaviour has a strong influence on the global flow field. Examples of transient simulations are detailed simulations of rotor-stator interaction effects, simulations of large unsteady separations etc. Sometimes when you perform a steady stationary simulation you can see tendencies of unsteady behaviour like for example periodic vortex shedding behind blunt trailing edges. This is often first seen as periodical variations of the residuals. If the unsteady tendencies are judged to not affect the overall simulation results it might be necessary to coarsen the mesh close to the vortex shedding or run a different turbulence model in order to make the simulation converge. Sometimes you are still forced to run a transient simulation and average the results if you don't obtain a converged steady solution.<br />
<br />
== Meshing ==<br />
<br />
In turbomachinery applications structured multi-block hexahedral meshes are most often used for flow-path simulations. In most solvers a structured grid requires less memory, provides superior accuracy and allows a better boundary-layer resolution than an unstructured grid. By having cells with a large aspect ratio around sharp leading and trailing edges a structured grid also provides a better resolution of these areas. Many companies have automatic meshing tools that automatically mesh blade sections with a structured mesh without much user intervention.<br />
<br />
Unstructured meshes are used for more complex and odd geometries where a structured mesh is difficult to create. Typical examples where unstructured meshes are often used are blade tip regions, areas involving leakage flows and secondary air systems, film cooling ducts etc.<br />
<br />
When meshing avoid to create large jumps in cell sizes. Typically the cell size should not change with more than a factor of 1.25 between neighbouring cells. For structured meshes also try to create fairly continous mesh lines and avoid discontinuities where the cell directions suddenly change. For multi-block structured meshes avoid placing the singular points where blocks meet in regions with strong flow gradients since most schemes have a lower accuracy in these singular points.<br />
<br />
=== Mesh size guidelines ===<br />
<br />
It is difficult to define, a priori, the mesh size. The required mesh size depends on the purpose of the simulation. <br />
<br />
If the main goal is to obtain static pressure forces a coarse mesh is often able to obtain a good solution, especially when an accurate resolution of the boundary layers is not required. For 2D inviscid simulations of one blade a mesh with say 3,000 cells is most often sufficient. For 3D inviscid blade simulations a mesh size of about 40,000 cells is usually sufficient. On inviscid Euler simulations the cells should be fairly equal in size and no boundary layer resolution should be present. Avoid having too skewed cells.<br />
<br />
For loss predictions and cases where boundary layer development and separation is important the mesh needs to have a boundary layer resolution. The boundary layer resolution can either be coarse and suitable for a [[Wall functions|wall function]] simulation or very fine and suitable for a [[Low-Re resolved boundary layers|low-Re]] simulation. For further information about selecting the near-wall turbulence model please see the [[#Turbulence modeling|turbulence modeling]] section. In 3D single-blade simulations a decent wall-function mesh typically has around 100,000 cells. This type of mesh size is suitable for quick design iterations where it is not essential to resolve all secondary flows and vortices. A good 3D wall-function mesh of a blade section intended to resolve secondary flows well should have at least 400,000 cells . A good low-Re mesh with resolved boundary layers typically has around 1,000,000 cells. <br />
<br />
In 2D blade simulations a good wall-function mesh has around 20,000 cells and a good low-Re mesh with resolved boundary layers has around 50,000 cells.<br />
<br />
Along the suction and pressure surfaces it is a good use about 100 cells in the streamwise direction. In the radial direction a good first approach is to use something like 30 cells for a wall-function mesh and 100 cells for a low-Re mesh.<br />
<br />
It is important to resolve leading and trailing edges well. Typically at least 10 cells, preferably 20 should be used around the leading and trailing edges. For very blunt and large leading edges, like those commonly found on HP turbine blades, 30 or more cells can be necessary.<br />
<br />
Cases which are difficult to converge with a steady simulation and which show tendencies of periodic vortex shedding from the trailing edge, can sometimes be "tamed" by using a coarse mesh around the trailing edge. This, of course, reduces the accuracy but can be a trick to obtain a converged solution if time and computer resources does not allow a transient simulation to be performed.<br />
<br />
=== Boundary layer mesh ===<br />
<br />
For design iteration type of simulations where a [[Wall functions|wall function]] approach is sufficient [[Dimensionless wall distance (y plus) | y+]] for the first cell should be somewhere between 20 and 200. The outer limit is dependent on the actual Re number of the simulations. For cases with fairly low Re numbers make sure to keep the maximum y+ as low as possible. For more accurate simulations with resolved boundary layers the mesh should have a y+ for the first cell which is below 1. Some new codes are now using a hybrid wall treatment that allows a smooth transition from a coarse wall-function mesh to a resolved low-Re mesh. Use some extra care when using this type of hybrid technique since it is still fairly new and unproven.<br />
<br />
Outside of the first cell at a wall a good rule of thumb is to use a growth ratio normal to the wall in the boundary layer of maximum 1.25. For a low-Re mesh this usually gives around 40 cells in the boundary layer whereas a wall-function mesh does not require more than 10 cells in the boundary layer.<br />
<br />
If you are uncertain of which wall distance to mesh with you can use a [http://www.cfd-online.com/Links/tools.html#yplus y+ estimation tool] to estitmate the distance needed to obtain the desired y+. These estimation tools are ''very handy'' if you have not done any previous similar simulations. <br />
<br />
As a rule of thumb a wall-function mesh typically requires areound 5 to 10 cells in the boundary layer whereas a resolved low-Re mesh requires about 40 cells in the boundary layer.<br />
<br />
== Boundary conditions ==<br />
<br />
Describe different types of boundary conditions and when they should be used:<br />
<br />
* Total pressure in, static pressure out<br />
* Absorbing boundary conditions<br />
* ...<br />
<br />
There are different types of boundary conditions you can use:<br />
*Mass flow inlet, static pressure outlet.<br />
To put this BC you must allocate inlet surface enough far away from the turbomachine impeller. The velocity distribution is not<br />
constant over all the surface. If you put this "lie" away from your problem it works well.<br />
<br />
<br />
=== Turbulence inlet conditions ===<br />
<br />
Prescribing realistic turbulence inlet conditions is important and usually difficult. For two-equation turbulence models two different turbulence values need to be specified on the inlet. The most common way of specifying the inlet turbulence variables is to give an inlet [[Turbulence intensity|turbulence level]] and [[Turbulence length scale|length-scale]]. For simulations where the incoming boundary layers are estimated to not have any significant effect on the secondary flows and global flow-field downstream it is usually sufficient to specify a constant incoming turbulence level and length-scale.<br />
<br />
The incoming [[Turbulence intensity|turbulence level]] is dependent on which component is analyzed. Best is of course to have measurments from a similar application in order to be able to prescribe a fairly realistic value. Without measurements it is necessary to make an educated guess. Simulations with very complex and turbulence-generating components upstream will have a very high incoming turbulence level. For example, a high-pressure turbine just downstream of a turbulence generating combustor might have incoming turbulence levels up to 20%. Fans and low-pressure compressors with not many components upstream might have as low incoming turbulence level as 1%. For components between these two extreme examples, like high-pressure compressors, low-pressure turbines etc. a turbulence level of around 5% might be realistic. If you do not have any measurements and are unsure about which incoming turbulence level to prescribe it is always a good idea to run a few different simulations with say one half and one double incoming turbulence level in order to estimate how important it is for the simulation results.<br />
<br />
The incoming [[Turbulence length scale|turbulence length-scale]] is often even more difficult to guess than the incoming turbulence level. Measurements might sometimes include the incoming turbulence level, but very seldom also include the incoming turbulent length-scale. The best way of guessing a realistic incoming length-scale is to use the geometrical properties of the upstream components. The incoming turbulence length-scale can be estimated as say the thickness of upstream blades or somewhere between 2% and 20% of the incoming channel heigth. Fortunately the incoming turbulence length-scale is usually not that important for the end results. However, some k-omega models can have an unrelisticly strong influence on the incoming turbulence length-scale. Hence, be extra carefull about the length-scale when using k-omega models. Note that the [[SST k-omega model]] does not have this unrealistic sensitivity to the inlet turbulence length-scale.<br />
<br />
Instead of specifying an incoming turbulence length-scale it is sometimes more convenient to specify an incoming [[Eddy viscosity ratio|eddy viscosity ratio]]. For low-turbulence cases with no well-specified turbulence generating components upstream it can be difficult to estimate a turbulence length-scale. Specifying an eddy viscosity ratio instead gives a more direct control over how large the effect of the incoming turbulence is. The eddy viscosity ratio describes how large the turbulence viscosity is related to the molecular viscosity. In turbomachinery the eddy viscosity ratio can vary from say 10 in low-turbulence components like fans up to say 1,000 or in rare cases even 10,000 in high-turbulence components like high-pressure turbines. In components between these extremes a typical eddy viscosity ration might be about 200. Even if specifying an inlet turbulence length scale it can still be good to compute what eddy viscosity ratio this corresponds to in order to estimate if it sounds reasonable.<br />
<br />
== Turbulence modeling ==<br />
<br />
Selecting a suitable turbulence model for turbomachinery simulations can be a challenging task. There is no single model which is suitable for all types of simulations. Which turbulence model CFD engineers use has as much to do with beliefs and traditions as with knowledge and facts. There are many different schools. However, below follows some advices that most CFD engineers in the turbomachinery field tend to agree upon.<br />
<br />
For attached flows close to the design point a simple algebraic model like the [[Baldwin-Lomax model]] can be used. Another common choice for design-iteration type of simulations is the one-equation model by [[Spalart-Allmaras model | Spalart-Allmaras]]. This model has become more popular in the last years due to the many inherent problems in more refined two-equation models. The big advantage with both the [[Baldwin-Lomax model]] and the [[Spalart-Allmaras model]] over more advanced models is that they are very robust to use and rarely produce completely unphysical results.<br />
<br />
In order to accurately predict more difficult cases, like separating flows, rotating flows, flows strongly affected by secondary flows etc. it is often necessary to use a more refined turbulence model. Common choices are two-equation models like the <math>k-\epsilon</math> model.<br />
<br />
Two-equation models are based on the [[Boussinesq eddy viscosity assumption]] and this often leads to an over-production of turbulent energy in regions with strong acceleration or deceleration, like in the leading edge region, regions around shocks and in the suction peak on the suction side of a blade. To reduce this problems it is common to use a special model variant using, for example, [[Durbin's realizability constraint]] or the [[Kato-Launder modification]]. Note that different two-equation models behave differently in these problematic stagnation and acceleration regions. Worst is probably the standard <math>k-\epsilon</math> model. <math>k-\omega</math> model are slightly better but still do not behave well. More modern variants like Menter's [[SST k-omega model]] also has problems, wheras the [[V2-f models|v2f model ]] by Durbin behaves better.<br />
<br />
=== Near-wall treatment ===<br />
<br />
For on-design simulations without any large separated regions it is often sufficient to use a [[wall-function model]] close to the wall, preferably with some form of non-equilibrium wall-function that is sensitised to streamwise pressure gradients.<br />
<br />
For off-design simulation, or simulations involving complex secondary flows and separations, it is often necessary to use a [[low-Re model]]. There exist many low-Re models that have been used with success in turbomachinery simulations. A robust and often good choice is to use a one-equation model, like for example the [[Wolfstein model]], in the inner parts of the boundary layer. There are also several Low-Re <math>k-\epsilon</math> models that work well. Just make sure they don't suffer from the problem with overproduction of turbulent energy in regions with strong acceleration or deceleration. In the last few years Menter's low-Re <math>SST k-\omega</math> model has gained increased popularity.<br />
<br />
=== Transition prediction ===<br />
<br />
Transition refers to the process when a laminar boundary layer becomes unstable and transitions to a turbulent boundary layer. There are two types of transition - natural transition, where inherent instabilities in the boundary layer cause the transition and by-pass transition, where convection and diffusion of turbulence from the free-stream into the boundary layer cause the transition. Most transitions in turbomachinery are by-pass transitions caused by free-stream turbulence and other external disturbances like wakes, vortices and surface defects.<br />
<br />
Simulating transition in a CFD code accurately is very difficult. Often a separate transition model needs to be solved in order to specify the transition location and length. Predicting natural transition in a pure CFD code is not possible. Predicting by-pass transition in a pure CFD code is almost impossible, although there are people who claim to be able to predict by-pass transition with low-Re two-equation models. However, this is usually on special test cases and with simulations that have been tuned for these special cases, see for example [Saville 2002]. In reality transition is a very complex and sensitive process where disturbances like incoming wakes and vortices from previous stages, surface roughness effects and small steps or gaps in the surfaces play a significant role. <br />
<br />
The turbomachinery codes that have transition prediction models often use old ad-hoc models like the Abu-Ghannam and Shaw model [Abu-Ghannam 1980] or the Mayle model [Mayle 1991]. These models can be quite reliable if they have been validated and tuned for a similar application. Do not trust your transition predictions without having some form of experimental validation. Menter has also recently developed a new form of transition model that might work fairly well, but it is still too new and untested.<br />
<br />
For some turbomachinery applications, like modern high-lift low-pressure turbines, transition is critical. For these applications a CFD code with a transition model that has been tuned for this type of applications should be used.<br />
<br />
== Numerical considerations ==<br />
<br />
Use at least a second order accurate scheme for the flow variables. Some codes require a first order scheme for the turbulent variables (<math>k</math> and <math>\epsilon</math>) in order to converge well. It might be sufficient with a first order scheme only on the turbulence variables, but a second order scheme is of course preferable.<br />
<br />
=== Convergence criteria ===<br />
<br />
To know when a solution is converged is not always that easy. You need some prior experience of your CFD code and your application to judge when a simulation is converged. For normal pure aero simulations without resolved walls, i.e. with wall functions or inviscid Euler simulations, convergence can most often be estimated just by looking at the residuals. Exactly what the residuals should be is not possible to say, it all depends on how your particular code computes and scales the residuals. Hence, make sure to read the manuals and plot the convergence of a few global parameters before you decide what the residuals should be for a solution to converge. Note also that many manuals for genereal purpose CFD codes list overly aggressive convergence criteria that often produce unconverged results. <br />
For simulations with resolved walls it is good to look at the convergence of some global properties, like total pressure losses from the inlet to the outlet. For heat transfer simulations it is even more tricky since the aerodynamic field can look almost converged although the thermal field is not converged at all. If doing heat transfer simulations make sure to plot the heat-transfer, run for some time, and plot it again to make sure that it doesn't change anymore. With very well resolved walls and heat transfer it can sometimes take 10 times longer for the thermal field to converge.<br />
<br />
=== Single or double precision ===<br />
<br />
With todays computers and cheap memory prices it often does not cost much extra to run in double precision. Before using single precision you should first investigate how your software and hardware works with double precision. If the extra time and memory needed for double precision is negligible you should of course always run in double precision. With double precision you never have to worry about round-off errors. Always using double precision is one way of avoiding one type of pit-falls in the complex world of CFD simulations. Use double precision when you have resolved boundary layers (Y+ around 1) and when you use advanced physical models like combustion, free-surface simulations, spray and transient simulations with quick mesh motions.<br />
<br />
== Multi-stage analysis ==<br />
<br />
Multi-stage analysis can be done in different ways:<br />
<br />
* Steady mixing-plane simulations<br />
* Frozen rotor simulations<br />
* Unsteady sliding-mesh stator-rotor simulations<br />
* Hybrid steady-unsteady stator-rotor simulations<br />
* Other '''advanced''' multi-stage methods<br />
<br />
=== Steady mixing-plane simulations ===<br />
<br />
Since the mixing-plane method was first introduced in 1979 [Denton & Singh 1979] it has become the industry standard type of rotor-stator simulations. A mixing-plane simulation is steady and only requires one rotor blade and one stator blade per stage. Between the rotating blade passage and the steady vane passage the flow properties are circumferentially averaged in a so-called mixing-plane interface. This will of course remove all transient rotor-stator interactions, but it still gives fairly representative results. In some commercial codes (CFX for example) mixing-plane interfaces are also called stage-interfaces.<br />
<br />
=== Frozen rotor simulations ===<br />
<br />
In a frozen rotor simulation the rotating and the stationary parts have a fixed relative position. A frame transformation is done to include the rotating effect on the rotating sections. This will give a steady flow and no transient effects are included. With a frozen-rotor simulation rotating wakes, secondary flows, leading edge pressure increases etc. will always stay in exactly the same positions. This makes a frozen rotor simulation very dependent on exactly how the rotors and the stators are positioned. Most often a mixing-plane simulation gives better results. Frozen rotor simulations are mainly performed to obtain a good starting flow-field before doing a transient sliding-mesh simulation.<br />
<br />
=== Unsteady sliding-mesh stator-rotor simulations ===<br />
<br />
This is the most complete type of stator-rotor simulation. In most engines the number of stators and rotors do not have a common denominator (to avoid instabilities caused by resonance between different rings). Hence, to make a full unsteady sliding-mesh computation it is necessary to have a mesh which includes the full wheel with all stators vanes and all rotor blades. This is often not possible, instead it is necessary to reduce the number of vanes and blades by finding a denominator that is '''almost''' common and then scale the geometry slightly circumferentially. Here is an example:<br />
<br />
*Real engine: 36 stator vanes, 41 rotor blades<br />
*Approximated engine: 41 stator vanes, 41 rotor blades, making it possible to simulate only 1 stator vane and 1 rotor blade<br />
*Scaling of stator: All stator vanes are scaled by 36/41 = 0.8780 circumferentially.<br />
<br />
<br />
=== Hybrid steady-unsteady stator-rotor simulations ===<br />
<br />
Hybrid steady-unsteady methods have been proposed in literature (Montomoli et al. 2009) in order to have an unsteady simulation embedded in a multistage steady study. <br />
There are several advantages related to this method: mainly grid size and number of iterations.<br />
<br />
=== Other '''advanced''' multi-stage methods ===<br />
<br />
Time-inclinded, Adamszyk stresses ...<br />
<br />
== Heat transfer predictions ==<br />
<br />
Besides listing the general heat transfer mechanisms involved <br />
(namely conduction, convection, radiation)<br />
heat transfer prediction in CFD may be seen as or split into two cases. <br />
<br />
'''Mesh consists of fluid domain(s)''': <br />
you want to know how heat inserted into the fluid domain (e.g. via the flowing medium) changes the temperature field along the flow path. Be it a steady or transient run, a fluid which enters with a given temperature will usually experience temperature variations, for instance, caused by convective boundary conditions, prescribed temperature profiles at flow obstacles etc. <br />
<br />
'''Mesh consists of fluid and solid domain(s)''': <br />
additionally to the above, you want info too wrt the (spatial, temporal or even spectral) temperature field distribution in surrounding, confining or immersed solids like channel walls or heat exchanger tubes. This is also called conjugate heattransfer CHT in the CFD context. CHT requires a good boundary layer resolution, usually the wall mesh needs to be rather refined, to obtain realistic heatflux results at the fluid/solid interface. Flow and heat transfer convergence require different time step settings, to properly capture changes in flow and heat quantities respectively. <br />
<br />
<br />
In either case, verify (strict necessity depends on CFD code used, CFX for instance checks and assists in regard) that model dimensions, boundary conditions and properties are in consistent units, hold appropriate values. Check temperature-dependence of properties and other numbers before the run.<br />
<br />
In heat transfer predictions (depending on the CFD code in use) <br />
besides the flow solver, you may have to activate the thermal solver too, <br />
as a job specification.<br />
<br />
== Acoustics and noise ==<br />
<br />
A whole separate research subject, difficult. <br />
<br />
Tone noise possible. Often run with linearzised solvers in the frequency domain.<br />
<br />
Jet noise possible. Often run with LES or DES simulations that either also resolve the sound waves or couples to a separate acoustic solver.<br />
<br />
Turbomachinery broadband noise not possible yet, or at least a great challenge.<br />
<br />
== Errors and uncertainties ==<br />
<br />
CFD is still a tool which requires that a user has a good understanding of uncertainties and errors that might spoil a CFD similation. There exists no error control in CFD and any CFD simulation must be interpreted by an expirenced user to have some credibility. Without some knowledge about possible errors and how they can be handled a CFD simulation can not be trusted. Errors can occur at different places:<br />
<br />
* Definition of the problem - What needs to be analyzed?<br />
* Selection of the solution strategy - What physical models and what numerical tools should be used?<br />
* Development of the computational model - How should the geometry and the numerical tools be set up?<br />
* Analysis and interpretation of the results - How should the model be analyzed and the results be interpreted?<br />
<br />
There exists many different definitions on errors. In this guide the errors are classified into four types of errors: problem definition errors, model errors, numerical errors and user and code errors. The chapters below describe these errors and give some guidelines on how to avoid them.<br />
<br />
=== Problem definition errors ===<br />
<br />
Problem definition errors are the most basic form of errors. In order to obtain usefull results a CFD simulation must of course analyze the correct problem, have suitable boundary contions and be based on a relevant geometry.<br />
<br />
==== Wrong type of simulation ====<br />
<br />
It is essential to have an overview of the physics involved and how the problem can best be analyzed. Running a 2D simulation in order to understand secondary flows or running a steady simulation in order to understand transient behaviour is of course no use. When assessing a CFD simulation the first thing to consider is what physical phenomena are important for the results and if the selected type of simulation is suitable to resolve this type of phenomena. For further information about selecting the most suitable type of simulation please see the previous chapter on [[#Deciding what type of simulation to do|deciding what type of simulation to perform]].<br />
<br />
==== Incorrect or uncertain boundary conditions ====<br />
<br />
A common source of errors is that incorrect boundary conditions are used. The boundary conditions must be specified in enough detail in order to resolve all the important physical features in the problem. For further information about specifying boundary conditions please see the previous chapter on [[#Boundary conditions|boundary conditions]].<br />
<br />
==== Geometrical errors ====<br />
<br />
It is almost always necessary to simplify the geometry in some form. When assessing a CFD simulation one should consider how the geometrical simplifications can affect the interesting physical phenomena. Typical geometrical errors are:<br />
<br />
*Simplifications<br />
:Small geometrical features like fillets, small steps or gaps etc. can often be disregarded. When disregarding this type of features one should consider if they might affect the important physics. For example, a very large fillet on the suction-side of a vane might affect corner separations near the end-walls. A large tip-leakage might affect the flow physics significantly in the upper part of a compressor.<br />
*Tolerances and manufacturing discrepancies<br />
:If the geometry has very large tolerances or is manufactured in a way which might produce a non-ideal shape or position it might be necessary to perform additional CFD simulations in order to cover the whole span of possible real geometries.<br />
*Surface conditions - roughness, welds, steps, gaps etc.<br />
:Often CFD simulations assume a perfectly smooth surface. A non-smooth surface which might have welds, steps or even gaps will of course produce different results. If the physical phenomena of interest might depend on the surface conditions these should of course be condidered. Typical phenomena that might be dependent on this type of errors are transition prediction, leakage flows etc.<br />
<br />
=== Model errors ===<br />
<br />
Errors related to the computational model.<br />
<br />
==== Wrong physical models ====<br />
<br />
Once the type of simulation has been selected the next step is to select what type of physical models the simulation should use. The following points should be considered:<br />
<br />
* Gas data (incompressible/compressible, perfect gas/real gas, ...)<br />
* Turbulence modeling (type of model, type of near-wall treatment, ...)<br />
* Other models (combustion, sprays, ...)<br />
<br />
When assessing model related errors it is important to know the features of the selected model and think carefully how these features and possible short comings might affect the predicted physical behaviour. Using the wrong turbulence model or combustion model can completely destroy the results of a CFD simulation.<br />
<br />
=== Numerical errors ===<br />
<br />
Errors related to the numerical solution of the developed model. Typical examples of numerical errors are discretization errors, convergence errors and round-off errors.<br />
<br />
==== Discretization errors ====<br />
<br />
Discretization errors can either be spatial errors in space or temporal errors in time.<br />
<br />
Spatial discretization errors are what people normally call discretization errors. These errors are due to the difference between the exact solution and the numerical representation of the solution in space. Describing exactly what discretization different codes use and what errors this might lead to is not possible here. Instead some general rules to avoid these errors can be summarized as:<br />
* Use at least a 2nd order accurate scheme, preferably a 3rd order accurate scheme. Some general purpose codes have a 1st order upwind scheme as default, this is a very diffusives schemes that often gives too smooth results.<br />
* For new applications always run a simulation with a finer mesh to see how grid independent your solution is.<br />
* Be aware of checker-board errors. Checker-board errors occur close to strong shocks and other large discontinuities and can be seen as a wavy pattern with a wavelength of two cells. Some schemes, especially those who behave like central differencing schemes, are more prone to checker-board errors. Upwind schemes are a bit better and schemes like TVD or chock-capturing schemes are even better.<br />
<br />
Temporal discretization errors mainly effect transient simulations. However, some codes use a time-marching method also for steady simulations and then a temporal discretization error might affect the final steady solution slightly. The discretization in time can be done with 1st or 2nd order schemes or a Runge-Kutta method, which is more accurate and saves memory. Some codes can adapt the time-step, but often it is necessary to prescribe a time-step in advance. Think of the time-step as your grid in time and make sure that the grid-resolution in time is fine enough to resolve the highest frequencies. To avoid problems with temporal discretization errors the following should be considered:<br />
* Use at least a 2nd order scheme in time.<br />
* Do a physical estimation of the typical frequencies in time of the phenomena that you are interested in and select a time-step which is fine enough to resolve these frequencies well. After the simulation also look at the frequencies captured and make sure that they are well resolved by the chosen time-step.<br />
* For new applications try a finer time-step to ensure that your solution in time is fairly grid independent in time.<br />
<br />
==== Convergence errors ====<br />
<br />
To judge when a CFD simulation is converged is not always that easy. Different codes and different applications behave very differently. For a pure aero-simulation on a fairly coarse grid convergence is easy to judge, but for more complex simulations involving resolved boundary layers, heat transfer, combustion etc. convergence can be very tricky. Aside from looking at residuals one should always also look at how global parameters like static pressure distributions, total pressure losses, skin friction, heat transfer etc. change in time.<br />
For more information about how to avoid convergence errors see the previous chapter about [[#Convergence criteria]].<br />
<br />
==== Round-off errors ====<br />
<br />
When using single precision care needs to be taken to avoid round-off errors. Inviscid Euler simulations and simulations using wall-function meshes can most often be performed in single precision. For well resolved boundary layers with Y plus close to 1 it is often necessary to use double precision. If using double precision for very fine mesh resolutions make sure that you also create the mesh in double precision and not just run the solver in double precision. Sometimes a single precision solver converges slower than a double precision solver due to numerical errors caused by round-off errors. When using advanced physical models like combustion, free-surface simulations, spray and transient simulations with quick mesh motions it is also often necessary to use double precision.<br />
<br />
=== User and code errors ===<br />
<br />
Errors related to bugs in the code used or mistakes made by the CFD engineer.<br />
<br />
=== What to trust and what not to trust ===<br />
<br />
CFD is generally quite good at predicting surface static pressure distributions. With care CFD can also be used to predict performance, total-pressure losses and blade turning. <br />
<br />
Predicting separation, stall and off-design performance can be a challenge and results with non-attached flows should be interpreted with care. <br />
<br />
Heat transfer is often very difficult to predict accurately and it is common to obtain heat-transfer coefficients that are 100% wrong or more. Validation data is critical in order to be able to trust heat transfer simulations.<br />
<br />
Transition is almost impossible to predict accurately in general. However, there exist models that have been tuned to predict transition and these tend to give acceptable results for cases close to the ones they were tuned for.<br />
<br />
== References ==<br />
<br />
* {{reference-paper|author=Abu-Ghannam, B.J. and Shaw, R.|year=1980|title=Natural Transition of Boundary Layers - the Effects of Turbulence, Pressure Gradient, and Flow History|rest=Journal of Mech. Eng. Science, vol. 22, no. 5, pp. 213–228}}<br />
<br />
* {{reference-paper|author=Adamczyk, J. J.|year=1985|title=Model Equation for Simulating Flows in Multistage Turbomachinery|rest=ASME Paper 85-GT-226, also NASA TM-86869}}<br />
<br />
* {{reference-paper|author=Adamczyk, J. J.|year=1999|title=Aerodynamic Analysis of Multistage Turbomachinery Flows in Support of Aerodynamic Design|rest=ASME Paper 99-GT-80.}}<br />
<br />
* {{reference-paper|author=Baldwin, B. S. and Lomax, H.|year=1978|title=Thin Layer Approximation and Algebraic Model for Separated Turbulent Flows|rest=AIAA Paper 78-257}}<br />
<br />
* {{reference-paper|author=Chen, J. P. and Barter, J. W.|year=1998|title=Comparison of Time-Accurate Calculations for the Unsteady Interaction in Turbomachinery Stage|rest=AIAA Paper 98-3292}}<br />
<br />
* {{reference-paper|author=Denton, J. and Singh, U.|year=1979|title=Time Marching Methods for Turbomachinery Flow Calculations|rest=VKI Lecture Series 1979-7, von Karman Institute}}<br />
<br />
* {{reference-paper|author=Erdos, J., Alzner, E. and McNally, W.|year=1977|title=Numerical Solution of Periodic Transonic Flow Through a Transonic Fan Stage|rest=AIAA Journal, vol. 15, no. 11, pp. 1559-1568}}<br />
<br />
* {{reference-paper|author=Gerolymos, G., Vinteler, D., Haugeard, R., Tsange, G. and Vallet, I.|year=1996|title=On the Computation of Unsteady Turbomachinery Flows – Part II – Rotor/Stator Interaction using Euler Equations|rest=AGARD Report CP-571}}<br />
<br />
* {{reference-paper|author=Giles, M. B.|year=1990|title=Stator/Rotor Interaction in a Transonic Turbine|rest=AIAA Journal of Propulsion and Power, vol. 6, no. 5}}<br />
<br />
* {{reference-paper|author=He, L, and Ning, W.|year=1998|title=Efficient Approach for Analysis of Unsteady Viscous Flows in Turbomachines|rest=AIAA Journal, vol. 36, no. 11, pp. 2005-2012}}<br />
<br />
* {{reference-paper|author=Mayle, R. E.|year=1991|title=The Role of Laminar-Turbulent Transition in Gas Turbine Engines|rest=ASME Journal of Turbomachinery, vol. 113, pp. 509-537}}<br />
<br />
* {{reference-paper|author=Menter, F.R. |year=1994|title=Two-equation eddy-viscosity turbulence models for engineering applications|rest=AIAA Journal, vol. 32, pp. 269-289}}<br />
<br />
* {{reference-paper|author= Montomoli, F., Hodson,H.P, Lapworth, L. |year=2009|title=RANS-URANS in axial compressors, a design methodology|rest=Journal of Power and Energy, 225 (A3), pp. 363-374 (2011)}}<br />
<br />
* {{reference-paper|author=Savill, M., Dick, E., Hanjalić, K. and Voke, P.|year=2002|title=Synthesis Report of the ERCOFTAC Transition Modeling – TRANSPRETURB Thematic Network Activities 1998-2002|rest=Ecoftac Bulletin 54, September 2002, pp. 5-16}}<br />
<br />
* {{reference-paper|author=Wang, X. and Chen J.|year=2004|title=A Post-Processor to Render Turbomachinery Flows Using Phase-Lag Simulations|rest=AIAA Paper 04-615}}<br />
<br />
== External links ==<br />
<br />
* [https://pronet.wsatkins.co.uk/marnet/guidelines/guide.html MARNET-CFD Best Practice Guidelines for Marine Applications of CFD]<br />
* [http://www.stanford.edu/group/ctr/ResBriefs/temp05/weide.pdf On Large Scale Turbomachinery Computations, by E. van der Weide et. al., Center for Turbulence Research, Annual Research Briefs 2005]</div>Frmontohttps://www.cfd-online.com/Wiki/Best_practice_guidelines_for_turbomachinery_CFDBest practice guidelines for turbomachinery CFD2011-03-22T22:51:00Z<p>Frmonto: /* References */</p>
<hr />
<div>This article contains a summary of the most important knowledge and experience a CFD engineer needs in order to perform CFD simulations of turbomachinery components. The guide is mainly aimed at axial turbomachinery. The goal is to give a CFD engineer, who has just started working with turbomachinery simulations, a head start and avoid some of the most difficult pit-falls. Experienced turbomachinery CFD engineers can also use the guidelines in order to learn what other experts consider best practice. The intended audience is expected to know basic CFD terminology and have a basic turbomachinery knowledge, but no detailed knowledge about CFD for turbomachinery is needed. <br />
<br />
== Deciding what type of simulation to do ==<br />
<br />
Before starting a new turbomachinery simulation it is wise to think carefully of what it is that should be predicted and what physical phenomena that affect the results. This chapter contains a brief overview of the various types of simulations and some hints of what can be predicted with them.<br />
<br />
=== 2D, Quasi-3D or 3D ===<br />
<br />
2D simulations are often used in the early design phase in order to obtain a typical 2D section of a blade. For cases with many long blades or vanes, like low-pressure turbines, a 2D simulation can also provide reasonable results. If the area of the flow-path changes significantly in the axial direction it might be necessary to instead make a quasi-3D simulation. A quasi-3D simulation is a 2D simulation in which extra source terms are used to account for the acceleration/deceleration caused by a changing channel height or growing end-wall boundary layers. Codes focused on turbomachinery applications often have the possibility to perform quasi-3D simulations, but most general purpose CFD codes can not do this type of simulations, or require user coding to implement the correct source terms in the equations. Please contact your software distributor if your code does not have the quasi-3d possibility and you require it. Many codes require special routines or hidden commands to enable this feature.<br />
<br />
Full 3D simulations are necessary if a true 3D geometry is needed to obtain correct secondary flows and/or shock locations. For low-aspect-ratio cases with only a few short blades, like for example structurally loaded turbine outlet guide vanes, the secondary flow development is important and a 3D simulation is often necessary in order to obtain reasonable results. For applications where the end-wall boundary layers grow very quickly and interact with a large part of the flow-field it is necessary to perform a full 3D simulation. This is often the case in compressors and fans, where the negative pressure gradients make the boundary layers grow much quicker than what they do in for example turbines. For cases where the shock location is very critical, like in transonic compressors, it is also often necessary to perform a 3D simulation in order to obtain reasonable shock locations.<br />
<br />
=== Inviscid or viscid ===<br />
<br />
For attached flows close to the design point and without any large separations it is often sufficient with an inviscid Euler simulation in order to obtain reasonable blade loadings and pressure distributions. Note that inviscid Euler simulations should only be used if the boundary layers are judged to not have a significant effect on the global flow-field. A viscid Navier-Stokes simulation is necessary in order to predict losses, secondary flows and separations. As soon as separations are of interest it is of course also necessary to do a viscid simulation. Note that with todays computers it is often not time and resources that make users run inviscid Euler simulations. Running viscid Navier-Stokes simulations is now so quick that it is not a time problem any more. Euler simulations are still interesting though, since with an inviscid Euler simulation you don't have to worry about wall resolutions, y+ values, turbulence modeling errors etc.<br />
<br />
=== Transient or Stationary ===<br />
<br />
Most turbomachinery simulations are performed as stationary simulations. Transient simulations are done when some kind of transient flow behaviour has a strong influence on the global flow field. Examples of transient simulations are detailed simulations of rotor-stator interaction effects, simulations of large unsteady separations etc. Sometimes when you perform a steady stationary simulation you can see tendencies of unsteady behaviour like for example periodic vortex shedding behind blunt trailing edges. This is often first seen as periodical variations of the residuals. If the unsteady tendencies are judged to not affect the overall simulation results it might be necessary to coarsen the mesh close to the vortex shedding or run a different turbulence model in order to make the simulation converge. Sometimes you are still forced to run a transient simulation and average the results if you don't obtain a converged steady solution.<br />
<br />
== Meshing ==<br />
<br />
In turbomachinery applications structured multi-block hexahedral meshes are most often used for flow-path simulations. In most solvers a structured grid requires less memory, provides superior accuracy and allows a better boundary-layer resolution than an unstructured grid. By having cells with a large aspect ratio around sharp leading and trailing edges a structured grid also provides a better resolution of these areas. Many companies have automatic meshing tools that automatically mesh blade sections with a structured mesh without much user intervention.<br />
<br />
Unstructured meshes are used for more complex and odd geometries where a structured mesh is difficult to create. Typical examples where unstructured meshes are often used are blade tip regions, areas involving leakage flows and secondary air systems, film cooling ducts etc.<br />
<br />
When meshing avoid to create large jumps in cell sizes. Typically the cell size should not change with more than a factor of 1.25 between neighbouring cells. For structured meshes also try to create fairly continous mesh lines and avoid discontinuities where the cell directions suddenly change. For multi-block structured meshes avoid placing the singular points where blocks meet in regions with strong flow gradients since most schemes have a lower accuracy in these singular points.<br />
<br />
=== Mesh size guidelines ===<br />
<br />
It is difficult to define, a priori, the mesh size. The required mesh size depends on the purpose of the simulation. <br />
<br />
If the main goal is to obtain static pressure forces a coarse mesh is often able to obtain a good solution, especially when an accurate resolution of the boundary layers is not required. For 2D inviscid simulations of one blade a mesh with say 3,000 cells is most often sufficient. For 3D inviscid blade simulations a mesh size of about 40,000 cells is usually sufficient. On inviscid Euler simulations the cells should be fairly equal in size and no boundary layer resolution should be present. Avoid having too skewed cells.<br />
<br />
For loss predictions and cases where boundary layer development and separation is important the mesh needs to have a boundary layer resolution. The boundary layer resolution can either be coarse and suitable for a [[Wall functions|wall function]] simulation or very fine and suitable for a [[Low-Re resolved boundary layers|low-Re]] simulation. For further information about selecting the near-wall turbulence model please see the [[#Turbulence modeling|turbulence modeling]] section. In 3D single-blade simulations a decent wall-function mesh typically has around 100,000 cells. This type of mesh size is suitable for quick design iterations where it is not essential to resolve all secondary flows and vortices. A good 3D wall-function mesh of a blade section intended to resolve secondary flows well should have at least 400,000 cells . A good low-Re mesh with resolved boundary layers typically has around 1,000,000 cells. <br />
<br />
In 2D blade simulations a good wall-function mesh has around 20,000 cells and a good low-Re mesh with resolved boundary layers has around 50,000 cells.<br />
<br />
Along the suction and pressure surfaces it is a good use about 100 cells in the streamwise direction. In the radial direction a good first approach is to use something like 30 cells for a wall-function mesh and 100 cells for a low-Re mesh.<br />
<br />
It is important to resolve leading and trailing edges well. Typically at least 10 cells, preferably 20 should be used around the leading and trailing edges. For very blunt and large leading edges, like those commonly found on HP turbine blades, 30 or more cells can be necessary.<br />
<br />
Cases which are difficult to converge with a steady simulation and which show tendencies of periodic vortex shedding from the trailing edge, can sometimes be "tamed" by using a coarse mesh around the trailing edge. This, of course, reduces the accuracy but can be a trick to obtain a converged solution if time and computer resources does not allow a transient simulation to be performed.<br />
<br />
=== Boundary layer mesh ===<br />
<br />
For design iteration type of simulations where a [[Wall functions|wall function]] approach is sufficient [[Dimensionless wall distance (y plus) | y+]] for the first cell should be somewhere between 20 and 200. The outer limit is dependent on the actual Re number of the simulations. For cases with fairly low Re numbers make sure to keep the maximum y+ as low as possible. For more accurate simulations with resolved boundary layers the mesh should have a y+ for the first cell which is below 1. Some new codes are now using a hybrid wall treatment that allows a smooth transition from a coarse wall-function mesh to a resolved low-Re mesh. Use some extra care when using this type of hybrid technique since it is still fairly new and unproven.<br />
<br />
Outside of the first cell at a wall a good rule of thumb is to use a growth ratio normal to the wall in the boundary layer of maximum 1.25. For a low-Re mesh this usually gives around 40 cells in the boundary layer whereas a wall-function mesh does not require more than 10 cells in the boundary layer.<br />
<br />
If you are uncertain of which wall distance to mesh with you can use a [http://www.cfd-online.com/Links/tools.html#yplus y+ estimation tool] to estitmate the distance needed to obtain the desired y+. These estimation tools are ''very handy'' if you have not done any previous similar simulations. <br />
<br />
As a rule of thumb a wall-function mesh typically requires areound 5 to 10 cells in the boundary layer whereas a resolved low-Re mesh requires about 40 cells in the boundary layer.<br />
<br />
== Boundary conditions ==<br />
<br />
Describe different types of boundary conditions and when they should be used:<br />
<br />
* Total pressure in, static pressure out<br />
* Absorbing boundary conditions<br />
* ...<br />
<br />
There are different types of boundary conditions you can use:<br />
*Mass flow inlet, static pressure outlet.<br />
To put this BC you must allocate inlet surface enough far away from the turbomachine impeller. The velocity distribution is not<br />
constant over all the surface. If you put this "lie" away from your problem it works well.<br />
<br />
<br />
=== Turbulence inlet conditions ===<br />
<br />
Prescribing realistic turbulence inlet conditions is important and usually difficult. For two-equation turbulence models two different turbulence values need to be specified on the inlet. The most common way of specifying the inlet turbulence variables is to give an inlet [[Turbulence intensity|turbulence level]] and [[Turbulence length scale|length-scale]]. For simulations where the incoming boundary layers are estimated to not have any significant effect on the secondary flows and global flow-field downstream it is usually sufficient to specify a constant incoming turbulence level and length-scale.<br />
<br />
The incoming [[Turbulence intensity|turbulence level]] is dependent on which component is analyzed. Best is of course to have measurments from a similar application in order to be able to prescribe a fairly realistic value. Without measurements it is necessary to make an educated guess. Simulations with very complex and turbulence-generating components upstream will have a very high incoming turbulence level. For example, a high-pressure turbine just downstream of a turbulence generating combustor might have incoming turbulence levels up to 20%. Fans and low-pressure compressors with not many components upstream might have as low incoming turbulence level as 1%. For components between these two extreme examples, like high-pressure compressors, low-pressure turbines etc. a turbulence level of around 5% might be realistic. If you do not have any measurements and are unsure about which incoming turbulence level to prescribe it is always a good idea to run a few different simulations with say one half and one double incoming turbulence level in order to estimate how important it is for the simulation results.<br />
<br />
The incoming [[Turbulence length scale|turbulence length-scale]] is often even more difficult to guess than the incoming turbulence level. Measurements might sometimes include the incoming turbulence level, but very seldom also include the incoming turbulent length-scale. The best way of guessing a realistic incoming length-scale is to use the geometrical properties of the upstream components. The incoming turbulence length-scale can be estimated as say the thickness of upstream blades or somewhere between 2% and 20% of the incoming channel heigth. Fortunately the incoming turbulence length-scale is usually not that important for the end results. However, some k-omega models can have an unrelisticly strong influence on the incoming turbulence length-scale. Hence, be extra carefull about the length-scale when using k-omega models. Note that the [[SST k-omega model]] does not have this unrealistic sensitivity to the inlet turbulence length-scale.<br />
<br />
Instead of specifying an incoming turbulence length-scale it is sometimes more convenient to specify an incoming [[Eddy viscosity ratio|eddy viscosity ratio]]. For low-turbulence cases with no well-specified turbulence generating components upstream it can be difficult to estimate a turbulence length-scale. Specifying an eddy viscosity ratio instead gives a more direct control over how large the effect of the incoming turbulence is. The eddy viscosity ratio describes how large the turbulence viscosity is related to the molecular viscosity. In turbomachinery the eddy viscosity ratio can vary from say 10 in low-turbulence components like fans up to say 1,000 or in rare cases even 10,000 in high-turbulence components like high-pressure turbines. In components between these extremes a typical eddy viscosity ration might be about 200. Even if specifying an inlet turbulence length scale it can still be good to compute what eddy viscosity ratio this corresponds to in order to estimate if it sounds reasonable.<br />
<br />
== Turbulence modeling ==<br />
<br />
Selecting a suitable turbulence model for turbomachinery simulations can be a challenging task. There is no single model which is suitable for all types of simulations. Which turbulence model CFD engineers use has as much to do with beliefs and traditions as with knowledge and facts. There are many different schools. However, below follows some advices that most CFD engineers in the turbomachinery field tend to agree upon.<br />
<br />
For attached flows close to the design point a simple algebraic model like the [[Baldwin-Lomax model]] can be used. Another common choice for design-iteration type of simulations is the one-equation model by [[Spalart-Allmaras model | Spalart-Allmaras]]. This model has become more popular in the last years due to the many inherent problems in more refined two-equation models. The big advantage with both the [[Baldwin-Lomax model]] and the [[Spalart-Allmaras model]] over more advanced models is that they are very robust to use and rarely produce completely unphysical results.<br />
<br />
In order to accurately predict more difficult cases, like separating flows, rotating flows, flows strongly affected by secondary flows etc. it is often necessary to use a more refined turbulence model. Common choices are two-equation models like the <math>k-\epsilon</math> model.<br />
<br />
Two-equation models are based on the [[Boussinesq eddy viscosity assumption]] and this often leads to an over-production of turbulent energy in regions with strong acceleration or deceleration, like in the leading edge region, regions around shocks and in the suction peak on the suction side of a blade. To reduce this problems it is common to use a special model variant using, for example, [[Durbin's realizability constraint]] or the [[Kato-Launder modification]]. Note that different two-equation models behave differently in these problematic stagnation and acceleration regions. Worst is probably the standard <math>k-\epsilon</math> model. <math>k-\omega</math> model are slightly better but still do not behave well. More modern variants like Menter's [[SST k-omega model]] also has problems, wheras the [[V2-f models|v2f model ]] by Durbin behaves better.<br />
<br />
=== Near-wall treatment ===<br />
<br />
For on-design simulations without any large separated regions it is often sufficient to use a [[wall-function model]] close to the wall, preferably with some form of non-equilibrium wall-function that is sensitised to streamwise pressure gradients.<br />
<br />
For off-design simulation, or simulations involving complex secondary flows and separations, it is often necessary to use a [[low-Re model]]. There exist many low-Re models that have been used with success in turbomachinery simulations. A robust and often good choice is to use a one-equation model, like for example the [[Wolfstein model]], in the inner parts of the boundary layer. There are also several Low-Re <math>k-\epsilon</math> models that work well. Just make sure they don't suffer from the problem with overproduction of turbulent energy in regions with strong acceleration or deceleration. In the last few years Menter's low-Re <math>SST k-\omega</math> model has gained increased popularity.<br />
<br />
=== Transition prediction ===<br />
<br />
Transition refers to the process when a laminar boundary layer becomes unstable and transitions to a turbulent boundary layer. There are two types of transition - natural transition, where inherent instabilities in the boundary layer cause the transition and by-pass transition, where convection and diffusion of turbulence from the free-stream into the boundary layer cause the transition. Most transitions in turbomachinery are by-pass transitions caused by free-stream turbulence and other external disturbances like wakes, vortices and surface defects.<br />
<br />
Simulating transition in a CFD code accurately is very difficult. Often a separate transition model needs to be solved in order to specify the transition location and length. Predicting natural transition in a pure CFD code is not possible. Predicting by-pass transition in a pure CFD code is almost impossible, although there are people who claim to be able to predict by-pass transition with low-Re two-equation models. However, this is usually on special test cases and with simulations that have been tuned for these special cases, see for example [Saville 2002]. In reality transition is a very complex and sensitive process where disturbances like incoming wakes and vortices from previous stages, surface roughness effects and small steps or gaps in the surfaces play a significant role. <br />
<br />
The turbomachinery codes that have transition prediction models often use old ad-hoc models like the Abu-Ghannam and Shaw model [Abu-Ghannam 1980] or the Mayle model [Mayle 1991]. These models can be quite reliable if they have been validated and tuned for a similar application. Do not trust your transition predictions without having some form of experimental validation. Menter has also recently developed a new form of transition model that might work fairly well, but it is still too new and untested.<br />
<br />
For some turbomachinery applications, like modern high-lift low-pressure turbines, transition is critical. For these applications a CFD code with a transition model that has been tuned for this type of applications should be used.<br />
<br />
== Numerical considerations ==<br />
<br />
Use at least a second order accurate scheme for the flow variables. Some codes require a first order scheme for the turbulent variables (<math>k</math> and <math>\epsilon</math>) in order to converge well. It might be sufficient with a first order scheme only on the turbulence variables, but a second order scheme is of course preferable.<br />
<br />
=== Convergence criteria ===<br />
<br />
To know when a solution is converged is not always that easy. You need some prior experience of your CFD code and your application to judge when a simulation is converged. For normal pure aero simulations without resolved walls, i.e. with wall functions or inviscid Euler simulations, convergence can most often be estimated just by looking at the residuals. Exacty what the residuals should be is not possible to say, it all depends on how your particular code computes and scales the residuals. Hence, make sure to read the manuals and plot the convergence of a few global parameters before you decide what the residuals should be for a solution to converege. Note also that many manuals for genereal purpose CFD codes list overly agressive convergence critera that often produce unconverged results. <br />
For simulations with resolved walls it is good to look at the convergence of some global properties, like total pressure losses from the inlet to the outlet. For heat transfer simulations it is even more tricky since the aerodynamic field can look almost converged although the thermal field is not converged at all. If doing heat transfer simulations make sure to plot the heat-transfer, run for some time, and plot it again to make sure that it doesn't change anymore. With very well resolved walls and heat transfer it can sometimes take 10 times longer for the thermal field to converge.<br />
<br />
=== Single or double precision ===<br />
<br />
With todays computers and cheap memory prices it often does not cost much extra to run in double precision. Before using single precision you should first investigate how your software and hardware works with double precision. If the extra time and memory needed for double precision is negligible you should of course always run in double precision. With double precision you never have to worry about round-off errors. Always using double precision is one way of avoiding one type of pit-falls in the complex world of CFD simulations. Use double precision when you have resolved boundary layers (Y+ around 1) and when you use advanced physical models like combustion, free-surface simulations, spray and transient simulations with quick mesh motions.<br />
<br />
== Multi-stage analysis ==<br />
<br />
Multi-stage analysis can be done in different ways:<br />
<br />
* Steady mixing-plane simulations<br />
* Frozen rotor simulations<br />
* Unsteady sliding-mesh stator-rotor simulations<br />
* Hybrid steady-unsteady stator-rotor simulations<br />
* Other '''advanced''' multi-stage methods<br />
<br />
=== Steady mixing-plane simulations ===<br />
<br />
Since the mixing-plane method was first introduced in 1979 [Denton & Singh 1979] is has become the industry standard type of rotor-stator simulations. A mixing-plane simulation is steady and only requires one rotor blade and one stator blade per stage. Between the rotating blade passage and the steady vane passage the flow properties are circumferentially averaged in a so-called mixing-plane interface. This will of course remove all transient rotor-stator interactions, but it still gives fairly representative results. In some commercial codes (CFX for example) mixing-plane interfaces are also called stage-interfaces.<br />
<br />
=== Frozen rotor simulations ===<br />
<br />
In a frozen rotor simulation the rotating and the stationary parts have a fixed relative position. A frame transformation is done to include the rotating effect on the rotating sections. This will give a steady flow and no transient effects are included. With a frozen-rotor simulation rotating wakes, secondary flows, leading edge pressure increases etc. will always stay in exactly the same positions. This makes a frozen rotor simulation very dependent on exactly how the rotors and the stators are positioned. Most often a mixing-plane simulation gives better results. Frozen rotor simulations are mainly performed to obtain a good starting flow-field before doing a transient sliding-mesh simulation.<br />
<br />
=== Unsteady sliding-mesh stator-rotor simulations ===<br />
<br />
This is the most complete type of stator-rotor simulation. In most engines the number of stators and rotors do not have a common denominator (to avoid instabilities caused by resonance between different rings). Hence, to make a full unsteady sliding-mesh computation it is necessary to have a mesh which includes the full wheel with all stators vanes and all rotor blades. This is often not possible, instead it is necessary to reduce the number of vanes and blades by finding a denominator that is '''almost''' common and then scale the geometry slightly circumferentially. Here is an example:<br />
<br />
*Real engine: 36 stator vanes, 41 rotor blades<br />
*Approximated engine: 41 stator vanes, 41 rotor blades, making it possible to simulate only 1 stator vane and 1 rotor blade<br />
*Scaling of stator: All stator vanes are scaled by 36/41 = 0.8780 circumferentially.<br />
<br />
<br />
=== Hybrid steady-unsteady stator-rotor simulations ===<br />
<br />
Hybrid steady-unsteady methods have been proposed in literature (Montomoli et al. 2009) in order to have an unsteady simulation embedded in a multistage steady study. <br />
There are several advantages related to this method: mainly grid size and number of iterations.<br />
<br />
=== Other '''advanced''' multi-stage methods ===<br />
<br />
Time-inclinded, Adamszyk stresses ...<br />
<br />
== Heat transfer predictions ==<br />
<br />
Besides listing the general heat transfer mechanisms involved <br />
(namely conduction, convection, radiation)<br />
heat transfer prediction in CFD may be seen as or split into two cases. <br />
<br />
'''Mesh consists of fluid domain(s)''': <br />
you want to know how heat inserted into the fluid domain (e.g. via the flowing medium) changes the temperature field along the flow path. Be it a steady or transient run, a fluid which enters with a given temperature will usually experience temperature variations, for instance, caused by convective boundary conditions, prescribed temperature profiles at flow obstacles etc. <br />
<br />
'''Mesh consists of fluid and solid domain(s)''': <br />
additionally to the above, you want info too wrt the (spatial, temporal or even spectral) temperature field distribution in surrounding, confining or immersed solids like channel walls or heat exchanger tubes. This is also called conjugate heattransfer CHT in the CFD context. CHT requires a good boundary layer resolution, usually the wall mesh needs to be rather refined, to obtain realistic heatflux results at the fluid/solid interface. Flow and heat transfer convergence require different time step settings, to properly capture changes in flow and heat quantities respectively. <br />
<br />
<br />
In either case, verify (strict necessity depends on CFD code used, CFX for instance checks and assists in regard) that model dimensions, boundary conditions and properties are in consistent units, hold appropriate values. Check temperature-dependence of properties and other numbers before the run.<br />
<br />
In heat transfer predictions (depending on the CFD code in use) <br />
besides the flow solver, you may have to activate the thermal solver too, <br />
as a job specification.<br />
<br />
== Acoustics and noise ==<br />
<br />
A whole separate research subject, difficult. <br />
<br />
Tone noise possible. Often run with linearzised solvers in the frequency domain.<br />
<br />
Jet noise possible. Often run with LES or DES simulations that either also resolve the sound waves or couples to a separate acoustic solver.<br />
<br />
Turbomachinery broadband noise not possible yet, or at least a great challenge.<br />
<br />
== Errors and uncertainties ==<br />
<br />
CFD is still a tool which requires that a user has a good understanding of uncertainties and errors that might spoil a CFD similation. There exists no error control in CFD and any CFD simulation must be interpreted by an expirenced user to have some credibility. Without some knowledge about possible errors and how they can be handled a CFD simulation can not be trusted. Errors can occur at different places:<br />
<br />
* Definition of the problem - What needs to be analyzed?<br />
* Selection of the solution strategy - What physical models and what numerical tools should be used?<br />
* Development of the computational model - How should the geometry and the numerical tools be set up?<br />
* Analysis and interpretation of the results - How should the model be analyzed and the results be interpreted?<br />
<br />
There exists many different definitions on errors. In this guide the errors are classified into four types of errors: problem definition errors, model errors, numerical errors and user and code errors. The chapters below describe these errors and give some guidelines on how to avoid them.<br />
<br />
=== Problem definition errors ===<br />
<br />
Problem definition errors are the most basic form of errors. In order to obtain usefull results a CFD simulation must of course analyze the correct problem, have suitable boundary contions and be based on a relevant geometry.<br />
<br />
==== Wrong type of simulation ====<br />
<br />
It is essential to have an overview of the physics involved and how the problem can best be analyzed. Running a 2D simulation in order to understand secondary flows or running a steady simulation in order to understand transient behaviour is of course no use. When assessing a CFD simulation the first thing to consider is what physical phenomena are important for the results and if the selected type of simulation is suitable to resolve this type of phenomena. For further information about selecting the most suitable type of simulation please see the previous chapter on [[#Deciding what type of simulation to do|deciding what type of simulation to perform]].<br />
<br />
==== Incorrect or uncertain boundary conditions ====<br />
<br />
A common source of errors is that incorrect boundary conditions are used. The boundary conditions must be specified in enough detail in order to resolve all the important physical features in the problem. For further information about specifying boundary conditions please see the previous chapter on [[#Boundary conditions|boundary conditions]].<br />
<br />
==== Geometrical errors ====<br />
<br />
It is almost always necessary to simplify the geometry in some form. When assessing a CFD simulation one should consider how the geometrical simplifications can affect the interesting physical phenomena. Typical geometrical errors are:<br />
<br />
*Simplifications<br />
:Small geometrical features like fillets, small steps or gaps etc. can often be disregarded. When disregarding this type of features one should consider if they might affect the important physics. For example, a very large fillet on the suction-side of a vane might affect corner separations near the end-walls. A large tip-leakage might affect the flow physics significantly in the upper part of a compressor.<br />
*Tolerances and manufacturing discrepancies<br />
:If the geometry has very large tolerances or is manufactured in a way which might produce a non-ideal shape or position it might be necessary to perform additional CFD simulations in order to cover the whole span of possible real geometries.<br />
*Surface conditions - roughness, welds, steps, gaps etc.<br />
:Often CFD simulations assume a perfectly smooth surface. A non-smooth surface which might have welds, steps or even gaps will of course produce different results. If the physical phenomena of interest might depend on the surface conditions these should of course be condidered. Typical phenomena that might be dependent on this type of errors are transition prediction, leakage flows etc.<br />
<br />
=== Model errors ===<br />
<br />
Errors related to the computational model.<br />
<br />
==== Wrong physical models ====<br />
<br />
Once the type of simulation has been selected the next step is to select what type of physical models the simulation should use. The following points should be considered:<br />
<br />
* Gas data (incompressible/compressible, perfect gas/real gas, ...)<br />
* Turbulence modeling (type of model, type of near-wall treatment, ...)<br />
* Other models (combustion, sprays, ...)<br />
<br />
When assessing model related errors it is important to know the features of the selected model and think carefully how these features and possible short comings might affect the predicted physical behaviour. Using the wrong turbulence model or combustion model can completely destroy the results of a CFD simulation.<br />
<br />
=== Numerical errors ===<br />
<br />
Errors related to the numerical solution of the developed model. Typical examples of numerical errors are discretization errors, convergence errors and round-off errors.<br />
<br />
==== Discretization errors ====<br />
<br />
Discretization errors can either be spatial errors in space or temporal errors in time.<br />
<br />
Spatial discretization errors are what people normally call discretization errors. These errors are due to the difference between the exact solution and the numerical representation of the solution in space. Describing exactly what discretization different codes use and what errors this might lead to is not possible here. Instead some general rules to avoid these errors can be summarized as:<br />
* Use at least a 2nd order accurate scheme, preferably a 3rd order accurate scheme. Some general purpose codes have a 1st order upwind scheme as default, this is a very diffusives schemes that often gives too smooth results.<br />
* For new applications always run a simulation with a finer mesh to see how grid independent your solution is.<br />
* Be aware of checker-board errors. Checker-board errors occur close to strong shocks and other large discontinuities and can be seen as a wavy pattern with a wavelength of two cells. Some schemes, especially those who behave like central differencing schemes, are more prone to checker-board errors. Upwind schemes are a bit better and schemes like TVD or chock-capturing schemes are even better.<br />
<br />
Temporal discretization errors mainly effect transient simulations. However, some codes use a time-marching method also for steady simulations and then a temporal discretization error might affect the final steady solution slightly. The discretization in time can be done with 1st or 2nd order schemes or a Runge-Kutta method, which is more accurate and saves memory. Some codes can adapt the time-step, but often it is necessary to prescribe a time-step in advance. Think of the time-step as your grid in time and make sure that the grid-resolution in time is fine enough to resolve the highest frequencies. To avoid problems with temporal discretization errors the following should be considered:<br />
* Use at least a 2nd order scheme in time.<br />
* Do a physical estimation of the typical frequencies in time of the phenomena that you are interested in and select a time-step which is fine enough to resolve these frequencies well. After the simulation also look at the frequencies captured and make sure that they are well resolved by the chosen time-step.<br />
* For new applications try a finer time-step to ensure that your solution in time is fairly grid independent in time.<br />
<br />
==== Convergence errors ====<br />
<br />
To judge when a CFD simulation is converged is not always that easy. Different codes and different applications behave very differently. For a pure aero-simulation on a fairly coarse grid convergence is easy to judge, but for more complex simulations involving resolved boundary layers, heat transfer, combustion etc. convergence can be very tricky. Aside from looking at residuals one should always also look at how global parameters like static pressure distributions, total pressure losses, skin friction, heat transfer etc. change in time.<br />
For more information about how to avoid convergence errors see the previous chapter about [[#Convergence criteria]].<br />
<br />
==== Round-off errors ====<br />
<br />
When using single precision care needs to be taken to avoid round-off errors. Inviscid Euler simulations and simulations using wall-function meshes can most often be performed in single precision. For well resolved boundary layers with Y plus close to 1 it is often necessary to use double precision. If using double precision for very fine mesh resolutions make sure that you also create the mesh in double precision and not just run the solver in double precision. Sometimes a single precision solver converges slower than a double precision solver due to numerical errors caused by round-off errors. When using advanced physical models like combustion, free-surface simulations, spray and transient simulations with quick mesh motions it is also often necessary to use double precision.<br />
<br />
=== User and code errors ===<br />
<br />
Errors related to bugs in the code used or mistakes made by the CFD engineer.<br />
<br />
=== What to trust and what not to trust ===<br />
<br />
CFD is generally quite good at predicting surface static pressure distributions. With care CFD can also be used to predict performance, total-pressure losses and blade turning. <br />
<br />
Predicting separation, stall and off-design performance can be a challenge and results with non-attached flows should be interpreted with care. <br />
<br />
Heat transfer is often very difficult to predict accurately and it is common to obtain heat-transfer coefficients that are 100% wrong or more. Validation data is critical in order to be able to trust heat transfer simulations.<br />
<br />
Transition is almost impossible to predict accurately in general. However, there exist models that have been tuned to predict transition and these tend to give acceptable results for cases close to the ones they were tuned for.<br />
<br />
== References ==<br />
<br />
* {{reference-paper|author=Abu-Ghannam, B.J. and Shaw, R.|year=1980|title=Natural Transition of Boundary Layers - the Effects of Turbulence, Pressure Gradient, and Flow History|rest=Journal of Mech. Eng. Science, vol. 22, no. 5, pp. 213–228}}<br />
<br />
* {{reference-paper|author=Adamczyk, J. J.|year=1985|title=Model Equation for Simulating Flows in Multistage Turbomachinery|rest=ASME Paper 85-GT-226, also NASA TM-86869}}<br />
<br />
* {{reference-paper|author=Adamczyk, J. J.|year=1999|title=Aerodynamic Analysis of Multistage Turbomachinery Flows in Support of Aerodynamic Design|rest=ASME Paper 99-GT-80.}}<br />
<br />
* {{reference-paper|author=Baldwin, B. S. and Lomax, H.|year=1978|title=Thin Layer Approximation and Algebraic Model for Separated Turbulent Flows|rest=AIAA Paper 78-257}}<br />
<br />
* {{reference-paper|author=Chen, J. P. and Barter, J. W.|year=1998|title=Comparison of Time-Accurate Calculations for the Unsteady Interaction in Turbomachinery Stage|rest=AIAA Paper 98-3292}}<br />
<br />
* {{reference-paper|author=Denton, J. and Singh, U.|year=1979|title=Time Marching Methods for Turbomachinery Flow Calculations|rest=VKI Lecture Series 1979-7, von Karman Institute}}<br />
<br />
* {{reference-paper|author=Erdos, J., Alzner, E. and McNally, W.|year=1977|title=Numerical Solution of Periodic Transonic Flow Through a Transonic Fan Stage|rest=AIAA Journal, vol. 15, no. 11, pp. 1559-1568}}<br />
<br />
* {{reference-paper|author=Gerolymos, G., Vinteler, D., Haugeard, R., Tsange, G. and Vallet, I.|year=1996|title=On the Computation of Unsteady Turbomachinery Flows – Part II – Rotor/Stator Interaction using Euler Equations|rest=AGARD Report CP-571}}<br />
<br />
* {{reference-paper|author=Giles, M. B.|year=1990|title=Stator/Rotor Interaction in a Transonic Turbine|rest=AIAA Journal of Propulsion and Power, vol. 6, no. 5}}<br />
<br />
* {{reference-paper|author=He, L, and Ning, W.|year=1998|title=Efficient Approach for Analysis of Unsteady Viscous Flows in Turbomachines|rest=AIAA Journal, vol. 36, no. 11, pp. 2005-2012}}<br />
<br />
* {{reference-paper|author=Mayle, R. E.|year=1991|title=The Role of Laminar-Turbulent Transition in Gas Turbine Engines|rest=ASME Journal of Turbomachinery, vol. 113, pp. 509-537}}<br />
<br />
* {{reference-paper|author=Menter, F.R. |year=1994|title=Two-equation eddy-viscosity turbulence models for engineering applications|rest=AIAA Journal, vol. 32, pp. 269-289}}<br />
<br />
* {{reference-paper|author= Montomoli, F., Hodson,H.P, Lapworth, L. |year=2009|title=RANS-URANS in axial compressors, a design methodology|rest=IMECHE Seminar: Grand review in the state-of-the-art in the numerical simulation of fluid flow 2}}<br />
<br />
* {{reference-paper|author=Savill, M., Dick, E., Hanjalić, K. and Voke, P.|year=2002|title=Synthesis Report of the ERCOFTAC Transition Modeling – TRANSPRETURB Thematic Network Activities 1998-2002|rest=Ecoftac Bulletin 54, September 2002, pp. 5-16}}<br />
<br />
* {{reference-paper|author=Wang, X. and Chen J.|year=2004|title=A Post-Processor to Render Turbomachinery Flows Using Phase-Lag Simulations|rest=AIAA Paper 04-615}}<br />
<br />
== External links ==<br />
<br />
* [http://www.qnet-cfd.net/newsletter/8th/n8_40-46.pdf QNET-CFD Best Practise Advice for Turbomachinery Internal Flows]<br />
* [http://www.qnet-cfd.net/newsletter/7th/n7_05.pdf State of the art in Industrial CFD for Turbomachinery Flows, QNET-CFD Network Newsletter, Volume 2, No. 3 – December 2003]<br />
* [https://pronet.wsatkins.co.uk/marnet/guidelines/guide.html MARNET-CFD Best Practice Guidelines for Marine Applications of CFD]<br />
* [http://www.stanford.edu/group/ctr/ResBriefs/temp05/weide.pdf On Large Scale Turbomachinery Computations, by E. van der Weide et. al., Center for Turbulence Research, Annual Research Briefs 2005]</div>Frmontohttps://www.cfd-online.com/Wiki/Best_practice_guidelines_for_turbomachinery_CFDBest practice guidelines for turbomachinery CFD2011-03-22T22:47:38Z<p>Frmonto: /* Multi-stage analysis */</p>
<hr />
<div>This article contains a summary of the most important knowledge and experience a CFD engineer needs in order to perform CFD simulations of turbomachinery components. The guide is mainly aimed at axial turbomachinery. The goal is to give a CFD engineer, who has just started working with turbomachinery simulations, a head start and avoid some of the most difficult pit-falls. Experienced turbomachinery CFD engineers can also use the guidelines in order to learn what other experts consider best practice. The intended audience is expected to know basic CFD terminology and have a basic turbomachinery knowledge, but no detailed knowledge about CFD for turbomachinery is needed. <br />
<br />
== Deciding what type of simulation to do ==<br />
<br />
Before starting a new turbomachinery simulation it is wise to think carefully of what it is that should be predicted and what physical phenomena that affect the results. This chapter contains a brief overview of the various types of simulations and some hints of what can be predicted with them.<br />
<br />
=== 2D, Quasi-3D or 3D ===<br />
<br />
2D simulations are often used in the early design phase in order to obtain a typical 2D section of a blade. For cases with many long blades or vanes, like low-pressure turbines, a 2D simulation can also provide reasonable results. If the area of the flow-path changes significantly in the axial direction it might be necessary to instead make a quasi-3D simulation. A quasi-3D simulation is a 2D simulation in which extra source terms are used to account for the acceleration/deceleration caused by a changing channel height or growing end-wall boundary layers. Codes focused on turbomachinery applications often have the possibility to perform quasi-3D simulations, but most general purpose CFD codes can not do this type of simulations, or require user coding to implement the correct source terms in the equations. Please contact your software distributor if your code does not have the quasi-3d possibility and you require it. Many codes require special routines or hidden commands to enable this feature.<br />
<br />
Full 3D simulations are necessary if a true 3D geometry is needed to obtain correct secondary flows and/or shock locations. For low-aspect-ratio cases with only a few short blades, like for example structurally loaded turbine outlet guide vanes, the secondary flow development is important and a 3D simulation is often necessary in order to obtain reasonable results. For applications where the end-wall boundary layers grow very quickly and interact with a large part of the flow-field it is necessary to perform a full 3D simulation. This is often the case in compressors and fans, where the negative pressure gradients make the boundary layers grow much quicker than what they do in for example turbines. For cases where the shock location is very critical, like in transonic compressors, it is also often necessary to perform a 3D simulation in order to obtain reasonable shock locations.<br />
<br />
=== Inviscid or viscid ===<br />
<br />
For attached flows close to the design point and without any large separations it is often sufficient with an inviscid Euler simulation in order to obtain reasonable blade loadings and pressure distributions. Note that inviscid Euler simulations should only be used if the boundary layers are judged to not have a significant effect on the global flow-field. A viscid Navier-Stokes simulation is necessary in order to predict losses, secondary flows and separations. As soon as separations are of interest it is of course also necessary to do a viscid simulation. Note that with todays computers it is often not time and resources that make users run inviscid Euler simulations. Running viscid Navier-Stokes simulations is now so quick that it is not a time problem any more. Euler simulations are still interesting though, since with an inviscid Euler simulation you don't have to worry about wall resolutions, y+ values, turbulence modeling errors etc.<br />
<br />
=== Transient or Stationary ===<br />
<br />
Most turbomachinery simulations are performed as stationary simulations. Transient simulations are done when some kind of transient flow behaviour has a strong influence on the global flow field. Examples of transient simulations are detailed simulations of rotor-stator interaction effects, simulations of large unsteady separations etc. Sometimes when you perform a steady stationary simulation you can see tendencies of unsteady behaviour like for example periodic vortex shedding behind blunt trailing edges. This is often first seen as periodical variations of the residuals. If the unsteady tendencies are judged to not affect the overall simulation results it might be necessary to coarsen the mesh close to the vortex shedding or run a different turbulence model in order to make the simulation converge. Sometimes you are still forced to run a transient simulation and average the results if you don't obtain a converged steady solution.<br />
<br />
== Meshing ==<br />
<br />
In turbomachinery applications structured multi-block hexahedral meshes are most often used for flow-path simulations. In most solvers a structured grid requires less memory, provides superior accuracy and allows a better boundary-layer resolution than an unstructured grid. By having cells with a large aspect ratio around sharp leading and trailing edges a structured grid also provides a better resolution of these areas. Many companies have automatic meshing tools that automatically mesh blade sections with a structured mesh without much user intervention.<br />
<br />
Unstructured meshes are used for more complex and odd geometries where a structured mesh is difficult to create. Typical examples where unstructured meshes are often used are blade tip regions, areas involving leakage flows and secondary air systems, film cooling ducts etc.<br />
<br />
When meshing avoid to create large jumps in cell sizes. Typically the cell size should not change with more than a factor of 1.25 between neighbouring cells. For structured meshes also try to create fairly continous mesh lines and avoid discontinuities where the cell directions suddenly change. For multi-block structured meshes avoid placing the singular points where blocks meet in regions with strong flow gradients since most schemes have a lower accuracy in these singular points.<br />
<br />
=== Mesh size guidelines ===<br />
<br />
It is difficult to define, a priori, the mesh size. The required mesh size depends on the purpose of the simulation. <br />
<br />
If the main goal is to obtain static pressure forces a coarse mesh is often able to obtain a good solution, especially when an accurate resolution of the boundary layers is not required. For 2D inviscid simulations of one blade a mesh with say 3,000 cells is most often sufficient. For 3D inviscid blade simulations a mesh size of about 40,000 cells is usually sufficient. On inviscid Euler simulations the cells should be fairly equal in size and no boundary layer resolution should be present. Avoid having too skewed cells.<br />
<br />
For loss predictions and cases where boundary layer development and separation is important the mesh needs to have a boundary layer resolution. The boundary layer resolution can either be coarse and suitable for a [[Wall functions|wall function]] simulation or very fine and suitable for a [[Low-Re resolved boundary layers|low-Re]] simulation. For further information about selecting the near-wall turbulence model please see the [[#Turbulence modeling|turbulence modeling]] section. In 3D single-blade simulations a decent wall-function mesh typically has around 100,000 cells. This type of mesh size is suitable for quick design iterations where it is not essential to resolve all secondary flows and vortices. A good 3D wall-function mesh of a blade section intended to resolve secondary flows well should have at least 400,000 cells . A good low-Re mesh with resolved boundary layers typically has around 1,000,000 cells. <br />
<br />
In 2D blade simulations a good wall-function mesh has around 20,000 cells and a good low-Re mesh with resolved boundary layers has around 50,000 cells.<br />
<br />
Along the suction and pressure surfaces it is a good use about 100 cells in the streamwise direction. In the radial direction a good first approach is to use something like 30 cells for a wall-function mesh and 100 cells for a low-Re mesh.<br />
<br />
It is important to resolve leading and trailing edges well. Typically at least 10 cells, preferably 20 should be used around the leading and trailing edges. For very blunt and large leading edges, like those commonly found on HP turbine blades, 30 or more cells can be necessary.<br />
<br />
Cases which are difficult to converge with a steady simulation and which show tendencies of periodic vortex shedding from the trailing edge, can sometimes be "tamed" by using a coarse mesh around the trailing edge. This, of course, reduces the accuracy but can be a trick to obtain a converged solution if time and computer resources does not allow a transient simulation to be performed.<br />
<br />
=== Boundary layer mesh ===<br />
<br />
For design iteration type of simulations where a [[Wall functions|wall function]] approach is sufficient [[Dimensionless wall distance (y plus) | y+]] for the first cell should be somewhere between 20 and 200. The outer limit is dependent on the actual Re number of the simulations. For cases with fairly low Re numbers make sure to keep the maximum y+ as low as possible. For more accurate simulations with resolved boundary layers the mesh should have a y+ for the first cell which is below 1. Some new codes are now using a hybrid wall treatment that allows a smooth transition from a coarse wall-function mesh to a resolved low-Re mesh. Use some extra care when using this type of hybrid technique since it is still fairly new and unproven.<br />
<br />
Outside of the first cell at a wall a good rule of thumb is to use a growth ratio normal to the wall in the boundary layer of maximum 1.25. For a low-Re mesh this usually gives around 40 cells in the boundary layer whereas a wall-function mesh does not require more than 10 cells in the boundary layer.<br />
<br />
If you are uncertain of which wall distance to mesh with you can use a [http://www.cfd-online.com/Links/tools.html#yplus y+ estimation tool] to estitmate the distance needed to obtain the desired y+. These estimation tools are ''very handy'' if you have not done any previous similar simulations. <br />
<br />
As a rule of thumb a wall-function mesh typically requires areound 5 to 10 cells in the boundary layer whereas a resolved low-Re mesh requires about 40 cells in the boundary layer.<br />
<br />
== Boundary conditions ==<br />
<br />
Describe different types of boundary conditions and when they should be used:<br />
<br />
* Total pressure in, static pressure out<br />
* Absorbing boundary conditions<br />
* ...<br />
<br />
There are different types of boundary conditions you can use:<br />
*Mass flow inlet, static pressure outlet.<br />
To put this BC you must allocate inlet surface enough far away from the turbomachine impeller. The velocity distribution is not<br />
constant over all the surface. If you put this "lie" away from your problem it works well.<br />
<br />
<br />
=== Turbulence inlet conditions ===<br />
<br />
Prescribing realistic turbulence inlet conditions is important and usually difficult. For two-equation turbulence models two different turbulence values need to be specified on the inlet. The most common way of specifying the inlet turbulence variables is to give an inlet [[Turbulence intensity|turbulence level]] and [[Turbulence length scale|length-scale]]. For simulations where the incoming boundary layers are estimated to not have any significant effect on the secondary flows and global flow-field downstream it is usually sufficient to specify a constant incoming turbulence level and length-scale.<br />
<br />
The incoming [[Turbulence intensity|turbulence level]] is dependent on which component is analyzed. Best is of course to have measurments from a similar application in order to be able to prescribe a fairly realistic value. Without measurements it is necessary to make an educated guess. Simulations with very complex and turbulence-generating components upstream will have a very high incoming turbulence level. For example, a high-pressure turbine just downstream of a turbulence generating combustor might have incoming turbulence levels up to 20%. Fans and low-pressure compressors with not many components upstream might have as low incoming turbulence level as 1%. For components between these two extreme examples, like high-pressure compressors, low-pressure turbines etc. a turbulence level of around 5% might be realistic. If you do not have any measurements and are unsure about which incoming turbulence level to prescribe it is always a good idea to run a few different simulations with say one half and one double incoming turbulence level in order to estimate how important it is for the simulation results.<br />
<br />
The incoming [[Turbulence length scale|turbulence length-scale]] is often even more difficult to guess than the incoming turbulence level. Measurements might sometimes include the incoming turbulence level, but very seldom also include the incoming turbulent length-scale. The best way of guessing a realistic incoming length-scale is to use the geometrical properties of the upstream components. The incoming turbulence length-scale can be estimated as say the thickness of upstream blades or somewhere between 2% and 20% of the incoming channel heigth. Fortunately the incoming turbulence length-scale is usually not that important for the end results. However, some k-omega models can have an unrelisticly strong influence on the incoming turbulence length-scale. Hence, be extra carefull about the length-scale when using k-omega models. Note that the [[SST k-omega model]] does not have this unrealistic sensitivity to the inlet turbulence length-scale.<br />
<br />
Instead of specifying an incoming turbulence length-scale it is sometimes more convenient to specify an incoming [[Eddy viscosity ratio|eddy viscosity ratio]]. For low-turbulence cases with no well-specified turbulence generating components upstream it can be difficult to estimate a turbulence length-scale. Specifying an eddy viscosity ratio instead gives a more direct control over how large the effect of the incoming turbulence is. The eddy viscosity ratio describes how large the turbulence viscosity is related to the molecular viscosity. In turbomachinery the eddy viscosity ratio can vary from say 10 in low-turbulence components like fans up to say 1,000 or in rare cases even 10,000 in high-turbulence components like high-pressure turbines. In components between these extremes a typical eddy viscosity ration might be about 200. Even if specifying an inlet turbulence length scale it can still be good to compute what eddy viscosity ratio this corresponds to in order to estimate if it sounds reasonable.<br />
<br />
== Turbulence modeling ==<br />
<br />
Selecting a suitable turbulence model for turbomachinery simulations can be a challenging task. There is no single model which is suitable for all types of simulations. Which turbulence model CFD engineers use has as much to do with beliefs and traditions as with knowledge and facts. There are many different schools. However, below follows some advices that most CFD engineers in the turbomachinery field tend to agree upon.<br />
<br />
For attached flows close to the design point a simple algebraic model like the [[Baldwin-Lomax model]] can be used. Another common choice for design-iteration type of simulations is the one-equation model by [[Spalart-Allmaras model | Spalart-Allmaras]]. This model has become more popular in the last years due to the many inherent problems in more refined two-equation models. The big advantage with both the [[Baldwin-Lomax model]] and the [[Spalart-Allmaras model]] over more advanced models is that they are very robust to use and rarely produce completely unphysical results.<br />
<br />
In order to accurately predict more difficult cases, like separating flows, rotating flows, flows strongly affected by secondary flows etc. it is often necessary to use a more refined turbulence model. Common choices are two-equation models like the <math>k-\epsilon</math> model.<br />
<br />
Two-equation models are based on the [[Boussinesq eddy viscosity assumption]] and this often leads to an over-production of turbulent energy in regions with strong acceleration or deceleration, like in the leading edge region, regions around shocks and in the suction peak on the suction side of a blade. To reduce this problems it is common to use a special model variant using, for example, [[Durbin's realizability constraint]] or the [[Kato-Launder modification]]. Note that different two-equation models behave differently in these problematic stagnation and acceleration regions. Worst is probably the standard <math>k-\epsilon</math> model. <math>k-\omega</math> model are slightly better but still do not behave well. More modern variants like Menter's [[SST k-omega model]] also has problems, wheras the [[V2-f models|v2f model ]] by Durbin behaves better.<br />
<br />
=== Near-wall treatment ===<br />
<br />
For on-design simulations without any large separated regions it is often sufficient to use a [[wall-function model]] close to the wall, preferably with some form of non-equilibrium wall-function that is sensitised to streamwise pressure gradients.<br />
<br />
For off-design simulation, or simulations involving complex secondary flows and separations, it is often necessary to use a [[low-Re model]]. There exist many low-Re models that have been used with success in turbomachinery simulations. A robust and often good choice is to use a one-equation model, like for example the [[Wolfstein model]], in the inner parts of the boundary layer. There are also several Low-Re <math>k-\epsilon</math> models that work well. Just make sure they don't suffer from the problem with overproduction of turbulent energy in regions with strong acceleration or deceleration. In the last few years Menter's low-Re <math>SST k-\omega</math> model has gained increased popularity.<br />
<br />
=== Transition prediction ===<br />
<br />
Transition refers to the process when a laminar boundary layer becomes unstable and transitions to a turbulent boundary layer. There are two types of transition - natural transition, where inherent instabilities in the boundary layer cause the transition and by-pass transition, where convection and diffusion of turbulence from the free-stream into the boundary layer cause the transition. Most transitions in turbomachinery are by-pass transitions caused by free-stream turbulence and other external disturbances like wakes, vortices and surface defects.<br />
<br />
Simulating transition in a CFD code accurately is very difficult. Often a separate transition model needs to be solved in order to specify the transition location and length. Predicting natural transition in a pure CFD code is not possible. Predicting by-pass transition in a pure CFD code is almost impossible, although there are people who claim to be able to predict by-pass transition with low-Re two-equation models. However, this is usually on special test cases and with simulations that have been tuned for these special cases, see for example [Saville 2002]. In reality transition is a very complex and sensitive process where disturbances like incoming wakes and vortices from previous stages, surface roughness effects and small steps or gaps in the surfaces play a significant role. <br />
<br />
The turbomachinery codes that have transition prediction models often use old ad-hoc models like the Abu-Ghannam and Shaw model [Abu-Ghannam 1980] or the Mayle model [Mayle 1991]. These models can be quite reliable if they have been validated and tuned for a similar application. Do not trust your transition predictions without having some form of experimental validation. Menter has also recently developed a new form of transition model that might work fairly well, but it is still too new and untested.<br />
<br />
For some turbomachinery applications, like modern high-lift low-pressure turbines, transition is critical. For these applications a CFD code with a transition model that has been tuned for this type of applications should be used.<br />
<br />
== Numerical considerations ==<br />
<br />
Use at least a second order accurate scheme for the flow variables. Some codes require a first order scheme for the turbulent variables (<math>k</math> and <math>\epsilon</math>) in order to converge well. It might be sufficient with a first order scheme only on the turbulence variables, but a second order scheme is of course preferable.<br />
<br />
=== Convergence criteria ===<br />
<br />
To know when a solution is converged is not always that easy. You need some prior experience of your CFD code and your application to judge when a simulation is converged. For normal pure aero simulations without resolved walls, i.e. with wall functions or inviscid Euler simulations, convergence can most often be estimated just by looking at the residuals. Exacty what the residuals should be is not possible to say, it all depends on how your particular code computes and scales the residuals. Hence, make sure to read the manuals and plot the convergence of a few global parameters before you decide what the residuals should be for a solution to converege. Note also that many manuals for genereal purpose CFD codes list overly agressive convergence critera that often produce unconverged results. <br />
For simulations with resolved walls it is good to look at the convergence of some global properties, like total pressure losses from the inlet to the outlet. For heat transfer simulations it is even more tricky since the aerodynamic field can look almost converged although the thermal field is not converged at all. If doing heat transfer simulations make sure to plot the heat-transfer, run for some time, and plot it again to make sure that it doesn't change anymore. With very well resolved walls and heat transfer it can sometimes take 10 times longer for the thermal field to converge.<br />
<br />
=== Single or double precision ===<br />
<br />
With todays computers and cheap memory prices it often does not cost much extra to run in double precision. Before using single precision you should first investigate how your software and hardware works with double precision. If the extra time and memory needed for double precision is negligible you should of course always run in double precision. With double precision you never have to worry about round-off errors. Always using double precision is one way of avoiding one type of pit-falls in the complex world of CFD simulations. Use double precision when you have resolved boundary layers (Y+ around 1) and when you use advanced physical models like combustion, free-surface simulations, spray and transient simulations with quick mesh motions.<br />
<br />
== Multi-stage analysis ==<br />
<br />
Multi-stage analysis can be done in different ways:<br />
<br />
* Steady mixing-plane simulations<br />
* Frozen rotor simulations<br />
* Unsteady sliding-mesh stator-rotor simulations<br />
* Hybrid steady-unsteady stator-rotor simulations<br />
* Other '''advanced''' multi-stage methods<br />
<br />
=== Steady mixing-plane simulations ===<br />
<br />
Since the mixing-plane method was first introduced in 1979 [Denton & Singh 1979] is has become the industry standard type of rotor-stator simulations. A mixing-plane simulation is steady and only requires one rotor blade and one stator blade per stage. Between the rotating blade passage and the steady vane passage the flow properties are circumferentially averaged in a so-called mixing-plane interface. This will of course remove all transient rotor-stator interactions, but it still gives fairly representative results. In some commercial codes (CFX for example) mixing-plane interfaces are also called stage-interfaces.<br />
<br />
=== Frozen rotor simulations ===<br />
<br />
In a frozen rotor simulation the rotating and the stationary parts have a fixed relative position. A frame transformation is done to include the rotating effect on the rotating sections. This will give a steady flow and no transient effects are included. With a frozen-rotor simulation rotating wakes, secondary flows, leading edge pressure increases etc. will always stay in exactly the same positions. This makes a frozen rotor simulation very dependent on exactly how the rotors and the stators are positioned. Most often a mixing-plane simulation gives better results. Frozen rotor simulations are mainly performed to obtain a good starting flow-field before doing a transient sliding-mesh simulation.<br />
<br />
=== Unsteady sliding-mesh stator-rotor simulations ===<br />
<br />
This is the most complete type of stator-rotor simulation. In most engines the number of stators and rotors do not have a common denominator (to avoid instabilities caused by resonance between different rings). Hence, to make a full unsteady sliding-mesh computation it is necessary to have a mesh which includes the full wheel with all stators vanes and all rotor blades. This is often not possible, instead it is necessary to reduce the number of vanes and blades by finding a denominator that is '''almost''' common and then scale the geometry slightly circumferentially. Here is an example:<br />
<br />
*Real engine: 36 stator vanes, 41 rotor blades<br />
*Approximated engine: 41 stator vanes, 41 rotor blades, making it possible to simulate only 1 stator vane and 1 rotor blade<br />
*Scaling of stator: All stator vanes are scaled by 36/41 = 0.8780 circumferentially.<br />
<br />
<br />
=== Hybrid steady-unsteady stator-rotor simulations ===<br />
<br />
Hybrid steady-unsteady methods have been proposed in literature (Montomoli et al. 2009) in order to have an unsteady simulation embedded in a multistage steady study. <br />
There are several advantages related to this method: mainly grid size and number of iterations.<br />
<br />
=== Other '''advanced''' multi-stage methods ===<br />
<br />
Time-inclinded, Adamszyk stresses ...<br />
<br />
== Heat transfer predictions ==<br />
<br />
Besides listing the general heat transfer mechanisms involved <br />
(namely conduction, convection, radiation)<br />
heat transfer prediction in CFD may be seen as or split into two cases. <br />
<br />
'''Mesh consists of fluid domain(s)''': <br />
you want to know how heat inserted into the fluid domain (e.g. via the flowing medium) changes the temperature field along the flow path. Be it a steady or transient run, a fluid which enters with a given temperature will usually experience temperature variations, for instance, caused by convective boundary conditions, prescribed temperature profiles at flow obstacles etc. <br />
<br />
'''Mesh consists of fluid and solid domain(s)''': <br />
additionally to the above, you want info too wrt the (spatial, temporal or even spectral) temperature field distribution in surrounding, confining or immersed solids like channel walls or heat exchanger tubes. This is also called conjugate heattransfer CHT in the CFD context. CHT requires a good boundary layer resolution, usually the wall mesh needs to be rather refined, to obtain realistic heatflux results at the fluid/solid interface. Flow and heat transfer convergence require different time step settings, to properly capture changes in flow and heat quantities respectively. <br />
<br />
<br />
In either case, verify (strict necessity depends on CFD code used, CFX for instance checks and assists in regard) that model dimensions, boundary conditions and properties are in consistent units, hold appropriate values. Check temperature-dependence of properties and other numbers before the run.<br />
<br />
In heat transfer predictions (depending on the CFD code in use) <br />
besides the flow solver, you may have to activate the thermal solver too, <br />
as a job specification.<br />
<br />
== Acoustics and noise ==<br />
<br />
A whole separate research subject, difficult. <br />
<br />
Tone noise possible. Often run with linearzised solvers in the frequency domain.<br />
<br />
Jet noise possible. Often run with LES or DES simulations that either also resolve the sound waves or couples to a separate acoustic solver.<br />
<br />
Turbomachinery broadband noise not possible yet, or at least a great challenge.<br />
<br />
== Errors and uncertainties ==<br />
<br />
CFD is still a tool which requires that a user has a good understanding of uncertainties and errors that might spoil a CFD similation. There exists no error control in CFD and any CFD simulation must be interpreted by an expirenced user to have some credibility. Without some knowledge about possible errors and how they can be handled a CFD simulation can not be trusted. Errors can occur at different places:<br />
<br />
* Definition of the problem - What needs to be analyzed?<br />
* Selection of the solution strategy - What physical models and what numerical tools should be used?<br />
* Development of the computational model - How should the geometry and the numerical tools be set up?<br />
* Analysis and interpretation of the results - How should the model be analyzed and the results be interpreted?<br />
<br />
There exists many different definitions on errors. In this guide the errors are classified into four types of errors: problem definition errors, model errors, numerical errors and user and code errors. The chapters below describe these errors and give some guidelines on how to avoid them.<br />
<br />
=== Problem definition errors ===<br />
<br />
Problem definition errors are the most basic form of errors. In order to obtain usefull results a CFD simulation must of course analyze the correct problem, have suitable boundary contions and be based on a relevant geometry.<br />
<br />
==== Wrong type of simulation ====<br />
<br />
It is essential to have an overview of the physics involved and how the problem can best be analyzed. Running a 2D simulation in order to understand secondary flows or running a steady simulation in order to understand transient behaviour is of course no use. When assessing a CFD simulation the first thing to consider is what physical phenomena are important for the results and if the selected type of simulation is suitable to resolve this type of phenomena. For further information about selecting the most suitable type of simulation please see the previous chapter on [[#Deciding what type of simulation to do|deciding what type of simulation to perform]].<br />
<br />
==== Incorrect or uncertain boundary conditions ====<br />
<br />
A common source of errors is that incorrect boundary conditions are used. The boundary conditions must be specified in enough detail in order to resolve all the important physical features in the problem. For further information about specifying boundary conditions please see the previous chapter on [[#Boundary conditions|boundary conditions]].<br />
<br />
==== Geometrical errors ====<br />
<br />
It is almost always necessary to simplify the geometry in some form. When assessing a CFD simulation one should consider how the geometrical simplifications can affect the interesting physical phenomena. Typical geometrical errors are:<br />
<br />
*Simplifications<br />
:Small geometrical features like fillets, small steps or gaps etc. can often be disregarded. When disregarding this type of features one should consider if they might affect the important physics. For example, a very large fillet on the suction-side of a vane might affect corner separations near the end-walls. A large tip-leakage might affect the flow physics significantly in the upper part of a compressor.<br />
*Tolerances and manufacturing discrepancies<br />
:If the geometry has very large tolerances or is manufactured in a way which might produce a non-ideal shape or position it might be necessary to perform additional CFD simulations in order to cover the whole span of possible real geometries.<br />
*Surface conditions - roughness, welds, steps, gaps etc.<br />
:Often CFD simulations assume a perfectly smooth surface. A non-smooth surface which might have welds, steps or even gaps will of course produce different results. If the physical phenomena of interest might depend on the surface conditions these should of course be condidered. Typical phenomena that might be dependent on this type of errors are transition prediction, leakage flows etc.<br />
<br />
=== Model errors ===<br />
<br />
Errors related to the computational model.<br />
<br />
==== Wrong physical models ====<br />
<br />
Once the type of simulation has been selected the next step is to select what type of physical models the simulation should use. The following points should be considered:<br />
<br />
* Gas data (incompressible/compressible, perfect gas/real gas, ...)<br />
* Turbulence modeling (type of model, type of near-wall treatment, ...)<br />
* Other models (combustion, sprays, ...)<br />
<br />
When assessing model related errors it is important to know the features of the selected model and think carefully how these features and possible short comings might affect the predicted physical behaviour. Using the wrong turbulence model or combustion model can completely destroy the results of a CFD simulation.<br />
<br />
=== Numerical errors ===<br />
<br />
Errors related to the numerical solution of the developed model. Typical examples of numerical errors are discretization errors, convergence errors and round-off errors.<br />
<br />
==== Discretization errors ====<br />
<br />
Discretization errors can either be spatial errors in space or temporal errors in time.<br />
<br />
Spatial discretization errors are what people normally call discretization errors. These errors are due to the difference between the exact solution and the numerical representation of the solution in space. Describing exactly what discretization different codes use and what errors this might lead to is not possible here. Instead some general rules to avoid these errors can be summarized as:<br />
* Use at least a 2nd order accurate scheme, preferably a 3rd order accurate scheme. Some general purpose codes have a 1st order upwind scheme as default, this is a very diffusives schemes that often gives too smooth results.<br />
* For new applications always run a simulation with a finer mesh to see how grid independent your solution is.<br />
* Be aware of checker-board errors. Checker-board errors occur close to strong shocks and other large discontinuities and can be seen as a wavy pattern with a wavelength of two cells. Some schemes, especially those who behave like central differencing schemes, are more prone to checker-board errors. Upwind schemes are a bit better and schemes like TVD or chock-capturing schemes are even better.<br />
<br />
Temporal discretization errors mainly effect transient simulations. However, some codes use a time-marching method also for steady simulations and then a temporal discretization error might affect the final steady solution slightly. The discretization in time can be done with 1st or 2nd order schemes or a Runge-Kutta method, which is more accurate and saves memory. Some codes can adapt the time-step, but often it is necessary to prescribe a time-step in advance. Think of the time-step as your grid in time and make sure that the grid-resolution in time is fine enough to resolve the highest frequencies. To avoid problems with temporal discretization errors the following should be considered:<br />
* Use at least a 2nd order scheme in time.<br />
* Do a physical estimation of the typical frequencies in time of the phenomena that you are interested in and select a time-step which is fine enough to resolve these frequencies well. After the simulation also look at the frequencies captured and make sure that they are well resolved by the chosen time-step.<br />
* For new applications try a finer time-step to ensure that your solution in time is fairly grid independent in time.<br />
<br />
==== Convergence errors ====<br />
<br />
To judge when a CFD simulation is converged is not always that easy. Different codes and different applications behave very differently. For a pure aero-simulation on a fairly coarse grid convergence is easy to judge, but for more complex simulations involving resolved boundary layers, heat transfer, combustion etc. convergence can be very tricky. Aside from looking at residuals one should always also look at how global parameters like static pressure distributions, total pressure losses, skin friction, heat transfer etc. change in time.<br />
For more information about how to avoid convergence errors see the previous chapter about [[#Convergence criteria]].<br />
<br />
==== Round-off errors ====<br />
<br />
When using single precision care needs to be taken to avoid round-off errors. Inviscid Euler simulations and simulations using wall-function meshes can most often be performed in single precision. For well resolved boundary layers with Y plus close to 1 it is often necessary to use double precision. If using double precision for very fine mesh resolutions make sure that you also create the mesh in double precision and not just run the solver in double precision. Sometimes a single precision solver converges slower than a double precision solver due to numerical errors caused by round-off errors. When using advanced physical models like combustion, free-surface simulations, spray and transient simulations with quick mesh motions it is also often necessary to use double precision.<br />
<br />
=== User and code errors ===<br />
<br />
Errors related to bugs in the code used or mistakes made by the CFD engineer.<br />
<br />
=== What to trust and what not to trust ===<br />
<br />
CFD is generally quite good at predicting surface static pressure distributions. With care CFD can also be used to predict performance, total-pressure losses and blade turning. <br />
<br />
Predicting separation, stall and off-design performance can be a challenge and results with non-attached flows should be interpreted with care. <br />
<br />
Heat transfer is often very difficult to predict accurately and it is common to obtain heat-transfer coefficients that are 100% wrong or more. Validation data is critical in order to be able to trust heat transfer simulations.<br />
<br />
Transition is almost impossible to predict accurately in general. However, there exist models that have been tuned to predict transition and these tend to give acceptable results for cases close to the ones they were tuned for.<br />
<br />
== References ==<br />
<br />
* {{reference-paper|author=Abu-Ghannam, B.J. and Shaw, R.|year=1980|title=Natural Transition of Boundary Layers - the Effects of Turbulence, Pressure Gradient, and Flow History|rest=Journal of Mech. Eng. Science, vol. 22, no. 5, pp. 213–228}}<br />
<br />
* {{reference-paper|author=Adamczyk, J. J.|year=1985|title=Model Equation for Simulating Flows in Multistage Turbomachinery|rest=ASME Paper 85-GT-226, also NASA TM-86869}}<br />
<br />
* {{reference-paper|author=Adamczyk, J. J.|year=1999|title=Aerodynamic Analysis of Multistage Turbomachinery Flows in Support of Aerodynamic Design|rest=ASME Paper 99-GT-80.}}<br />
<br />
* {{reference-paper|author=Baldwin, B. S. and Lomax, H.|year=1978|title=Thin Layer Approximation and Algebraic Model for Separated Turbulent Flows|rest=AIAA Paper 78-257}}<br />
<br />
* {{reference-paper|author=Chen, J. P. and Barter, J. W.|year=1998|title=Comparison of Time-Accurate Calculations for the Unsteady Interaction in Turbomachinery Stage|rest=AIAA Paper 98-3292}}<br />
<br />
* {{reference-paper|author=Denton, J. and Singh, U.|year=1979|title=Time Marching Methods for Turbomachinery Flow Calculations|rest=VKI Lecture Series 1979-7, von Karman Institute}}<br />
<br />
* {{reference-paper|author=Erdos, J., Alzner, E. and McNally, W.|year=1977|title=Numerical Solution of Periodic Transonic Flow Through a Transonic Fan Stage|rest=AIAA Journal, vol. 15, no. 11, pp. 1559-1568}}<br />
<br />
* {{reference-paper|author=Gerolymos, G., Vinteler, D., Haugeard, R., Tsange, G. and Vallet, I.|year=1996|title=On the Computation of Unsteady Turbomachinery Flows – Part II – Rotor/Stator Interaction using Euler Equations|rest=AGARD Report CP-571}}<br />
<br />
* {{reference-paper|author=Giles, M. B.|year=1990|title=Stator/Rotor Interaction in a Transonic Turbine|rest=AIAA Journal of Propulsion and Power, vol. 6, no. 5}}<br />
<br />
* {{reference-paper|author=He, L, and Ning, W.|year=1998|title=Efficient Approach for Analysis of Unsteady Viscous Flows in Turbomachines|rest=AIAA Journal, vol. 36, no. 11, pp. 2005-2012}}<br />
<br />
* {{reference-paper|author=Mayle, R. E.|year=1991|title=The Role of Laminar-Turbulent Transition in Gas Turbine Engines|rest=ASME Journal of Turbomachinery, vol. 113, pp. 509-537}}<br />
<br />
* {{reference-paper|author=Menter, F.R. |year=1994|title=Two-equation eddy-viscosity turbulence models for engineering applications|rest=AIAA Journal, vol. 32, pp. 269-289}}<br />
<br />
* {{reference-paper|author=Savill, M., Dick, E., Hanjalić, K. and Voke, P.|year=2002|title=Synthesis Report of the ERCOFTAC Transition Modeling – TRANSPRETURB Thematic Network Activities 1998-2002|rest=Ecoftac Bulletin 54, September 2002, pp. 5-16}}<br />
<br />
* {{reference-paper|author=Wang, X. and Chen J.|year=2004|title=A Post-Processor to Render Turbomachinery Flows Using Phase-Lag Simulations|rest=AIAA Paper 04-615}}<br />
<br />
== External links ==<br />
<br />
* [http://www.qnet-cfd.net/newsletter/8th/n8_40-46.pdf QNET-CFD Best Practise Advice for Turbomachinery Internal Flows]<br />
* [http://www.qnet-cfd.net/newsletter/7th/n7_05.pdf State of the art in Industrial CFD for Turbomachinery Flows, QNET-CFD Network Newsletter, Volume 2, No. 3 – December 2003]<br />
* [https://pronet.wsatkins.co.uk/marnet/guidelines/guide.html MARNET-CFD Best Practice Guidelines for Marine Applications of CFD]<br />
* [http://www.stanford.edu/group/ctr/ResBriefs/temp05/weide.pdf On Large Scale Turbomachinery Computations, by E. van der Weide et. al., Center for Turbulence Research, Annual Research Briefs 2005]</div>Frmontohttps://www.cfd-online.com/Wiki/Best_practice_guidelines_for_turbomachinery_CFDBest practice guidelines for turbomachinery CFD2007-02-14T13:23:53Z<p>Frmonto: /* Meshing */</p>
<hr />
<div>== Introduction ==<br />
<br />
This guide is mainly aimed at axial turbomachinery. Feel free to extend it to other types of turbomachinery though.<br />
<br />
== Deciding what type of simulation to do ==<br />
<br />
=== 2D, Quasi-3D or 3D ===<br />
<br />
=== Inviscid or viscid ===<br />
<br />
=== Transient or Stationary ===<br />
<br />
== Meshing ==<br />
<br />
In turbomachinery applications, generally, structured meshes are used for the analysis fo flow path, generally during the design process. The main advantace using structured meshes is the time required by the operator to generate the mesh (a lot of companies have in house mesh generators able to mesh a standard blade in few seconds); in addition coupling a structured solver and a structured mesh is it possible to have a very fast design tools.<br />
The unstructured meshes are used generally to study the blade and other features like blade tip, wheel space, film cooling ducts etc. In the second case generally the computational time required with the same number of elements is higher (if in the first case a structured solver is chosen) related to the elements connections (in a structured mesh is trivial, in an unstructured grid an array is required to store the connectivity). <br />
<br />
<br />
=== Mesh size guidelines ===<br />
<br />
It is difficult to define, a priori, the mesh size. Mainly this depends on the purpose of the simulation. If the main goal is to obtain pressure forces a coarse mesh is able to obtain a good solution and not an accurate resolution of boundary layer is required (an inviscid calculation with a kutta condition on trailing edge is able to detect quite well the loading of a blade, if separations are not presents).<br />
<br />
For losses prediction the mesh have to be denser in the BL region. Check if the BL is currently represented by the solution. For the heat transfer is really difficult to give a general rule. In all simulation the distance of first node to the wall is related to the turbulence closure but this is really important in heat transfer prediction.<br />
<br />
In 3D a decent wall-function mesh typically has around 100,000 cells. This type of mesh size is suitable for quick design iterations where it is not essential to resolve all secondary flows and vortices. A good wall-function mesh intended to resolve secondary flows well should have at least 400,000 cells. A good low-Re mesh with resolved boundary layers typically has around 1,000,000 cells.<br />
<br />
In 2D a good wall-function mesh has around 10,000 and a good low-Re mesh with resolved boundary layers has around 30,000 cells.<br />
<br />
<br />
<br />
=== Boundary layer mesh ===<br />
<br />
For design iteration type of simulations where, a [[wall function]] approach is sufficient, [[y-plus | y+]] for the first cell should be somewhere between 30 and 300. For more accurate simulations with resolved boundary layers the mesh should have a y+ for the first cell which is below 1. A good rule of thumb is to use a growth ratio in the boundary layer of 1.2 - 1.25. <br />
<br />
If you are uncertain of which wall distance to mesh with you can use a [http://www.cfd-online.com/Links/tools.html#yplus y+ estimation tool] to estitmate the distance needed to obtain the desired y+.<br />
<br />
As a rule of thumb a wall-function mesh typically requires about 10 cells in the boundary layer whereas a resolved low-Re mesh requires about 40 cells in the boundary layer.<br />
<br />
== Boundary conditions ==<br />
<br />
Describe different types of boundary conditions and when they should be used:<br />
<br />
* Total pressure in, static pressure out<br />
* Absorbing boundary conditions<br />
* ...<br />
<br />
Describe how to select inlet turbulence level and length-scale <br />
<br />
== Turbulence modeling ==<br />
<br />
Selecting a suitable turbulence model for turbomachinery simulations can be a challenging task. There is no single model which is suitable for all types of simulations. Which turbulence model CFD engineers use often has as much to do with beliefs and traditions as with knowledge and facts. There are many diffrent schools. However, below follows some advices that most CFD engineers in the turbomachinery field tend to agree upon.<br />
<br />
For attached flows close to the design point a simple algebraic model like the [[Baldwin-Lomax model]] can be used. Another common choice for design-iteration type of simulations is the one-equation model by [[Spalart-Allmaras model | Spalart-Allmaras]]. The big advantage with both the [[Baldwin-Lomax model]] and the [[Spalart-Allmaras model]] over more advanced models are that they are very robust to use and rarely produce complete unphysical results.<br />
<br />
In order to accurately predict more difficult cases, like flows that are close to or even fully separated, rotating flows, flows strongly affected by secondary flows etc. it is often necessary to use a more refined turbulence model. Common choices are a two-equation models like the <math>k-\epsilon</math>. <math>k-\epsilon</math> models can give good results but this type of models need to include some form of correction to avoíd over-production of turbulent energy in regions with strong acceleration or decelleration. Typical such corrections are some form or [[realizability constraint]] or the [[Kato-Launder modification]]. Antoher common choice in turbulence model is Menter's [[SST k-omega model]] or the slightly more elaborate [[v2f model]] by Durbin.<br />
<br />
=== Near-wall treatment ===<br />
<br />
For on-design simlations without any large separated regions it is often sufficient to use a [[wall-function model]] close to the wall, preferably using some form of non-equilibrium wall-function that is sensitised to streamwise pressure gradients.<br />
<br />
For off-design simulation, or simulations involving complex secondary flows and separations, it is often necessary to use a [[low-Re model]]. There exists many low-Re models that have been used with success in turbomachinery simulations. A robust and often good choice is to use a one-equation model, like for example the [[Wolfstein model]], in the inner parts of the boundary layer. There are also several Low-Re <math>k-\epsilon</math> models that work well. Just make sure they don't suffer from the problem with overproduction of turbulent energy in regions with strong acceleration or deceleration. In the last few years Menter's low-Re <math>SST k-\omega</math> model has gained increased popularity.<br />
<br />
=== Transition prediction ===<br />
<br />
Transition refers to the process when a lamainar boundary layer becomes unstable and transitions to a turbulent boundary layer. There are two types of transition - natural transition, where inherent instabilities in the boundary layer cause the transition and by-pass transition, where convection and diffusion of turbulence from the free-stream into the boundary layer causes transition. <br />
<br />
== Numerical considerations ==<br />
<br />
== Multi-stage analysis ==<br />
<br />
Types of analysis:<br />
<br />
* Frozen rotor<br />
:Frozen rotor defines the domain interface to transfer flow and thermal data across the interface between the stationary and rotating domain. Frozen rotor interface connects the two doamins (rotating and stationary) in such a way that these two domains have a fixed relative position throughout the solution, but with desired frame transformation occurring across the interface. Transient effects cannot be modelled with this interface. This the the only disadvantage of the frozen rotor interface.<br />
* Mixing-plane<br />
In the Mixing-plane also called as "Stage-Interface" approah in the commercial code CFX, variables are circumferentially averaged before passing from one domain to the other, say for instance from stator to rotor. This is used typically when there are blade rows on either sides of the interface. The advantage in this approach is that only one blade passage need to be modeled. One situation where this is less appropriate is while simulating impeller and a volute in a pump/ compressor. Transient effects are completely ignored and often this approach closely matches test data near design point.<br />
* Sliding-mesh<br />
* Time-inclinded<br />
* Adamszyk stresses ...<br />
<br />
''Describe how to scale blade-sections when doing sliding-mesh computations''<br />
<br />
== Heat transfer predictions ==<br />
<br />
== Acoustics and noise ==<br />
<br />
A whole separate research subject, difficult. <br />
<br />
Tone noise possible. Often run with linearzised solvers in the frequency domain.<br />
<br />
Jet noise possible. Often run with LES or DES simulations that either also resolve the sound waves or couples to a separate acoustic solver.<br />
<br />
Turbomachinery broadband noise not possible yet, or at least a great challenge.<br />
<br />
== What to trust and what not to trust ==<br />
<br />
CFD is generally quite good at predicting surface static pressure distributions. With care CFD can also be used to predict performance, total-pressure losses and blade turning. <br />
<br />
Predicting separation, stall and off-design performance can be a challenge and results with non-attached flows should be interpreted with care. <br />
<br />
Heat transfer is often very difficult to predict accurately and it is common to obtain heat-transfer coefficients that are 100% wrong or more. Validation data is critical in order to be able to trust heat transfer simulations.<br />
<br />
Transition is almost impossible to predict accurately in general. However, there exist models that have been tuned to predict transition and these tend to give acceptable results for cases close to the ones they were tuned for.<br />
<br />
== External links ==<br />
<br />
[http://www.qnet-cfd.net/newsletter/8th/n8_40-46.pdf QNET-CFD Best Practise Advice for Turbomachinery Internal Flows]</div>Frmontohttps://www.cfd-online.com/Wiki/Best_practice_guidelines_for_turbomachinery_CFDBest practice guidelines for turbomachinery CFD2007-02-13T23:42:46Z<p>Frmonto: /* Meshing */</p>
<hr />
<div>== Introduction ==<br />
<br />
This guide is mainly aimed at axial turbomachinery. Feel free to extend it to other types of turbomachinery though.<br />
<br />
== Deciding what type of simulation to do ==<br />
<br />
=== 2D, Quasi-3D or 3D ===<br />
<br />
=== Inviscid or viscid ===<br />
<br />
=== Transient or Stationary ===<br />
<br />
== Meshing ==<br />
<br />
In turbomachinery application, generally, structured meshes are used for the analysis fo flow path, generally during the design process. The main advantace using structured meshes is the time required by the operator to generate the mesh (a lot of companies have in house mesh generators able to mesh a standard blade in few seconds); in addition coupling a structured solver and a structured mesh is it possible to have a very fast design tools.<br />
The unstructured meshes are used generally to study the blade and other features like blade tip, wheel space, film cooling ducts etc. In the second case generally the computational time required with the same number of elements is higher (if in the first case a structured solver is chosen) related to the elements connections (in a structured mesh is trivial, in an unstructured grid an array is required to store the connectivity). <br />
<br />
<br />
=== Mesh size guidelines ===<br />
<br />
It is difficult to define, a priori, the mesh size. Mainly this depends on the purpose of the simulation. If the main goal is to obtain pressure forces a coarse mesh is able to obtain a good solution and not an accurate resolution of boundary layer is required (an inviscid calculation with a kutta condition on trailing edge is able to detect quite well the loading of a blade, if separations are not presents).<br />
<br />
For losses prediction the mesh have to be denser in the BL region. Check if the BL is currently represented by the solution. For the heat transfer is really difficult to give a general rule. In all simulation the distance of first node to the wall is related to the turbulence closure but this is really important in heat transfer prediction.<br />
<br />
In 3D a decent wall-function mesh typically has around 100,000 cells. This type of mesh size is suitable for quick design iterations where it is not essential to resolve all secondary flows and vortices. A good wall-function mesh intended to resolve secondary flows well should have at least 400,000 cells. A good low-Re mesh with resolved boundary layers typically has around 1,000,000 cells.<br />
<br />
In 2D a good wall-function mesh has around 10,000 and a good low-Re mesh with resolved boundary layers has around 30,000 cells.<br />
<br />
<br />
<br />
=== Boundary layer mesh ===<br />
<br />
For design iteration type of simulations where, a [[wall function]] approach is sufficient, [[y-plus | y+]] for the first cell should be somewhere between 30 and 300. For more accurate simulations with resolved boundary layers the mesh should have a y+ for the first cell which is below 1. A good rule of thumb is to use a growth ratio in the boundary layer of 1.2 - 1.25. <br />
<br />
If you are uncertain of which wall distance to mesh with you can use a [http://www.cfd-online.com/Links/tools.html#yplus y+ estimation tool] to estitmate the distance needed to obtain the desired y+.<br />
<br />
As a rule of thumb a wall-function mesh typically requires about 10 cells in the boundary layer whereas a resolved low-Re mesh requires about 40 cells in the boundary layer.<br />
<br />
== Boundary conditions ==<br />
<br />
Describe different types of boundary conditions and when they should be used:<br />
<br />
* Total pressure in, static pressure out<br />
* Absorbing boundary conditions<br />
* ...<br />
<br />
Describe how to select inlet turbulence level and length-scale <br />
<br />
== Turbulence modeling ==<br />
<br />
Selecting a suitable turbulence model for turbomachinery simulations can be a challenging task. There is no single model which is suitable for all types of simulations. Which turbulence model CFD engineers use often has as much to do with beliefs and traditions as with knowledge and facts. There are many diffrent schools. However, below follows some advices that most CFD engineers in the turbomachinery field tend to agree upon.<br />
<br />
For attached flows close to the design point a simple algebraic model like the [[Baldwin-Lomax model]] can be used. Another common choice for design-iteration type of simulations is the one-equation model by [[Spalart-Allmaras model | Spalart-Allmaras]]. The big advantage with both the [[Baldwin-Lomax model]] and the [[Spalart-Allmaras model]] over more advanced models are that they are very robust to use and rarely produce complete unphysical results.<br />
<br />
In order to accurately predict more difficult cases, like flows that are close to or even fully separated, rotating flows, flows strongly affected by secondary flows etc. it is often necessary to use a more refined turbulence model. Common choices are a two-equation models like the <math>k-\epsilon</math>. <math>k-\epsilon</math> models can give good results but this type of models need to include some form of correction to avoíd over-production of turbulent energy in regions with strong acceleration or decelleration. Typical such corrections are some form or [[realizability constraint]] or the [[Kato-Launder modification]]. Antoher common choice in turbulence model is Menter's [[SST k-omega model]] or the slightly more elaborate [[v2f model]] by Durbin.<br />
<br />
=== Near-wall treatment ===<br />
<br />
For on-design simlations without any large separated regions it is often sufficient to use a [[wall-function model]] close to the wall, preferably using some form of non-equilibrium wall-function that is sensitised to streamwise pressure gradients.<br />
<br />
For off-design simulation, or simulations involving complex secondary flows and separations, it is often necessary to use a [[low-Re model]]. There exists many low-Re models that have been used with success in turbomachinery simulations. A robust and often good choice is to use a one-equation model, like for example the [[Wolfstein model]], in the inner parts of the boundary layer. There are also several Low-Re <math>k-\epsilon</math> models that work well. Just make sure they don't suffer from the problem with overproduction of turbulent energy in regions with strong acceleration or deceleration. In the last few years Menter's low-Re <math>SST k-\omega</math> model has gained increased popularity.<br />
<br />
=== Transition prediction ===<br />
<br />
Transition refers to the process when a lamainar boundary layer becomes unstable and transitions to a turbulent boundary layer. There are two types of transition - natural transition, where inherent instabilities in the boundary layer cause the transition and by-pass transition, where convection and diffusion of turbulence from the free-stream into the boundary layer causes transition. <br />
<br />
== Numerical considerations ==<br />
<br />
== Multi-stage analysis ==<br />
<br />
Types of analysis:<br />
<br />
* Frozen rotor<br />
:Frozen rotor defines the domain interface to transfer flow and thermal data across the interface between the stationary and rotating domain. Frozen rotor interface connects the two doamins (rotating and stationary) in such a way that these two domains have a fixed relative position throughout the solution, but with desired frame transformation occurring across the interface. Transient effects cannot be modelled with this interface. This the the only disadvantage of the frozen rotor interface.<br />
* Mixing-plane<br />
In the Mixing-plane also called as "Stage-Interface" approah in the commercial code CFX, variables are circumferentially averaged before passing from one domain to the other, say for instance from stator to rotor. This is used typically when there are blade rows on either sides of the interface. The advantage in this approach is that only one blade passage need to be modeled. One situation where this is less appropriate is while simulating impeller and a volute in a pump/ compressor. Transient effects are completely ignored and often this approach closely matches test data near design point.<br />
* Sliding-mesh<br />
* Time-inclinded<br />
* Adamszyk stresses ...<br />
<br />
''Describe how to scale blade-sections when doing sliding-mesh computations''<br />
<br />
== Heat transfer predictions ==<br />
<br />
== Acoustics and noise ==<br />
<br />
A whole separate research subject, difficult. <br />
<br />
Tone noise possible. Often run with linearzised solvers in the frequency domain.<br />
<br />
Jet noise possible. Often run with LES or DES simulations that either also resolve the sound waves or couples to a separate acoustic solver.<br />
<br />
Turbomachinery broadband noise not possible yet, or at least a great challenge.<br />
<br />
== What to trust and what not to trust ==<br />
<br />
CFD is generally quite good at predicting surface static pressure distributions. With care CFD can also be used to predict performance, total-pressure losses and blade turning. <br />
<br />
Predicting separation, stall and off-design performance can be a challenge and results with non-attached flows should be interpreted with care. <br />
<br />
Heat transfer is often very difficult to predict accurately and it is common to obtain heat-transfer coefficients that are 100% wrong or more. Validation data is critical in order to be able to trust heat transfer simulations.<br />
<br />
Transition is almost impossible to predict accurately in general. However, there exist models that have been tuned to predict transition and these tend to give acceptable results for cases close to the ones they were tuned for.<br />
<br />
== External links ==<br />
<br />
[http://www.qnet-cfd.net/newsletter/8th/n8_40-46.pdf QNET-CFD Best Practise Advice for Turbomachinery Internal Flows]</div>Frmonto