CFD

This page is maintained by Nik Lebedenko - if you want to ask questions / see a mistake / request more details to be added to this page, feel free to email me or message me on slack.

Computational Fluid Dynamics (CFD) is the process of solving fluid mechanics equations with the use of computers, usually with the Finite Volume Method.

Essentially F=ma, but with many simultaneous equations.

OpenFOAM installation instructions here

Getting Started with CFD

OpenFOAM installation instructions here

Skip this section if you dislike broad-strokes philosophical discussion.

The path you should take for CFD differs depending on what your end goal is, and what budget you have. The main choice is between OpenFOAM and a commercial package (ANSYS Fluent / CFX, STAR-CCM, etc).

OpenFOAM Pros vs commercial packages:

• Free
• Open Source
• You can edit any part of the software, any setting, any way you want to.
• No limits, no "paid version only" features. (ANSYS limits you to 2 CPU threads and 100k cells for simulation)

OpenFOAM Cons vs commercial packages:

• Difficult to install
• Difficult to use
• Difficult to learn - less of a learning curve, more like a cliff.
• No graphical user interface
• Mesh generation software is terrible. IMO, the best way to generate a mesh in OpenFOAM, is not to generate a mesh in OpenFOAM
  • Pro tip: use ANSYS meshing software (either the mechanical mesher, or the Fluent mesher) to generate CFD meshes. It will be 10x quicker (including setup time), take 5x less RAM, and be a higher quality than what you could achieve with OpenFOAM. Then import it into OpenFOAM with fluentMeshToFoam <options> <.msh file>. ANSYS does not put a cap on the mesh size you can generate, only the mesh size you can simulate is limited.
  • There are other free & open source meshing programs, e.g. Gmsh, but I have not tried them.

OpenFOAM throws you into the deep end, and forces you to learn nearly everything at once. If you stick through to the end of the learning cliff, you will understand much more about CFD than you would have otherwise learned with a commercial package.

If you just need to do one or two small sims, a commercial package e.g. ANSYS is your best choice. (Just not SOLIDWORKS CFD simulations).

The remainder of this wiki is dedicated to free and open source software, including OpenFOAM.

Crash course on the Finite Volume Method (FVM)

There are many resources for learning how CFD works properly (linked below), but this is a crash course. This section is designed for people who would like to find out a bit more about how CFD works, beyond a "black-box" understanding, but without going too far in depth with all the details. So, here are the bare minimum requirements for understanding roughly what is going on under the hood in any CFD solver. I will assume you know:

• Some basic high-school physics about gases (e.g. what is pressure, how does it change with temperature)
• What a partial derivative is,
• What simultaneous equations are,
• How to write simultaneous equations as matrices, and
• What a vector is.

Sections marked "Optional" are not required for a basic level of understanding of how the software works, but give a bit more detail for those who want it.

Overview

The most common method of doing CFD is with the Finite Volume Method (FVM). An informal derivation of some flow equations along with application of the FVM to them is in this section.

It is also possible to do CFD with the Finite Element Method (FEM), which is more typically associated with Structural Analysis / Elastodynamics problems, but we won't discuss that here.

CFD solvers work by splitting up the region of interest (a process called meshing the domain) into a bunch of small boxes (called the cells in the mesh), and solving a set of equations in each of those cells, taking into account how the flow variables (velocity, temperature, pressure) are related between neighbouring cells. Most commonly:

• The continuity equation: mass is not created or destroyed (conservation of mass).
• The momentum equation: "F=ma" but for fluids (conservation of momentum).
• The energy equation: energy is not created or destroyed (conservation of energy).

The continuity equation

To clarify this, consider the example below of a simple uniform pipe, with a cross-section shown in the left image. Now, let us mesh the domain into four cells (split the pipe into 4 boxes), image right.

• 

  2D pipe cross-section with a flow from left to right

• 

  Pipe split into cells, with cell centroids marked with circles

