CFD Online Discussion Forums

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)
-   ANSYS Meshing & Geometry (https://www.cfd-online.com/Forums/ansys-meshing/)
-   -   [GAMBIT] mesh to capture boundary layer (https://www.cfd-online.com/Forums/ansys-meshing/131105-mesh-capture-boundary-layer.html)

Arvin March 9, 2014 04:50

mesh to capture boundary layer
 
Hi, I want to capture the boundary layer developed in natural convection phenomena in a cube geometry with flux supplied at bottom of cube. I want more mesh near the bottom of cube and coarse mesh at top. I tried by creating two volumes and meshed separately but it doesn't work in fluent.

Please provide me with a solution. I would really appreciate your time and effort.Thanks!!

ghost82 March 9, 2014 08:17

Hi,
you can use boundary layer:

http://combust.hit.edu.cn:8080/fluen...301.htm#mg0301

Or size functions:

https://www.sharcnet.ca/Software/Gam...ide/mg0502.htm

No need to create 2 volumes.

What does it mean "but it doesn't work in fluent"??

Daniele

Arvin March 9, 2014 08:44

hi
 
Hi Daniele, I tried using boundary layer mesh. I want to pack 1000 rows in a depth of say 15 units. But, Gambit crashes whenever I try to do that. I am able to pack 190 rows within depth of 5 units only with growth factor of 1. After that any change causes Gambit to crash. Why is that?

Heat flux must be supplied at bottom face of my geometry.But when I load the double volume mesh file, flux gets applied in the interior wall which I created to separate the two volumes. I defined the type of that wall as interior and also checked my grid and boundary conditions, but flux keeps getting applied to interior wall. That is the volume which I meshed densely doesn't get solved. Why is that?

Thanks!!

ghost82 March 9, 2014 08:52

Maybe you have "problems" with hardware (low amount of ram or similar)..
So split your volume ("the big cube") by a face and let connected the 2 volumes, so that the face which divides the 2 volumes is shared by both volumes.
Don't assign any boundary condition to that internal face, it will automatically detected in fluent as an internal face.

Daniele

-mAx- March 10, 2014 02:13

As Daniele mentionned it sounds like a hardware issue.
You wrote that you were able to mesh your model with 190 rows. In this case how many cells do you have in your domain, and how much RAM do you have on your hardware?

Arvin March 10, 2014 09:22

Hi Daniele, I didn't assign any boundary condition to that internal face but still the flux gets applied to the top face instead of bottom face. I meshed the volume below the interior densely since I am supplying flux to bottom face only. I can't understand what is the problem.

Arvin March 10, 2014 09:23

Hi Max
I have 3,45,600 hex cells and my RAM is 4GB.

ghost82 March 10, 2014 12:02

Quote:

Originally Posted by Arvin (Post 479137)
Hi Daniele, I didn't assign any boundary condition to that internal face but still the flux gets applied to the top face instead of bottom face. I meshed the volume below the interior densely since I am supplying flux to bottom face only. I can't understand what is the problem.

upload the cas file somewhere and I will look at it.

-mAx- March 11, 2014 00:34

Quote:

Originally Posted by Arvin (Post 479138)
Hi Max
I have 3,45,600 hex cells and my RAM is 4GB.

If you are working on windows OS, there is no real 64-bit version of Gambit. That means Gambit is limited on RAM (especially if you are trying to mesh your domain on the fly, eg just one volume)
As Daniele mentionned, you may try to split your volume, for giving Gambit any chance to mesh your BL without crashing, for instance isolate your BL region as a volume and mesh it again with more than 190 rows)


All times are GMT -4. The time now is 06:56.