[blockMesh] BlockMesh error with growing mesh size

kian · September 21, 2007, 01:08

Hello,

I just upgraded to 1.4.1 by compiling the source.
I have noticed that blockMesh does not like more than 962 cells in the x-direction in the sonicFoam/shockTube example (1 block), and it gives this error if you specify more than 962 cells:

--> FOAM FATAL ERROR : face 0 in patch 0 does not have neighbour cell face: 4(0 2 3 1)#0

I don't know if this is related to the problem or not, since I had not started to really use version 1.4.1, but I had made changes to the source of sonicFoam and executed Allwmake in the applications directory. I saw some errors in vtkFoam application (different gcc versions), but the modified sonicFoam application works fine.

Thank you for your help.

Kian Mehravaran

msrinath80 · September 21, 2007, 01:11

The error message seems to suggest that there is a problem in your blockMeshDict. Paste it here. Someone might be able to identify the source of the problem.

kian · September 21, 2007, 11:01

Dear Srinath,
Thank you for your reply.
It is the one in sonicFoam/shockTube. I haven't changed the blockMeshDict. As I said, the error goes away if the mesh size is 962, instead of the original 1000! I feel that something is wrong with my blockMesh. The full error is below the letter.
Thanks, Kian Mehravaran
--> FOAM FATAL ERROR : face 0 in patch 0 does not have neighbour cell face: 4(0 1 3 2)#0 Foam::error::printStack (Foam:

stream&) in "/home/kian/OpenFOAM/OpenFOAM-1.4.1/lib/linuxGccSPOpt/libOpenFOAM.so"
#1 Foam::error::abort() in "/home/kian/OpenFOAM/OpenFOAM-1.4.1/lib/linuxGccSPOpt/libOpenFOAM.so"
#2 Foam::polyMesh::facePatchFaceCells(Foam::List<foam ::face> const&, Foam::List<foam::list<int> > const&, Foam:: List<foam::list<foam::face> > const&, int) const in "/home/kian/OpenFOAM/OpenFOAM-1.4.1/lib/linuxGccSPOpt/libOpen FOAM.so"
#3 Foam::polyMesh::polyMesh(Foam::IOobject const&, Foam::Field<foam::vector<float> > const&, Foam::List<foam::ce> const&, Foam::List<foam::list<foam::face> > const&, Foam::List<foam::word> const&, Foam::List<foam::word> const&, Foam::word const&, Foam::List<foam::word> const&, bool) in "/home/kian/OpenFOAM/OpenFOAM-1.4.1/lib/linu xGccSPOpt/libOpenFOAM.so"
#4 main in "/home/kian/OpenFOAM/OpenFOAM-1.4.1/applications/bin/linuxGccSPOpt/blockMesh"
#5 __libc_start_main in "/lib/tls/libc.so.6"
#6 __gxx_personality_v0 at ../sysdeps/i386/elf/start.S:122

msrinath80 · September 21, 2007, 13:09

Wierd. It works perfectly fine for me here. Compare your blockMeshDict with this one:

blockMeshDict

kian · September 24, 2007, 17:00

Thank you for posting your blockMeshDict, mine is exactly the same. Weird indeed.

Another weird problem that I had, reminded me of the difference our systems might have:
I compiled mine with single precision.
I noticed that when I use a deltaT lower than 1.0E-05, it is basically regarded as zero. In other words, time is always zero!
I checked the deltaT.value() in the code (sonicFoam), and it contains the correct value.

