|
[Sponsors] |
[ICEM] surface mesh size, unstructured 3d mesh |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
March 2, 2015, 14:35 |
surface mesh size, unstructured 3d mesh
|
#1 |
New Member
Join Date: Nov 2012
Posts: 2
Rep Power: 0 |
hello,
I hope somebody could clarify, why tris sizes differ so much on the same part (see screenshot). I am trying to generate 3D tetras, and this kind of mesh gets generated when I go straight to tetras (Mesh -> Compute Mesh -> Volume Mesh). If I only compute surface mesh (patch independent), this does not happen, though another problems appears. The part mesh size max is set as 0.004 (I can set it as 0.002, it makes no difference), curvature refinement is on with 0.003 min size limit. The surface edges are 0.01 apart, the geometry has been built in ICEM. Thank you. |
|
March 2, 2015, 17:07 |
|
#3 |
New Member
Join Date: Nov 2012
Posts: 2
Rep Power: 0 |
it does not work.
Sorry for not being clear: settings for max element size are only being respected on part of the surface, and my question is why it takes place? I also found recently that it only happens when I generate tetras with hexa-core. Maybe that is the reason. Thanks |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[snappyHexMesh] problems generating clean mesh | Christian_tt | OpenFOAM Meshing & Mesh Conversion | 2 | June 20, 2019 06:39 |
[Other] dynamicTopoFVMesh and pointDisplacement | RandomUser | OpenFOAM Meshing & Mesh Conversion | 6 | April 26, 2018 08:30 |
[snappyHexMesh] SnappyHexMesh no layers and no decent mesh for complex geometry | pizzaspinate | OpenFOAM Meshing & Mesh Conversion | 1 | February 25, 2015 08:05 |
Cluster ID's not contiguous in compute-nodes domain. ??? | Shogan | FLUENT | 1 | May 28, 2014 16:03 |
Icemcfd 11: Loss of mesh from surface mesh option? | Joe | CFX | 2 | March 26, 2007 19:10 |