[sita]

SORRY, SOLVED THIS ALREADY!!



Dear all,


Last week I installed OpenFOAM-dev (build dev-54cb927cee89) on a Scientific Linux cluster, next to our existing OpenFOAM-5.x (buid 5.x-019c14b8cf0a). The tutorials I tested so far all run fine, but when I run renumberMesh or decomposePar on one of my own cases, it results in an error: keyword UnMean is undefined in dictionary ..../0/U.boundaryField._xmin


This keyword is undefined indeed, but that's because I'm not using it anywhere, it's a variable that I used for some test a few weeks ago and then removed.


Using OpenFOAM-5.x on the same case, I don't get this error when running renumberMesh or decomposePar, but apparently OpenFOAM-dev keeps finding this keyword in 0/U.boundaryField._xmin, even after I created an entirely new 0/U.


So now I'm wondering: how can I view/edit 0/U.boundaryField.<patch name>? And what should I do to prevent OpenFOAM-dev from running into this old variable?


Many thanks,
Sita


EDIT: It turns out that the keyword Umean in OpenFOAM-5.x has changed into UnMean in OpenFOAM-dev, so it wasn't an old variable name after all...