[sippanspojk]

Hi all,

I am writing my own functionObject where I want to loop over each face in a specified patch and do some computations on the pressure values.

I generated a new file with foamNewFunctionObject. Then I found online the following code snippet that is almost doing what I want:

const polyBoundaryMesh& boundaryMesh = mesh.boundaryMesh();             // Boundary mesh

forAll(mesh.boundary(), patch)
{
    const word& patchName = mesh.boundary()[patch].name();              // Boundary patch name
    forAll(mesh.boundary()[patch], facei)
    {
        const label& face = boundaryMesh[patch].start() + facei;        // FaceID
    }
}

I would like to add a new variable myPressureField and extract the pressure value in the center of each face in the inner loop. Somthing like this:

const surfaceScalarField& myPressureField = p.boundaryMesh(); 


forAll(mesh.boundary()[patch], facei)
    {
        const scalar& faceP = myPressureField[patch][facei]
    }

I am new to programming in OpenFOAM so I am more or less guessing how I should do it based on what I can find online.

I would be thankful for some guidance with this.

Cheers,
David

[clapointe]

Here's a bit of code I've used in the past for T values on a patch -- changing for p should be trivial.

    const volScalarField& Temp = mesh().lookupObject<volScalarField>("T");
    Foam::label patchLabel = mesh().boundaryMesh().findPatchID("myName");
    const Foam::fvPatch& patch = mesh().boundary()[patchLabel];

    forAll(currPatch,facei)
    {
        Foam::label faceCelli = currPatch.faceCells()[facei];
        Foam::scalar Tempi = Temp[faceCelli];
    }

Caelan

[sippanspojk]

Thank you Caelan for your answer!

Am I right when I say I should define this directly in my .C file?

At the moment I am just trying out the first row where I define my field, like this:

    const volScalarField& myPressure= mesh_.lookupObject<volScalarField>("p");

and it doesn't work. I also tried with volVectorFiled and "U" but the same problem.

Do I need to #include some special library(ies) to be able to access the fields?

//David

[clapointe]

Yes, it'll go in the .C file for your function object.

Caelan

[sippanspojk]

I finally got it to work when I included "fvcGrad.H". Does that make sense? What is in that library?

[clapointe]

Ultimately you'd need to link in something like fvCFD.H, which most function objects would do (I hope you didn't start from scratch, and copied an existing function object to work from!). That said, while the code I pasted doesn't need fvcGrad.H, it might need something that the .H file loops in. It is used to compute gradients of a volume field. Without seeing the compilation error it is hard to tell.

Caelan