Merge rnv/win_swig_generation branch.

[modules/smesh.git] / doc / salome / gui / SMESH / input / about_meshes.doc

diff --git a/doc/salome/gui/SMESH/input/about_meshes.doc b/doc/salome/gui/SMESH/input/about_meshes.doc
index 621a47e990cd5cb5febd22133da91b94cdafbd3d..be900bc1decb309399b3aa196b3631197ef327fc 100644 (file)
--- a/doc/salome/gui/SMESH/input/about_meshes.doc
+++ b/doc/salome/gui/SMESH/input/about_meshes.doc
@@ -3,8 +3,7 @@
 \page about_meshes_page About meshes
 
 \n \b MESH represents a discrete approximation of a subset of the
 \page about_meshes_page About meshes
 
 \n \b MESH represents a discrete approximation of a subset of the

-three-dimensional space by \ref mesh_entities "elementary geometrical
-elements".
+three-dimensional space by \ref mesh_entities "elementary geometrical elements".

 
 A SALOME study can contain multiple meshes, but they do not
 implicitly compose one super-mesh, and finally each of them
 
 A SALOME study can contain multiple meshes, but they do not
 implicitly compose one super-mesh, and finally each of them


@@ -35,19 +34,19 @@ Mesh module provides several ways to create the mesh:
   </li>
   <li>Bottom-up way, using \ref modifying_meshes_page "mesh modification"
     operations, especially \ref extrusion_page "extrusion" and \ref
   </li>
   <li>Bottom-up way, using \ref modifying_meshes_page "mesh modification"
     operations, especially \ref extrusion_page "extrusion" and \ref

-    revolution_page "revolution". To create an empty mesh not based on a
+    revolution_page "revolution". To create an empty mesh not based on

     geometry, use the same dialog as to \ref constructing_meshes_page
     geometry, use the same dialog as to \ref constructing_meshes_page

-    "construct the mesh on geometry" but do not specify a geometry
-    or a meshing algorithm.
+    "construct the mesh on geometry" but specify neither the geometry
+    nor meshing algorithms.

   </li>
   <li>The mesh can be \subpage importing_exporting_meshes_page "imported" from
     (and exported to) the file in MED, UNV, STL, CGNS, DAT, GMF and
     SAUVE formats.
   </li>
   </li>
   <li>The mesh can be \subpage importing_exporting_meshes_page "imported" from
     (and exported to) the file in MED, UNV, STL, CGNS, DAT, GMF and
     SAUVE formats.
   </li>

-  <li>The 3D mesh can be generated from the 2D mesh, which was \ref
-    importing_exporting_meshes_page "imported" or manually created. To
-    setup the meshing parameters of a mesh not based on a geometry, just
-    invoke \ref editing_meshes_page "Edit mesh / sub-mesh" command on
+  <li>The 3D mesh can be generated from the 2D mesh not based on geometry,
+    which was either \ref importing_exporting_meshes_page "imported" or created in
+    other way. To setup the meshing parameters of a mesh not based on geometry,
+    just invoke \ref editing_meshes_page "Edit mesh / sub-mesh" command on

     your 2D mesh.
   </li>
   <li>Several meshes can be \subpage building_compounds_page "combined"
     your 2D mesh.
   </li>
   <li>Several meshes can be \subpage building_compounds_page "combined"


@@ -72,10 +71,9 @@ Attractive meshing capabilities include:
 
 The \b structure of a SALOME mesh is described by nodes and elements based on
 these nodes. The geometry of an element is defined by the sequence of
 
 The \b structure of a SALOME mesh is described by nodes and elements based on
 these nodes. The geometry of an element is defined by the sequence of

-nodes constituting it and
-the <a href="http://www.code-aster.org/outils/med/html/connectivites.html">
-  connectivity convention </a> (adopted from MED library). Definition of
-the element basing on the elements of a lower dimension is NOT supported.
+nodes constituting it and the \ref connectivity_page "connectivity convention"
+(adopted from MED library). Definition of the element basing on the elements
+of a lower dimension is NOT supported.

 
 \anchor mesh_entities
 The mesh can include the following entities:
 
 \anchor mesh_entities
 The mesh can include the following entities:


@@ -89,8 +87,8 @@ The mesh can include the following entities:
 <li>\b Volume &mdash; 3D mesh element representing a part of 3D
   space bound by volume facets. Nodes of a volume describing each
   facet are defined by
 <li>\b Volume &mdash; 3D mesh element representing a part of 3D
   space bound by volume facets. Nodes of a volume describing each
   facet are defined by

-  the <a href="http://www.code-aster.org/outils/med/html/connectivites.html">
-  MED connectivity convention.</a> A volume can be a tetrahedron, hexahedron,
+  the \subpage connectivity_page "connectivity convention".
+  A volume can be a tetrahedron, hexahedron,

   pentahedron, pyramid, hexagonal prism or polyhedron.</li>
 <li>\b 0D element &mdash; mesh element defined by one node.</li>
 <li>\b Ball element &mdash; discrete mesh element defined by a
   pentahedron, pyramid, hexagonal prism or polyhedron.</li>
 <li>\b 0D element &mdash; mesh element defined by one node.</li>
 <li>\b Ball element &mdash; discrete mesh element defined by a


@@ -100,7 +98,8 @@ The mesh can include the following entities:
 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
 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.
+associated geometrical entity. This attribute is set up by meshing
+algorithms generating elements and nodes.

 
 Mesh entities are identified by integer IDs starting from 1.
 Nodes and elements are counted separately, i.e. there can be a node
 
 Mesh entities are identified by integer IDs starting from 1.
 Nodes and elements are counted separately, i.e. there can be a node