[CFDFoundation]

The OpenFOAM Foundation is pleased to announce the release of version 5.0 of the OpenFOAM open source CFD toolbox. Version 5.0 is a snapshot of the OpenFOAM development version that is “always-releasable” quality, through rapid-turnaround feedback between code maintainers and users. It provides new functionality and major improvements to existing code, with strict demands on usability, reliability and maintainability. It is produced for the benefit of all users, rather than a handful of commercial organisations.

Version 5.0 is a new major version release in which some backward compatibility to OpenFOAM version 4 is not maintained (requiring some changes to case input files), containing 816 code commits since version 4.0. OpenFOAM 5.0 uses all features of the ISO/IEC 14882:2011 (C++11) standard, and has been tested with C++ compilers that conform to that standard, such as GCC v4.8+, Clang v3.7+ and Intel ICC v17.0.4+.
OpenFOAM 5.0 is distributed under the General Public Licence by the OpenFOAM Foundation for:

• Ubuntu Linux: packaged installation for Ubuntu 14.04, 16.04 and 17.04;
• Other Linux: installation with a Docker container; or compilation from source code;
• Windows 10: installation using Windows Subsystem for Linux with Ubuntu packs;
• macOS: installation with a Docker container.

Multiphase for Marine/Offshore Engineering

• Wave Modelling: implemented boundary conditions for applying waves at an inlet that meets standards of code quality, maintainability and licensing
• Wave Initialisation: new setWaves utility for initialising waves
• Wave Damping: new verticalDamping fvOption damps the vertical motions of an interface in the region approaching an outlet to avoid reflections
• Data Processing: a interfaceHeight function object reports height of a phase interface from a set of locations
• Hull: new interfaceCompression boundary condition improves cases where a fluid interface hits a surface at shallow angle

Further Information: “Water Waves in OpenFOAM”.

General Multiphase

• Performance/Numerics: increased robustness of multiphase solvers through improved inflow/outflow boundary conditions; better restart and more efficient Crank-Nicolson implementation for interFoam family of solvers; introduced a limiter to stabilise the interfacial pressure work term in the energy equation for multiphase flows; improved mass conservation in compressibleInterFoam using continuity error correction; improved calculation of MULES limiter at walls; for setWaves, generalised tetrahedron and triangle cutting, enabling cutting with level-sets as well as planes; added functions for volume averaging of discontinuous fields
• Surface Tension Modelling: new framework for runtime-selectable surface tension models in the interfaceProperties library; convenient handling of temperature-dependent surface tension through liquidProperties class; new temperatureDependentContactAngleForce model added to surface film functionality
• Film Modelling: new experimental compressibleInterFilmFoam multiphase solver supporting transfer between volume of fluid interface capturing and film approximation

Transport and Turbulence Modelling

• Viscosity Modelling: new general strainRateFunction, non-Newtonian viscosity model where users can select the function at run-time using the Function1 functions, such as table, csvFile, polynomial, etc.; new Casson model for blood rheology, see User Guide 7.3
• Laminar Stress Models: new generalised framework for laminar stress models including linear, non-linear, viscoelastic, etc.; new framework for viscoelastic modelling including Maxwell and Oldroyd-B models
• Turbulence Models: Reynolds Stress turbulence supported in VoF and other incompressible multiphase solvers; corrected k-omega SST Sato model; corrected C3 dilatation term in turbulence modelling for compressible flows; improved low-Reynolds number behavior in omegaWallFunction and epsilonWallFunction

Particles and Tracking

• Tracking: completely replaced the existing tracking, which failed for meshes whose decomposition into tetrahedra (tets) include “negative” tets; the replacement, known as barycentric tracking, is reliable on any mesh, irrespective of tet quality; optimised the averaging methods in MPPIC using particle barycentric coordinates for 2x speed up; changed interpolation for particles to use the barycentric coordinates, making it much faster and more reliable
• Particle Injection: created the massRosinRammler distribution to handle varying number of particles per parcel for fixed-mass parcels
• Optimisation: added solveFlow switch to freeze the flow field, but keep the particles running, in sprayFoam

Further Information: “OpenFOAM Barycentric Tracking”.

Combustion

