Metafor

ULiege - Aerospace & Mechanical Engineering

User Tools

Site Tools

You are here: metafor.ltas.ulg.ac.be » doc » Documentation » geometry » mesh » 2D Meshers (Surfaces)
Trace:
doc:user:geometry:mesh:2d

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
doc:user:geometry:mesh:2d [2014/08/08 16:03] – jorisdoc:user:geometry:mesh:2d [2021/12/17 14:02] (current) – boman
Line 1: Line 1:
-====== 2D meshers ======+====== 2D Meshers (Surfaces) ======
  
 Metafor has a few integrated meshers, quite simple but usually capable of meshing parts that are not too complicated. However, 2D meshers require that the ''[[doc:user:geometry:user:contours|wire]]'' delimiting the domain has the right orientation. The wire must be defined with its "area to the left", which means that when the wire is followed along its orientation (defined by the succession of its [[doc:user:geometry::user:courbes|curves]]), the matter of the part is on the left-hand  Metafor has a few integrated meshers, quite simple but usually capable of meshing parts that are not too complicated. However, 2D meshers require that the ''[[doc:user:geometry:user:contours|wire]]'' delimiting the domain has the right orientation. The wire must be defined with its "area to the left", which means that when the wire is followed along its orientation (defined by the succession of its [[doc:user:geometry::user:courbes|curves]]), the matter of the part is on the left-hand 
Line 40: Line 40:
            (mat31, mat32, ..., mat3nbmax),             (mat31, mat32, ..., mat3nbmax), 
            (mat41, mat42, ..., mat4nbmax)   )            (mat41, mat42, ..., mat4nbmax)   )
-    TransfiniteMesher2D(sideset(number)).execute2(mat, type)+    TransfiniteMesher2D(sideset(number)).execute2(mat, type, tri)
  
 where ''mat'' is a python [[doc:user:general:glossaire#tuple]] with 4 components. Each component is a tuple which contains the number of the curves which constitute each edge. Each of these four edges can be made of a different number of curves. where ''mat'' is a python [[doc:user:general:glossaire#tuple]] with 4 components. Each component is a tuple which contains the number of the curves which constitute each edge. Each of these four edges can be made of a different number of curves.
Line 80: Line 80:
 ==== Description ==== ==== Description ====
  
-This mesher is a new implementation of L. Stainer's work, which contains an offset and frontal mesher. It is usually rather disappointing.+{{:doc:user:ico-expert.png?40 |Expert!}}{{:doc:user:ico-danger.png?40 |Danger!}} This mesher is a new implementation of L. Stainer's work, which contains an offset and frontal mesher. It is usually rather disappointing.
  
 ==== Use ==== ==== Use ====
Line 94: Line 94:
 where ''d'' is the average length of the mesh elements edges to generate. where ''d'' is the average length of the mesh elements edges to generate.
  
-===== Gen4 mesher=====+===== Gen4 mesher =====
  
 ==== Description ==== ==== Description ====
Line 100: Line 100:
 This quadrangular mesher is based on [[http://www-lacan.upc.es/sarrate/|Sarrate]] algorithm. This method consists in diving the domain in a recursive way until only one quadrangle remains. It is very robust, and enables efficient meshing of complex domains. This quadrangular mesher is based on [[http://www-lacan.upc.es/sarrate/|Sarrate]] algorithm. This method consists in diving the domain in a recursive way until only one quadrangle remains. It is very robust, and enables efficient meshing of complex domains.
  
 +<note important> By design, running twice Gen4 with the exact same parameters does not necessary lead to the same mesh. This can lead to some issues when running a simulation on a computer and trying to load results on another. To avoid this, the mesh generated is saved in a ".gen4" file, which will be read when loading a fac instead of creating the mesh anew. This ".gen4" file is not automatically deleted when cleaning the worskpace, so if you modify your mesh parameters, you must manually delete this file. </note>
 ==== Possibilities ==== ==== Possibilities ====
  
Line 110: Line 111:
   * with topological correction   * with topological correction
  
-==== Use====+==== Use ====
  
 These lines are used to mesh the face #1 of the domain, whose vertices (points #1, #2, #3 and #4) densities are 0.1, 0.1, 0.2 and 0.05. These lines are used to mesh the face #1 of the domain, whose vertices (points #1, #2, #3 and #4) densities are 0.1, 0.1, 0.2 and 0.05.
Line 121: Line 122:
   mesher.execute()    mesher.execute() 
  
-A default density, used unless explicitly stated differently, can be defined. This way, a density is only defined on specific mesh points. It no value is assigned in the data set, $0.1$ is taken as default density value.+A default density, used unless explicitly stated differently, can be defined. This way, a density is only defined on specific mesh points. If no value is assigned in the data set, $0.1$ is taken as default density value.
  
 __CAREFUL__ : The face #1 must be defined in the XY plane. __CAREFUL__ : The face #1 must be defined in the XY plane.
Line 138: Line 139:
 ==== Use ==== ==== Use ====
  
-See, for example, the case ''apps.qs.triangleMesher''. After creatin a face ''Side(1)'', it was meshed with a maximal area of 0.05 as criterion.+See, for example, the case ''apps.qs.triangleMesher''. After creating a face ''Side(1)'', it was meshed with a maximal area of 0.05 as criterion.
  
 <code> <code>
doc/user/geometry/mesh/2d.1407506635.txt.gz · Last modified: 2016/03/30 15:22 (external edit)
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki