snappyHexMesh does not remove internal cells
1 Attachment(s)
Hi everyone. I would really appreciate your help.
I use snappyHexMesh to create a grid around a pile. The pile is in stl format. But when I apply castellatedMesh it does not remove the cells inside. The geometry doesn't have any holes and I have execute the checkmesh, it seems eveything is OK. Here is my snappyHexMeshDict: Quote:
|
This is the results of surfaceCheck command:
Quote:
|
1) Is your stl geometry fully closed?
2) Is the locationInMesh coordinate inside the domain but out of the box? 3) Are you viewing the latest time step in paraview? Sent from my LG-H818 using CFD Online Forum mobile app |
Thank you sooo much, I just made a silly mistake. The refinementSurfaces should be "big" but not "big.stl".
|
Quote:
Thx a lot!I've fixed it. |
I would like to also thank the contributors to this entry. I had a similar issue and came across the following techniques to resolve it:
1- Always make sure of the quality of the surface before running snappyHexMesh. Under the triSurface directory, run: surfaceCheck object.stl This should confirm the following: a: surface must be close b: all edges must be connected to two faces c: number of unconnected parts = 1 d: number of zones = 1 2- In snappyHexMeshDict and under refinementSurfaces, you must have the name of the surface e.g. object, NOT the filename of the surface object.stl. 3- Make sure you use locationInMesh with a coordinate that is NOT on a face or edge even after refinement, but always inside a cell. |
Hello Amir,
Thank you for your valuable addition. Is there a way before meshing to make sure that locationInMeeesh is within the cell rather than on face or on the edge of the cell. Regards |
SnappyHexMesh does not remove cells
Hello everyone,
I have the same problem. However, I multiple stl files. They are not closed individually but all of them together closes all the boundaries. I need your help. |
Hello Jalil,
Little information about your case and problem would be beneficial to give some suggestions. In general, if overall body is closed, then there should not be any problem. Open your all stl files in paraview and check again if they are water tight. Regards |
no snapping!
Quote:
I dont know how I can check if the whole geometry is "water tight" or not, should I do that visually or there is a way to do it properly? |
Quote:
this is not a problem, you should do the following: create a folder that contains only your muliple stls (no other stls files at least) I am assuming they a re assci stls (and not binary) 1. you open terminal $ cat *.stl >> model.stl (this will create a only stl that if your surface meshes are correct, this should give a water tight mesh you can check it with surfaceChek command.) 2. you use a region stl configuration in snappy hex inside the geometry dict. example bellow. 3. one really important thing to take in accound is that you should give a refiment level, even if it is (0 0) to each region in castellated if you dont do this snappy will have problems. Code:
/*--------------------------------*- C++ -*----------------------------------*\ best regards. |
Quote:
surfaceCheck model.stl | tail -9 | head -1 should give you as output only that line, but in any case you will see this in surfaceCheck. as I menioned in my previous post, when using multiple stls you should fuse it into one and then use surfaceCheck to see it is waterthight. (2 separate stls can be not waterthight but their fussion can be) best regards. |
Quote:
If I am not mistaken, for snappyHexMesh and simualation, I need to have separated stl file for each boundary condition. When I give the separated stl files, snappyHexMesh does not snap the outer part (I am interested in the inner part). I am sure about the locationInMesh. Do you have any advice? |
Quote:
you dont need separate stls files, you need an stl with regions (one file). following the step 1. in https://www.cfd-online.com/Forums/op...tml#post805195 will give you exactly that, an stl with a region for each stl that you used to create them. imagine you have 1.stl, 2.stl & 3.stl , you use cat *.stl >>model.stl you will have 4 stls in total the three originals that you will not use, and model.stl that will be separated in regions inside of the file (each region will be each of original stls). you should use the 4th stl (model.stl) for snappy, have a look at the geometryDict inside the example in snappy that I post in the post I mentionned previously. here you indicate one file, with regions inside of it. Franco |
Quote:
just one more question, to add boundary layers, I modified the dictionary as below, but it didnt create the boundary layers. addLayersControls { relativeSizes true; layers { InnerCylinder { regions { "wall1" { nSurfaceLayers 3; } } } } I have also tried this, but no luck! addLayersControls { relativeSizes true; layers { "wall1" { nSurfaceLayers 3; } } |
Quote:
the layers you have to define them like this: Code:
layers also take in accound that if snappy does not achive the 100% of the meshQuality, it will not create layers. so in my opinion from the little info, or you defined wrong in the layer dictionary or you are not achiving the quality so snappy is able to add the layer ps please use CODE mode when posting part of dictionaries so it is easier to read. |
Quote:
Thank you very much. It was indeed becasue of low quality of mesh. After refining, I got the boundary layers. The pdf is also very useful. |
All times are GMT -4. The time now is 13:02. |