Dear all,
We were testing the new binary boundary file functionality in 3D v7p2r0, and we found that only a small number of boundary points were actually given values, and the other boundary points received zero velocity and tracer values. After some code-digging, we found that the problem may be due to line 227 in read_bin_frliq.f:
IF(NUMLIQ%I(IPTFR).EQ.0) EXIT
Sometimes, there are still non-zero boundary points after the first point with NUMLIQ%I(IPTFR).EQ.0 and so those are skipped. If we change the EXIT command to cycle, i.e.
IF(NUMLIQ%I(IPTFR).EQ.0) CYCLE
then everything works alright.
We generated our binary boundary file using the Pythonscript convertToBND.py from v7p2r0.
Anyone else experienced this issue?