Note: the cells here are 3D - we are looking at a 2D cross section. We will assume that the velocity is purely in the x direction. Consider an arbitrary cell within this mesh labelled [math]\displaystyle{ P }[/math], with its western and eastern neighbours labelled [math]\displaystyle{ W }[/math] and [math]\displaystyle{ E }[/math] respectively. The faces between [math]\displaystyle{ W }[/math] & [math]\displaystyle{ P }[/math] and [math]\displaystyle{ P }[/math] & [math]\displaystyle{ E }[/math] are labelled [math]\displaystyle{ w }[/math] and [math]\displaystyle{ c }[/math]. The following abbreviations for flow variables will be used:

• [math]\displaystyle{ x }[/math]: Position,
• [math]\displaystyle{ \rho }[/math] (rho): Density,
• [math]\displaystyle{ p }[/math]: Pressure,
• [math]\displaystyle{ U }[/math]: Velocity (in the x-axis),
• [math]\displaystyle{ V }[/math]: Volume of the cell,
• [math]\displaystyle{ A }[/math]: Area of a face,
• Any variable with a subscript corresponds to the value of that variable at that location. E.g. [math]\displaystyle{ U_{\small{W}} }[/math] is the velocity of the fluid at [math]\displaystyle{ W }[/math]. The area of face [math]\displaystyle{ w }[/math] is [math]\displaystyle{ A_w }[/math].

• 

  An arbitrary cell P neighboured by cells W and E on the west and east sides respectively

• 

  A graph showing cell values (grey circles) and the linear interpolated face values (blue circles)

The continuity equation tells us that mass is not created or destroyed. For an arbitrary cell P, knowing that the mass flow rate through a given face is [math]\displaystyle{ {\rho}UA }[/math], we can write

Rate of change of mass in [math]\displaystyle{ P }[/math] = Mass flow rate in - Mass flow rate out

[math]\displaystyle{ \frac{\partial (\rho V)_{\small{P}}}{\partial t} = ({\rho}UA)_{w} - ({\rho}UA)_{e} }[/math]

If we assume an incompressible (constant density) fluid, e.g. water, we can divide by the density term [math]\displaystyle{ \rho }[/math] on both sides. If we assume a steady flow, then nothing changes with time, i.e. all time derivatives are zero. The equation becomes

[math]\displaystyle{ 0 = ({\rho}UA)_w - ({\rho}UA)_e }[/math]

[math]\displaystyle{ 0 = (UA)_w - (UA)_e }[/math] - (1)

At the moment, we are using values of velocity at the faces between the cells. But in a CFD solver, we only store the values at the cell centroid. The process of calculating face values using cell values on either side of the face is called interpolation. The most obvious interpolation scheme (method) is linear interpolation - that is, assume that all variables vary linearly between two points, as in the image above. Note: interpolation isn't unique to the variable [math]\displaystyle{ U }[/math] - it can be applied to all flow variables.

In our case, the cells and faces are all perfectly uniformly spaced, so if we use linear interpolation to work out the face values,

[math]\displaystyle{ U_w = {1 \over 2} (U_{\small{W}} + U_{\small{P}}), \quad U_e = {1 \over 2} (U_{\small{P}} + U_{\small{E}}) }[/math]

This is the same as saying that the face values are the average of the neighbouring cell values. Let's use a more general equation to represent linear interpolation.

[math]\displaystyle{ U_w = i_{\small{W}}U_{\small{W}} + (1-i_{\small{W}})U_{\small{P}}, \quad U_e = i_{\small{E}}U_{\small{P}} + (1-i_{\small{E}})U_{\small{E}} }[/math]

where [math]\displaystyle{ i_{\small{W}} = \frac{x_w - x_{\small{W}}}{x_{\small{P}} - x_{\small{W}}} }[/math] and [math]\displaystyle{ i_{\small{E}} = \frac{x_e - x_{\small{P}}}{x_{\small{E}} - x_{\small{P}}} }[/math]

Don't be intimidated by the complicated-looking fractions! [math]\displaystyle{ i_{\small{W}} }[/math] simply represents how far the face [math]\displaystyle{ w }[/math] is from cell [math]\displaystyle{ W }[/math], divided by the distance between [math]\displaystyle{ W }[/math] and [math]\displaystyle{ P }[/math]. This way, if the face is exactly half-way between [math]\displaystyle{ W }[/math] and [math]\displaystyle{ P }[/math], then [math]\displaystyle{ i_{\small{W}} = {1 \over 2} }[/math], giving the same equation as before. If instead, the face was closer to [math]\displaystyle{ W }[/math] than to [math]\displaystyle{ P }[/math], then [math]\displaystyle{ i_{\small{W}} \lt {1 \over 2} }[/math], and vice versa.

After this point, the continuity equation will only work for cells that aren't on the boundary. We also factor out the areas of each face, since they are just constants. The continuity equation becomes

[math]\displaystyle{ 0 = (U_{\small{W}}i_{\small{W}} + U_{\small{P}}(1-i_{\small{W}})) \cdot A_w - (U_{\small{P}}i_{\small{E}} + U_{\small{E}}(1-i_{\small{E}})) \cdot A_e }[/math]

We now expand and simplify the equation, combining the constants into single variables.

[math]\displaystyle{ 0 = U_{\small{W}}i_{\small{W}}A_w + U_{\small{P}}(1-i_{\small{W}})A_w - U_{\small{P}}i_{\small{E}}A_e - U_{\small{E}}(1-i_{\small{E}})A_e }[/math]

[math]\displaystyle{ 0 = U_{\small{W}}k_{\small{P,W}} + U_{\small{P}}k_{\small{P,P}} + U_{\small{E}}k_{\small{P,E}} }[/math]

where

• [math]\displaystyle{ k_{\small{P,W}} = i_{\small{W}}A_w }[/math]
• [math]\displaystyle{ k_{\small{P,P}} = (1-i_{\small{W}})A_w - i_{\small{E}}A_e }[/math]
• [math]\displaystyle{ k_{\small{P,E}} = -(1-i_{\small{E}})A_e }[/math].

We can now apply this equation for cells 2 and 3. However, we can't apply this equation to cells 1 and 4, as they are on the boundary of the domain - the linear interpolation step does not work on the boundary. Without knowing what the value of U is at the boundaries, we cannot solve the continuity equation. Therefore we must apply some special treatment at the boundaries (called boundary conditions) in order to solve this issue. Boundary conditions are specified by the CFD user. We will use these boundary conditions:

• Flow velocity on the left boundary is fixed at 5 m/s (called a Dirichlet boundary - mnemonic: kind of sounds like "directly").
  • Plugging this condition into equation (1) gives the equation [math]\displaystyle{ 0 = 5A_w - U_{\small{P}}i_{\small{E}}A_e - U_{\small{E}}(1-i_{\small{E}})A_e }[/math]
• The gradient of velocity [math]\displaystyle{ \frac {\partial U}{\partial x} }[/math] on the right boundary is zero - so the velocity on the right boundary is the same as the velocity at cell centroid 4.
  • Plugging this condition into equation (1) gives the equation [math]\displaystyle{ 0 = U_{\small{W}}i_{\small{W}}A_w + U_{\small{P}}(1-i_{\small{W}})A_w - U_{\small{P}}A_e }[/math]

• The constants are again combined into variables of the form [math]\displaystyle{ k_{a,b} }[/math]. Here is a summary of all the equations found so far:
• Cell 1: [math]\displaystyle{ 0 = 5A_w + U_1k_{1,1} + U_2k_{1,2} }[/math]
• Cell 2: [math]\displaystyle{ 0 = 0 + U_1k_{2,1} + U_2k_{2,2} + U_3k_{2,3} }[/math]
• Cell 3: [math]\displaystyle{ 0 = 0 + U_2k_{3,2} + U_3k_{3,3} + U_4k_{3,4} }[/math]
• Cell 4: [math]\displaystyle{ 0 = 0 + U_3k_{4,3} + U_4k_{4,4} }[/math]

We now have a set of four simultaneous equations to solve for four unknowns (the velocity at each cell centroid).

Let us simplify the notation a bit using matrices and vectors.

[math]\displaystyle{ \begin{bmatrix} 0 \\ 0 \\ 0 \\ 0 \end{bmatrix} = \begin{bmatrix} 5A_w \\ 0 \\ 0 \\ 0 \end{bmatrix} + \begin{bmatrix} k_{1,1} & k_{1,2} & 0 & 0 \\ k_{2,1} & k_{2,2} & k_{2,3} & 0 \\ 0 & k_{3,2} & k_{3,3} & k_{3,4} \\ 0 & 0 & k_{4,3} & k_{4,4} \end{bmatrix} \begin{bmatrix} U_1 \\ U_2 \\ U_3 \\ U_4 \end{bmatrix} }[/math]

[math]\displaystyle{ \begin{bmatrix} k_{1,1} & k_{1,2} & 0 & 0 \\ k_{2,1} & k_{2,2} & k_{2,3} & 0 \\ 0 & k_{3,2} & k_{3,3} & k_{3,4} \\ 0 & 0 & k_{4,3} & k_{4,4} \end{bmatrix} \begin{bmatrix} U_1 \\ U_2 \\ U_3 \\ U_4 \end{bmatrix} = \begin{bmatrix} -5A_w \\ 0 \\ 0 \\ 0 \end{bmatrix} }[/math].

Abbreviated with a matrix of coefficients [math]\displaystyle{ \boldsymbol{M} }[/math], a solution vector [math]\displaystyle{ \boldsymbol{U} }[/math], and a right-hand-side vector [math]\displaystyle{ \boldsymbol{B} }[/math]:

[math]\displaystyle{ \boldsymbol{MU=B} }[/math], where

[math]\displaystyle{ \boldsymbol{M}= \begin{bmatrix} k_{1,1} & k_{1,2} & 0 & 0 \\ k_{2,1} & k_{2,2} & k_{2,3} & 0 \\ 0 & k_{3,2} & k_{3,3} & k_{3,4} \\ 0 & 0 & k_{4,3} & k_{4,4} \end{bmatrix} }[/math], [math]\displaystyle{ \boldsymbol{U} = \begin{bmatrix} U_1 \\ U_2 \\ U_3 \\ U_4 \end{bmatrix} }[/math], and [math]\displaystyle{ \boldsymbol{B} = \begin{bmatrix} -5A_w \\ 0 \\ 0 \\ 0 \end{bmatrix} }[/math]

At this point a CFD solver would calculate each of the coefficients of the matrix and RHS vector. Here we have a uniform cell spacing and a uniform face area of 1.

[math]\displaystyle{ \boldsymbol{M}= \begin{bmatrix} -0.5 & -0.5 & 0 & 0 \\ 0.5 & 0 & -0.5 & 0 \\ 0 & 0.5 & 0 & -0.5 \\ 0 & 0 & 0.5 & -0.5 \end{bmatrix} }[/math]

[math]\displaystyle{ \boldsymbol{B} = \begin{bmatrix} -5 \\ 0 \\ 0 \\ 0 \end{bmatrix} }[/math]

We could now invert the matrix [math]\displaystyle{ \boldsymbol{M} }[/math], and calculate the solution vector [math]\displaystyle{ \boldsymbol{U} }[/math] using [math]\displaystyle{ \boldsymbol{U=M^{-1}B} }[/math].

[math]\displaystyle{ \boldsymbol{M^{-1}}= \begin{bmatrix} -1 & 1 & -1 & 1 \\ -1 & -1 & 1 & -1 \\ -1 & -1 & -1 & 1 \\ -1 & -1 & -1 & -1 \end{bmatrix} }[/math] This yields a solution of U = 5 m/s everywhere. Hooray!

