X-Git-Url: http://git.salome-platform.org/gitweb/?p=modules%2Fsmesh.git;a=blobdiff_plain;f=doc%2Fsalome%2Fgui%2FSMESH%2Finput%2Fabout_meshes.doc;h=a69bd1223f9e10455a2870a0176a64de99619a0f;hp=3864329e427815fdcdcf7666436b65f16a345c55;hb=fd1943809d016d0223da20a2a492b157cb17146a;hpb=79b1ac2b6df9117f16f11d444b1f165d477a1813;ds=sidebyside diff --git a/doc/salome/gui/SMESH/input/about_meshes.doc b/doc/salome/gui/SMESH/input/about_meshes.doc index 3864329e4..a69bd1223 100644 --- a/doc/salome/gui/SMESH/input/about_meshes.doc +++ b/doc/salome/gui/SMESH/input/about_meshes.doc @@ -2,85 +2,100 @@ \page about_meshes_page About meshes -\n \b MESH represents a discretization of a geometrical CAD model into -a set of entities with a simple topology. In MESH there are two -options of creation of meshes, you can: +\n \b MESH represents a discrete approximation of a subset of the +three-dimensional space by \ref mesh_entities "elementary geometrical elements". +Mesh module provides several ways to create the mesh: -The topology of a mesh is described by the relationships between its -entities including: +Meshes can be edited using the MESH functions destined for +\ref modifying_meshes_page "modification" of meshes. - - -        These entities are -considered as topological entities and they don't -imply any geometric representation. Only \b Nodes reference geometric -representations of points with definite coordinates. The node entity -will contain additional information about its position in the space -and its relations with the meshed CAD model. Its position could be -described in the following way: - - - -

Connections

-Each mesh entity bounds 0 or more mesh entities of higher -dimension. In the same way each mesh entity is bounded by 0 or more -mesh entities of lower dimension: +The \b structure of a SALOME mesh is described by nodes and elements based on +these nodes. Geometry of the element is defined by the sequence of +nodes constituting it and +the + connectivity convention (adopted from MED library). Definition of +the element basing on elements of lower dimension is NOT supported. +\anchor mesh_entities +The mesh can include the following entities: -You can notice that there are two types of connections: \b inverse and -\b direct connections. - -

Inverse connections

- -This relationship has a particularity that the order of bounded -entities has not a direct meaning. Also the number of bounded entities -is not fixed. - -\b Example: The edges surrounding a node. The 3rd edge has no more -sense that the 5th one. - -

Direct connections

- -This relationship has a particularity that the order of bounding -entities is meaningful. The number of bounding entities is fixed and -depends on the type of the entity (hexahedron, tetrahedron,?). - -\b Example: An edge is composed of two nodes. A face is composed of 3 -or 4 edges depending if we are dealing with triangles or quadrangles. - -The connections are not only restricted to entities of one dimension -higher or lower. For example some algorithms may be interested to -retrieve all the faces surrounding a node. +Every mesh entity has an attribute associating it to a sub-shape it is +generated on (if any). The node generated on the geometrical edge or +surface in addition stores its position in parametric space of the +associated geometrical entity. + +SALOME supports elements of second order, without central node +(quadratic triangle, quadrangle, tetrahedron, hexahedron, pentahedron +and pyramid) and with central nodes (bi-quadratic triangle and +quadrangle and tri-quadratic hexahedron).
+Quadratic mesh can be obtained in two ways: +- Using a global \ref quadratic_mesh_anchor "Quadratic Mesh" +hypothesis. (Elements with the central node are not generated in this way). +- Using \ref convert_to_from_quadratic_mesh_page operation. */