|February 13, 2010, 08:25||
Join Date: Sep 2009
Posts: 142Rep Power: 7
I used "mapFields -consistent" successfully to map my first mesh results on a new finer mesh.
When I restart the job I have "floating poit exception".
I saw in new mapped mesh some strange point (see the figure attached). I think because in old coarses mesh where now is air, was surface! So here I got 0 value and I obtain "floating point exception" (I have not "nan"). Is it right?
Then I tried "mapFields" without "-consistent" but I obtain:
Thanks in advance
|February 17, 2010, 23:57||
Join Date: Mar 2009
Posts: 255Rep Power: 12
Seems likely that you get the floating point exception due to some point that get unphysical values after the mapping. It would be nice with a OF utility that allows the user to bound scalars with some min() and max() function (setFields?). A way to do that manually would be to import the (ascii) data into matlab and use the functions there... seems a bit messy, but could still save time if it takes long time to obtain the mapped fields.
|Thread||Thread Starter||Forum||Replies||Last Post|
|Needed Benchmark Problems for FSI||Mechstud||Main CFD Forum||4||July 26, 2011 12:13|
|mapFields ignores sourceTime for -parallel source||andersking||OpenFOAM Bugs||2||September 2, 2009 10:38|
|Some problems with Star CD||Micha||CD-adapco||0||August 6, 2003 13:55|
|unstructured grid||sreekanth||Main CFD Forum||1||August 6, 2001 15:09|
|Using Fluent for Geophysical Problems||Hassid Samuel||FLUENT||0||February 23, 2001 07:04|