|
[Sponsors] |
October 4, 2013, 12:37 |
Probe Warning, Probe Does Not Work
|
#1 |
New Member
Join Date: Jan 2013
Location: Lisboa-Funchal
Posts: 23
Rep Power: 13 |
Greetings people,
I am running a case, with parallel computing, and before the computations I got this warning message: Code:
--> FOAM Warning : From function probes::read() in file probes/probes.C at line 71 Did not find location (0.03 0.11 0) in any cell. Skipping location. --> FOAM Warning : From function probes::read() in file probes/probes.C at line 71 Did not find location (0.03 0.11125 0) in any cell. Skipping location. --> FOAM Warning : From function probes::read() in file probes/probes.C at line 71 Did not find location (0.03 0.1125 0) in any cell. Skipping location. --> FOAM Warning : From function probes::read() in file probes/probes.C at line 71 Did not find location (0.03 0.1225 0) in any cell. Skipping location. --> FOAM Warning : From function probes::read() in file probes/probes.C at line 71 Did not find location (0.04 0.12375 0) in any cell. Skipping location. --> FOAM Warning : From function probes::read() in file probes/probes.C at line 71 Did not find location (0.0475 0.1275 0) in any cell. Skipping location. Code:
--> FOAM Warning : From function probes::read() in file probes/probes.C at line 71 Did not find location (0.0475 0.1275 0) in any cell. Skipping location.
__________________
Se Urso Vires Foge Tocando Gaita Para Hamburgo |
|
October 5, 2013, 15:49 |
|
#2 |
Senior Member
Nima Samkhaniani
Join Date: Sep 2009
Location: Tehran, Iran
Posts: 1,267
Blog Entries: 1
Rep Power: 25 |
checkMesh and see whether your mesh is in domain or not
__________________
My Personal Website (http://nimasamkhaniani.ir/) Telegram channel (https://t.me/cfd_foam) |
|
October 14, 2013, 08:04 |
|
#3 |
New Member
Join Date: Jan 2013
Location: Lisboa-Funchal
Posts: 23
Rep Power: 13 |
As I said (and confirmed), the probes are in the domain. If I DO NOT decompose the problem, i. e. run the simulation in only one processor, OpenFOAM still gives me one warning. Is there any problems between decomposing the mesh and probe locations ? And why I get the warning, if the probe is in the domain ?
__________________
Se Urso Vires Foge Tocando Gaita Para Hamburgo |
|
April 10, 2014, 10:41 |
|
#4 |
New Member
Wallace Green
Join Date: May 2010
Posts: 19
Rep Power: 16 |
rather than using a probe functionObject try a polyLine set where the original probeLocations are now the points.
|
|
April 10, 2014, 10:54 |
|
#5 |
Senior Member
|
Hi,
actually warning are self-explanatory Code:
Did not find location (0.03 0.1225 0) in any cell. Skipping location. Check dimensions of the mesh, check where you put your probes. Try to put all the probes inside the mesh. |
|
April 10, 2014, 12:45 |
|
#6 |
New Member
Wallace Green
Join Date: May 2010
Posts: 19
Rep Power: 16 |
sure alexeym, but I have noticed the probe functionObject having trouble locating points that are inside a mesh when running in parallel. There are slight differences in the implementation of the particular findCell() function for probes, polyLines, clouds, etc. and in my experience, there are some bugs.
|
|
April 10, 2014, 13:27 |
|
#7 |
Senior Member
|
Oh, sorry, missed several messages.
Does the number of warnings depend on the decomposition (number of subdomains, decomposition method)? Maybe probes are on processor boundaries (though in this case another warning should be issued)? I've looked though the implementation of findCell method and wasn't able to find anything that won't be working in parallel cases. |
|
April 11, 2014, 14:38 |
|
#8 |
New Member
Wallace Green
Join Date: May 2010
Posts: 19
Rep Power: 16 |
I've attached a case where I noticed this happening. The controlDict has functionObjects that write out velocity and pressure at 120 locations inside the domain at each iteration, once using type probes from libsampling and once using type sets with polyLine. The polyLine method works fine, but the probes approach skips four locations. Just use Allrun - hopefully it's self-explanatory.
If you get to the bottom of that and are still motivated, check out http://www.openfoam.org/mantisbt/view.php?id=0001147 for a another sampling peculiarity. |
|
April 14, 2014, 04:38 |
|
#9 |
Senior Member
|
Hi,
unfortunately I wasn't able to reproduce the error, here is the output of the solver for the attached case: Code:
Build : 2.2.2-9739c53ec43f Exec : simpleFoam -parallel ... SIMPLE: convergence criteria field p tolerance 0.001 field U tolerance 0.0001 field "(k|epsilon)" tolerance 0.0001 Starting time loop Reading set description: polyLine Time = 1 smoothSolver: Solving for Ux, Initial residual = 1, Final residual = 0.0762530558, No Iterations 1 smoothSolver: Solving for Uy, Initial residual = 0.69705505, Final residual = 0.651831039, No Iterations 1000 smoothSolver: Solving for Uz, Initial residual = 1, Final residual = 0.0752473553, No Iterations 1 GAMG: Solving for p, Initial residual = 1, Final residual = 0.0835314711, No Iterations 2 time step continuity errors : sum local = 1.10938559e-16, global = -3.04128912e-18, cumulative = -3.04128912e-18 smoothSolver: Solving for epsilon, Initial residual = 0.999999992, Final residual = 0.0309136051, No Iterations 2 smoothSolver: Solving for k, Initial residual = 0.999999991, Final residual = 0.0339960612, No Iterations 2 ... |
|
April 16, 2014, 06:01 |
|
#10 |
New Member
Wallace Green
Join Date: May 2010
Posts: 19
Rep Power: 16 |
thanks for trying that out. I noticed from your output log that you are running 2.2.2. I had been running 2.3.x. I've built 2.2.x again and tested the same case - my output is now just like yours - no errors. If you (or anyone else) have 2.3.x available, I'd be interested in how that works for you. In the meantime though, I'll submit a bug report when I have an opportunity.
|
|
April 18, 2014, 17:03 |
|
#11 |
Senior Member
|
I'd like to confirm that bug can be reproduced with 2.3.x.
There was certain changes in findCell algorithm between 2.2.2 and 2.3.x though I wasn't able yet to determine the reason why everything is OK under 2.2.2 and not OK under 2.3.x (though I guess the reason is tetrahedral cells near the probes as mainly the algorithm was changed for tetrahedral mesh). |
|
February 20, 2015, 07:48 |
|
#12 |
New Member
Michael
Join Date: Feb 2015
Posts: 18
Rep Power: 11 |
hello!
I can also confirm the bug. I'm using version 2.3.0 and for a list of 45 points which clearly ly within the domain 8 are not found. If I use the sample application the same error accures. Did somebody find a solution for the problem? |
|
September 5, 2017, 14:21 |
|
#13 |
New Member
Mukul
Join Date: Nov 2016
Posts: 6
Rep Power: 10 |
Hi, I'm facing a similar issue in OpenFOAM 4.1. Did someone file a bug report?
|
|
September 19, 2017, 06:13 |
|
#14 |
New Member
Michael
Join Date: Feb 2015
Posts: 18
Rep Power: 11 |
Hei hei I used also version 3.0+ and there I do not have any problems to find the probes
|
|
Tags |
probe warning |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
How to use setField to create sphere | sega | OpenFOAM Pre-Processing | 38 | January 13, 2022 01:39 |
foamToTecplot360 | thomasduerr | OpenFOAM Post-Processing | 121 | June 11, 2021 11:05 |
[swak4Foam] installation problem with version 0.2.3 | Claudio87 | OpenFOAM Community Contributions | 9 | May 8, 2013 11:20 |
[blockMesh] BlockMesh FOAM warning | gaottino | OpenFOAM Meshing & Mesh Conversion | 7 | July 19, 2010 15:11 |
OpenFOAM14 for Mac OSX Darwin 104 | gschaider | OpenFOAM Installation | 118 | July 20, 2008 06:19 |