[onesecto]

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.

[otaolafr]

Originally Posted by onesecto

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

/*
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]

Originally Posted by otaolafr

...

you have a problem in te boundary definition. If i were you, i would try this:
1.comment the boundaries dictionary

/*
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]

Originally Posted by olesen

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

[olesen]

Originally Posted by otaolafr

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.