[RobertHB]

Question is related to this one.

I'm using a mesh where the cyclic boundaries do not have the same number of faces and not in the same location. I got the meshing process working by using cyclicAMI instead of cyclic. For the blockMesh, where the two patches are the same size, it is no problem to start a solver. However, after running snappyHexMesh and implementing a surface topography, the solver stops after calculating the courant number, but no error is given. So, the mesh can't be that wrong.

Did anybody experience a similar problem and knows a solution to it?

PISO: Operating solver in PISO mode

Reading field p

AMI: Creating addressing and weights between 1128 source faces and 1503 target faces
AMI: Patch source sum(weights) min/max/average = 0, 1.12692, 0.959816
AMI: Patch target sum(weights) min/max/average = 0, 1.10355, 0.951041
Reading field U

Reading/calculating face flux field phi

Selecting incompressible transport model Newtonian
Selecting turbulence model type laminar
Selecting laminar stress model Stokes
No MRF models present

Creating finite volume options from "constant/fvOptions"

Selecting finite volume options model type meanVelocityForce
    Source: momentumSource
    - selecting all cells
    - selected 399802 cell(s) with volume 23.2754
    Initial pressure gradient = 0

Starting time loop

Time = 1e-07

Courant Number mean: 2.05302e-09 max: 1.85352e-08