Differences

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

--- doc:user:geometry:import:importgmsh [2015/01/08 11:07] – boman
+++ doc:user:geometry:import:importgmsh [2016/03/30 15:23] (current) – external edit 127.0.0.1
@@ Line 28: / Line 28: @@
 <note important>Problems may occur if ''gmsh.exe'' is not reachable from ''Metafor''. The easiest way to solve this problem is to manually copy ''gmsh.exe'' in the same folder as ''Metafor.exe'' (e.g. in ''c:\Program Files\Metafor'').</note>
-Examples can be found in ''apps.externalMeshers.gmshtestXX''
+__Example:__ Element generation:
+If the "Physical Group" #300 is defined in gmsh as a list of finite elements, it is converted into a ''Group'' with the same number in Metafor. This ''Group'' can be obtained from the ''GroupSet'' using the ''operator()'' member function. This ''Group'' is useful to define a ''FieldApplicator'' in Metafor.
+  app1 = FieldApplicator(1)
+  app1.push( groupset(300) )
+  interactionset.add( app1 )
+__Example:__ Boundary conditions:
+Similarly, if the "Physical Group" #200 is defined in gmsh as a list of nodes, it is converted into a ''Group'' with the same number in Metafor. This ''Group'' can be obtained from the ''GroupSet'' using the ''operator()'' member function. This ''Group'' is useful to prescribe boundary conditions in Metafor. For example, if we want to prescribe a 0-displacement to all the nodes of this group along the ''x'' direction:
+  loadingset.define(groupset(200), Field1D(TX,RE))
+\\
+More Examples can be found in ''apps.externalMeshers''