</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
- "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>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"
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:
<li>\b Volume — 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 — mesh element defined by one node.</li>
<li>\b Ball element — discrete mesh element defined by a
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
(quadratic triangle, quadrangle, polygon, tetrahedron, hexahedron,
pentahedron and pyramid) and with central nodes (bi-quadratic triangle
and quadrangle and tri-quadratic hexahedron).<br>
-Quadratic mesh can be obtained in two ways:
+Quadratic mesh can be obtained in three 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.
-
+- Using an appropriate option of some meshing algorithms, which
+generate elements of several dimensions starting from mesh segments.
*/
