Entries for December 2016

Originally Posted by wyldckat

Greetings Ben,

I think it's not impossible, but it's probably very arduous to do. There are a few solutions I can think of:

• Do it interactively: http://openfoamwiki.net/index.php/Contrib/SwiftBlock
• Cheat by using snappyHexMesh, as shown in the tutorial "mesh/snappyHexMesh/iglooWithFridges".
• Use Plot3D format to design the mesh, then convert with datToFoam and then run blockMesh.
• Use OpenFOAM's codeStream and code it directly

Originally Posted by wyldckat

Greetings Danath,

Well, since you're building your own code, I suggest that you study this wiki page: http://openfoamwiki.net/index.php/HowTo_debugging

As for the output you're getting:

1. Line #1 is telling you that a SIGFPE has been triggered: http://en.wikipedia.org/wiki/SIGFPE#SIGFPE
2. Line #3 is telling you more or less where the problem occurred.

Best regards,
Bruno

Originally Posted by hjasak

Well, put on your 1970-s hat (or a shirt with huge collars!) and let's talk about memory peaks. For simpleFoam, the memory peak is at the point of creation of the pressure equation, because, unlike PISO, I am allowed to delete the momentum matrix before the creation of the pressure matrix. Therefore, I make the momentum matrix a tmp and call UEqn.clear(); at an opportune place in the code and drop the peak memory requirement by one complete assymetric matrix!

Originally Posted by knuckles

In system/fvSolution, I can specify tolerances on matrix solvers:

My understanding is that openfoam will construct an equation of the form Ax = b, solve it in some iterative way, and will stop iterating when the residual, |Ax