September 21, 2007, 11:01	Dear Srinath, Thank you for y	#3
kian New Member Kian Mehravaran Join Date: Mar 2009 Location: London, U.K Posts: 22 Rep Power: 17	Dear Srinath, Thank you for your reply. It is the one in sonicFoam/shockTube. I haven't changed the blockMeshDict. As I said, the error goes away if the mesh size is 962, instead of the original 1000! I feel that something is wrong with my blockMesh. The full error is below the letter. Thanks, Kian Mehravaran --> FOAM FATAL ERROR : face 0 in patch 0 does not have neighbour cell face: 4(0 1 3 2)#0 Foam::error::printStack (Foam:stream&) in "/home/kian/OpenFOAM/OpenFOAM-1.4.1/lib/linuxGccSPOpt/libOpenFOAM.so" #1 Foam::error::abort() in "/home/kian/OpenFOAM/OpenFOAM-1.4.1/lib/linuxGccSPOpt/libOpenFOAM.so" #2 Foam::polyMesh::facePatchFaceCells(Foam::List<foam ::face> const&, Foam::List<foam::list<int> > const&, Foam:: List<foam::list<foam::face> > const&, int) const in "/home/kian/OpenFOAM/OpenFOAM-1.4.1/lib/linuxGccSPOpt/libOpen FOAM.so" #3 Foam::polyMesh::polyMesh(Foam::IOobject const&, Foam::Field<foam::vector<float> > const&, Foam::List<foam::ce> const&, Foam::List<foam::list<foam::face> > const&, Foam::List<foam::word> const&, Foam::List<foam::word> const&, Foam::word const&, Foam::List<foam::word> const&, bool) in "/home/kian/OpenFOAM/OpenFOAM-1.4.1/lib/linu xGccSPOpt/libOpenFOAM.so" #4 main in "/home/kian/OpenFOAM/OpenFOAM-1.4.1/applications/bin/linuxGccSPOpt/blockMesh" #5 __libc_start_main in "/lib/tls/libc.so.6" #6 __gxx_personality_v0 at ../sysdeps/i386/elf/start.S:122

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
how to set periodic boundary conditions	Ganesh	FLUENT	15	November 18, 2020 07:09
[blockMesh] blockMesh to generate the mesh of a deep cavity	eddykendo	OpenFOAM Meshing & Mesh Conversion	4	July 5, 2015 17:54
[ICEM] Generating Mesh for STL Car in Windtunnel Simulation	tommymoose	ANSYS Meshing & Geometry	48	April 15, 2013 05:24
Phase locked average in run time	panara	OpenFOAM	2	February 20, 2008 15:37
fluent add additional zones for the mesh file	SSL	FLUENT	2	January 26, 2008 12:55

September 21, 2007, 01:08	BlockMesh error with growing mesh size	#1
kian New Member Kian Mehravaran Join Date: Mar 2009 Location: London, U.K Posts: 22 Rep Power: 17	Hello, I just upgraded to 1.4.1 by compiling the source. I have noticed that blockMesh does not like more than 962 cells in the x-direction in the sonicFoam/shockTube example (1 block), and it gives this error if you specify more than 962 cells: --> FOAM FATAL ERROR : face 0 in patch 0 does not have neighbour cell face: 4(0 2 3 1)#0 I don't know if this is related to the problem or not, since I had not started to really use version 1.4.1, but I had made changes to the source of sonicFoam and executed Allwmake in the applications directory. I saw some errors in vtkFoam application (different gcc versions), but the modified sonicFoam application works fine. Thank you for your help. Kian Mehravaran

September 21, 2007, 01:11	The error message seems to sug	#2
msrinath80 Senior Member Srinath Madhavan (a.k.a pUl\|) Join Date: Mar 2009 Location: Edmonton, AB, Canada Posts: 703 Rep Power: 21	The error message seems to suggest that there is a problem in your blockMeshDict. Paste it here. Someone might be able to identify the source of the problem.

September 21, 2007, 13:09	Wierd. It works perfectly fine	#4
msrinath80 Senior Member Srinath Madhavan (a.k.a pUl\|) Join Date: Mar 2009 Location: Edmonton, AB, Canada Posts: 703 Rep Power: 21	Wierd. It works perfectly fine for me here. Compare your blockMeshDict with this one: blockMeshDict

September 24, 2007, 17:00	Thank you for posting your blo	#5
kian New Member Kian Mehravaran Join Date: Mar 2009 Location: London, U.K Posts: 22 Rep Power: 17	Thank you for posting your blockMeshDict, mine is exactly the same. Weird indeed. Another weird problem that I had, reminded me of the difference our systems might have: I compiled mine with single precision. I noticed that when I use a deltaT lower than 1.0E-05, it is basically regarded as zero. In other words, time is always zero! I checked the deltaT.value() in the code (sonicFoam), and it contains the correct value.