v2406: OpenFOAM Community

New submodule: Data-Driven Modelling SIG repository

TOP

A new community submodule has been launched to include a collection of nested submodules from the Data-Driven Modelling Special Interest Group within the OpenFOAM Governance. The submodule is hosted in the public Data-Driven Modelling Special Interest Group repository.

The community submodule serves as a host for academic and industrial contributions related to CFD and machine-learning models, creating a space for knowledge exchange and fostering collaboration.

Prospective contributions can be hosted on any git-based source code repository hosting service, such as Bitbucket or GitHub, and linked to the OpenFOAM software through this submodule.

In this release, we are pleased to announce the release of the following submodules:

 

Source code

Attribution

  • OpenCFD would like to acknowledge and thank the data-driven modelling special interest group members; Weishuo Liu and their colleagues for their valuable contributions and assistance.

New contributions to the Turbulence TC repository

TOP

We are pleased to announce the release of the following six repositories under the umbrella of the Turbulence Technical Committee repository:

Source code

Attribution

OpenCFD would like to acknowledge and thank

  • the Turbulence Technical Committee
  • Matheus Macedo, Chenyu Wu, Yufei Zhang Michael Alletto, Mario J. Rincón, Alberto Passalacqua, Eleonora Gajetti, and their colleagues for their valuable contributions and assistance.

Thank you

TOP

A big Thank you to the following people who contributed to OpenFOAM.

Special thanks

 

  • Nilsson (Hakan Nilsson) turbomachinery test case contributions including the rotating axial turbine tutorial using meshing in cylindrical coordinates and simulation with periodic boundary conditions.
  • Johan Rønby Pedersen: Helping us for multiphase-framework parallelisation
  • Markus Nordlund: Helping us with technical discussions involving fluid-porous interface modelling.

 

Contributions to the issue tracking: