|
[Sponsors] |
October 17, 2008, 10:03 |
Empty cells in mesh
|
#1 |
Guest
Posts: n/a
|
Let's say that I create my geometry, and I want to make a part of it moving. Hence, i have to create the mesh taking into account the whole path of the object. Par exampe my object is 5cm in X-dir, it moves for 10cm in X-dir, so the mesh dimension in X-dir should be 15cm. So, in the first time step, the 10 out of 15cm will be totally empty.
My question is this: do the empty cells of the mesh affect the calculation time? Do I have to create "blocking boxes" so as to cover all the empty cells each time step? |
|
October 22, 2008, 00:14 |
Re: Empty cells in mesh
|
#2 |
Guest
Posts: n/a
|
In this case you will need a big mesh. If you use "blocking boxes" then you will have to make them moving so that part of interest can move into new location. For a moving object all the cells necessary are so all the cells occupied by moving object are allocated to the memory. So using the "blocking boxes" will not help much in this case. You can use a stationary blocking box in the part of the domain where the moving object or any fluid won't arrive.
Now about the "Empty cells": all the cells not occupied by a solid object (open cells) get allocated to the memory. But if a open cell is empty then the solver doesnot spend time performing calculations in this cell. So empty cells will affect the calculation time as they occupy memory but the solver doesnot get completely bogged down as it doesn't have to spend time in calculation in these cells. In general it is recommended to block as many cells as possible. |
|
October 22, 2008, 00:17 |
Re: Empty cells in mesh
|
#3 |
Guest
Posts: n/a
|
looks like the last line got truncated in my earlier response. Here is the correct line: So empty cells will affect the calculation time as they occupy memory but the solver doesnot get completely bogged down as it doesn't have to spend time performing calculations in these cells. In general it is recommended to block as many cells as possible.
|
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Mesh motion with Translation & Rotation | Doginal | CFX | 2 | January 12, 2014 07:21 |
[snappyHexMesh] non-smooth mesh | Svensson | OpenFOAM Meshing & Mesh Conversion | 11 | January 18, 2012 10:13 |
Adapt mesh without modifying boundary layer cells? | Freeman | FLUENT | 0 | February 22, 2009 15:11 |
[mesh manipulation] TranformPoints gives skewed mesh Possible Bug | andersking | OpenFOAM Meshing & Mesh Conversion | 3 | March 25, 2008 22:33 |
Mesh motion Hex cells vs tets | kev4573 | OpenFOAM Running, Solving & CFD | 6 | December 13, 2007 15:37 |