First, I would like to thank everybody who will spend time reading this post.
So, that's it : for the second time I tried to make a calculation with a coarse mesh and nothing wrong happened. Then I tried with a finer mesh and I had this kind of error at the first iteration:
This is my case:
(You can click to enlarge the pictures)
I wanted to use pisoFoam with a k-epsilon turbulence model.
This is my first mesh (around 50 000 cells):
...and the result of the first calculation:
I found this result good, so I did a finer mesh (around 500 000 cells):
... and I made a "mapField" onto it from the coarse mesh:
But the story ends here...
My fvSchemes :
I think you used a fine mesh near the surface the body, this is good, but there
is a problem with the change of cellīs size. I think the solution maybe not to
make big change of size between cells.
I donīt know why you are using triangular cells. Square cells are better.
Iīm doing a case similar to yours. I simulate a flat plate with pisoFoam, if you want we could talk about it. I calculate the forces in the bluff body and the aerodynamic coef.
My name is Daniel and my email is:
The error message tells you that you are dividing by 0 within the k-epsilon equations. Are you sure that you have not changed the boundary conditions/internal values for either k or epsilon from the coarse to the fine mesh? Neither property most be 0, but should take a finite value.
Thank you very much for your replies.
Actually, I did that case as an example for a school project consisting in presenting and giving the bases of OpenFOAM. As I didn't find my mistake, I made another case, very similar but not exactly the same, and this time it worked. So, I don't spend any time on this case at all, but would be glad to speak about OpenFOAM anyway. :)
Just for the pleasure, my final case:
The rough mesh :
(You can click to enlarge the pictures)
The velocity field after few iterations:
The mesh with a refinement box enclosing the high velocity gradient zone:
The refinement box to enclose the vortex after having rotated the mesh:
The final result:
PS: The mesh isn't triangular. :) It's a matter of visualization with Paraview when you use a cutting plane.
Thank you very much for your details about the error. As a novice like me, one of the much difficult thing to do is to decrypt the error messages.
I thought this kind of error appeared when the calculation "blows up" (diverges). I have already seen such error after maybe 150 iterations on a case, and after reducing the current number this error disappeared.
In fact, I don't know how to read these error messages. For example, what are these "#1", "#2", etc.
And, how do we know that it is a division by zero in the k-epsilon equation ? Yes, one can read "divide" and "KEpsilon" in the error message, but how to be sure it is a division by zero ? :)
I think I should learn to understand these message by reading some C++ documentation, isn't it ? :)
But thank you very much for your explanation.
Sure, here is a small explanation. I have always interpreted the numbering as a kind of unwinding of the error, essentially like an onion, where the inner part, the actual problem is given "#0", and then you can trace back from there. So:
#2: (SIGFPE) You can always try wiki, however, this error tells you that you have performed an illegal arithmetic operation.
#3: This tells you that the SIGFPE reported in #2 originates from a divide operator, meaning that the denominator is numerically taken as zero.
#6: Those in #4 and #5 tells something about the fields, which cause the error, and this part of the error tells you that it occurs in kEpsilon.correct().
Therefore find the place in this method in the object kEpsilon, where you divide by zero.
The reason for my suggestion to the origin of the error is:
1. It is the very first encounter with a solution to either k or epsilon after the start of the simulation, because the top of what you have reported states "starting time loop".
2. I have seen questions about this error so many times on this forum during the last 3-4 years. (I know it does not help you, though :) )
I hope my suggestions have solved your problem.
Happy Easter :)
Hi,friend,i got the same error when i calculated my case.Did you solve your question? Can you give me some advice? Thanks a lot .My e-mail is :firstname.lastname@example.org.Please contact me,ok?
Unfortunatelly, I didn't solved this problem and won't use OpenFoam before a while I think (no time).
If you are like me using a coarser and a finer mesh, you can maybe take a look to the danielcebrian or ngj advices below (cells too much different between coarse and fine meshes or a change in the k-epsilon boundary or initial conditions) ?
In each case, have a happy new year ! :)
Thanks for your reply.I think i should discuss it with my boss.Happy new year.
|All times are GMT -4. The time now is 10:30.|