Think: does this result make sense, given our assumptions?

Why matrix inversion rarely happens

The matrix [math]\displaystyle{ \boldsymbol{M} }[/math] always has size n x n, where n is the number of cells in the mesh (in this case 4). But typical CFD cases will have n in the thousands or millions - inverting matrices of this size becomes very time consuming. So instead, CFD solvers use an iterative approach on the equation [math]\displaystyle{ \boldsymbol{MU=B} }[/math], where they start with a guess for [math]\displaystyle{ \boldsymbol{U} }[/math], and improve their guess with successive iterations of an algorithm until the solution vector [math]\displaystyle{ \boldsymbol{U} }[/math] is "close enough" (this threshold is determined by the CFD user). The error in a solution for a variable is characterised by the residual. A small residual means the solution has only a small error, and vice versa. The CFD user specifies what residual value qualifies as "close enough".

The momentum equation

In a similar process to the continuity equation, we can convert F=ma but for fluids into an actual equation, with the intermediate equation: rate of change of momentum at any point = rate of momentum flow in - rate of momentum flow out. For an arbitrary cell C experiencing pressure forces and an external force F, noting that

[math]\displaystyle{ UA = }[/math] the rate of flow of volume through a face, and

[math]\displaystyle{ \frac{mU}{V} = \frac{\rho U V}{V} = \rho U = }[/math] the momentum per unit volume of fluid, we can write

[math]\displaystyle{ \frac{\partial (\rho V U)_{\small{P}}}{\partial t} = ({\rho}UUA)_w - ({\rho}UUA)_e + (pA)_w - (pA)_e + F }[/math]

Next we apply the assumptions of steady incompressible flow and zero external force.

[math]\displaystyle{ 0 = ({\rho}UUA)_w - ({\rho}UUA)_e + (pA)_w - (pA)_e + F }[/math]

[math]\displaystyle{ 0 = (UUA)_w - (UUA)_e + \frac{(pA)_w}{\rho} - \frac{(pA)_e}{\rho} + \frac{F}{\rho} }[/math]

[math]\displaystyle{ 0 = (UUA)_w - (UUA)_e + \frac{(pA)_w}{\rho} - \frac{(pA)_e}{\rho} }[/math]

At this point, depending on the location of cell P, we would continue by applying either

• Boundary conditions for faces on the boundary, or
• An interpolation scheme (often linear) for internal faces.

Then we would calculate the coefficients of the matrix, and either invert the matrix or use an iterative method to solve it. For brevity, I will not go through this process, as the general process is similar with the continuity equation.

Optional exercise: try applying these steps with

• Zero pressure gradient on the left boundary,
• Fixed pressure of 0 on the right boundary,
• The solution found in the previous section for U.

You should find that the pressure everywhere is 0 Pa.

Optional: The energy equation

In case we also wanted to find the temperature of the fluid throughout the domain, we could solve the energy equation: rate of change of energy at a given point = rate of energy flow in - rate of energy flow out. I will not go through the derivation here - it is enough to know that the CFD solver performs an iterative approach to solve for temperature using the conservation of energy until the residual is low enough.

In the case of an incompressible flow, this isn't necessary, since density is constant. But for a compressible flow, the density at a given location is a function of temperature, so it is necessary to find the temperature everywhere in the fluid, so that the density can be found.

Optional: Higher dimensions

• In this example, we have been solving for velocity in the x direction by applying conservation of momentum in just one direction - the x axis.
• In 2D, we must also solve for velocity in the y direction. For this, we will apply conservation of momentum in the y axis.
• Similarly in 3D, we need to solve the momentum equation in all three axes: x, y, and z to obtain the components of velocity in each direction.
• The momentum equation can be generalised to work in arbitrary dimensions - the process isn't important for now, although you should know that the spatial derivatives (e.g. [math]\displaystyle{ \frac{\partial}{\partial x} }[/math]) are written with different notation, resulting in some terms called the gradient, the divergence, and the laplacian of a variable. This is called vector calculus - I recommend this Khan Academy course, if this is unfamiliar to you.

Optional: Viscosity and turbulence

We ignored the effects of viscosity, but this is straightforward to include in the momentum equation, simply by adding an extra force to the equation to account for viscosity.

We ignored turbulence in the momentum equation for this example, but real flows often exhibit turbulence ("random" fluctuations), especially at high speeds and low viscosities. Since the effect of turbulence is to increase mixing between layers, it can be modelled using a modified viscosity. This modified viscosity is the sum of the ordinary viscosity and the turbulent viscosity - this turbulent viscosity is calculated at every location in the mesh by a turbulence model. The turbulence models calculate some variables which quantify the turbulence at every location, and use those variables to calculate the turbulent viscosity. Some common turbulence models include (along with some broad pros & cons):

• K-epsilon model: best for use when the cells are quite large ("coarse") near the walls, and for preliminary simulations.
• K-omega model: requires smaller (finer) cells near the walls in order to work best. Generally more accurate than K-epsilon, but more computationally expensive, and requires a finer mesh. Is also more sensitive to boundary conditions than K-epsilon.
• K-omega SST (Shear Stress Transport) model: a combination of the K-epsilon and K-omega models, with an added shear stress transport model. Generally more accurate than K-omega and K-epsilon, but requires a finer mesh and is more computationally expensive than K-epsilon.

Optional: Stability tips

• CFD simulations can sometimes have variables blow up to infinity or show unphysical oscillations in the flow, if care is not taken with the setup process. The stability of a simulation (i.e. how likely it is to avoid blowing up) can be influenced by choice of numerical scheme, the quality of the mesh, and the selection of boundary conditions.
• In OpenFOAM, each operation has its own numerical scheme selection - for example:
  • Interpolation (we used the linear scheme for this operation in the example above),
  • Gradient,
  • Divergence - this one is particularly influential to stability,
  • Laplacian.
• Details on the selection of which scheme to use is beyond the scope of this section, but a good rule-of-thumb is that less accurate schemes (e.g. upwind interpolation) tend to be more stable, and vice versa. Gradient limiters can also be used to add stability at the expense of accuracy.
• Meshing is not as straightforward as shown here, especially with more complicated geometries. Sometimes, poor quality meshes can cause problems with the simulation. There are numbers that meshing software can calculate to represent the quality of a mesh (called a mesh quality metric).
  • For example, meshes with orthogonal cells perform better than those with non-orthogonal cells. In our example, all the cells were perfectly orthogonal - that is, the faces were perpendicular to the lines between the adjacent cell centroids.
  • How close the cells are to having perpendicular faces is called the orthogonal quality in ANSYS.
  • In OpenFOAM, the opposite of this is given as the non-orthogonality angle.
  • Other examples include cell skewness (lower is better) and cell aspect ratio (closer to 1 is better). It is important to ensure these quality metrics are not too bad, otherwise the stability and accuracy of the simulation can be affected.

Optional: Common tripping points

The solution vector [math]\displaystyle{ \boldsymbol{U} }[/math] does not store the components of velocity, i.e. [math]\displaystyle{ U_x, U_y, U_z }[/math], but instead stores the velocities at each cell centroid, i.e. [math]\displaystyle{ U_1, U_2, U_3, U_4 }[/math]. Indeed, the solution vector [math]\displaystyle{ \boldsymbol{U} }[/math] summarises the x-velocity at every point in our domain, while hypothetically the scalars [math]\displaystyle{ U_x, U_y, U_z }[/math] would only specify the 3D velocity at one point. Since we are currently only concerned with x-velocity, this might be more clear, but in higher dimensions it is important not to get confused.

