[Danubi]

Hi all,

I am writing because I have tried everything and the moment to ask for help has arrived.

I am trying to obtain Cd and Cl drag and lift coefficients of an already run simulation using the wonderful capability of postProcessing.

when I use the following:

pimpleFoam -postProcess -func forceCoeffsIncompressible

I obtain:

nProcs : 1
sigFpe : Enabling floating point exception trapping (FOAM_SIGFPE).
fileModificationChecking : Monitoring run-time modified files using timeStampMaster
allowSystemOperations : Allowing user-supplied system call operations

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

Create mesh for time = 0


PIMPLE: Operating solver in PISO mode

forces forceCoeffsIncompressible:
--> FOAM Warning : 
    From function Foam::labelHashSet Foam::polyBoundaryMesh::patchSet(const Foam::UList<Foam::wordRe>&, bool, bool) const
    in file meshes/polyMesh/polyBoundaryMesh/polyBoundaryMesh.C at line 794
    Cannot find any patch or group names matching patch1
--> FOAM Warning : 
    From function Foam::labelHashSet Foam::polyBoundaryMesh::patchSet(const Foam::UList<Foam::wordRe>&, bool, bool) const
    in file meshes/polyMesh/polyBoundaryMesh/polyBoundaryMesh.C at line 794
    Cannot find any patch or group names matching patch2
    Not including porosity effects
forceCoeffs forceCoeffsIncompressible:
--> FOAM Warning : 
    From function Foam::labelHashSet Foam::polyBoundaryMesh::patchSet(const Foam::UList<Foam::wordRe>&, bool, bool) const
    in file meshes/polyMesh/polyBoundaryMesh/polyBoundaryMesh.C at line 794
    Cannot find any patch or group names matching patch1
--> FOAM Warning : 
    From function Foam::labelHashSet Foam::polyBoundaryMesh::patchSet(const Foam::UList<Foam::wordRe>&, bool, bool) const
    in file meshes/polyMesh/polyBoundaryMesh/polyBoundaryMesh.C at line 794
    Cannot find any patch or group names matching patch2
    Not including porosity effects
Time = 0
Reading field p

Reading field U

Reading/calculating face flux field phi

Selecting incompressible transport model Newtonian
Selecting turbulence model type laminar
No MRF models present

When I don't have any 'patch1' nor 'patch2' ...
I have tried to run it with the function included in the controlDict and it worked fine but the problem is that the simulation took weeks to get here so I can't rerun it again.

Please if any can take a look to the case I attach in the message the case folder. It only needs to:

bash ./AllMesh
pimpleFoam

This is OF4. Please run some timesteps and when you already have several time folders try to get the forceCoeffs from the written folders with postProcess.


Thanks a lot in advance

[parthiv1991]

I am having the same problem. I am trying to find out the force coefficients for flow around a cylinder using OpenFoam 4.1, and the post-processing is not working somehow.

[Danubi]

I can't believe it is so weird that nobody is encountering the same problem. I am trying now to postProcess some probes and I am having similar problems. It is like it never reaches to read dictionaries specifying details of the call.

It looks to me that this -postProcess CLI approach is useful when everything can be specified on the command line, like patchAverage, where there is only a need for specifying U and the patch name. Otherwise, when it needs to read a dictionary, it fails... well... at least I can't do it.

Regards

[Danubi]

Hello parthiv1991 and whoever stucks in the same stone,

He it goes:

This post explains some of the needed info:
bullmut threat

Also the user guide:
usedGuide

But! Important:

Go to $FOAM_ETC, then to etc/caseDicts/postProcessing/forces
Later copy whatever file with the title of the function you need (the non *.cfg file) to your system directory.
Do no add NOTHING to the controlDict 'functions' library.
And later execute the CLI command:

pimpleFoam -postProcess -func 'forceCoeffsIncompressible' -latestTime

Important: the function that has been specified between ' ' has to have the same name as the file that had been copied to system/ folder....

Thanks to the people in the other thread!