Notes on preCICE

Compatible preCICE versions

The latest version of the adapter is always designed for the latest version of preCICE. In particular, the adapter works with preCICE v2, but not with preCICE v1 anymore.

Please remember: If you are using preCICE as a static library, you need to specify its dependencies when building the adapter. These are described in the building instructions of preCICE.

Notes on preCICE features

The adapter is developed with all the features of preCICE in mind. However, some specific features are not yet fully supported.

Nearest-projection mapping

The nearest-projection mapping in the adapter is for CHT cases fully supported. Details can be found in the nearest-projection tutorial case.

For FSI cases, OpenFOAM acts as a fluid participant and in standard FSI calculations, only the Solid participant needs to provide mesh connectivity information. Hence, the connectivity in the Fluid participant is not needed and it is not implemented for FSI.

Checkpointing

In the case of implicit coupling, the participants are required to store checkpoints of their state. The adapter tracks all the registered objects of type volScalarField, volVectorField, surfaceScalarField and surfaceVectorField. After reading a checkpoint, the boundaries are evaluated again for all the tracked volScalarField and volVectorField objects, to improve the stability.

However, there is a known bug in the current implementation, where trying to evaluate the boundaries after reading a checkpoint, for some fields, will lead to an error. This is currently known to happen only for the epsilon field of the kEpsilon turbulence model. In case this field is available, it is not tracked and a warning is reported. Please let us know if this happens in any other case. (See issue #4)

You may also disable the evaluation of the boundaries after reading a checkpoint, by using the evaluateBoundaries false option. (See Configuration)