Salome HOME
Documenting the nodal connectivity
authoreap <>
Wed, 22 Jun 2016 12:45:22 +0000 (15:45 +0300)
committereap <>
Wed, 22 Jun 2016 12:45:22 +0000 (15:45 +0300)
14 files changed:
doc/salome/gui/SMESH/images/connectivity_edge.png [new file with mode: 0644]
doc/salome/gui/SMESH/images/connectivity_hex_prism.png [new file with mode: 0644]
doc/salome/gui/SMESH/images/connectivity_hexa.png [new file with mode: 0644]
doc/salome/gui/SMESH/images/connectivity_penta.png [new file with mode: 0644]
doc/salome/gui/SMESH/images/connectivity_polygon.png [new file with mode: 0644]
doc/salome/gui/SMESH/images/connectivity_polyhedron.png [new file with mode: 0644]
doc/salome/gui/SMESH/images/connectivity_pyramid.png [new file with mode: 0644]
doc/salome/gui/SMESH/images/connectivity_quad.png [new file with mode: 0644]
doc/salome/gui/SMESH/images/connectivity_tetra.png [new file with mode: 0644]
doc/salome/gui/SMESH/images/connectivity_tria.png [new file with mode: 0644]
doc/salome/gui/SMESH/input/connectivity.doc [new file with mode: 0644]

diff --git a/doc/salome/gui/SMESH/images/connectivity_edge.png b/doc/salome/gui/SMESH/images/connectivity_edge.png
new file mode 100644 (file)
index 0000000..9d7af87
Binary files /dev/null and b/doc/salome/gui/SMESH/images/connectivity_edge.png differ
diff --git a/doc/salome/gui/SMESH/images/connectivity_hex_prism.png b/doc/salome/gui/SMESH/images/connectivity_hex_prism.png
new file mode 100644 (file)
index 0000000..d5cbfcd
Binary files /dev/null and b/doc/salome/gui/SMESH/images/connectivity_hex_prism.png differ
diff --git a/doc/salome/gui/SMESH/images/connectivity_hexa.png b/doc/salome/gui/SMESH/images/connectivity_hexa.png
new file mode 100644 (file)
index 0000000..326b3ef
Binary files /dev/null and b/doc/salome/gui/SMESH/images/connectivity_hexa.png differ
diff --git a/doc/salome/gui/SMESH/images/connectivity_penta.png b/doc/salome/gui/SMESH/images/connectivity_penta.png
new file mode 100644 (file)
index 0000000..1990a1d
Binary files /dev/null and b/doc/salome/gui/SMESH/images/connectivity_penta.png differ
diff --git a/doc/salome/gui/SMESH/images/connectivity_polygon.png b/doc/salome/gui/SMESH/images/connectivity_polygon.png
new file mode 100644 (file)
index 0000000..3594178
Binary files /dev/null and b/doc/salome/gui/SMESH/images/connectivity_polygon.png differ
diff --git a/doc/salome/gui/SMESH/images/connectivity_polyhedron.png b/doc/salome/gui/SMESH/images/connectivity_polyhedron.png
new file mode 100644 (file)
index 0000000..c59506f
Binary files /dev/null and b/doc/salome/gui/SMESH/images/connectivity_polyhedron.png differ
diff --git a/doc/salome/gui/SMESH/images/connectivity_pyramid.png b/doc/salome/gui/SMESH/images/connectivity_pyramid.png
new file mode 100644 (file)
index 0000000..40cc35a
Binary files /dev/null and b/doc/salome/gui/SMESH/images/connectivity_pyramid.png differ
diff --git a/doc/salome/gui/SMESH/images/connectivity_quad.png b/doc/salome/gui/SMESH/images/connectivity_quad.png
new file mode 100644 (file)
index 0000000..0b7cdd3
Binary files /dev/null and b/doc/salome/gui/SMESH/images/connectivity_quad.png differ
diff --git a/doc/salome/gui/SMESH/images/connectivity_tetra.png b/doc/salome/gui/SMESH/images/connectivity_tetra.png
new file mode 100644 (file)
index 0000000..cd86363
Binary files /dev/null and b/doc/salome/gui/SMESH/images/connectivity_tetra.png differ
diff --git a/doc/salome/gui/SMESH/images/connectivity_tria.png b/doc/salome/gui/SMESH/images/connectivity_tria.png
new file mode 100644 (file)
index 0000000..593ff05
Binary files /dev/null and b/doc/salome/gui/SMESH/images/connectivity_tria.png differ
index 2795d885ed4660de5c923c714ea42c44dd38271b..b58293d6a5291de936c80e6acb6d3cea5c344b0e 100644 (file)
@@ -72,10 +72,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
-nodes constituting it and
-the <a href="">
-  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:
@@ -89,8 +88,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
-  the <a href="">
-  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
index 855b7e5ea364c0a35c3baafc46974fd91f4bd6eb..173db3ce1e32f194696fe57a233f16327b1beb99 100644 (file)
@@ -22,8 +22,7 @@
 The convention of nodal connectivity of elements used in SALOME is
 the MED library convention. You can consult the description of
 nodal connectivity of elements in the documentation on MED library or 
