|
[Sponsors] |
October 16, 2012, 14:13 |
Cells disappearing when a z plane is taken
|
#1 |
New Member
Christopher Hughes
Join Date: Oct 2012
Posts: 27
Rep Power: 13 |
I am modeling flow around a cylinder that is flowing in the axial direction of the cylinder. The mesh scene displays cells in all the regions; however, when I take a z=0 cross-section (the base of the model), the following image appears. This image was taken after an initialization, just to add clarity to the problem. Has anyone encountered a similar problem? I have double checked the meshes validity and the missing cells reappear when I move just above the z=0 plane (z=1 picometer).
|
|
October 17, 2012, 01:41 |
|
#2 |
Senior Member
siamak rahimi ardkapan
Join Date: Jul 2010
Location: Copenhagen, Denmark
Posts: 220
Rep Power: 17 |
Is it a symmetry plane?
|
|
October 17, 2012, 07:43 |
|
#3 |
New Member
Christopher Hughes
Join Date: Oct 2012
Posts: 27
Rep Power: 13 |
In the model that area is defined as an inlet boundary. The z=0 plane is a derived part. The model was generated in STAR-CCM+ based on sketches and extrusions, etc from the x-y plane.
|
|
October 17, 2012, 11:59 |
|
#4 |
Senior Member
siamak rahimi ardkapan
Join Date: Jul 2010
Location: Copenhagen, Denmark
Posts: 220
Rep Power: 17 |
I think there is no problem. The reason is that you add a plane at the edge of the domain. I you move the plane section further ( for example z=0.001) then you will see there is no problem.
|
|
October 17, 2012, 13:33 |
|
#5 |
New Member
Christopher Hughes
Join Date: Oct 2012
Posts: 27
Rep Power: 13 |
Why should cells that exist on the boundary, not show up when a z plane of that boundary is taken? How is that not cause for concern? As it is, this shows that there is no value at those locations (in this case it is temperature). How does no temperature at z=0 not be a problem?
|
|
October 17, 2012, 14:44 |
|
#6 |
Senior Member
Join Date: Oct 2009
Location: Germany
Posts: 636
Rep Power: 21 |
The reason why you don't see values there is the plane section, just like siara817 already said.
But let's start from the beginning: "Why should cells that exist on the boundary, not show up when a z plane of that boundary is taken?" This plane section should exactly go through your boundary, at least in theory. The issue is, you're not modelling something on a sheet of paper, where you can say 0.000000000000000000000000001 = 0.000000000000000000000000001. You're modelling something with a computer. And what you're modelling requires floating point numbers. And there are no exact floating point numbers for a computer, you will always have some deviation. See http://en.wikipedia.org/wiki/Floatin...dern_computers for more details. Let's say the deviation is some 1e-7m. Then the plane section you put ON the boundary is NOT everywhere ON the boundary. There might be positions where it is just outside the domain. Even when it's only some 1e-7m, it IS outside. Or the cell faces are slightly moved towards the domain - also just some 1e-7m, but it's enough for the plane section not to cut through the cell face. "How is that not cause for concern?" Pretty simple - you just need to know why you don't see any values there and you know that it is nothing to be concerned. "As it is, this shows that there is no value at those locations (in this case it is temperature)." Right. But who cares? It's outside the domain, so there is no need for values. "How does no temperature at z=0 not be a problem?" The same reason why a temperature at z=-989898435798745 is no problem. The solver doesn't care if there is a value at z=0 - just because it is OUTSIDE THE DOMAIN. It is just a visibility problem. That you can't see a value there doesn't mean, the solver will have problems, as long as there is a value provided on every boundary face. Since this face might lie behind you plane section, there can a value be provided, although you don't see it. So what I suggest: Don't try to visualize a plane section which is located exactly on a boundary surface. Visualize the boundary surface itself. Just put it in the displayer instead of the plane section, and you will see, it's all okay.
__________________
We do three types of jobs here: GOOD, FAST AND CHEAP You may choose any two! |
|
October 17, 2012, 16:18 |
|
#7 |
New Member
Christopher Hughes
Join Date: Oct 2012
Posts: 27
Rep Power: 13 |
I get it now, thank you for both of your responses.
|
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[snappyHexMesh] No layers in a small gap | bobburnquist | OpenFOAM Meshing & Mesh Conversion | 6 | August 26, 2015 09:38 |
[Netgen] Import netgen mesh to OpenFOAM | hsieh | OpenFOAM Meshing & Mesh Conversion | 32 | September 13, 2011 05:50 |
[snappyHexMesh] snappyHexMesh won't work - zeros everywhere! | sc298 | OpenFOAM Meshing & Mesh Conversion | 2 | March 27, 2011 21:11 |
[snappyHexMesh] snappyHexMesh aborting | Tobi | OpenFOAM Meshing & Mesh Conversion | 0 | November 10, 2010 03:23 |
physical boundary error!! | kris | Siemens | 2 | August 3, 2005 00:32 |