OpenFOAM v2212 リリースノート
OpenCFD is pleased to announce the December 2022 release of OpenFOAM® v2212. This release extends OpenFOAM-v2206 features across many areas of the code. The new functionality represents development sponsored by OpenCFD's customers, internally funded developments, and integration of features and changes from the OpenFOAM community.
OpenFOAM is distributed by OpenCFD under the GPL License. In addition to source code packages suitable for compilation on a variety of Linux and other POSIX systems, this release also has a number of pre-compiled binary packages
- Ubuntu Linux: packaged installation for Ubuntu 22.04 (LTS), 20.04 (LTS), 18.04 (LTS), 22.10
- openSUSE Linux: packaged installation for Leap15.4, Leap15.3
- Redhat Linux variants: packaged installation for CentOS/Rocky 8, 7 and Fedora 37, 36, 35, ...
Windows users have three options for pre-compiled packages (more information):
- Using Windows Subsystem for Linux (based on Ubuntu, openSUSE etc.)
- Native executables with cross-compiled
- A docker installation
OpenFOAM apptainer support is provided via description files rather than pre-assembled images
- See packaging/containers
Mac OSX users have the option to compile from source, or use Docker containers for pre-compiled packages (more information).
v2212 User Upgrade Guide
Changes in behaviour
timeActivatedFileUpdate
For timeActivatedFileUpdate
, missing files are now treated as a critical error (FatalIOError). These were previously treated as a simple error (FatalError), which downgrades to a Warning only when loading a functionObject and meant that configuration errors would not be noticed.
Spalart-Allmaras DES models
For SpalartAllmaras
-based DES
models, the previously-active ft2
term is deactivated by default. Its activation can now be managed using the new optional ft2
entry which is false
by default.
Input Dictionaries
Force, Force coefficients
More consistent handling of priorities for binModels, forces. If the dictionaries are overspecified, give a coordinateSystem
entry a higher prioriy than the CofR
shortcuts.
Streamline Improvements
Some of the streamline handling has been further refined (eg, barycentric coordinates in interpolation instead of x/y/z). In the process the input requirements has been relaxed:
- default tracking direction is 'forward'
- The
U
(velocity) field doesn't need to be named in the sampled fields.
Improved handling of coordinateSystems
Wherever the coordinate system definition is embedded within a sub-dictionary scope the origin
keyword is now optional. For example,
dict1
{
coordinateSystem
{
origin (0 0 0); // now optional here
rotation ...;
}
}
However, it remains mandatory if constructed without a sub-dict. For example,
dict2
{
origin (0 0 0); // still mandatory
e1 (1 0 0);
e3 (0 0 1);
}
With this change, the transform sub-dictionary can be written more naturally:
formatOptions
{
vtk
{
scale 1000; // m -> mm
transform
{
rotationCentre (1 0 0);
rotation axisAngle;
axis (0 0 1);
angle -45;
}
}
}
Deprecated entries in histogram
The setFormat
and formatOptions
entries have been silently deprecated from the histogram
function object.
Changes in utilities
Updated option names for transformPoints
and surfaceTransformPoints
New options -auto-centre
and -centre
replace -auto-origin
and -origin
, respectively (old options still accepted as compatibility aliases). Changing to -centre
avoids possible confusion in meaning with coordinate system origin()
.
effectivenessHeatExchangerSource
The effectivenessHeatExchangerSource
fvOption has been renamed to heatExchangerSource
. Its previous behaviour can be recovered by using the heatExchangerSource
with the submodel of effectivenessTable
.
histogram
The histogram
function object has been refactored. Its previous behaviour can be recovered by using the histogram
with the submodel of equalBinWidth
. Also, output files per time-step are replaced with a single output file.
v2212 Developer Upgrade Guide