What's wrong with the patch / p...?
 

Hello,

I want to test a hydrofoil (symmetry case based on motorBike case) and keep getting error messages from potentialFoam and simpleFoam.

What's wrong?

Find attached the error messages and the case (without the foil, as the file exceeds 97kB).

E.g. potentialFoam log:

/*---------------------------------------------------------------------------*\
| ========= | |
| \\ / F ield | OpenFOAM: The Open Source CFD Toolbox |
| \\ / O peration | Version: 2.0.1 |
| \\ / A nd | Web: www.OpenFOAM.org |
| \\/ M anipulation | |
\*---------------------------------------------------------------------------*/
Build : 2.0.1-5ae28021cd90
Exec : potentialFoam -noFunctionObjects -writep
Date : Jan 04 2012
Time : 22:25:53
Host : tenno-EP45-UD3R
PID : 7255
Case : /home/tenno/OpenFOAM/tenno-2.0.1/run/tutorials/incompressible/simpleFoam/wing
nProcs : 1
sigFpe : Enabling floating point exception trapping (FOAM_SIGFPE).
fileModificationChecking : Monitoring run-time modified files using timeStampMaster
allowSystemOperations : Disallowing user-supplied system call operations

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

Create mesh for time = 0

Reading field p



--> FOAM FATAL IO ERROR:

patch type 'patch' not constraint type 'symmetryPlane'
for patch maxY_domain_upper_wall of field p in file "/home/tenno/OpenFOAM/tenno-2.0.1/run/tutorials/incompressible/simpleFoam/wing/0/p"

file: /home/tenno/OpenFOAM/tenno-2.0.1/run/tutorials/incompressible/simpleFoam/wing/0/p::boundaryField::maxY_domain_upper_wall from line 27 to line 27.

From function symmetryFvPatchField<Type>::symmetryFvPatchField
(
const fvPatch& p,
const Field<Type>& field,
const dictionary& dict
)

in file fields/fvPatchFields/constraint/symmetry/symmetryFvPatchField.C at line 99.

FOAM exiting

Your symmetry planes are defined as patches in:

/constant/polyMesh/boundary

You need to change those to symmetry plane. The error message is telling you that you are trying to apply a symmetry condition to a patch.

Now I am running into the next problem - patch name .stl ...
 

Thank you!

But now I am running into the next patch problem.

SimpleFoam doesn't get the patch name of the wing. The wing is represented through wing.stl and the name defined in that file is also wing (first line is: solid wing).

Error: Cannot find any patch names matching wing_wing

SimpleFoam is looking for a patch name wing_wing which is to my knowledge made up internaly: name of wing.stl defined in sHMDict+ _name defined in the wing.stl file.

My trial & error approach didn't work.

Any idea, what needs to be changed? Find attached the simpleFoam log file.

Klaus

Case file - I am still not able to define the patch name
 

Hello,

find attached my case file - I am still not able to define the patchname for my wing (wing.stl).

I need to fix the following SimpleFoam error:

Reading surface description:
yNormal

--> FOAM Warning :
From function polyBoundaryMesh::patchSet(const wordReList&, const bool) const
in file meshes/polyMesh/polyBoundaryMesh/polyBoundaryMesh.C at line 573
Cannot find any patch names matching wing_wing
--> FOAM Warning :
From function polyBoundaryMesh::patchSet(const wordReList&, const bool) const
in file meshes/polyMesh/polyBoundaryMesh/polyBoundaryMesh.C at line 573
Cannot find any patch names matching wing_wing

Any ideas how to do that?

Klaus

Sorry for the slow response. The error message I get when running your case is:

This is because you specified the following in your /0/nu file:

I'm assuming that your "minX_inlet" is in fact an inlet, as such, the /0/nut file should have the following instead:

Once that is fixed, the code issues the same error for maxX_outlet. So this one should also be changed to 'type calculated;" in the 0/nut

Additionally, the case also complains about use of deprecated syntax. This is not a big deal (and does not cause the code to stop); however, I recommend reviewing the messages and adjusting your input files per the instructions. The case will run without doing so.

With the above two modifications, the case successfully ran the first iteration on my machine. I did not check your boundary condition types in any level of detail as there are several examples on the forums of people modeling airfoils, and personally, I do not have much experience doing so, but I would recommend reviewing your wing boundary condition. Wouldn't it be more common to use a wall function than a fixed value for an object in the flow?

Best of luck!

hi danish i am also getting the same error which you have mentioned. i changed it to type calculated. but still getting the same error. i think it is because in constant/polymesh/boundary i mentioned it as patch.
is there any other way to eliminate this error?

Hello!
I having the same error message. I trying run a landing gear fairing in OpenFoam, but the mesage that the cpolaina cannot be found on polyBoundaryMesh. Do you know what can be wrong?

Is this patch created when I run the file snappyHexMesh, right?

Thank you by your attention.