OpenFOAM: Difference between revisions
No edit summary |
(Marked this version for translation) |
||
Line 70: | Line 70: | ||
Mesh preparation (<code>blockMesh</code>) may be fast enough to be done at the command line (see [[Running jobs]]). The solver (<code>icoFoam</code> and others) is usually the most expensive step and should always be submitted as a Slurm job except in very small test cases or tutorials. | Mesh preparation (<code>blockMesh</code>) may be fast enough to be done at the command line (see [[Running jobs]]). The solver (<code>icoFoam</code> and others) is usually the most expensive step and should always be submitted as a Slurm job except in very small test cases or tutorials. | ||
=== Segfaults with OpenMPI 3.1.2 === | === Segfaults with OpenMPI 3.1.2 === <!--T:16--> | ||
<!--T:17--> | |||
Users have reported random segfaults on Cedar when using OpenFOAM versions compiled for OpenMPI 3.1.2 in single-node jobs (shared memory communication). These issues seem not to happen with other versions of OpenMPI. If you experience such problems, first try to use an OpenMPI 2.1.1-based toolchain. For example: | Users have reported random segfaults on Cedar when using OpenFOAM versions compiled for OpenMPI 3.1.2 in single-node jobs (shared memory communication). These issues seem not to happen with other versions of OpenMPI. If you experience such problems, first try to use an OpenMPI 2.1.1-based toolchain. For example: | ||
<!--T:18--> | |||
{{Commands | {{Commands | ||
|module load gcc/5.4.0 | |module load gcc/5.4.0 |
Revision as of 21:29, 20 January 2020
The OpenFOAM (Open Field Operation and Manipulation) CFD Toolbox is a free, open source software package for computational fluid dynamics. OpenFOAM has an extensive range of features to solve anything from complex fluid flows involving chemical reactions, turbulence and heat transfer, to solid dynamics and electromagnetics.
Module files[edit]
To load the recent version, run
[name@server ~]$ module load openfoam
The OpenFOAM development community consists of:
- The OpenFOAM Foundation Ltd., with web sites openfoam.org and cfd.direct
- OpenCFD Ltd., with web site openfoam.com
Up to version 2.3.1, released in December 2014, the release histories appear to be the same. Compute Canada module names after 2.3.1 which begin with "v" are derived from the .com branch (for example, openfoam/v1706); those beginning with a digit are derived from the .org branch (for example, openfoam/4.1).
See Using modules for more on module commands.
Documentation[edit]
OpenFOAM.com documentation and CFD Direct user guide.
Usage[edit]
OpenFOAM requires substantial preparation of your environment. In order to run OpenFOAM commands (such as paraFoam
, blockMesh
, etc), you must load a module file.
Here is an example of a serial submission script for OpenFOAM 5.0:
#!/bin/bash
#SBATCH --time=00:01:00
#SBATCH --account=def-someuser
module purge
module load openfoam/5.0
blockMesh
icoFoam
Here is an example of a parallel submission script:
#!/bin/bash
#SBATCH --account=def-someuser
#SBATCH --ntasks=4 # number of MPI processes
#SBATCH --mem-per-cpu=1024M # memory; default unit is megabytes
#SBATCH --time=0-00:10 # time (DD-HH:MM)
module purge
module load openfoam/5.0
decomposePar
blockMesh
setFields
srun interFoam -parallel
Mesh preparation (blockMesh
) may be fast enough to be done at the command line (see Running jobs). The solver (icoFoam
and others) is usually the most expensive step and should always be submitted as a Slurm job except in very small test cases or tutorials.
Segfaults with OpenMPI 3.1.2[edit]
Users have reported random segfaults on Cedar when using OpenFOAM versions compiled for OpenMPI 3.1.2 in single-node jobs (shared memory communication). These issues seem not to happen with other versions of OpenMPI. If you experience such problems, first try to use an OpenMPI 2.1.1-based toolchain. For example:
[name@server ~]$ module load gcc/5.4.0
[name@server ~]$ module load openmpi/2.1.1
[name@server ~]$ module load openfoam/7
Performance[edit]
OpenFOAM can emit a lot of debugging information in very frequent small writes (e.g. hundreds per second). This may lead to poor performance on our network file systems. If you are in stable production and don't need the debug output, you can reduce or disable it with:
[name@server ~]$ mkdir -p $HOME/.OpenFOAM/$WM_PROJECT_VERSION
[name@server ~]$ cp $WM_PROJECT_DIR/etc/controlDict $HOME/.OpenFOAM/$WM_PROJECT_VERSION/
Then edit the debugSwitches
dictionary in $HOME/.OpenFOAM/$WM_PROJECT_VERSION/controlDict
, changing flags from values >0 to 0. (Contribution from C. Lane)