-<a href="">
-  here </a>.
+\ref connectivity_page "here".
 <em>To add a node or an element to your mesh:</em>
index 2fd906bafbde6abd91d248ca97f7e08ce7be0a9f..912e59baa32ec18962187603e901be1a57a4d51c 100644 (file)
@@ -16,9 +16,8 @@ side, it is a tri-quadratic element (or HEXA27).
 The convention of nodal connectivity of elements used in SALOME is
 the MED library convention. You can consult the description of nodal
-connectivity of elements in the documentation on MED library or 
-<a href="">
-  here </a>.
+connectivity of elements in the documentation on MED library or
+\ref connectivity_page "here".
 There are several ways to create quadratic elements in your mesh:
 - manually (this way is described below);
diff --git a/doc/salome/gui/SMESH/input/connectivity.doc b/doc/salome/gui/SMESH/input/connectivity.doc
new file mode 100644 (file)
index 0000000..28c863f
--- /dev/null
@@ -0,0 +1,45 @@
+\page connectivity_page Nodal connectivity of elements
+The following images show order of nodes in correctly defined elements.
+  <tr><td> Edge (segment): linear and quadratic<br>
+      \image html connectivity_edge.png </td></tr>
+  <tr><td> Triangle: linear, quadratic and bi-quadratic <br>
+      \image html connectivity_tria.png </td></tr>
+  <tr><td> Quadrangle: linear, quadratic and bi-quadratic <br>
+      \image html connectivity_quad.png </td></tr>
+  <tr><td align="left"> Polygon: linear and quadratic <br>
+      \image html connectivity_polygon.png </td></tr>
+  <tr><td> Tetrahedron: linear and quadratic <br>
+      \image html connectivity_tetra.png </td></tr>
+  <tr><td> Hexahedron: linear, quadratic and tri-quadratic <br>
+      \image html connectivity_hexa.png </td></tr>
+  <tr><td> Pentahedron: linear and quadratic <br>
+      \image html connectivity_penta.png </td></tr>
+  <tr><td> Pyramid: linear and quadratic <br>
+      \image html connectivity_pyramid.png </td></tr>
+  <tr><td> Hexagonal prism <br>
+      \image html connectivity_hex_prism.png </td></tr>
+  <tr><td> Polyhedron is defined by <ul>
+      <li> a sequence of nodes defining all facets</li>
+      <li> a sequence of number of nodes per facet</li>
+      </ul>
+      \b Nodes: <br>
+      Node1_of_Facet1, Node2_of_Facet1, ..., NodeN_of_Facet1, <br>
+      Node1_of_Facet2, Node2_of_Facet2, ..., NodeN_of_Facet2, <br>
+      Node1_of_FacetM, Node2_of_FacetM, ..., NodeN_of_FacetM  <br>
+      \b Quantity of nodes per facet: <br>
+      NbNodes_in_Facet1, NbNodes_in_Facet2, ..., NbNodes_in_FacetM
+      For example the polyhedron shown in the image below is defined by nodes <br>
+      [ 1,2,3, 1,4,5,2, 2,5,6,3, 3,6,4,1, 4,7,9,5, 5,9,8,6, 6,8,7,4, 7,8,9 ]<br>
+      and quantities [ 3, 4, 4, 4, 4, 4, 4, 3 ]
+      \image html connectivity_polyhedron.png
+      Order of nodes of a facet must assure outward direction of its normal.
+  </td></tr>