Skip to content

wall distance does not correct point-connected cells or multi-patch cells

Summary

wall distance models optionally correct wall-connected cells. This includes cells with only a point on the boundary. This might be broken since 056bb4f0. Additionally will behave differently if patch is split into multiple patches.

Steps to reproduce

  • start off from e.g. cavity. Skew mesh a bit.
  • make movingWall, fixedWalls type wall
  • run checkMesh -writeFields '(wallDistance)' with e.g. meshWave` as wall distance method (in fvSchemes)
  • check that corner cells (= on two patches) use both patches i.e. look across patches
  • split cells into tets
  • any cell with a point but not face on a wall should have different values depending on correctWalls setting

Example case

What is the current bug behaviour?

What is the expected correct behavior?

Relevant logs and/or images

Environment information

  • OpenFOAM version : v2406

Possible fixes

  1. loops inside cellDistFuncs do not check across patches

  2. (From visual inspection) cellDistFuncs::correctBoundaryPointCells checks duplicate baffle behaviour (used in cyclicACMI) but uses incorrect logic. If polyPatch::areaFraction is null the patch is a normal patch. Only if it is set.