The term [math]\displaystyle{ p/\rho }[/math] is sometimes called the kinematic pressure. When an incompressible fluid is used, it is sometimes what the CFD software (e.g. OpenFOAM) will confusingly call p. So when finding the pressure drop, you may have to multiply by density. The best way to check whether you need to multiply by density, is to look at the units of p that the CFD software gives you. Ordinary pressure has units [math]\displaystyle{ kgm^{-1}s^{-2} }[/math], while kinematic pressure has units [math]\displaystyle{ m^{2}s^{-2} }[/math].

Optional: Further reading

Hopefully this has been an understandable / intuitive explanation of roughly what most CFD solvers do. If you want to explore the topics mentioned here in more detail, here are some resources that might help:

• RECOMMENDED: An Introduction to Computational Fluid Dynamics: The Finite Volume Method - commonly known as just "Versteeg" - https://books.google.co.uk/books/about/An_Introduction_to_Computational_Fluid_D.html?id=RvBZ-UMpGzIC
  • Absolutely brilliant. Please read either this or Moukalled before anything else.
  • It is usually behind a paywall, but you can sometimes find an old freely available copy by simply googling versteeg cfd filetype:pdf
• RECOMMENDED: The Finite Volume Method in Computational Fluid Dynamics - commonly known as just "Moukalled" - https://link.springer.com/book/10.1007/978-3-319-16874-6
  • Slower paced than Versteeg - recommended for those who are a little shaky on their fluid dynamics knowledge. Also contains some more OpenFOAM-specific knowledge.
  • It is usually behind a paywall, but you can sometimes find an old freely available copy by simply googling moukalled cfd filetype:pdf
• Fluid Mechanics 101 - YouTube channel: https://www.youtube.com/channel/UCcqQi9LT0ETkRoUu8eYaEkg/
  • Has some very well explained and illustrated videos on a random selection of CFD topics.
• ANSYS Fluent Theory Guide - find it with google.
  • Usually a bit easier to find a copy of, but isn't ideal for someone who isn't already familiar with CFD and the finite volume method. See Versteeg for that.
• OpenFOAM: A little user manual - https://github.com/ParticulateFlow/OSCCAR-doc/blob/master/openFoamUserManual_PFM.pdf
  • More specific to OpenFOAM and its code syntax, but contains some discussion of the fundamental algorithms which are used everywhere, e.g. SIMPLE, PISO, PIMPLE, as well as some turbulence models.
• OpenFOAM wiki - http://openfoamwiki.net/index.php/Main_Page
  • Contains some useful derivations of equations as well as tips & tricks, but is a bit hit-and-miss in quality and ease of navigation.

Fluid-structure interaction (FSI)

FSI installation instructions here

This technique allows complex interactions between flexible structures and fluid flows. This has been used to predict fin flutter at hypersonic speeds for Griffin 1.

Simulations of this kind are achievable with the combination of the following free open-source software packages:

• OpenFOAM (website, OpenFOAM installation instructions here) - a C/C++ library for the solution of fluid mechanics problems formulated with the Finite Volume Method (FVM),
  • Important: there are two main versions of OpenFOAM, provided at OpenFOAM.com and OpenFOAM.org. I have only used the .com version, but everything here should also be possible with the .org version.
• FEniCS (website) - a Python interface to the DOLFIN C++ library for the solution of solid mechanics problems formulated with the Finite Element Method (FEM), and
• preCICE (website) - a very powerful library which allows the coupling of arbitrary solvers using human-readable syntax.
  • Note: in order to use OpenFOAM and FEniCS with preCICE, it is also necessary to download their respective adapters. See this page for OpenFOAM and this page for FEniCS from the preCICE website for further information.

Step-by-step instructions

IMPORTANT: Although I hope that these instructions will be easily understood by anyone, this is not a beginner's project! If you want a better introduction to CFD, please read the crash-course section above, or any of the linked resources.

This section has moved to a separate page.