Hi all,

I was hoping that a very frustrating error would have been eliminated in the new CFX-Build 5.6:
Could not find the file *.fro for displaying purposes



Unfortunately, it is still there. What does it mean? What should I do to prevent it from occuring again, and again, and again? I can't figure it out. I think it depends on the local monthly rainfall or something like that.

Cheers, Astrid


I have mentioned the error before:

http://www.cfd-online.com/Forum/cfx_....cgi?read=3957

Counter to your experience, local meteorological conditions do not affect this....it occurs when the surface mesher has not returned a valid error or warning and CFX-Build looks unsuccessfully for a surface mesh to display. If this occurs repeatedly, then instead of creating the whole surface mesh, try verifying parts of the mesh and using a simple bisection method when the problem occurs, you will soon find the offending surface. Then try modifying the mesh length scales on the offending surface and if that is unsuccessful, you may need to rebuild the surface itself. Alternatively, the surface mesher may not have started (hence you get no errors from it) and the topology of the geometry you are trying to mesh is invalid, but the process is not trapping it. What type of geometry are you trying to mesh? Are there subdomains etc.? There are rarely changes to improve topology issues and hence 5.5.1 & 5.6 would probably behave the same

I work under Linux (Red hat 7.3) on a relatively easy case. I get the error when I write out the .def-file. Sometimes I get it during surface meshing, sometimes during the creation of the prismatic elemtents and somtimes during volume meshing. I can't figure out what goes wrong. When I quit build and reopen the case for some unknown reason the problems can be gone with the wind.

Some surfaces are singly parameterised. Can that be the problem? Otherwise, I'm lost..........

Astrid

It may be that this error message is just showing up as a catch all when any part of the meshing process fails and control is handed back from the meshing executable to Build. The fact that when you shutdown Build and restart things are OK, points to problem files appearing in the temporary working directory (#cfx.xxxx). Are you working in a directory with a long path?