An object-oriented Computational Fluid Dynamics(CFD) toolkit
Description
OpenFOAM core is an extensible framework written in C++, i.e. it provides a sufficient abstraction for a programmer to build their own code for an underlying mathematical model.
Prerequisites
OpenFOAM is a free, open source software which is released under the GNU-GPL license
Modules
The following versions of OpenFOAM are installed in HLRN system
OpenFOAM version | OpenFOAM module file | Requirements | HLRN Site |
---|---|---|---|
v4 | openfoam/gcc.9/4 | gcc/9.2.0, openmpi/gcc.9/3.1.5 | Berlin, Goettingen |
v5 | openfoam/gcc.9/5 | gcc/9.2.0, openmpi/gcc.9/3.1.5 | Berlin, Goettingen |
v6 | openfoam/gcc.9/6 | gcc/9.2.0, openmpi/gcc.9/3.1.5 | Berlin, Goettingen |
v7 | openfoam/gcc.9/7 | gcc/9.2.0, openmpi/gcc.9/3.1.5 | Berlin, Goettingen |
v8 | openfoam/gcc.9/8 | gcc/9.2.0, openmpi/gcc.9/3.1.5 | Berlin |
v1912 | openfoam/gcc.9/v1912 | gcc/9.2.0, openmpi/gcc.9/3.1.5 | Berlin, Goettingen |
v2012 | openfoam/gcc.9/v2012 | gcc/9.2.0, openmpi/gcc.9/3.1.5 | Berlin |
v2112 | openfoam/gcc.9/v2112 | gcc/9.3.0, openmpi/gcc.9/* | Berlin |
The module name is openfoam. Other versions may be installed. Inspect the output of : module avail openfoam
Example Jobscripts
The next example is derived from https://develop.openfoam.com/committees/hpc/-/wikis/HPC-motorbike. It utilizes two full nodes and has collated file I/O. All required input/case files can be downloaded here: motorbike_with_parallel_slurm_script.tar.gz.
Some important advice when running OpenFOAM on a supercomputer
Typically, OpenFOAM causes a lot of meta data operations. This default behavior jams no only your job but may slow down the shared parallel file system (=Lustre) for all other users. Also, your job is interrupted if the limit of the quota system (type hlrnquota) is exceeded.
If you can not use our local 2TB-SSDs (see Special Filesystems) #SBATCH --partition={standard,large,huge}96:ssd at $LOCAL_TMPDIR please refer to our general advices to reduce Metadata Usage on WORK (=Lustre).
To adapt/optimize your OpenFOAM job specifically for I/O operations on $WORK (=Lustre) we strongly recommend the following steps:
Always, to avoid that each processor writes in its own file please use collated file I/O.
This feature was released 2017 for all OpenFOAM versions.
[ESI www.openfoam.com/releases/openfoam-v1712/parallel.php]
[Foundation www.openfoam.org/news/parallel-io]OptimisationSwitches { fileHandler collated; // all processors share a file }
to the /.OpenFOAM/v#/controlDict file or per-case override in the $FOAM_CASE/system/controlDict file.
Always, set
runTimeModifiable false;
to reduce I/O activity. Only set "true" (default), if it is strictly necessary to re-read dictionaries (controlDict, ...) each time step.
Possibly, do not save every time step:
[www.openfoam.com/documentation/guides/latest/doc/guide-case-system-controldict.html]
[www.cfd.direct/openfoam/user-guide/v6-controldict]writeControl timeStep; writeInterval 100;
Possibly, save only the latest n time steps (overwrite older ones), such as:
purgeWrite 1000;
Typically, only a subset of variables is needed frequently (post-processing). The full set of variables can be saved less frequently (e.g., restart purposes). This can be achieved with [https://wiki.bwhpc.de/e/OpenFoam]:
writeControl clockTime; writeInterval 21600; // write ALL variables every 21600 seconds = 6 h functions { writeFields { type writeObjects; libs ("libutilityFunctionObjects.so"); objects ( T U // specified variables ); outputControl timeStep; writeInterval 100; // write specified variables every 100 steps } }
In case your HLRN run accidentally generated thousands of small files, please pack them (at least the small-size metadata files) into a single file afterwards:
tar -xvzf singlefile.tar.gz -C /folder/subfolder/location/
Thanks a lot for your contribution making HLRN a great place for all...
Compiling Own Code Over OpenFOAM
...
OpenFOAM Best Practices
...