OpenFOAM and the OpenFOAM community offer several solutions for conjugate heat transfer, fluid-structure interaction, and other coupled multi-physics problems. These include the intinsic chtMultiRegionFoam solver, solids4foam, and more. An important advantage of these solutions is that they are OpenFOAM-internal, and therefore familiar to OpenFOAM users. They are, however, also OpenFOAM-specific. Since many of these solutions are numerically partitioned (even if implemented in the same software unit), a question raises on whether we could simulate some of the regions in external simulation software, combining features of OpenFOAM with those of third-party codes (such as completely different discretization methods), or just features of different OpenFOAM versions (such as different physical models). The open-source, massively parallel coupling library preCICE allows coupling arbitrary simulation codes, providing a high-level API in C++, C, Fortran, Python, MATLAB, and Julia, as well as ready-to-use integrations with OpenFOAM, CalculiX, deal.II, FEniCS, Nutils, SU2, code aster, and more. As an OpenFOAM function object, the integration with OpenFOAM allows using preCICE in standard OpenFOAM solvers without any code modifications. It has been in development since a long time, while a related article has recently been published at the OpenFOAM Journal. This talk will give an overview of alternative coupling approaches, recap the basic features of the OpenFOAM-preCICE adapter, and will present validation and performance-related results first discussed in the recent OpenFOAM Journal publication [4]. It will also give a first overview of new features, such as support for volume coupling, and recent extensions to the fluid-fluid coupling feature.     «

OpenFOAM and the OpenFOAM community offer several solutions for conjugate heat transfer, fluid-structure interaction, and other coupled multi-physics problems. These include the intinsic chtMultiRegionFoam solver, solids4foam, and more. An important advantage of these solutions is that they are OpenFOAM-internal, and therefore familiar to OpenFOAM users. They are, however, also OpenFOAM-specific. Since many of these solutions are numerically partitioned (even if implemented in the same software...     »