[bruce]

Hello all

I have installed OpenFOAM-1.5.x from git and using SnappyHexMesh. But i have a specific reason to use OpenFOAM 1.4.1. But it seems the mesh generated in SnappyHexMesh is not supported in 1.4.1 version?

problem observed:

checkMesh has failed. And all solvers and utilities fails to create mesh.

#0 Foam::error::printStack(Foam::Ostream&) in "/opt/software/openfoam/OpenFOAM-1.4.1/lib/linux64g++DPOpt/libOpenFOAM.so"
#1 Foam::sigSegv::sigSegvHandler(int) in "/opt/software/openfoam/OpenFOAM-1.4.1/lib/linux64g++DPOpt/libOpenFOAM.so"
#2 __restore_rt at sigaction.c:0
#3 Foam::polyMesh::initMesh() in "/opt/software/openfoam/OpenFOAM-1.4.1/lib/linux64g++DPOpt/libOpenFOAM.so"
#4 Foam::polyMesh::polyMesh(Foam::IOobject const&) in "/opt/software/openfoam/OpenFOAM-1.4.1/lib/linux64g++DPOpt/libOpenFOAM.so"
#5 main in "/opt/software/openfoam/OpenFOAM-1.4.1/applications/bin/linux64g++DPOpt/checkMesh"
#6 __libc_start_main in "/lib64/libc.so.6"
#7 Foam::regIOobject::readIfModified() in "/opt/software/openfoam/OpenFOAM-1.4.1/applications/bin/linux64g++DPOpt/checkMesh"
Segmentation fault


Does mesh format Version has changed?
Somebody have workaround for that?:eek:

Kind Regards

[bastil]

Originally Posted by bruce

Does mesh format Version has changed?
Somebody have workaround for that?
Kind Regards

Yes format has changed. See forum for some discussions. I am not aware of an workaround.

Regards.

[bigphil]

Hi Bruce,

I came across this same problem, but it is possible to get snappy meshes to work in OpenFOAM-1.4.

There is a slight difference in meshing between the versions 1.5 and 1.4: the only difference being the neighbour dictionary in polyMesh directory. In OF-1.4.1 both owner and neighbour dictionaries have the same number of data, whereas in OF-1.5 that is not the case; difference being the number of '-1' data in old version.

So, after producing a mesh in OF-1.5 just add in neighbour dictionary as much '-1' as needed to have the same number of data as in the owner dictionary, and also change the number at the top of the neighbour dictionary to be the same as the owner. (I've copied and pasted '-1' from another neighbour dictionary produced in OF-1.4.1 as it's quicker).

When you run checkMesh, if there isn't the right number of '-1' then it'll say either it expected '-1' instead of ')' (ie not enough -1), or it'll say expected ')' instead of '-1' (ie too many -1).

It's a bit awkward, but someone could probably write a conversion utility if they wanted.

I haven't done this in a while so I hope the steps are right, but this does work as I have done it


Hope it helps,
Philip C

[bruce]

Hi

I too observed that thanks for info