• TDAC/ISAT: new TDACChemistryModel chemistry model providing Tabulation of Dynamic Adaptive Chemistry (TDAC); new Eddy Dissipation Concept (EDC) turbulent combustion model, including support for TDAC/ISAT for efficient chemistry; added variable time-step and local time stepping (LTS) in ISAT for TDAC chemistry
  
• Other: new limiting of local time step (for solving steady-state) to specie reaction rate in reactingFoam; support for isothermal, compressible flow in reactingEulerFoam; reactions can optionally be enabled only in a specified list of cellZones.

Meshes

• snappyHexMesh: improved input syntax for triSurfaceMesh files; stopped writing of redundant files that break other applications and waste disk space
• blockMesh: new point/edge projection onto geometric surfaces, see User Guide 5.3.3; new sloshingCylinder tutorial, demonstrating projection to create a cylindrical background mesh; added block face orientation checks to aid debugging; updated blockMeshDict files to use multi-grading in the pitzDaily tutorials, see User Guide 5.3.1.4
• refineMesh: corrected parallel operation
• Mesh Motion: new template cylindrical background mesh significantly improves robustness and accuracy of rotating geometry simulations; added mesh-motion solver for multiple moving regions, e.g. for 2 counter-rotating AMI regions; added dynamic mesh versions of DPMDyMFoam and MPPICDyMFoam solvers; improved 2nd-order time discretisation schemes for moving meshes; improved stability by bounding the localEuler time scheme for steady-state cases with mesh-motion

Energy, Heat Transfer and Thermophysical Modelling

• Liquid Thermophysical Modelling: rewritten thermophysical modelling to make solid/liquidProperties and specie classes compatible; simplified and generalized the user interface for liquid properties; added general fluidThermo model to enable run-time selection of thermophysical model type; added equation of state for the Boussinesq approximation for buoyant flows, see User Guide 7.1.5
• Compressible solvers: made rhoSimpleFoam (steady flow) work with any thermophysical model including liquids and more stable; added support for transonic flow of liquids and real gases in rhoPimpleFoam and improved stability and convergence
• Other: combined functionality and improved usability of externalWallHeatFluxTemperature boundary condition and changed ambient temperature (Ta) to support time variation; added radiation modelling fvOption that can be used in any simulation where energy is solved; added support for residual convergence controls to chtMultiRegionFoam

Parallel I/O

• new collated file format introduced in which the data for each decomposed field (and mesh) is collated into a single file that is written (and read) on the master processor
• new masterUncollated option writes data with the original uncollated format without NFS
• file writing can be threaded allowing the simulation to continue running while the data is being written to file: see “Threading Support”

Further Information: “OpenFOAM Parallel I/O”

Productivity and Usability

• Data Visualisation: updated the native OpenFOAM reader module for ParaView version 5.4.0; maintenance of the native reader module ensures continued trouble-free visualisation of OpenFOAM data.
• Command Line Interface: added Bash [TAB] completion to all OpenFOAM applications and scripts; added -list... options, e.g. -listScalarBCs in solvers for more relevant listing of BCs, fvOptions, turbulence models, etc (as a replacement to foamList), see User Guide 5.2.3; enabled applications running with the -doc option, e.g. paraFoam -doc, to open the application documentation at http://cpp.openfoam.org
• Case Management: foamCloneCase can now clone cases from configuration directories, and copy script files and 0.orig directories; major maintenance of scripts, improving -help option and POSIX compliance
• Inlet and outlet: generalised the swirlInletVelocity boundary condition to reads individual velocity components as Function1; new matchedFlowRateOutletVelocity boundary condition which matches the flow rate at outlet to a corresponding inlet
• User Input: input syntax for fvOptions has been made much more user-friendly; made ...Coeffs sub-dictionaries optional for input model parameters; standardised notation in input parameters in radiation boundary conditions
• Parallel Computation: added -copyZero option to decomposePar to copy the 0 directory to processor directories, to avoid field/mesh inconsistencies, especially when generating the mesh in parallel; integrated much faster, scalable reconstructParMesh
• Configured Function Objects: add and subtract fields; XiReactionRate to write reaction-rate fields for the Xi-based combustion models; dsmcFields to write DSM fields; flowRateFaceZone to calculate flow rate through a face zone; streamFunction to calculate stream function; wallHeatFlux to calculate wall heat flux; writeCellVolumes to write out cell volume data and writeCellCentres to write out cell centre data, see User Guide 6.2
• Function1: added a range of generic ramp functions, including linear, quadratic, halfCosine, quarterCosine and quaterSine functions which can be superimposed onto any other function using scale, see User Guide 5.2.3.4; damper function for smoother start-up under an applied impulse in rigidBodyMeshMotion
• “Limiting” fvOptions: limitVelocity to limit the maximum velocity, e.g. to avoid excessive unphysical velocities generated during slamming event; made settings and documentation consistent in limitTemperature

