[Florian Mlehliw]

Hello together!

I'm following a tutorial case by the wonderful Tobias Holzmann (https://holzmann-cfd.com/community/t...h-safety-valve) and adapting it to my case of a dam breach, treating the dam baffle as some kind of pressure valve.

I've run through snappyHex, renumberMesh and topoSet and my outputs are the same as his with only the names changed. (I can post the Dicts and outputs here, if needed, but didn't want this post to get even longer.)

However, when I get to createBaffles, things begin to fall apart. My createBafflesDict looks like this, which is basically a copy of Tobias' code:

internalFacesOnly     true;

noFields             false;

baffles
{
    // Here we use the previous created faceSet to create 4 times the same
    // faces which are moved to different boundary conditions
    // The reason for that is that the activePressureForceBaffle needs
    // a) a cyclic boundary set (master/slave)
    // b) an additional wall
     quadruplicateTheInternalFaces
    {
        type        faceZone;
        zoneName    damFaceZone;
        patches
        {
            // a) Create the cyclic guys
            dam_master_cyclic
            {
                name            dam_master;
                type            cyclic;
                sampleMode        nearestPatchFace;
                neighbourPatch    dam_slave;
                sameGroup        off;
                patchFields
                {
                }
            }
            
            dam_slave_cyclic 
            { 
                name            dam_slave;
                type            cyclic;
                sampleMode        nearestPatchFace;
                neighbourPatch    dam_master;
                sameGroup        off;
                patchFields
                {
                } 
            }
            
            // b) create another set of walls (will be merged in the next step)
            dam_master_wall
            {
                name            damWall1;
                type            wall;
            }
            dam_slave_wall
            {
                name            damWall2;
                type            wall;
            }
        }
    }
}

When I run it, however, the output differs in a very important line:

(base) createBaffles -overwrite
/*---------------------------------------------------------------------------*\
| =========                 |                                                 |
| \\      /  F ield         | OpenFOAM: The Open Source CFD Toolbox           |
|  \\    /   O peration     | Version:  2112                                  |
|   \\  /    A nd           | Website:  www.openfoam.com                      |
|    \\/     M anipulation  |                                                 |
\*---------------------------------------------------------------------------*/
Build  : _14aeaf8dab-20211220 OPENFOAM=2112 version=v2112
Arch   : "LSB;label=32;scalar=64"
Exec   : createBaffles -overwrite
Date   : Aug 12 2023
Time   : 10:53:21
Host   : login.cirrus
PID    : 1796095
I/O    : uncollated
Case   : /data/scratch/*****/Dissertation/OpenFOAM/testCases/DynamicMesh
nProcs : 1
trapFpe: Floating point exception trapping enabled (FOAM_SIGFPE).
fileModificationChecking : Monitoring run-time modified files using timeStampMaster (fileModificationSkew 5, maxFileModificationPolls 20)
allowSystemOperations : Allowing user-supplied system call operations

// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time

Create mesh for time = 0

Reading baffle criteria from createBafflesDict

Not converting faces on non-coupled patches.

Reading geometric fields

Created zone quadruplicateTheInternalFaces at index 1 with 2292 faces
Converted 0 faces into boundary faces in patches 4(damWall1 damWall2 dam_master dam_slave)

--> FOAM Warning :
    From int main(int, char **)
    in file createBaffles.C at line 867
    Setting field on boundary faces to zero.
You might have to edit these fields.
Writing mesh to 0
End

while the output of his case reads:

/*---------------------------------------------------------------------------*\
| =========                 |                                                 |
| \\      /  F ield         | OpenFOAM: The Open Source CFD Toolbox           |
|  \\    /   O peration     | Version:  2112                                  |
|   \\  /    A nd           | Website:  www.openfoam.com                      |
|    \\/     M anipulation  |                                                 |
\*---------------------------------------------------------------------------*/
Build  : _14aeaf8dab-20211220 OPENFOAM=2112 version=v2112
Arch   : "LSB;label=32;scalar=64"
Exec   : createBaffles -overwrite
Date   : Aug 12 2023
Time   : 10:11:40
Host   : login.cirrus
PID    : 1779499
I/O    : uncollated
Case   : /data/scratch/*****/Dissertation/OpenFOAM/testCases/tankWithSavetyValve
nProcs : 1
trapFpe: Floating point exception trapping enabled (FOAM_SIGFPE).
fileModificationChecking : Monitoring run-time modified files using timeStampMaster (fileModificationSkew 5, maxFileModificationPolls 20)
allowSystemOperations : Allowing user-supplied system call operations

// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time

Create mesh for time = 0

Reading baffle criteria from createBafflesDict

Not converting faces on non-coupled patches.

Reading geometric fields

Reading volScalarField: cellLevel
Created zone quadruplicateTheInternalFaces at index 1 with 50 faces
Converted 100 faces into boundary faces in patches 4(raptureDiscWall1 raptureDiscWall2 raptureDisc_master raptureDisc_slave)

--> FOAM Warning : 
    From int main(int, char **)
    in file createBaffles.C at line 867
    Setting field on boundary faces to zero.
You might have to edit these fields.
Writing mesh to 0
 End

As you can see, in my case the faces are not converted and the line "Reading volScalarField: cellLevel" is missing completely. When I take a look at constant/polyMesh/cellLevel (which I think this points to), our files are virtually the same.



So my questions are:
What does the missing line do? How can I get it to show up in my code as well?
I hope anyone can help. Thanks!

[Florian Mlehliw]

I got it, I think.

In Tobias' controlDict, he had writeformat as binary, while I had mine as ascii. When I changed my Dict, it went through.



Now I'm stuck on the actual simulation, but I will post a separate question for that.