bugs of buoyantBoussinesqPisoFoam or fixedFluxPressure in foam-extend 3.1 and 3.2
Dear foamers,
I have found some bugs in foam-extend3.1 and foam-extend3.2 My test case is /heatTransfer/buoyantBoussinesqPisoFoam/hotRoom [1]bugs in foam-extend 3.1 I changed the pressure boundary from buoyantPressure to fixedFluxPressure, Quote:
Quote:
then, I run the above case in foam-extend3.2 use one cpu thread, I found it can run!!! and with out "lookup of (1|A(U)) from objectRegistry region0 successful, but it is not a volScalarField, it is a surfaceScalarField" bugs. However, when I use mpirun, it occurs bugs: Quote:
Best Regrads, Aaron |
I am sorry I didn't seen this http://www.cfd-online.com/Forums/ope...d-1-6-ext.html
Quote:
or can administrator help me delete this post? |
Hi, Foamers
this problem has been solved, check this thread https://sourceforge.net/p/openfoam-e...ndrelease/304/ this is not a bug, change boundary field of p to this, then the case works fine Quote:
Aaron |
Hi Aaron,
I am using foam extend -3.2 and when i make the changes you suggested in the above posts while using fixedFluxPressure boundary condition, i still get error as shown below. I am using interfoam Code:
Code:
|
Hi, Vignesh
{ type fixedFluxPressure; rho rhok; rAU rUA; } this change can work in foam-extend-3.1 I encountered the same problem in extend-3.2, so I am not using extend-3.2, sorry I cannot solve your problem...... |
Hi Aaron,
Thanks for the reply, i found now an intermediate solution. it works with { type fixedFluxPressure; rho rho; rAU rAU; } After setFields, the last entry changes to (1/A(U)) which must be reset again to rAU. Then the solver runs ... But in parallel, reconstructing the case creates the problem ... |
All times are GMT -4. The time now is 15:43. |