Contributors

OpenFOAM v5.0 was produced by:

• Architect/Lead: Henry Weller
• Management: Henry Weller, Chris Greenshields
• Maintenance/Testing/Contributions: Henry Weller, Chris Greenshields, Will Bainbridge, Mattijs Janssens, Bruno Santos.
• Other Contributions:
  • Combustion: Francesco Contino (+ macOS), Zhiyi Li, Alessandro Parente
  • Reacting Multiphase: Juho Peltola, Alberto Passalacqua, Ronald Oertel
  • Lagrangian: Timo Niemi (+ function objects), Karl Meredith
  • Parallel Running: Paul Edwards, Kevin Nordin-Bates, Alexey Matveichev
  • Heat transfer: Stephan Goeke, Tobias Holtzmann

Thanks to the OpenFOAM enthusiasts who have contributed to a better code through the Issue Tracking System.

To download OpenFOAM 5.0, click here.

[zhangyan]

Hi,
I am using the latest version of OpenFOAM, but I can't show the particles in paraview.
Because the file "positions" is different with the older version.

[CFDFoundation]

The ParaView reader module in OpenFOAM v5 does read the new particle I/O so positions are displayed. You need to use a version of ParaView that includes the reader module from OpenFOAM, e.g. the ParaView that is shipped with OpenFOAM v5. If there is an issue with the ParaView reader module in OpenFOAM, report it on the OpenFOAM Issue Tracking System.

[openfoammaofnepo]

Dear zhangyan,

I met the same problem as you had. When I ran 'paraFoam' in the case directory, I cannot display the particle due to the problems of "position" data. Finally how did you visualize the particles? Thanks!

My question was posted in this thread:
cannot visualize the lagrangian data using Paraview from OpenFOAM 5.0

OFFO

Originally Posted by zhangyan

Hi,
I am using the latest version of OpenFOAM, but I can't show the particles in paraview.
Because the file "positions" is different with the older version.

[CFDFoundation]

