[Andyjoe]

Hello,

scince I'm able to configure an run simple OpenFoam cases, I went through the motorBike tutorial the last days. Everything worked. So I changed the stl file with a new geometry made in Blender. A big surprise happend: it worked imediately. Motivated by that, I began to write a superSonic case. I still used the "windtunnel" and the snappyHexMeshDict from the motorBike tutorial. After some trying it worked, but at a certain time the simulation stoped, because of too many iterations. Have I done anything wrong or is this a numerical problem?
Scince I want to apply the data in real life, it would be better, to know what I do. So I tryed to understand the motorBike tutorial in detail. But there are almost no explanations anywhere. Here some things, I don't understand:
First to the snappyHexMeshDict:

geometry
{
    phoenix.stl
    {
        type triSurfaceMesh;
        name phoenix;
    }

    refinementBox
    {
        type searchableBox;
        min (-1.0 -0.7 0.0);
        max ( 8.0  0.7 2.5);
    }
};

I don't understand the refinemantBox. Actually I found some text in the Internet about it, but it's still not clear. Is it a place, from which the refinement of the Mesh starts?

addLayersControls
{
    relativeSizes true;

    // Per final patch (so not geometry!) the layer information
    layers
    {
        minZ
        {
            nSurfaceLayers 1;
        }
        motorBike_frt-fairing:001%1
        {
            nSurfaceLayers 1;
        }
        motorBike_windshield:002%2
        {
            nSurfaceLayers 1;
        }
        motorBike_rr-wh-rim:005%5
        {
            nSurfaceLayers 1;
        }
        motorBike_rr-wh-rim:010%10
        {
            nSurfaceLayers 1;
        }
        motorBike_fr-wh-rim:011%11
        {
            nSurfaceLayers 1;
        }
        [... and so on ...]
        }
        motorBike_radiator-shadow%86
        {
            nSurfaceLayers 1;
        }
        motorBike_rear-shock-link-shadow%87
        {
            nSurfaceLayers 1;
        }
        motorBike_rear-brake-fluid-pot-bracket-shadow%88
        {
            nSurfaceLayers 1;
        }
        motorBike_rr-wh-chain-hub-shadow%89
        {
            nSurfaceLayers 1;
        }
    }

I don't know, what the %number , for example %88 means. Is it ok for my case, when I write

addLayersControls
{
    relativeSizes true;

    // Per final patch (so not geometry!) the layer information
    layers
    {
        minZ
        {
            nSurfaceLayers 1;
        }
        phoenix
        {
            nSurfaceLayers 1;
        }
    }

Has anyone an idea, what minZ means?
When I start the case, the terminal shows me, that many patches of the stl file are read in, 8224. So in the boundary file I've got 8224 patches. Is this ok? If yes, why this is done? Wouldn't it be enough to have one wall? Actually the original motorBike boundary file hasn't as much patches, only the patches mentioned in the layer definition in the snappyHexMeshDict.
My boundary file looks like this:

   8230
(
    frontAndBack
    {
        type            patch;
        nFaces          440;
        startFace       1580732;
    }
    inlet
    {
        type            patch;
        nFaces          64;
        startFace       1581172;
    }
    outlet
    {
        type            patch;
        nFaces          64;
        startFace       1581236;
    }
    lowerWall
    {
        type            wall;
        nFaces          4366;
        startFace       1581300;
    }
    upperWall
    {
        type            patch;
        nFaces          244;
        startFace       1585666;
    }
    phoenix_patch0
    {
        type            wall;
        nFaces          0;
        startFace       1585910;
    }
   [..... all patches look similar....]
    }
    phoenix_patch8223
    {
        type            wall;
        nFaces          0;
        startFace       1585910;
    }
   phoenix_patch8224
    {
        type            wall;
        nFaces          108556;
        startFace       1585910;
    }

Furthermore I wanted to ask something about the decomposeParDict
the header looks like this:

FoamFile
{
    version         2.0;
    format          ascii;

    root            "/home/penfold/mattijs/foam/mattijs2.1/run/icoFoam";
    case            "cavity";
    instance        "system";
    local           "";

    class           dictionary;
    object          decomposeParDict;
}

Seemingly there is a path of the computer of the developer of this file. Because my root would be /home/andreas. I think I have to change it. But this file is out of the motorBike tutorial. Why there is "case "cavity" "?
Here some other lines of the code:

manualCoeffs
{
    dataFile        "cellDecomposition";
}

I used the search function of my computer, but couldn't find any file "cellDecomposition".
A lot of questions. I would be thankful if theres anyone who can help me.