You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So whatever is going on wrong, is because the rho field is zero or infinite.
Based on this information I've looked at the files in the 0 folder and the problem seems to be that you have the p_rgh field set to zero, which is prohibited in this version. Given that there is heat exchange, in OpenFOAM 5 you must use the absolute pressure values (minus the hydrostatic term for the p_rgh field), given that it will calculate the rho based on pressure and temperature, using absolute values.
--> FOAM FATAL ERROR:
cannot be called for a calculatedFvPatchField
on patch room of field h in file "C:/Openfoam_Models/Meshing/check/0/domain0/h"
You are probably trying to solve for a field with a default boundary condition.
The h file in 0/domain0 cannot use the boundary condition calculated. In this specific field, it's an actual boundary that needs a condition, it cannot be merely a value calculated by the solver as a consequence of something like h=p*T.
Problem solved. As you said, my temperature boundary condition is set to calculated. I changed it to fixed value and it solved the problem. Many million thanks for your support. For now, you can close the issue and I wish your support in my future endeavors.
Activity
wyldckat commentedon Aug 10, 2020
Greetings @ananddoss2004,
The two errors that I can see from the stacktrace are the following:
ZN4Foam6sigFpe13sigFpeHandlerEi -> sigFpe
ZN4FoamdvERKNS_5UListIdEES3 -> Foam::UList
The second one seems a bit strange, but the first one indicates a sigFpe, namely "Signal Floating Point Error": https://en.wikipedia.org/wiki/Signal_(IPC)#SIGFPE
In order to get a more accurate indication of what exactly failed, please follow the instructions given here: https://github.com/blueCFD/Core/wiki/Quick-notes-on-how-to-update-build#setting-up-the-work-environment - which will tell you how to activate the
X:drive, which will allow the stack tracer to get a more accurate depiction of what went wrong.The run the solver once again and when it crashes, provide us with the full stack trace once again, including the lines of text that come before that.
Best regards,
Bruno
ananddoss2004 commentedon Aug 10, 2020
Greeting Bruno (wyldckat),
I followed your steps and attaching the full stack trace of the result below.
-attached the original file below.
check.zip
Regards,
Anand
wyldckat commentedon Aug 11, 2020
Hi Anand,
This gives us a much clearer picture :)
The sigFPE still occurs, now indicating that it occurred due to a division gone wrong:
Since now we have a specific line where the issue occurs, we can go to the source code... namely line 41 goes wrong here: https://github.com/blueCFD/OpenFOAM-dev/blob/blueCFD-Core-5.x/applications/solvers/heatTransfer/chtMultiRegionFoam/fluid/compressibleCourantNo.C#L37
So whatever is going on wrong, is because the
rhofield is zero or infinite.Based on this information I've looked at the files in the 0 folder and the problem seems to be that you have the
p_rghfield set to zero, which is prohibited in this version. Given that there is heat exchange, in OpenFOAM 5 you must use the absolute pressure values (minus the hydrostatic term for thep_rghfield), given that it will calculate therhobased on pressure and temperature, using absolute values.Best regards,
Bruno
ananddoss2004 commentedon Aug 11, 2020
Hi Bruno,
Although it solve sigFpe error, now i have patch field error that i am posting below.
Regards,
Anand Doss
wyldckat commentedon Aug 11, 2020
Hi Anand,
This actually is fairly verbal:
The
hfile in0/domain0cannot use the boundary conditioncalculated. In this specific field, it's an actual boundary that needs a condition, it cannot be merely a value calculated by the solver as a consequence of something likeh=p*T.Best regards,
Bruno
ananddoss2004 commentedon Aug 12, 2020
Hi Bruno,
Problem solved. As you said, my temperature boundary condition is set to calculated. I changed it to fixed value and it solved the problem. Many million thanks for your support. For now, you can close the issue and I wish your support in my future endeavors.
My feedback for you: 5/5.
Regards,
Anand Doss