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
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.
|All times are GMT -4. The time now is 16:40.|