CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Software User Forums > OpenFOAM > OpenFOAM Meshing & Mesh Conversion

[blockMesh] --> FOAM FATAL ERROR: face 0 in patch 2 does not have neighbour cell face: 4(0 3 10

Register Blogs Members List Search Today's Posts Mark Forums Read

Like Tree3Likes
  • 1 Post By otaolafr
  • 1 Post By olesen
  • 1 Post By olesen

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   June 8, 2021, 06:12
Question --> FOAM FATAL ERROR: face 0 in patch 2 does not have neighbour cell face: 4(0 3 10
  #1
New Member
 
Ole
Join Date: Jun 2021
Posts: 1
Rep Power: 0
onesecto is on a distinguished road
Hi,
this is my first Post and one of my first blockMeshDicts. I got this Error
--> FOAM FATAL ERROR:
face 0 in patch 2 does not have neighbour cell face: 4(0 3 10 9)
and i think i have Problems with most of the Patches.

blockMeshDict:

convertToMeters 1;

vertices
(
(0 0 0) //0
(0.15 0 0) //1
(0.15 1 0) //2
(0 1 0) //3
(0 0 0.1) //4
(0.15 0 0.1) //5
(0.15 1 0.1) //6
(0 1 0.1) //7
(0.15 0 0.05) //8 zwischen 1 und 5
(0 0 0.05) //9 zwischen 0 und 4
(0 1 0.05) //10 zwischen 3 und 7
(0.15 1 0.05) //11 zwischen 2 und 6

);

blocks
(
hex (0 1 2 3 11 10 9 8) (25 75 10) simpleGrading (1 10.7028 1)
hex (7 6 5 4 8 9 10 11) (25 75 10) simpleGrading (1 0.0934 1)
//hex (0 1 2 3 4 5 6 7) (25 75 10) simpleGrading (1 1 1)
);

edges
(
);

boundary // keyword
(
bottomWall
{
type wall;
faces ((4 5 6 7));
}
topWall
{
type wall;
faces ((0 1 2 3));
}
//Obere Häfte
/* top_inlet // patch name
{
type cyclic;
neighbourPatch top_outlet;
faces
(
(0 1 8 9)
);
} */
top_outlet
{
type cyclic;
neighbourPatch top_inlet;
faces
(
(2 3 10 11)
}
);
top_side_left
{
type cyclic;
neighbourPatch top_side_right;
faces ((1 8 11 2));
}
top_side_right
{
type cyclic;
neighbourPatch top_side_left;
faces ((0 9 10 3));
}
//untere Hälfte
bot_inlet // patch name
{
type cyclic;
neighbourPatch bot_outlet;
faces
(
(5 4 9 8)
);
}
bot_outlet // patch name
{
type cyclic; // patch type for patch 1
neighbourPatch bot_inlet;
faces
(
(6 7 10 11) //(1 2 6 5)
);
}


I would be thankfull for your help.
onesecto is offline   Reply With Quote

Old   June 10, 2021, 12:01
Default
  #2
Senior Member
 
Franco
Join Date: Nov 2019
Location: Compiègne, France
Posts: 129
Rep Power: 6
otaolafr is on a distinguished road
Quote:
Originally Posted by onesecto View Post
Hi,
this is my first Post and one of my first blockMeshDicts. I got this Error
--> FOAM FATAL ERROR:
face 0 in patch 2 does not have neighbour cell face: 4(0 3 10 9)
and i think i have Problems with most of the Patches.

blockMeshDict:

convertToMeters 1;

vertices
(
(0 0 0) //0
(0.15 0 0) //1
(0.15 1 0) //2
(0 1 0) //3
(0 0 0.1) //4
(0.15 0 0.1) //5
(0.15 1 0.1) //6
(0 1 0.1) //7
(0.15 0 0.05) //8 zwischen 1 und 5
(0 0 0.05) //9 zwischen 0 und 4
(0 1 0.05) //10 zwischen 3 und 7
(0.15 1 0.05) //11 zwischen 2 und 6

);

blocks
(
hex (0 1 2 3 11 10 9 8) (25 75 10) simpleGrading (1 10.7028 1)
hex (7 6 5 4 8 9 10 11) (25 75 10) simpleGrading (1 0.0934 1)
//hex (0 1 2 3 4 5 6 7) (25 75 10) simpleGrading (1 1 1)
);

edges
(
);

boundary // keyword
(
bottomWall
{
type wall;
faces ((4 5 6 7));
}
topWall
{
type wall;
faces ((0 1 2 3));
}
//Obere Häfte
/* top_inlet // patch name
{
type cyclic;
neighbourPatch top_outlet;
faces
(
(0 1 8 9)
);
} */
top_outlet
{
type cyclic;
neighbourPatch top_inlet;
faces
(
(2 3 10 11)
}
);
top_side_left
{
type cyclic;
neighbourPatch top_side_right;
faces ((1 8 11 2));
}
top_side_right
{
type cyclic;
neighbourPatch top_side_left;
faces ((0 9 10 3));
}
//untere Hälfte
bot_inlet // patch name
{
type cyclic;
neighbourPatch bot_outlet;
faces
(
(5 4 9 8)
);
}
bot_outlet // patch name
{
type cyclic; // patch type for patch 1
neighbourPatch bot_inlet;
faces
(
(6 7 10 11) //(1 2 6 5)
);
}


I would be thankfull for your help.
please when you post a code/dictionary use the [CODE] feature in the forum, it makes way easier to read.
you have a problem in te boundary definition. If i were you, i would try this:
1.comment the boundaries dictionary
Code:
/*
boundaries
*/
2. use blockMesh if you do not get any error
3. run paraFoam -block
you can then trouble shoot your block mesh. you have a point brongly defined.
if the blockMesh still does not want to run comment one by one the different blocks.
best regards
using paraFoam
olesen likes this.
otaolafr is offline   Reply With Quote

Old   June 11, 2021, 04:30
Default
  #3
Senior Member
 
Mark Olesen
Join Date: Mar 2009
Location: https://olesenm.github.io/
Posts: 1,712
Rep Power: 40
olesen has a spectacular aura aboutolesen has a spectacular aura about
Quote:
Originally Posted by otaolafr View Post
...

you have a problem in te boundary definition. If i were you, i would try this:
1.comment the boundaries dictionary
Code:
/*
boundaries
*/
2. use blockMesh if you do not get any error

Exactly the way to do it but you also have the option of "blockMesh -write-vtk" to inspect the topology without requiring the special paraview reader plugin.
otaolafr likes this.
olesen is offline   Reply With Quote

Old   June 11, 2021, 04:49
Default
  #4
Senior Member
 
Franco
Join Date: Nov 2019
Location: Compiègne, France
Posts: 129
Rep Power: 6
otaolafr is on a distinguished road
Quote:
Originally Posted by olesen View Post
Exactly the way to do it but you also have the option of "blockMesh -write-vtk" to inspect the topology without requiring the special paraview reader plugin.
did not known about this flag of blockMesh... nice thanks for the info.
I think the paraFoam way is a little bit better specially in a case when you trouble shoot, as it shows the number of the point next to the point.... that with the blockmesh flag path does not. but still quite nice!
best regards
otaolafr is offline   Reply With Quote

Old   June 12, 2021, 14:17
Default
  #5
Senior Member
 
Mark Olesen
Join Date: Mar 2009
Location: https://olesenm.github.io/
Posts: 1,712
Rep Power: 40
olesen has a spectacular aura aboutolesen has a spectacular aura about
Quote:
Originally Posted by otaolafr View Post
did not known about this flag of blockMesh... nice thanks for the info.
I think the paraFoam way is a little bit better specially in a case when you trouble shoot, as it shows the number of the point next to the point.... that with the blockmesh flag path does not. but still quite nice!
best regards
At the right end of the paraview toolbar there is a "hover point" button. Click that and then can inspect the vertex numbers - without reliance on any additional plugins.
The point labels that the blockMesh plugin shows are generally OK, but even after several attempts to get them properly fixed, they still tend to be too persistent (sticky).

If you have a slightly more complex blockMesh, can view the corresponding vtk file with "shink elements" - quite effective during diagnostics since it also makes it easy to find "hidden" vertices.
otaolafr likes this.
olesen is offline   Reply With Quote

Reply

Tags
blockmesh, cyclic

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
[blockMesh] Foam fatal error: neighbour cell face anu.raghun OpenFOAM Meshing & Mesh Conversion 2 June 26, 2019 11:53
steadyUniversalMRFFoam Tutorial fails in MixingPlane HenrikJohansson OpenFOAM Bugs 0 February 14, 2019 04:48
[CGNS] CGNS converters available mbeaudoin OpenFOAM Meshing & Mesh Conversion 137 December 14, 2018 04:20
error with reactingFoam BakedAlmonds OpenFOAM Running, Solving & CFD 4 June 22, 2016 02:21
[blockMesh] Errors during blockMesh meshing Madeleine P. Vincent OpenFOAM Meshing & Mesh Conversion 51 May 30, 2016 10:51


All times are GMT -4. The time now is 03:36.