|July 28, 2009, 13:02||
Monitor engineering data - Mflux not consistent?
Join Date: Jul 2009
Posts: 1Rep Power: 0
I have a simple model of a duct with variable cross-section area. Along its length, I've defined several shells which represent cross sections.
If I load the converged solution and calculate the mass flow rates through Post >> Fluxsum >> Shell type..., I get the same value for all shells, and that's how it should be.
However, if I define an internal boundary at these cross sections and let Mflux be monitored, the values I get in the *.erd file make no sense at all (not in kg/s nor in kg/( m2 s) ).
I'm pretty sure the internal boundaries are defined correctly - all faces are oriented to the same direction and so on. The Mflux (in [kg/s]) are consistent at the inlet and outlet with the boundary conditions. But the ones within the solution domain are not.
Does anyone know what is going wrong?
|flux, mass, mass flux, mflux, monitor mass flux|
|Thread||Thread Starter||Forum||Replies||Last Post|
|Exporting data (cell values, ascii) and obtaining more data than cells!||TfG||FLUENT||3||April 3, 2015 00:18|
|【Help】"Error: Update_Time_Level: invalid data"||Chen||FLUENT||2||August 24, 2014 07:51|
|export data at nodes||Meenu||FLUENT||1||December 30, 2011 02:24|
|Saving particle (DPM) data to file?||Philip||FLUENT||2||June 12, 2006 01:41|
|How to update polyPatchbs localPoints||liu||OpenFOAM Running, Solving & CFD||6||December 30, 2005 18:27|