CFD Online Discussion Forums

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)
-   OpenFOAM (https://www.cfd-online.com/Forums/openfoam/)
-   -   Strange thing in boundary file (https://www.cfd-online.com/Forums/openfoam/130257-strange-thing-boundary-file.html)

Tobi February 22, 2014 14:46
Strange thing in boundary file
 
Hi all,

is it normal that I am able to run a case where I define no boundary type like that:
Code:
6
(
    up
    {
        type            ;
        nFaces          40;
        startFace      15760;
    }
    down
    {
        type            ;
        nFaces          40;
        startFace      15800;
    }
    heatedWall
    {
        type            ;
        nFaces          20;
        startFace      15840;
    }
    left
    {
        type            ;
        nFaces          180;
        startFace      15860;
    }
    right
    {
        type            ;
        nFaces          200;
        startFace      16040;
    }
    frontAndBack
    {
        type            empty;
        nFaces          16000;
        startFace      16240;
    }
)
There is no error message an the case runs exactly the same way - with and without the types.

Solver: buoyantBoussinesqSimpleFoam

I am confused... :confused:

flames February 24, 2014 15:39
This file is from constant folder. You should have defined them in 0 folder. Or it cannot run I believe.

Tobi February 24, 2014 16:24
Normally if you define the boundary as slip you have to use it in the initialfiles to (U,p,T...).

If there is a mismatch you will get an error. But in this case i can use wall on boundary condition and slip in T file (for example).

alexeym February 25, 2014 02:39
Hi,

Quote:
Originally Posted by Tobi (Post 476565)
Normally if you define the boundary as slip you have to use it in the initialfiles to (U,p,T...).

If there is a mismatch you will get an error. But in this case i can use wall on boundary condition and slip in T file (for example).
No sure I've got your question right but when there's no definition for the patch type patch itself become just genericPatch (OpenFOAM/meshes/polyMesh/polyPatches/polyPatch/polyPatchNew.C)

Code:
    if (cstrIter == dictionaryConstructorTablePtr_->end())
    {
        if (!disallowGenericPolyPatch)
        {
            cstrIter = dictionaryConstructorTablePtr_->find("genericPatch");
        }
...
In case of slip BC it is a child of basicSymmetryFvPatchField which in turn is a child of transformPathField and there are no check on patch field type in these classes (unlike for example in wall functions where patch has to be of wall type).


All times are GMT -4. The time now is 19:47.