The ParaView reader module in OpenFOAM v5 does read the new particle I/O so positions are displayed. You need to use a version of ParaView that includes the reader module from OpenFOAM, e.g. the ParaView that is shipped with OpenFOAM v5, which are compiled with the packages supplied for Ubuntu (see https://openfoam.org/download/5-0-ubuntu/). If there is an issue with the ParaView reader module in OpenFOAM, report it on the OpenFOAM Issue Tracking System.

[openfoammaofnepo]

Thank you very much. I used two versions: one is from blueCFD for windows for my desktop and one for source pack in the HPC cluster. For either of them, is it possible to install the OF reader module in paraview? Or use the paraview with this module? Thanks!

Originally Posted by CFDFoundation

The ParaView reader module in OpenFOAM v5 does read the new particle I/O so positions are displayed. You need to use a version of ParaView that includes the reader module from OpenFOAM, e.g. the ParaView that is shipped with OpenFOAM v5, which are compiled with the packages supplied for Ubuntu (see https://openfoam.org/download/5-0-ubuntu/). If there is an issue with the ParaView reader module in OpenFOAM, report it on the OpenFOAM Issue Tracking System.

[CFDFoundation]

Here are some options that use the OpenFOAM reader module for ParaView:

• We maintain software repositories for the OpenFOAM and third-party software including ParaView, with compilation scripts which work correctly. There are instructions for compiling from source code.
• We provide pre-compiled packages of the software for Ubuntu which work correctly; they can be installed directly on Windows 10.
• We provide images for Docker that provide a self-contained environment that includes code, runtime, system tools and libraries, independent of the underlying operating system. This can be installed on other Linux systems and macOS.

[openfoammaofnepo]

Thank you very much for your suggestions. I will try to resolve this problem following these helpful suggestions.

Originally Posted by CFDFoundation

Here are some options that use the OpenFOAM reader module for ParaView:

• We maintain software repositories for the OpenFOAM and third-party software including ParaView, with compilation scripts which work correctly. There are instructions for compiling from source code.
• We provide pre-compiled packages of the software for Ubuntu which work correctly; they can be installed directly on Windows 10.
• We provide images for Docker that provide a self-contained environment that includes code, runtime, system tools and libraries, independent of the underlying operating system. This can be installed on other Linux systems and macOS.

[openfoammaofnepo]

By the way, why the openfoam package (the latest version, including of50) and paraview from BlueCFD cannot visualize the particle data with paraFoam? Thanks!

[openfoammaofnepo]

Hello,

Thank you very much for your suggestion. I tested the second method, and tried to install ubuntu on Win 10, following the procedures given here: https://openfoam.org/download/windows-10/

Everything is fine now. When I tried to run one tutorial in OpenFOAM 5.0, I go the attached error about "write" permission. Could you please tell me how to fix this issue? Thanks!

Originally Posted by CFDFoundation

Here are some options that use the OpenFOAM reader module for ParaView:

• We maintain software repositories for the OpenFOAM and third-party software including ParaView, with compilation scripts which work correctly. There are instructions for compiling from source code.
• We provide pre-compiled packages of the software for Ubuntu which work correctly; they can be installed directly on Windows 10.
• We provide images for Docker that provide a self-contained environment that includes code, runtime, system tools and libraries, independent of the underlying operating system. This can be installed on other Linux systems and macOS.

[wyldckat]

Originally Posted by openfoammaofnepo

By the way, why the openfoam package (the latest version, including of50) and paraview from BlueCFD cannot visualize the particle data with paraFoam? Thanks!

Quick answers:


blueCFD-Core uses the pre-built version of ParaView from the ParaView.org website, which only provides the built-in reader that ParaView/VTK have got, which are not able to read the particle data from OpenFOAM 5. You would have to run foamToVTK to convert the cases data to VTK format and then open the files inside that folder.


In order for the builds provided with blueCFD-Core to be able to use ParaView to fully open OpenFOAM cases, it would be necessary to build ParaView from source code with MSys2+MinGW-w64, which at the moment is not certain if it will work or not and therefore it is very likely it would be a costly effort on its own. But once ParaView could be built with MSys2+MinGW-w64, it would then be possible to also build OpenFOAM's own reader as an add-on for ParaView, so that it could be binary-compatible.


edit: As for the most recent comment, you should already know this by now, but you should not run the OpenFOAM tutorial cases directly from inside of the original copy of the "tutorials" folder. You should first create a copy of the tutorial case that you want to run. Re-read the second chapter of the OpenFOAM User Guide

[openfoammaofnepo]

Dear Bruno,

Thanks. Finally I use Windows Subsystem for Linux and install the openfoam package within it. It also works very well.

Originally Posted by wyldckat

Quick answers:


blueCFD-Core uses the pre-built version of ParaView from the ParaView.org website, which only provides the built-in reader that ParaView/VTK have got, which are not able to read the particle data from OpenFOAM 5. You would have to run foamToVTK to convert the cases data to VTK format and then open the files inside that folder.


In order for the builds provided with blueCFD-Core to be able to use ParaView to fully open OpenFOAM cases, it would be necessary to build ParaView from source code with MSys2+MinGW-w64, which at the moment is not certain if it will work or not and therefore it is very likely it would be a costly effort on its own. But once ParaView could be built with MSys2+MinGW-w64, it would then be possible to also build OpenFOAM's own reader as an add-on for ParaView, so that it could be binary-compatible.


edit: As for the most recent comment, you should already know this by now, but you should not run the OpenFOAM tutorial cases directly from inside of the original copy of the "tutorials" folder. You should first create a copy of the tutorial case that you want to run. Re-read the second chapter of the OpenFOAM User Guide