December 17, 2019 at 7:03 pmkabitSubscriber
in order to calculate the mass exchanged across a surface for a steady state simulation, I have created a seperated mesh region. In the post processing, I splitted the region into a surface with a positive normal velocity component and a surface with a negative velocity component. The results of the massFlow function for both surfaces are approximately zero, which should not be the case. Calculating the mass flow by areaint(u*density) gives reasonable results. However, the results for the two surfaces should be equal, but differ significantly.
Does anybody know, why this happens and if there is a workaround for this problem?
December 18, 2019 at 11:40 amRobAnsys Employee
If you're reporting on an interior surface turn it into a wall (you'll see wall & wall:shadow) and then back to an interior. It's because the interior surface normals aren't set in the mesh.
December 18, 2019 at 2:51 pmkabitSubscriber
Thank you very much for your reply.
Do you know if there is also a way to do this in CFX?
December 20, 2019 at 9:22 amRobAnsys Employee
Probably much the same approach in CFD Post using the velocity components normal to the surface(s) or a flux.
December 20, 2019 at 9:36 amDrAmineAnsys Employee
You can try using the mesh location for that. For that reason you decompose in pre-processing and then define monitor in CFX-Pre and access the primitive 2D boundary in CFD-Post.
December 26, 2019 at 3:31 pmkabitSubscriber
Thank you both for your help.
The calculation of the mass flow on the interior surfaces seems to work now. However, another problem has now occured. If I calculate the mass flow across an iso-clip surface, I get different results than on the interior surface, even if both surfaces are equal.
Does anybody know, how to fix this?
January 2, 2020 at 11:39 amRobAnsys Employee
How different? The isosurface will pull data from surrounding cells and interpolate, the interior calculates the value directly with no interpolation. Also remember the issue with normals I mentioned.
January 21, 2020 at 4:57 pmkabitSubscriber
sorry for my late respond. I just used the interior surface directly for my calculations to avoid the interpolation errors, which seems to work fine.
Thank you very much for your help.
- You must be logged in to reply to this topic.
Boost Ansys Fluent Simulations with AWS
Computational Fluid Dynamics (CFD) helps engineers design products in which the flow of fluid components is a significant challenge. These different use cases often require large complex models to solve on a traditional workstation. Click here to join this event to learn how to leverage Ansys Fluids on the cloud, thanks to Ansys Gateway powered by AWS.
Earth Rescue – An Ansys Online Series
The climate crisis is here. But so is the human ingenuity to fight it. Earth Rescue reveals what visionary companies are doing today to engineer radical new ideas in the fight against climate change. Click here to watch the first episode.
Subscribe to the Ansys Blog to get great new content about the power of simulation delivered right to your email on a weekly basis. With content from Ansys experts, partners and customers you will learn about product development advances, thought leadership and trends and tips to better use Ansys tools. Sign up here.
- Suppress Fluent to open with GUI while performing in journal file
- Floating point exception in Fluent
- What are the differences between CFX and Fluent?
- Heat transfer coefficient
- Getting graph and tabular data from result in workbench mechanical
- Difference between K-epsilon and K-omega Turbulence Model
- The solver failed with a non-zero exit code of : 2
- Time Step Size and Courant Number
- Mesh Interfaces in ANSYS FLUENT
- error: Received signal SIGSEGV
© 2023 Copyright ANSYS, Inc. All rights reserved.